From Overdue Invoice to Escalation: A Demand-Letter Scenario With Decision Points

Imagine a small engineering supplier, Meridian Components, that completes a £28,000 custom order for a long-standing business customer. The customer has paid twelve previous invoices on time. Invoice 913 is due on June 30 and remains unpaid.

This is an illustrative scenario, not a real case. Its purpose is to show how a routine receivable can change into a legal recovery file—and why the creditor should change strategy as the facts change.

Day 5 overdue: treat it as an accounts problem first

Meridian’s accounts team sends a polite reminder with the invoice and purchase-order number.

The customer replies the same day: “Approved; next payment run is Friday.”

At this point, a formal demand would probably add little value. The debtor has acknowledged the invoice and given a near-term payment explanation.

Meridian records the acknowledgment and schedules a follow-up for the promised date.

Day 12: the promised payment does not arrive

The customer says the payment run was delayed and asks for another week.

Meridian now changes one thing: it stops relying on verbal timing. It requests a written payment date and asks whether any part of the invoice is disputed.

The customer confirms that the full £28,000 is approved and promises payment on July 18.

That confirmation becomes an important part of the file.

Day 20: a new dispute appears

On July 18 there is still no payment. A different employee at the customer writes that the goods may have been delivered late and says the invoice is “under review.”

Meridian does not respond, “You already admitted the debt, pay immediately.” Instead it asks for the factual basis of the new issue:

Which contractual delivery date is relied on?
What delivery date does the customer say occurred?
Was any rejection or reservation made?
What loss or contractual deduction is claimed?
Who has authority to resolve the account?

The collection team also pulls the signed purchase order, delivery record, acceptance email, invoice and earlier acknowledgment into one indexed folder.

The matter is no longer just an accounts reminder.

Day 27: the entities do not line up

While reviewing the file, Meridian notices that the purchase order was issued by “Harbor Retail Ltd,” but the invoice was addressed to “Harbor Retail Operations Ltd.” Previous payments came from the parent company.

This could be administrative noise, or it could be central to liability.

Meridian pauses escalation long enough to identify the actual contracting party and obtain advice on whether the invoice or demand should be corrected. It does not simply name all group companies as debtors.

That pause saves a potentially serious pleading problem later.

Day 35: the creditor calculates the claim properly

The principal amount is reconciled. Meridian confirms there are no unposted credits or partial payments.

It then reviews whether contractual or statutory interest may be available. GOV.UK explains that qualifying late commercial payments can attract statutory interest and recovery costs, but Meridian does not assume eligibility from the headline rule alone.

It records separately:

principal;
any contractual interest;
any statutory interest claimed in the alternative;
recoverable fixed sums or costs, if applicable;
the calculation date.

This makes the eventual demand auditable.

Day 42: a formal letter of claim becomes proportionate

The debtor has now missed multiple promises and has not substantiated the delivery complaint.

Meridian prepares a formal pre-action letter with local legal input.

Because the matter is in England and Wales, the team checks the current Civil Procedure Rules and whether the Debt Claims Pre-Action Protocol applies to this debtor and claim. It does not assume that a protocol called “Debt Claims” governs every B2B invoice.

The team also notes the October 1, 2026 protocol update concerning email delivery of Letters of Claim where appropriate. The broader lesson is simple: a demand template should have a version date.

Day 55: the debtor offers 60% immediately

The customer offers £16,800 within 48 hours in full and final settlement, saying liquidity is deteriorating.

Meridian does not reject the offer out of anger. It asks a commercial question: what is the expected net value of holding out?

The team considers the evidence strength, likely court fee, professional fees, management time, delay, solvency indicators and enforcement prospects. It also checks whether other creditors appear to be taking action.

A settlement discount is not automatically weakness. It is a pricing decision under uncertainty.

Day 58: no settlement is agreed

Meridian counters at a higher figure with a short acceptance period. The debtor does not accept.

Now the file reaches a real fork.

Option A: continue negotiation if new money or new evidence appears.
Option B: use mediation if the delivery issue is genuine and both sides want a commercial compromise.
Option C: issue a money claim if the claim is supportable, costs are proportionate and collectability is reasonable.

GOV.UK provides an online/paper route for money claims in England and Wales, subject to eligibility and fees.

Before issuing: the enforcement question

Meridian’s lawyer asks a question the sales team had not asked: “If you win, where does the money come from?”

The company checks lawful public information about the debtor’s corporate status and trading activity. It considers whether a judgment would likely be enforceable.

This matters because a court judgment is a legal asset, not guaranteed cash.

If payment still does not follow judgment, enforcement options in England and Wales can include warrants of control, third-party debt orders and charging orders depending on circumstances.

The decision table Meridian keeps

Date	New fact	What changed	Next action
Day 5	invoice acknowledged	low dispute risk	wait to promised date
Day 12	payment missed	reliability risk	obtain written schedule
Day 20	delivery complaint	dispute risk	request particulars and preserve evidence
Day 27	entity mismatch	liability risk	verify contracting party
Day 35	claim reconciled	amount becomes auditable	calculate lawful additions
Day 42	repeated non-payment	informal route weakening	formal pre-action review
Day 55	discounted offer	solvency signal	compare settlement vs expected recovery
Day 58	no deal	escalation point	mediate or issue if proportionate

What this scenario teaches

The most important action is not sending a stronger letter. It is recognizing when the type of problem changes.

Accounts reminder → evidence dispute → entity question → formal claim → settlement economics → enforcement.

At each stage, the creditor should preserve what it knows, identify what it does not know, and choose the next route based on recoverability rather than emotion.

This is a fictional scenario for general education, not legal advice. Real debts may involve different contracts, protocols, limitation periods, consumer protections, insolvency rules and cross-border enforcement issues. Obtain qualified local advice before formal proceedings or insolvency action.

Scenario variation: the customer pays part and disputes the rest

Suppose the buyer pays 70 percent after the letter and says the remaining 30 percent reflects defective work. The recovery file should split immediately. Record the undisputed payment, identify exactly which deliverables are challenged, preserve acceptance and quality records, and stop describing the whole original invoice as simply “unpaid.”

A sensible next step may be a technical review, commercial compromise or focused claim for the remaining balance. The partial payment can be relevant evidence, but its legal meaning depends on the contract and jurisdiction. Do not turn it into an unsupported admission theory.

Scenario variation: the debtor offers installments

An installment proposal can be commercially useful, especially when cash-flow trouble is temporary. But “we’ll pay something each month” is not a plan. Put the amount, dates, payment method, treatment of interest or costs, consequences of missed installments, and any reservation of rights into writing.

Also ask whether accepting the arrangement changes existing security, guarantees, limitation issues or enforcement options. Those questions are jurisdiction- and contract-specific. The operational lesson is simpler: a negotiated pause should create more certainty than the uncertainty it replaces.

At each branch in the scenario, update the chronology rather than replacing it. Keep the original invoice, every revised position, each payment, each promised date and the response to each disputed item. A clean chronology lets a new decision-maker understand the file without reconstructing months of email. It also exposes whether the dispute is narrowing toward resolution or simply rotating through new reasons for delay. Before any formal step, recheck the contract, applicable procedure, service requirements, limitation position and the identity of the legal debtor. That final identity check is especially important where a trading name, affiliate, guarantor or group company appears in the correspondence. Confirm it before filing anything.