Why the first version of most chase automations gets abandoned
Invoice chase is one of the most commonly automated finance workflows, and one of the most commonly abandoned. The pattern we see: someone builds a scheduled reminder that emails every overdue invoice on the same cadence, finance turns it on, and within a month it’s muted — because it can’t tell the difference between a client who forgot and a client who’s disputing the invoice, and it keeps chasing both the same way.
The lesson from that failure mode shaped how we approached this build: the automation had to run on status and exceptions, not just a timer.
Status first, timing second
Every invoice in the workflow carries a status, not just a due date: sent, reminder-due, disputed, escalated, paid. The chase cadence only applies to invoices actually in a chaseable state — a disputed invoice gets pulled out of the automated sequence immediately and routed to a person, instead of getting a fourth automated nudge that makes the client more frustrated, not less.
That one change — treating disputes as an exception path instead of letting the timer keep running — was what got finance to trust the system enough to stop double-checking it manually.
What the workflow actually does
On the sent date, the workflow starts tracking the invoice. If it’s not marked paid by the due date, it sends the first reminder automatically. If it’s still unpaid after a second interval, it escalates — not with another automated email, but with a flag to a person on the finance team, with the invoice history attached so they’re not starting from zero.
Every state change is logged, so finance can see exactly where an invoice is in the sequence without asking anyone, and exactly why it stopped being automated if it did.
The result
Within the first month, the finance team stopped manually tracking overdue invoices in a separate spreadsheet — the one they’d kept running in parallel with the previous, less trusted automation. That’s usually the real signal a build has worked: not that it runs, but that the manual backup process it was supposed to replace actually gets shut off.