It is nine o'clock on Sunday night and you are rewriting the same email you sent three weeks ago: "Just circling back on invoice 2214." You will soften it twice before sending, because the man who owes you the money is someone you'll see at the supply house on Thursday.
Why collections drift to Sunday night
Chasing money is the one job in the building nobody wants, including the owner. It isn't hard; it's awkward. Asking to be paid feels adjacent to accusing someone, especially in a trade where the customer is also a referral source or a neighbor. So the chasing gets deferred to hours when nobody is watching, which is how it becomes a Sunday-night job — done sporadically, and always in an apologetic voice.
The deferral is not neutral. An invoice ages badly. Every week that passes, the memory of the work fades: the roof no longer leaks, the machine runs fine. The urgency that once belonged to the customer has quietly transferred to you.
The aging report is the honest scoreboard
Your ledger already keeps score. The report is called accounts receivable aging, and it sorts every open invoice into buckets: current, 1–30 days past due, 31–60, 61–90, and 90-plus. The buckets mean different things. 1–30 is the ordinary friction of somebody's accounts-payable routine. 31–60 is where invoices go when nobody is watching them. By 61–90 your invoice has lost its place in line to louder creditors. Past 90, invoices collect partially, slowly, or not at all. Most owners run this report quarterly and wince at it. The first job of any collection system is smaller than it sounds: put the buckets in front of you every week — totals per bucket, and which direction each one moved — so drift gets caught at 35 days instead of discovered at 95.
The asymmetry worth naming
Here is the mechanism this whole page turns on. A person who knows the customer cannot comfortably send the third reminder. The relationship gets in the way, every time, and it is not a character flaw. A system sends the third reminder in exactly the tone of the first. The part that is easy to miss: the customer can tell the difference too, and it helps. A message that plainly comes from the billing process reads as the shop's routine, not the owner's grievance. Nobody's pride is involved on either end. "Our system sends those automatically" is a sentence that lets both sides off the hook — and it only works if it is true.
What the sequence actually looks like
A few days before the due date: a short note with the invoice attached and a payment link — due Friday, here it is again. On the due date: one line. A week past: a reminder with a current statement attached. Around three weeks past: the third reminder — the one that never gets sent by hand — still polite, stating the balance and the original date, and offering a phone call if anything about the work is in question. Around five weeks, the messages stop and a human calls, because past a certain age an invoice is a conversation, not a notification. Every message names the business, states the amount and the invoice number, and carries the same payment link.
The pay link, and stopping the moment money moves
Friction keeps invoices unpaid longer than malice does. An invoice that requires finding a checkbook competes badly with everything else on someone's desk; a reminder carrying a link that takes card or bank payment in ninety seconds removes the last excuse. Card processing costs a few percent and bank transfer costs less — on a five-figure invoice that difference is real money, and who absorbs it is a decision to make once, up front.
The other half matters just as much: stop-on-payment. The instant a payment posts — through the link, or a check keyed into the ledger on Tuesday — the sequence for that invoice halts. Nobody should ever be reminded about an invoice they have already paid; one such message costs more goodwill than ten reminders recover. This is why the reminder system has to read from the ledger itself, not run alongside it on a spreadsheet that somebody updates when they remember.
What this won't collect
A disputed invoice gets angrier with every automated touch, not closer to paid — a dispute needs a human within one message of surfacing. An insolvent customer pays nothing regardless of cadence; the aging report just tells you sooner, which has its own value. Contract terms outrank reminders: retainage in construction is withheld on purpose, and dunning it makes you look like you haven't read your own contract, while a pay-when-paid general contractor pays on their trigger, not yours. And past a certain age, collection becomes a legal question with deadlines of its own — lien rights in Texas run on a statutory calendar that does not care about your email cadence, and that timeline belongs in a conversation with your attorney.
What you'd watch
Two numbers, monthly, from your own ledger: the total sitting in the 31-plus buckets, and the average days from invoice to payment. If the sequence is working, both fall. The third number is harder to graph — it is how you spend Sunday nights.
Where to start
Run the aging report today — it is one click in QuickBooks or whatever you keep the books in — and total everything past 30 days. That figure is what the current collection process, meaning you at 9pm, is producing. Then decide whether the third reminder should keep being your job.