Updated by BYOND Enterprises
This is a free build spec for status-aware invoice reminders and escalation. It covers six checkpoints from invoice issued to payment reconciled, and it names stop conditions up front, so a disputed invoice or a payment-plan client never gets the same automated nudge as someone who simply forgot.
The job is done, the invoice is out, and now it just sits there while you hope. Chasing money you already earned is the most awkward kind of follow-up, so most owners either over-chase clients who were always going to pay or under-chase the ones who need a real escalation. This blueprint separates the two before you send a single reminder.
The six checkpoints run invoice issued, receipt confirmed, due date watched, reminder sent, exception handled, payment reconciled, in that order. Like the estimate-side blueprint, each checkpoint carries an owner, evidence, a pass condition, and an exception route, so "reminder sent" is not just a task that happened, it is a task with proof it happened and a stated next step if it does not land.
The two checkpoints that matter most are the last two before reconciliation: stop rules and exception paths. Those are the fields most homegrown collections processes skip, which is exactly why a good client who is one day late gets the same cold, automated tone as someone who has ghosted three invoices in a row.
This is a build specification for your own accounts receivable process, not an importable file for any accounting or CRM platform. It is the map for what to configure and in what order, verified against four specific contact states before it is called done: paid, overdue, disputed, and payment-plan.
Each checkpoint carries an owner, evidence, a pass condition, and an exception route in the full spec.
The download ships with a completed run for the same fictional business used across this build spec family, where days-outstanding moves from a 31-day baseline to a 14-day target once every checkpoint has a named owner and a stated exception route. That number belongs to the sample file, not to a real customer result, your own baseline is whatever your open invoices actually show right now.
Five files: blueprint.html is an interactive version of the spec, source.md is the full written spec, completed-example.json is the fictional worked example, plus sell-sheet.md and README.md.
No. This is a build specification, not an importable snapshot or workflow export for any accounting or CRM platform.
No. It opens as a document or a browser file. A few Launch20 assets plug in faster if you already run a CRM like GoHighLevel, but none of them require one.
This blueprint is a build spec focused specifically on the reminder and escalation branch, meant to be configured inside your own system. The Invoice-to-Paid Process Map is a ready-to-follow swimlane and SOP covering the full billing cycle end to end, including the happy path where nothing goes wrong.
Your first win
Open blueprint.html and fill in your own owner for "invoice issued" and "reminder sent," the two checkpoints most businesses already have some version of. The rest of the spec builds outward from those two.
Free download. No card, no catch.