Updated by BYOND Enterprises
This is a free swimlane map plus a 10-step written SOP covering the full invoicing cycle: from the moment a job or milestone is marked complete to the moment payment is reconciled, with automated reminders that escalate to a real person at day 10. It is a field-tested map and message-cadence reference you adapt to your own tools, not an importable workflow for any one platform.
If chasing invoices only happens because you personally remember to do it, the week you are slammed on a job site is the week a payment quietly slides past 30, then 60, then 90 days. This map moves that job out of your memory and into a process with a named handoff point.
The SOP runs ten real steps: milestone complete, generate the invoice, send invoice plus a direct payment link, client review, an automated due-date check, on-time payments reconcile automatically, a neutral 3-day reminder fires if it is late, a late payment still reconciles the same as on-time, and if it is still unpaid at day 10, it becomes a personal call or message from Finance or the Owner, not another automated touch. The cycle closes with financials marked paid.
Two roles carry the whole map. Systems generates the invoice, sends the automated reminders, and reconciles payment. Finance or the Owner sends the initial invoice and makes the one personal call that matters, the day-10 follow-up, which is the exact point where the map deliberately takes automation out of the loop.
The exceptions are stated, not implied: if a client disputes an invoice, the reminder sequence pauses immediately until the dispute is resolved, no further automated contact goes out in the meantime. Repeat late payers, two or more invoices in a row past 10 days, move to prepay-only terms for future work, and that decision gets flagged to the owner rather than made unilaterally by the system.
A companion workflow file adds the build-side detail: a swimlane table by role and tool, n8n implementation notes (a schedule or webhook trigger feeding an invoicing API node, an email send, a wait step, then a status check that branches to a reminder or a Slack escalation), the same logic mapped as two Zapier zaps, and the one metric that actually matters here, days sales outstanding, with a stated target of 90 percent of invoices paid within terms.
A swimlane map (invoice-to-paid-process-map.html), a written 10-step SOP with roles and exceptions (invoice-to-paid-process-map-SOP.md), and a README.
No. The SOP works with whatever tools you already use to invoice and get paid. The n8n and Zapier notes are there as one concrete way to automate the reminder steps if you want to, not a requirement.
The reminder sequence pauses immediately. No further automated contact goes out until the dispute is resolved, per the stated exception rule in the SOP.
This map covers the full invoice-to-paid path end to end, including the happy path where nothing goes wrong, and is ready to follow as written. The Accounts Receivable Blueprint is a build spec focused specifically on the reminder and escalation branch, meant to be configured inside whatever system you use.
Your first win
Read the 10 steps once, then circle the exact step where your own last overdue invoice actually stalled. For most owners it is step 9, the personal follow-up, because nobody had a stated day to own it.
Free download. No card, no catch.