Writing
There is a moment in every services business where someone finally pulls the receivables report, sorts it by age, and goes quiet. The work was done. The invoices were sent. And a startling amount of the money is just... out there. Thirty days. Sixty days. A few at ninety-plus that everyone has silently agreed not to talk about.
Here is the uncomfortable truth underneath that report: an invoice is not money. An invoice is a request. The distance between request and cash is covered by a discipline most businesses never deliberately built, because collections feels awkward, nobody owns it, and everyone is busy doing the actual work. Which is exactly why receivables discipline is the most boring competitive advantage available to a services business. Your competitors find it awkward too. Most of them will not build it.
Start by dropping the assumption that late payment means a bad client. Most late payment is structural, not moral.
Your invoice arrived at the wrong desk. The person who loves your work is not the person who pays invoices. If your invoice does not reach accounts payable with the right PO number, format, or approval trail, it sits in a queue nobody is watching.
Your terms were never really agreed. "Net 30" written at the bottom of an invoice is not an agreement; it is a suggestion. Payment terms negotiated at contract signing, out loud, are a different thing entirely.
You trained them. Every time an invoice went unchased for weeks without consequence, you taught the client your due dates are soft. Clients pay their strictest suppliers first. That is not cynicism; it is how any finite pile of cash gets allocated.
Month-end batching. "We'll invoice at month-end" feels tidy and costs you real time. Work finished on the 3rd and invoiced on the 30th starts its net-30 clock a month late. Across a year, that habit alone can hold weeks of your cash hostage.
The fix is not aggression. It is a calm, predictable sequence that starts before the invoice is even late:
On sending: confirm receipt. One line to the right person: "Invoice attached, due on the 14th, let me know if anything is needed for processing." This surfaces missing POs and wrong contacts on day one instead of day forty.
A few days before due: a friendly nudge. "Just flagging this comes due Friday." Nothing to apologize for; large companies run entirely on reminders.
Day after due: a direct, warm note. Not "sorry to bother you." Something like: "This came due yesterday, could you let me know when it's scheduled?" You are asking a normal business question about a normal business obligation.
A week late: a phone call. Email is easy to ignore; a pleasant human voice is not. Most "difficult" receivables die here, because it turns out the invoice was simply stuck.
Beyond that: escalation you decided in advance. Pausing new work, involving the relationship owner, payment plans for genuinely struggling clients. The point is that the steps exist before you are angry, so the process stays professional when you need it most.
Two design rules hold the whole thing up. First, one person owns the cadence, with a standing weekly look at the aging report; collections that belong to everyone belong to no one. Second, the tone is consistent and unembarrassed from the first email to the last call. You did the work. Asking to be paid on the agreed date is not a confrontation. It is the agreement.
Invoice the day the work ships. Confirm it landed. Chase on a schedule, warmly and without apology. None of it is clever, and that is precisely why it works: it is a system, running while your competitors are still hoping the money shows up.
I'm Arslan. I run SaaS Ledger Co, where receivables discipline is part of what we build for SaaS, ecommerce, and services businesses. If your aging report has a column nobody talks about, start there.