The automation map
Go through every task in your receivables process and ask two questions: does it happen the same way every time, and what does a mistake cost? Repetitive and cheap-to-fix goes to software. Variable or costly-to-fix stays with a person, at least for now.
| Task | Automate? | Why |
|---|---|---|
| Importing open invoices from your books | Yes | Pure copying. Doing it by hand is how invoices get missed. |
| Sending reminders on a schedule | Yes | The schedule is a rule, and an invoice nobody asks about is easy for a customer to leave for later. |
| Writing the reminder | Yes, with review at first | Good writing depends on context (history, last reply), which software can read. Review until you trust it. |
| Sorting replies | Yes, with a fallback | Most replies are one of a few types. Anything unclear should come to a person. |
| Pausing on a promise to pay | Yes | A rule: stop until the date, resume if it passes. |
| Taking payment | Yes | A pay link per invoice removes a step for the customer. |
| Recording payments in the books | Yes | Manual entry is slow and error-prone, and errors cause wrong reminders. |
| Resolving disputes | No | Needs someone who knows the work and can decide. |
| Calling a silent customer | No | A person on the phone gets answers email can’t. |
| Deciding to pause work or require prepayment | No | A business decision with a relationship attached. |
Start with the books
It’s tempting to start with reminders, because that’s the visible part. Start one step earlier. If payments aren’t recorded promptly and against the right invoice, automated reminders will chase customers who have already paid, and they’ll do it on schedule, every time.
So the first automation to get right is the loop back into your accounting system. When a customer pays through a link, the payment should land in QuickBooks or Xero against that invoice. When you record a payment yourself, the reminders should notice and stop. Get that loop working and everything downstream is accurate.
Earning trust: approval first
Handing your customer emails to software is a leap. The safe way to make it is in stages:
- Approval mode. Software drafts every reminder; nothing goes out until you approve it. You see exactly what your customers would see.
- Edit and watch. Note what you change. If you’re rewriting most drafts, the tool isn’t right yet, or your settings aren’t.
- Batch approval. Once drafts are mostly right, approve the day’s batch in one go, reading the unusual ones.
- Automatic sending. Switch approval off. Keep reading the log for a while, and keep the queue of replies that need you.
There’s no fixed timetable. Some businesses get there in a week; some keep approval on for their largest customers forever. A good tool lets you do either.
What to keep human
Three areas are worth protecting from automation, at least at small and mid-sized scale.
Disputes. When a customer says the work wasn’t done or the bill is wrong, they need a person who can check and decide. Automation should stop chasing that invoice, park it in a queue with the customer’s words, and keep chasing their other invoices normally.
The relationship call. Whether to keep working with someone who pays at day 75 depends on margin, history and what else they bring. No rule captures that well.
The phone. After weeks of silence, a call from a person, ideally someone the customer knows, often gets an answer that another email won’t.
How AR automation goes wrong
Most failures are predictable, which means they’re preventable:
- Chasing paid invoices, because payments weren’t recorded or synced. Fix the books loop first.
- Reminding people who already replied. A reminder the day after “paying Friday” makes the whole system look careless. Replies must stop the cadence.
- Writing to the wrong person. Old contacts, departed staff. Clean contacts before you automate.
- Treating every customer the same. A single schedule for a 10-year client and a brand-new one. Use different cadences where your tool allows it.
- No off switch. You should be able to stop everything in one click. Check before you need it.
The stakes are real: in Intuit’s Small Business Late Payments Report 2026, 39% of owners with unpaid invoices said a single late payment had strained their ability to cover payroll or bills. Automation that chases the wrong invoice doesn’t help with that; automation that chases the right one on time does.
What OnDue automates today
Measured against the map above, honestly. OnDue is in early access on QuickBooks Online and Xero.
| Task | OnDue today |
|---|---|
| Importing open invoices | Yes, synced every 15 minutes. |
| Sending reminders on a schedule | Drafted on the standard cadence (days 1, 7, 14, 30 after due); each one waits for your approval. Custom cadences and an automatic mode are Coming soon |
| Writing the reminder | Yes, AI-drafted; you approve or skip. Editing drafts is coming soon. |
| Sorting replies and pausing on a promise | Yes, with anything unclear sent to you. |
| Taking payment | Not yet. A Stripe pay page is Coming soon |
| Recording payments in the books | Not yet. OnDue reads payments you record and stops the reminders; writing pay-page payments back is coming soon. |