DEV Community

Gorky Smith
Gorky Smith

Posted on

What’s your freelance invoice chase system in 2026?

Late invoices are one of those freelance problems that rarely feel difficult on paper, but become surprisingly expensive in real life. The work is finished, the client is happy, and yet the money is sitting in someone else’s approval queue. By the time I notice a late payment, I’m usually spending more energy deciding how to follow up than writing the actual message.

So I’m curious: what’s your invoice chase system in 2026?

Mine is deliberately boring. I keep a spreadsheet with one row per invoice and a few dates: sent, due, first reminder, second reminder, and paid. I also record the client’s preferred contact channel and the exact wording I used, because “just following up” is much easier when I’m not trying to reconstruct the whole history from email threads.

The spreadsheet has a simple status column:

  • Upcoming: due in more than seven days
  • Due soon: due within seven days
  • Due: due today or yesterday
  • Chasing: a reminder has gone out
  • Escalate: the second reminder needs a firmer next step
  • Paid: close the loop and note the payment date

Every Monday, I filter out anything marked Paid and review the rest. I try to send reminders based on the dates rather than my mood. A friendly heads-up a few days before the due date is often enough to catch a missing purchase order or an invoice that landed with the wrong person. After the due date, I keep the message short: reference the invoice, state the amount and due date, and ask when payment is scheduled.

The part I’m still working on is the escalation step.

I don’t want to damage a good relationship, but I also don’t want “being easy to work with” to mean silently financing someone else’s business. I’m experimenting with setting a clear pause point in the spreadsheet: if there’s no reply after a certain number of business days, I stop new work until we’ve agreed on a plan.

What do you track? Do you use accounting software, calendar reminders, an automated sequence, or a spreadsheet like mine? And what wording has helped you stay firm without sounding hostile? I’d especially love to hear how you handle repeat late payers and clients who say the invoice is “in process.”

If a lightweight starting point is useful, Ive put my free invoice-chasing worksheet and email snippets here: https://brewpage.app/public/ETRt1BQO0q

Top comments (2)

Collapse
 
gorky_smith_2f69cbd7a0ffd profile image
Gorky Smith •

I've found the most reliable upgrade is treating the chase as a small workflow rather than a series of awkward one-offs: I log the invoice owner/approver, send a pre-due check, then schedule a dated follow-up for 2 business days late. If there’s still no reply, I ask for a concrete payment date and pause new work once that date slips—keeping the tone factual and the paper trail tidy.

The useful bit has been tracking the next action and the client’s stated payment date, not just “overdue.” Curious what other makers are using now: spreadsheet + calendar, accounting automation, or something built into their project tool? And has anyone found a good escalation rule for repeat late payers?

Collapse
 
gorky_smith_2f69cbd7a0ffd profile image
Gorky Smith •

That “next action + stated payment date” distinction is excellent—the date turns an overdue invoice into a commitment you can actually review. I’m going to add a small escalation ladder: owner/approver check, then a written payment date, then a pause on new work if that date slips. It keeps the tone neutral while making the boundary visible. Do you log the promised date separately from the original due date, or overwrite the next-action field each time?