The job finished in March. The invoice went out on the first of April with net 30 printed at the bottom, and it is now the middle of May. Every week that passes makes the phone call harder, because the person who has to make it is usually the same person who wants this customer's next job.
Why the call never happens
The awkwardness is structural, not personal. In a small operation, the person who collects the money is the person who did the work or sold it, and asking about a late invoice feels like accusing a customer of something. So the call slides to next week. The aging report — the standard accounting summary that sorts unpaid invoices into 1–30, 31–60, and 61–90 day buckets — gets pulled when cash feels tight instead of every Monday morning. By the time an invoice reaches the 61–90 column, the follow-up that would have fixed it in a week has turned into a negotiation.
The other half of the problem sits on the customer's side, and it is worth saying plainly: most late invoices are not refusals. The invoice went to a project manager who left. It is waiting in an approval queue for someone to match it against a purchase order number that nobody put on it. The email address had a typo from day one. These are clerical failures, and clerical failures stall silently.
What a follow-up system actually does
The mechanism is plain. The system watches your accounting software — QuickBooks Online and Xero both expose each invoice's status, including whether it has been sent, opened, and paid — and runs a schedule keyed to the due date. A workable sequence looks like this: a short note three days before the due date, another the day the invoice goes past due, again at day seven and day fourteen, and then a flag for a human. Every message carries the invoice number, the amount, the PDF itself, and a payment link, so the recipient can settle from a phone without hunting for the original email.
Two properties matter more than the schedule. First, the tone never escalates, because software is not embarrassed and holds no grudge from the last uncomfortable conversation. Second, every touch is logged. When a person finally does pick up the phone, they are holding a dated record of five polite attempts instead of a vague sense of grievance, and that changes the character of the call entirely.
The reminder before the due date is the one that matters
Most invoices that are badly late at day forty-five were already stalled at day five. The pre-due-date note exists to find that out while it is still a clerical fix. A reply of "we never received this" on day twenty-seven costs you a re-send. The same discovery on day sixty costs you a billing cycle.
The open-tracking data earns its keep here. An invoice that has never been opened is a delivery problem — wrong address, a departed employee, a spam filter — and no amount of patient reminding will fix it. An invoice that was opened three times and not paid is a decision. Decisions are what the human call is for, and the system's job is to make sure the human only makes calls of that kind.
Watch one number
You do not need a dashboard to know whether this works. Pull the aging report today and write down the totals in the 31–60 and 61–90 buckets. Run the follow-up sequence for a full quarter. Pull the report again. If money has moved out of the old buckets toward current, the system is paying for itself, and your own books tell you by how much. That is the whole measurement. It belongs to you, not to a vendor's slide.
Texting about money has rules
A text reminder about a customer's own invoice is transactional — it concerns an existing relationship and an expected obligation — and that is the defensible end of business texting. It still has requirements. Since early 2025, US carriers block business text traffic from unregistered numbers, so the sending number must first be registered under the industry's A2P 10DLC system, and that registration takes days to weeks, not hours. STOP replies must work immediately and permanently. Messages should stay inside the 8 a.m. to 9 p.m. window in the recipient's time zone. And there is a line that must never be crossed: the moment that same list of numbers receives a promotion, the messages stop being transactional and require prior express written consent under federal telemarketing law. Week one of a project like this is paperwork. That paperwork is protection, not bureaucracy.
What no reminder sequence can collect
Automation retrieves stalled invoices. It does not create money that is not there. A customer who is short-paying because the punch list is still open has a dispute, not a memory problem, and a reminder will only irritate them. A customer who genuinely cannot pay needs a payment plan and a decision about future work, both of which are owner judgments. And if a third of your receivables cross sixty days every quarter, that is usually a pricing or client-selection problem wearing a collections costume.
For the trades there is one more hard boundary. Lien and bond-claim rights run on statutory calendars measured in months from when the work was performed, and they expire whether or not your emails were polite. The follow-up schedule should be built around those dates, and those dates come from your attorney, not from software.
Where to start
Pull the aging report before you talk to anyone about automating anything. If the 31–60 column holds four invoices, you need an afternoon and a phone, not a system. If it runs a page long every month, count the invoices and the hours you spend chasing them. That number is the entire business case, and you will have built it yourself.