Customer Not Paying Invoice? A Cash-Protection Playbook
An overdue invoice needs more than another reminder. Build an escalation process that connects payment commitments, collection evidence, and supplier payment decisions.

If a customer is not paying an invoice, verify the outstanding balance and contractual due date, contact the person responsible for payment, and request either a specific payment commitment or a documented dispute. If the customer remains unresponsive or breaks that commitment, escalate through your credit policy and consider a formal demand or professional recovery advice. Meanwhile, do not treat promised payment as available cash.
For controllers and CFOs, there are two connected jobs: recover the receivable and prevent the shortfall from disrupting supplier payments. This guide focuses on that connection—not simply sending more reminders, but deciding what evidence justifies escalation, revised forecasts, and changes to payment plans.
Establish what is owed before escalating
A collection demand should start with a defensible balance. Reconcile the invoice against receipts, unapplied cash, credit notes, deductions, and any agreed adjustments. Check the governing contract, customer entity, delivery or acceptance evidence, and invoice submission requirements.
Ask the customer to distinguish between an invoice they cannot process, an amount they dispute, and an obligation they accept but cannot currently pay. Those situations need different decisions.
- Processing issue: Obtain the missing requirement, responsible contact, and expected resolution date.
- Commercial dispute: Record the disputed amount and reason. Ask whether the undisputed portion can be paid separately.
- Cash constraint: Request a realistic proposal and route any extended terms through credit approval.
- Payment reportedly sent: Request a payment reference and investigate receipt before demanding payment again.
Keep the original due date visible. Recording a new payment promise should not silently replace contractual terms or make an overdue balance appear current.
Turn a vague promise into an accountable commitment
“It is with finance” is a status update, not a payment commitment. “It will be in the next run” is incomplete unless the customer identifies the amount and release date.
Create a promise-to-pay record containing the invoice reference, amount, currency, named customer contact, promised release date, expected receipt date, and supporting correspondence. Record who on your team owns the next action.
Separate payment release from receipt. A customer may authorize a transfer before funds reach your account. A remittance notice can support an investigation, but it does not prove that money is available for your supplier payments.
A practical follow-up message
Subject: Payment confirmation required for invoice [reference]
Our records show an outstanding balance of [amount and currency] on invoice [reference], due [date]. Please confirm the amount you will pay and the payment release date by [response deadline]. If any portion is disputed, identify that amount and the reason so we can route it for resolution. If payment has already been sent, please share the payment reference and remittance details through our agreed channel.
Use a response deadline appropriate to the account and contract. Keep communications factual, avoid unsupported threats, and verify changes to banking instructions through an independently established channel.
Escalate on events, not just invoice age
Ageing reports identify exposure, but age alone does not explain the next action. An older invoice under an active, documented dispute is different from an accepted invoice with repeated broken promises.
The following is a suggested operating policy, not a legal timetable. Adapt it to contractual notice requirements, customer risk, and local law.
| Trigger | Collection action | Cash-planning response | Decision owner |
|---|---|---|---|
| Due date missed | Confirm balance and request commitment | Flag receipt timing as uncertain | AR owner |
| Specific dispute raised | Assign resolution; separate undisputed amount | Reassess disputed cash separately | Commercial owner and controller |
| Payment commitment missed | Escalate to customer finance leadership | Revise collection assumptions | Credit lead or controller |
| Customer requests instalments | Obtain written, approved terms | Forecast agreed instalments individually | Authorized credit approver |
| Silence or repeated default | Review demand and recovery options | Plan without the uncertain receipt | CFO and legal adviser |
Make every escalation end with an owner, an action, and a review date. Otherwise, a more strongly worded email simply creates another untracked task.
Choose a recovery route without overstating your rights
Payment plans and commercial concessions
A payment plan can be appropriate when the customer acknowledges the debt and has a credible route to payment. Document instalment amounts, dates, treatment of the remaining balance, and what happens if a commitment is missed. Have an authorized person approve any waiver, discount, or change to credit terms.
Evaluate new work separately. Continuing delivery can increase exposure even while the customer makes small payments against old debt. A customer relationship may warrant flexibility, but that flexibility should have an explicit limit.
Late fees, service suspension, and formal recovery
Do not add an arbitrary late fee to create leverage. FreshBooks’ guidance on overdue-invoice interest emphasizes communicating payment terms and considering applicable restrictions. In the United States, enforceability can depend on the agreement, state law, and transaction type. Other jurisdictions have different statutory frameworks.
Before suspending service, check contractual rights, notice requirements, and the consequences of stopping performance. Before sending a formal demand, assemble the contract, invoice, delivery evidence, balance reconciliation, and correspondence.
A collection agency, lawyer, or court claim may be appropriate depending on the debt, jurisdiction, available evidence, and expected recovery costs. Small-claims eligibility and limits vary. Warning signs of insolvency warrant prompt professional advice rather than an ordinary reminder sequence. This is an operational framework, not legal advice.
Protect AP commitments without passing the problem downstream
An unpaid customer invoice does not automatically change what you owe suppliers. AR should own collection activity; treasury should own liquidity assumptions; AP should execute approved supplier payment decisions.
Maintain two distinct views:
- Collection outlook: Expected receipts, supporting evidence, customer commitments, and uncertainty.
- Payment funding: Available funds and approved funding sources against scheduled obligations.
Use a downside scenario that excludes uncertain customer receipts. Identify which supplier commitments would become unfunded and escalate before payment release—not after a transfer fails. Do not automatically cancel a supplier payment because a related customer invoice is late.
If a shortfall requires rescheduling, seek agreement with the supplier rather than quietly editing the due date. Record the original obligation, approved revised schedule, and commercial consequences. The distinction between forecast liquidity and usable balances is also central to real-time treasury management.
Hypothetical example: a broken promise before a payment run
A services business expects a customer receipt before its contractor payment run. The customer promises to release funds but later reports an internal delay. AR records the missed commitment and escalates. Treasury removes the receipt from the immediate funding assumption. AP checks the approved payment schedule against available funds and escalates any gap for a funding decision or negotiated rescheduling.
The control is not a faster reminder. It is preventing an unverified promise from authorizing commitments the business cannot fund.
Automate the handoffs, not the legal judgment
OneAdvanced’s overview of AP and AR automation describes efficiency opportunities across both workflows. For an overdue-invoice process, the useful connection is shared status and reliable handoffs—not an assumption that automation can make an unwilling or insolvent customer pay.
When assessing accounts receivable automation, ask a vendor to demonstrate how a customer reply changes the workflow. A dispute should route to an accountable owner, while a matched receipt should stop inappropriate reminders. A missed commitment should trigger review rather than another identical email.
On the payable side, test whether AP automation keeps invoice capture, approval, and payment status distinct. An approved invoice still needs an authorized, funded payment decision. Require evidence that revised schedules, exceptions, and user actions remain auditable.
Track commitment fulfilment, unresolved dispute age, recovery effort, and receipt forecast accuracy alongside overdue balances. Measure automation against resolved exceptions and reliable decisions—not messages sent.
A checklist for the next overdue account review
- Reconcile the balance and preserve the contractual due date.
- Document the customer's explanation and supporting evidence.
- Obtain a specific payment commitment or route the dispute.
- Assign the next escalation owner and review date.
- Approve concessions and recovery actions through the correct authority.
- Update the receipt forecast without treating a promise as cash.
- Check supplier payment funding before release.
Start with your most material overdue accounts and their associated cash assumptions. A stronger process should answer three questions clearly: what can be collected, what evidence supports the expected timing, and which supplier commitments remain funded if the customer does not pay.
Created with AI assistance. Sources are linked in the article; this content is general information, not legal, tax, or financial advice.
Run your entire money cycle on one ledger
Global payouts, AP/AR automation, and AI agents with their own wallets and spend limits.
Get started


Discussion
0 commentsBe the first to join the discussion.