Start from the right assumption: most late payment is an invoice sitting unapproved, sent to the wrong person, or missing a reference the customer's system requires. That is friction, and it responds to a different approach than refusal does. Run a fixed ladder — a short note three days before the due date, a neutral reminder in the first fortnight, a phone call between 16 and 30 days asking one specific question, a written escalation between 31 and 60, and a decision at 60. Clean the aging before every round so you never chase someone who has already paid. Consistency does more work than wording ever will.
What this actually feels like
You did the work, you sent the invoice, and it is now 40 days. You do not want to be the business that chases, and you also cannot fund a customer indefinitely, so the email sits in drafts getting rewritten.
Meanwhile nobody at their end is refusing to pay. It is genuinely sitting in someone's approval queue, and it will keep sitting there until somebody asks.
What it costs to do by hand
An hour a week, properly done — segmenting the aging, checking for payments already applied, drafting the right message at the right tone for each stage.
It is also the hour most likely to be skipped, because chasing money is unpleasant and there is always something more urgent. That is the actual failure mode: not doing it badly, but doing it unpredictably, which teaches customers your terms are advisory.
The accounts receivable follow-up process
The full ladder with what to say at each stage, the friction fixes that prevent the problem, and the two numbers worth tracking.
Read the guide →Input, skill, output
- QuickBooks — AR aging plus 12 months of payment history.
- PayPal — Recent settlements — anyone who just paid is skipped.
- Stripe — Optional — folds Stripe overdue invoices into the sweep.
- Score each customer — Ranks them good, occasional, or repeat-late.
- Match the tone — Gentle, neutral or firm copy to fit the score.
- Hold for approval — Drafts everything — sends nothing until you say go.
- Tone-matched reminders — One consolidated email per customer.
- Approval summary — Customer, amount, days late and channel.
- Sent or queued — Nothing leaves without your sign-off.
Who this is for
- You invoice on terms and at least some customers exceed them routinely.
- You have avoided chasing someone because the relationship matters more than the invoice.
- Nobody currently owns collections as a weekly job.
If none of those describe you, this is probably not your first priority — and the rest of the library may point somewhere more useful.
Common questions
When should I start chasing?
Before it is overdue. A short note three days before the due date resolves a surprising share of late payments, because it catches the invoice while it is still moving through approval.
Will chasing damage the relationship?
Chasing badly will. Assuming bad faith in the first message damages it; a calm factual reminder does not. Firmness later lands much better for having been calm early.
Should I charge late fees?
Only if the term is in your contract and you will actually enforce it. A late fee threatened and then waived teaches the customer your terms are negotiable.
What gets invoices paid fastest?
Removing friction. Invoice the day work completes, send it to the approver rather than a generic inbox, include their PO reference, and make it payable by card or ACH.
When should I stop and write it off?
When expected recovery is below the cost of pursuit, including your attention. Carrying uncollectable balances also corrupts the cash forecast built on them.
See it on your own books, once
The First Close is one real month of your books, closed properly and configured to your chart of accounts, delivered inside two weeks. Full reconciliation against every processor, every exception flagged with the transaction behind it, and the narrative written. $497, refundable if the packet is not delivered, and it credits in full toward the first month if you continue.
Get Your First Close — $497 See a sample packet