Workflow
Invoice chase sequence
Overdue invoices chase themselves and stop the moment the money lands.
- By
- Caleb and Ryan, the founders
- Updated
- August 28, 2026
- Version
- 1.0, in the library
- n8n
- Make
Recipe card three: a workflow that watches your accounting for invoices past due, sends the reminders you would have sent at the intervals you choose, escalates in your voice, and stops the moment payment lands. Built for n8n and Make, with the reminder ladder as editable templates.
Built, documented, running.
Part of the working library we deploy from on every engagement.
Bring this into a project- Complete and documented: the same files we run ourselves.
- Deployed and tuned to your stack as part of an engagement.
The file
Draft excerptSubject: Invoice {{invoice_number}}, a week past due Hi {{contact_first_name}}, Invoice {{invoice_number}} for {{amount}} was due on {{due_date}}. If it isalready on its way, thank you and please ignore this. If something isholding it up, reply here and we will sort it out. {{payment_link}} {{owner_name}}{{company}} ---stop_when: payment recorded in the ledgerescalate_to: day-14.md
What is inside
6 items. Includes video guide, deployment guide, sample data.
n8n/invoice-chase.jsonThe n8n workflow: daily check, the ladder, the stop.make/invoice-chase.blueprint.jsonThe same as a Make scenario.reminders/Day 1, day 7, day 14, day 30: four messages in a firm, polite voice, with the variables named.sample-invoices.csvA fictional ledger for a dry run.GUIDE.mdConnecting the ledger, choosing the intervals, and the stop rule that matters most.walkthrough.mp4Sixty seconds of a reminder going out and stopping on payment.
Who it is for
- Someone spends Friday afternoon chasing money.
- You use QuickBooks, Xero or Stripe invoicing and reminders are manual.
- You want the tone to escalate the way you would, not the way a debt collector would.
Requirements
- n8n or Make
- QuickBooks, Xero or Stripe
- Gmail or Outlook for the reminders
- Twilio for texts (optional)
Install
- 01
Import the workflow or blueprint.
- 02
Connect the ledger and the mailbox.
- 03
Run it against sample-invoices.csv with sending off, and read what it would have sent.
The recipe this ships
Tools in the chain: QuickBooks, then Reminder, then Text, then Stripe.
Get paid faster
Watches your accounting for invoices past due, sends the reminders you would have sent, escalates in your voice, and stops the moment the money lands.
Days sales outstanding cut by 15 to 33 daysSource: Chaser and Billtrust customer data
Finance
Where this sits
This system
Invoice chase sequence
In the library, running.
Pairs with
We connect the ledger with you and run the first live reminder together.
In your stack
The audit finds which system earns its place first; we install and tune it around how you work.
Questions
- Will it chase a client who already paid?
- No. The stop rule checks the ledger before every send, and the guide's first test is exactly that case.
- Can I change the tone?
- The four reminders are plain markdown. Edit them; the variables stay.
- Does it work with Stripe invoicing?
- Yes. QuickBooks, Xero and Stripe are covered; others with a node or API work with one swap.
- What if it does not fit our stack?
- Then we say so, and the guide names the swap. Every pack documents exactly what it needs to run.
Changelog
- August 28, 2026In the library. Version 1.0 runs in our own operation.
Related
Agent pack
Document intake and extraction
Paperwork reads itself and files its own fields
Works with n8n, Anthropic API.
Built and runningWorkflow
Meeting actions router
Every commitment made in a meeting lands where work happens, owned and dated
Works with n8n, Anthropic API.
Built and runningWorkflow
Approvals chaser
Nothing waits three days for a yes that takes thirty seconds
Works with n8n, Zapier.
Built and running