I think most overdue invoices fall into 4 buckets
The more I work on Billzy, the less I believe in treating every overdue invoice the same way.
I think most of them fall into 4 buckets:
1. Setup gap
Wrong contact, missing PO, unclear terms, no payment path.
2. Ownership gap
Nobody clearly owns approval or the next action.
3. Priority gap
The client probably intends to pay, but nothing in the workflow makes it urgent.
4. Real problem
Cash issue, dispute, missing deliverable, or something genuinely blocking payment.
The reason I keep coming back to this is simple:
each bucket needs a different next step.
Better reminder copy will not fix a missing PO.
More follow-up will not fix missing ownership.
A polite nudge will not fix a priority problem if nothing else changes.
And no amount of perfect wording will solve a real dispute by itself.
That is why I think one of the biggest mistakes in overdue recovery is using the same playbook for completely different problems.
The invoice is late.
But why is it late?
That question matters more than most people think.
Because once you know the bucket, the next move gets clearer:
- setup gap -> fix the missing information
- ownership gap -> surface the responsible person
- priority gap -> change the workflow
- real problem -> resolve the dispute or blockage
That has become a useful lens for me while building Billzy.
I do not just want it to say "this invoice is overdue."
I want it to help answer "what kind of overdue problem is this?"
That feels like a much better foundation for recovery than generic reminders on a timer.
This idea applies outside invoicing too.
A lot of messy operations improve the moment you stop treating every delay like the same problem.
Curious how other founders and freelancers see it:
Which of these 4 buckets causes the most trouble in your business?
I ran into the ownership gap and promised-date bucket the most, those were the invoices that looked like late payment when the real issue was nobody owned the next click. I tried a spreadsheet first, then Stripe reminders, and now I'm building ChaseFlow around that triage layer, ngl the bucket framing is way more useful than a single aging number.
Priority gap, easily. Most of my late payments were from clients who genuinely intended to pay, but my invoice just got buried. Two things that made a real difference: sending the invoice the same day work is completed (not end of week) and switching from 30-day to 14-day terms. The shorter window created urgency without upsetting anyone.
The ownership gap is sneaky too. Once I started asking "who actually clicks approve?" at the start of a project and adding that person to the invoice email, chasing dropped a lot.
For UK freelancers, there's also a legal angle worth knowing - you can charge statutory interest on late payments under the Late Payment of Commercial Debts Act. Most clients do not know this. I built a free calculator for it at landolio.com/tools/late-payment-interest-calculator if anyone wants to see what they might be owed.
This is a really good breakdown.
I think priority gap is probably the most common one too, because intent and urgency are not the same thing. A client can fully intend to pay and still let the invoice slide if nothing in the workflow keeps it visible.
Sending the invoice the same day and shortening terms to 14 days both make a lot of sense to me, because they reduce drift before the recovery process even starts.
And I agree on the ownership point too. "Who actually clicks approve?" is such a better question than discovering halfway through chasing that the real approver was never in the loop.
Also useful callout on the UK late-payment angle. Even if someone never uses it, just knowing that statutory interest exists probably changes how they think about delay.
Curious: which change had the biggest impact for you in practice, same-day invoicing, 14-day terms, or adding the approver early?