How to automate invoice chasing (without sounding like a robot)

Chasing overdue invoices is the work everyone agrees is important and nobody wants to do. So it slips — and the cash you're owed sits in someone else's account for another month. The good news: it's one of the easiest things to automate well, if you automate the right parts.

What to automate, and what to keep human

The instinct is to automate everything. Don't. The reliable split is:

• Automate the routine. Reading which invoices are overdue, drafting the first and second reminders, sending them on schedule, and logging the result. This is repetitive, rules-based work — perfect for a workflow.
• Keep the judgement human. A disputed amount, a client who's gone quiet, a relationship you don't want to risk with an automated nudge. These should be flagged to a person, not sent on autopilot.

Get that line right and you remove 90% of the effort while keeping the 10% that actually needs a human.

Make the reminders sound like you

The fastest way to make automation backfire is a reminder that reads like a system wrote it. Three things matter:

1. Send from your own inbox, so replies come back to you like any other email.
2. Match your tone — learned from how you actually write, not a generic template.
3. Escalate politely. The third reminder should read differently from the first.

A simple, reliable flow

A dependable invoice-chasing workflow looks like this:

• Read overdue invoices from your accounting tool (e.g. Xero).
• For each, decide: routine chase, or flag to a human?
• Draft a chaser in your tone and send it (or hold it for one-tap approval).
• Log who was chased, when, and what they said.

That's exactly the automated invoice chasing workflow we build for clients — done for you, monitored, and adjusted as your process changes.

The honest catch: it has to keep working

An invoice-chasing workflow only helps while it keeps working, and the things it depends on change:

• Your accounting tool updates, and a field the workflow reads gets renamed.
• Your email connection expires after a password change, and reminders silently stop going out.
• A client pays part of an invoice, and a rule written for "paid" or "unpaid" chases them for the full amount.

The first two are loud: something stops. The third is quiet: the workflow keeps running and sends the wrong message. That's the one that costs you a client relationship. (Why automations break, and who fixes them.)

If you build it yourself, watching for all three is your job. With Scribe.sg, it's ours. We watch every run, fix the workflow when something changes, test the fix on real invoices before it goes live, and tell you what happened. Because this workflow touches money, a person checks the result before any fix goes live. If you'd rather build it once and have it keep working, book a call.