Invoice chase finance will actually leave on
Most chase automations get muted in a month. This one stayed on — because disputes exit the drip, escalations land with history, and status replaces the overdue spreadsheet.
- Strategy
- AR chaseExceptions firstn8n
- Design
- Status modelHuman escalation
- Client
- Finance / ARShipped in weeks
Outcomes
What changed after handoff
The chase spreadsheet got shut off
Finance had run a parallel overdue tracker for months because they didn't trust the previous automation's status. Within the first month of this one, that spreadsheet stopped getting updated — system status was accurate enough to be the only source of truth, not a second copy someone kept just in case.
Disputes stop the drip
The old system sent the same reminder on the same schedule no matter what — a disputed invoice could rack up a third or fourth automated nudge before a person ever saw it. Now a dispute exits the sequence the moment it's flagged and lands with a person, full chase history attached, same day.
What shipped
The system in plain terms
- Statuses: sent, reminder-due, disputed, escalated, paid
- Reminders only for invoices in a chaseable state
- First reminder after due date — automatic
- Human escalation with invoice history attached
- Audit log of every state change
The build
How we got there
Background
Invoice chase is one of the most commonly automated finance jobs — and one of the most commonly abandoned. A timer that emails every overdue invoice the same way can’t tell “forgot to pay” from “disputing the line items.” Finance mutes it and goes back to the sheet.
The brief wasn’t “send more reminders.” It was “build something we’ll leave on.” That meant status first, timing second.
Challenges
The previous automation treated every unpaid invoice the same. Disputes kept getting chased. Finance ran a spreadsheet in parallel because they didn’t trust the system.
A rebuild only worked if exception paths were first-class — not an afterthought bolted onto a schedule.
Finance adoption required:
- Disputes exit automation the moment they’re flagged
- Escalations include the full chase history
- No reminder fires without a clear current status
Solution
Every invoice carries a status, not just a due date. Cadence applies only to chaseable states. Escalation is a person with context — not another email template.
Built with an n8n workflow on the tools finance already used. Fixed scope, weeks not quarters. The manual backup process actually got archived.
Next
Got a workflow that hurts this much?
Bring us the one costing your team the most time. We’ll tell you straight whether it needs a build — or a smaller fix.