Accounts receivable automation
Automate invoice follow-up: cadence, variation, and what not to automate
Updated 28 April 2026 · 14 min read
How to automate invoice follow-up so it stays human: different messages by age of debt, a steady cadence, and a clear handoff when the message must be a judgment call, not a template.
To automate invoice follow-up well, separate two ideas. Cadence is the clock: when a touch is allowed. Message variation is the content: what is different about day 2 after due versus day 20. The worst implementations automate cadence and ignore variation, so the customer gets the same “please remit” paragraph six times. The good ones use automation to do what a disciplined person would have done, every time, without the cognitive load. That is the bar.
A sane default cadence for commercial B2B (adapt to your policy)
- 3–5 business days before the due date: one factual pre-due nudge with amount, due date, and pay route.
- Day 1 after due: a status check, not a demand, unless the contract says otherwise for that segment.
- 7–10 days after due: restate age of debt, ask for a pay date, offer to fix a billing line item.
- Beyond that, escalate in step with a written policy (pause work, require prepay on new work, or a named call)—not a surprise invented in a bad mood.
Stack options: spreadsheet, email sequences, and AR tools
A shared spreadsheet and calendar reminders is automation at 10%: enough for some freelancers. A mail-merge sequence in a generic email tool is automation at 40%: good cadence, weak thread memory. A dedicated layer that is email-native, keeps replies with the right thread, and lets you pause for disputes is closer to what lean teams need when they outgrow memory. The honest point is: pick the smallest layer that does not make you a human cron job. For trade-offs, read manual vs. automated and invoice reminder tools comparison.
What should still be a human in the loop
When the customer is clearly in distress, or when the dispute is about deliverables, an automated dunning blitz does damage. Your policy should say when automation pauses: keyword flags, a manual override, or a “disputed” state. If your tool cannot do that, you will eventually train customers that your emails are not serious. Then nothing is automated, because nobody reads them.
Frequently asked questions
Why not send the same email every three days until they pay?
Because it signals either a broken process or a bot with no state. A human receivable is supposed to add information as time passes: a new pay date, a new PO, or an escalation you already said could happen. Identical nudges train customers to filter you as noise, which is the opposite of automation’s goal—consistency without stupidity.
Back to all resources or the Arkvela home page.