By the Onsites AI team · Last updated · 5-minute read
An overdue invoice is one of the strangest conversations in business: you did the work, the money is owed, and the email still has to be written as if you were apologizing for mentioning it. Most chasers go wrong by skipping that etiquette — too soft (paid when convenient) or too sharp (paid, then never again). The four-touch ladder below earns payment on the honest cases in two touches and draws the line cleanly on the rest, and the desk makes the whole operation mechanical: invoice statuses (sent, seen, overdue) turn "who owes us what" into a list, the shared inbox carries the thread history, and the account record shows whether a slow payer is a first-timer or a pattern. Here is the escalation, with scripts, from day 3 to the day you change the relationship's terms.
The first touch assumes innocence, because most late invoices are: "Hi Ana — a small nudge that invoice #1041 (€12,400, due last Tuesday) hasn't hit our account yet. If it's already in motion, all good; if something's stuck on your side in approvals, tell me where and I'll help unblock. Thanks!" Why this works: it names the exact document and amount (the money sentence does the precision), offers the face-saving exit ("in motion"), and frames follow-up as help — which in most cases it genuinely is: stuck approvals and forgotten renewals are the modal overdue cause, not malice. One nudge, one week's grace, no cc yet, no mention of terms. Track it on the invoice's own trail: the status flip and the thread carry the fact of the nudge, so nobody politely nudges twice.
No response? Sharpen the tone without touching the respect: "Invoice #1041 is now 10 days past its due date (€12,400, due June 30). Our terms are payment within 14 days — I want to flag it plainly rather than let it drift. If there's a dispute with the invoice itself, tell me and we'll sort that today; otherwise, when can we expect payment?" The structural changes: the words "past due," a direct question with a timeframe, and the dispute door opened deliberately — a payer with a genuine grievance usually takes this exit and turns a chase into a fix. CC the person who signed the quote now (the PO's owner, not "leadership"), and keep the channel the deal lived on: the same shared thread where the quote-to-invoice lineage is visible is exactly where accountability reads best.
Twenty-eight days past due moves the conversation from chase to consequence, and the sentence should be as boring as the fact: "Invoice #1041 is now a month past due. As per our payment terms, we pause open work and hold new shipments on accounts past 30 days. Your open order (#1042) is on hold from Monday — it releases the moment the payment posts. I can keep the production slot until Friday to give the approval cycle room to close." Three things make the hold survivable: it follows stated terms (a term nobody quoted becomes pressure, and you become the villain); it names the concrete date and the release condition; and it offers the slot-holding gesture, which signals the relationship matters more than the stand. This is also the touch where payment plans get offered — half now, half on delivery — because the art of saying no includes saying yes-shaped things that are real on your side.
Whatever the touch, four rules protect tomorrow's relationship while today's payment is earned. Facts over adjectives: "invoice #1041, €12,400, 30 days past due" carries more force than any "unfortunately" — precision is the tone on money. Assume systems, assume intention, in writing both: approvals stalled and renewals lapsed by themselves; write as if you believe it, even when your account record suggests otherwise — the payer who is dodging reads the benefit of the doubt too, which is exactly the pressure the record creates. Escalate consequences, never persons: the hold moves from the order to the account's terms, not from your inbox to their character. And leave the door visibly open: every touch ends with a working condition ("releases the moment payment posts"), because the goal of chasing is a paid invoice and a next order — an account paid off and kept is the whole point of the ladder.
The best chase is the one a business never needs to write, and two habits prevent most overdue invoices at the source. Terms stated before the work, in every quote: payment window in days, method, the hold condition at 30 days — quoted on the document the buyer signs, so the ladder later cites the buyer's own agreement rather than an ambush. The quote anatomy carries exactly this clause, which is also why teams with disciplined quotes chase less: the due date was never negotiable because it was never invisible. The renewal and checkpoint system: recurring invoices get status-tracked reminders before expiry — the same statuses that drive the overdue ladder drive the "your annual plan renews in two weeks" note, which converts most accidental late payments into timely renewals before they ever become chased accounts. And when a customer does go late anyway, the account record's pattern view (nudge, reminder, hold, demand) sets the honest terms: prepayment for proven repeat offenders, standard terms for everyone else, and the desk-side memory to keep it that way.
Past sixty days the register changes from customer service to recovery, and the honest move is to make the change visible: the final demand comes from the business owner or finance lead, in formal formality, stating the full account status, the accumulated amount if your terms carry late fees say them precisely (never invent a percentage on the spot — the guardrail rules apply doubly in demands), the exact remedy, and the next step if silence continues (collections, or per your jurisdiction, legal process). What it must never do is threaten anything you won't execute or insult the person you hope to bill again. And the desk-side discipline: the account record now shows the full history — nudge, reminder, hold, demand — so whoever eventually takes the call reads the whole arc in two minutes, and new terms ("prepayment going forward") are recorded on the account so the next quote inherits reality, not optimism.
How soon should we chase an unpaid invoice?
A gentle nudge at day 3-7 after the due date — assume a system hiccup rather than bad faith. Most late invoices are stuck approvals; the first touch earns payment on the honest cases without any relationship cost.
What do we say when the first nudge gets no answer?
A firm reminder at day 14: name the invoice and the days past due, state the payment terms, ask directly when to expect payment, and offer the dispute door — a payer with a real complaint takes it, and the chase becomes a fix.
When is it legitimate to pause work or shipments?
Once your stated terms allow it and the account is ~30 days past due: a written hold notice naming the specific order, the hold date, and the exact release condition. The gesture worth adding is holding a production slot briefly — firmness on the account, room for the process.
What belongs in the final demand?
The full account status and amount, precise late-fee terms only if your terms actually carry them, the exact remedy and next step, sent by the owner or finance lead rather than support. No threats you won't execute, no insults — and the payment history recorded on the account so future quotes inherit reality.
How does a help desk make invoice chasing easier?
Invoice statuses make it mechanical: overdue flips on the trail, the shared inbox carries each chase thread, and the account record shows the payment pattern — so the next quote, credit line and even AI-drafted replies inherit the truth instead of re-learning it.