Collection Letters That Work: What to Write at Each Stage

Collection Letters That Work: What to Write at Each Stage | HL Hunt
Payments & AI

Collection Letters That Work: What to Write at Each Stage

Most collection messages fail for the same reason: they communicate displeasure when they should communicate information. A recipient who has to look up which invoice you mean, calculate what's outstanding, and figure out how to pay is a recipient who defers — not because they refuse, but because you've handed them a task instead of a transaction. The messages that get paid are specific, short, and end at a payment link. This guide covers the structure, what to write at each stage from pre-due through final demand, the language that creates legal exposure, and templates you can adapt directly.

By the HL Hunt Research Desk · 15 min read · Updated August 2026

Specificity beats pressure

The segmentation in our collections framework identifies four reasons accounts go unpaid, and the largest is administrative — a lost invoice, a wrong contact, a stuck approval, a missing purchase order number. Given that, the first job of a collection message is not persuasion. It's giving the recipient everything they need to resolve it without doing any work.

Concretely, that means the message contains the invoice number, the amount, the date issued, the due date, what it was for, and a link that takes payment. A recipient with all six can pay in under a minute. A recipient missing any of them has to investigate, and investigation is where invoices go to age.

The corollary is that pressure applied early is both ineffective and expensive. A firmly worded message to someone whose accounts payable department simply never received the invoice damages a relationship over a problem a reminder would have solved — and given that around 92% of businesses are paid after their due date, per our trade credit analysis, treating lateness as adversarial means treating most of your customer base as adversaries.

The structure that works

Every collection message, at every stage, has the same four parts. What changes across stages is the framing around them, not the components.

  1. The specifics. Invoice number, amount, issue date, due date, description. Front-loaded, not buried in a paragraph.
  2. The ask. One clear request with an amount and a date. "Please pay $4,320 by March 14" beats "please bring your account current."
  3. The path. A payment link that works on a phone, plus alternative methods. The message should end at payment.
  4. The exit. A way to respond if something is wrong or if they need a plan — because a dispute routed to resolution and a cash-constrained customer routed to installments are both better outcomes than silence.

Three formatting rules that matter more than they should:

  • Short. Under 150 words for early stages. Long messages get skimmed and the amount gets missed.
  • Scannable. The invoice details as a small block or list, not embedded in prose.
  • One call to action. A message offering to pay, to call, to reply, and to visit a portal offers four decisions, and four decisions produce none.
Six facts and a link
Invoice number, amount, issue date, due date, description, and a payment link that works on a phone. A recipient with all six can resolve it in under a minute; missing any one, they have to investigate — and investigation is where invoices age.

What to write at each stage

Before due — the reminder

The highest-return message in the entire sequence and the one most businesses never send. It costs nothing, carries no relationship risk, and moves your invoice into the current payment run rather than the next one.

Subject: Invoice 4471 due Friday — $4,320

Hi [name], a quick reminder that invoice 4471 for $4,320 is due this Friday, March 14. It covers the February site work.

You can pay here: [link]

If anything looks wrong or you need a different arrangement, just reply and I'll sort it out.

Days 1–7 past due — assume oversight

Assume the invoice was missed. It usually was. Tone: helpful, brief, no reference to lateness as a problem.

Subject: Invoice 4471 — $4,320 outstanding

Hi [name], invoice 4471 for $4,320 was due March 14 and I don't have it recorded as paid yet. It's likely just crossed in the post.

Details: Invoice 4471 · $4,320 · issued Feb 12 · February site work · PO 88104

Pay here: [link] — or reply if you need it resent or there's a query on it.

Days 15–30 — direct and specific

Escalate the directness, not the temperature. Name a date. Introduce the plan option here, because this is the stage where cash-constrained customers first become identifiable.

Subject: Invoice 4471 — 21 days past due

Hi [name], invoice 4471 for $4,320 is now 21 days past due. Could you let me know a date I can expect payment?

Details: Invoice 4471 · $4,320 · due March 14 · February site work · PO 88104

Pay in full: [link] · Or spread it across three payments: [link]

If there's a problem with the invoice, tell me and I'll put this on hold while we resolve it.

Days 45–60 — formal, with accurate consequences

Now the message becomes a business communication rather than a note. State terms accurately, and reference only consequences you will actually apply.

Subject: Overdue account — Invoice 4471 — action required

[Name], invoice 4471 for $4,320, due March 14, remains unpaid at 52 days past due.

Under our agreed terms, accounts more than 60 days past due are placed on credit hold, and no further orders will be released until the balance is cleared.

Please pay in full by April 20: [link]. If you're unable to clear it in one payment, reply today and we'll agree a schedule.

If you believe this invoice is incorrect, tell me now and we'll resolve it before that date.

Final demand — precise, not theatrical

The final demand should be the most restrained message in the sequence. Its force comes from accuracy and finality, not from adjectives. Send it in writing with proof of delivery.

Subject: Final notice — Invoice 4471 — $4,320

[Name], invoice 4471 in the amount of $4,320, issued February 12 and due March 14, remains unpaid.

This is a final request for payment. Please remit $4,320 by May 5.

If payment is not received by that date, we will place this account with a collection agency in accordance with our terms of sale.

Payment: [link]. To discuss a payment arrangement instead, contact me at [details] before May 5.

Note what the final demand does not say: no threat of litigation unless you will litigate, no reference to credit reporting unless you furnish data, and no characterization of the customer. The clause about agency placement is stated because it is true and because your terms provide for it — which is why the credit application language in our terms guide matters at this exact moment.

Subject lines and channel

Subject lines should contain the invoice number and the amount. Not "Following up," not "Quick question," not "Overdue account." A subject line carrying the specifics gets opened by the right person and forwarded correctly by the wrong one.

Effective patterns: Invoice 4471 due Friday — $4,320 · Invoice 4471 — 21 days past due · Final notice — Invoice 4471 — $4,320. Avoid anything that could read as marketing, anything vague, and anything in all capitals.

Channel choice by stage:

ChannelStrengthsBest used
EmailRecord, reaches AP directly, carries a link, forwardableThe default for most B2B stages
TextVery high open rates, immediateConsumer and small business, with consent and opt-out handling
PhoneResolves complexity, gets commitmentsLarger balances, and once to establish what's actually happening
Physical letterWeight, proof of deliveryFormal demand and final notice
Portal notificationIn-context, no deliverability riskWhere an ongoing account relationship exists

Two operational points. Send to the accounts payable contact, not the person who signed the order — this single routing fix resolves a meaningful share of "we never got it" delays. And watch deliverability: collection emails land in spam more than ordinary correspondence, so plain formatting, no heavy imagery, and a monitored sending domain matter.

Language that creates exposure

Collection messages are governed by unfair and deceptive practices standards even when you're collecting your own debts — the perimeter our first-party compliance guide maps. The governing rule is accuracy, and most violations are carelessness in a template rather than intent.

Do not write:

  • "We will take legal action" unless you will and can. Threatening litigation you don't intend to pursue is a classic deceptive practice.
  • "This will be reported to credit bureaus" unless you furnish data — and if you do, the accuracy and dispute obligations that come with furnishing apply.
  • "Your wages will be garnished" as though automatic. Garnishment requires a judgment first, per our garnishment analysis, and describing it as imminent misrepresents the process.
  • Anything implying criminality. Unpaid commercial or consumer debt is civil, and suggesting otherwise is among the most serious allegations a regulator pursues.
  • Fees or interest your contract doesn't authorize, or amounts you can't substantiate.
  • False urgency — a settlement deadline that isn't real, or a "final notice" followed by three more.
  • Anything about the customer personally. Describe the invoice, not the person.

The control that catches nearly all of this: review every template as though a regulator were reading it. Templates scale, which means one careless sentence reaches every customer rather than one — making template review higher-leverage than any amount of individual training.

Tone across the sequence

The tone arc that works is warm to formal, never polite to hostile.

Early: friendly, assumes oversight, apologetic if anything ("this may have crossed with your payment"). Middle: neutral, direct, asks for a specific commitment. Late: formal, factual, states accurate consequences. Final: precise and restrained.

Three things that consistently improve response regardless of stage:

  • Write as a person. A named sender with a real signature outperforms "Accounts Department," because a human is harder to ignore and easier to reply to.
  • Ask a question. "Can you let me know a date?" invites a reply; a statement invites nothing. A reply — even one saying "not until the 30th" — converts silence into information you can act on.
  • Keep the door open. Every message should contain a way to raise a dispute or request a plan. A customer who can't pay in full and sees no alternative disengages, which is how recoverable accounts become the write-offs our decision guide analyzes.

And the discipline underneath the whole sequence: escalate on schedule, not on frustration. Consistent timing recovers more than sporadic intensity, and it means the tone at each stage is a policy decision made in advance rather than a reflection of how the last conversation went.

What to test

Collection messaging is measurable, and small changes produce meaningful differences at volume.

  • Payment link versus payment instructions. Usually the largest single effect available, and worth confirming on your own data.
  • Subject line specificity — invoice number and amount versus generic.
  • Send timing. Aligning to accounts payable run days rather than to your own convenience.
  • Plan offer placement — introducing installments at day 15 versus day 45 changes who takes it.
  • Sender identity — named individual versus department.
  • Message length, where shorter usually wins early and longer is tolerable at formal stages.

Measure the right outcome: payment rate within a defined window, not open rate or reply rate. A message with a high open rate and no payments is a message people read and set aside.

The sequence, running by itself

HL Hunt AI Debt Collection runs the full stage sequence automatically under your own brand — specifics pulled into every message, payment links and installment options included throughout, channel and timing matched to each customer, and contact limits enforced by the system.

Explore HL Hunt AI Debt Collection

Frequently asked questions

What should a collection email say?

The specifics of what's owed, one clear ask with an amount and date, a way to pay immediately, and a way to respond if something's wrong. Everything else is optional.

How aggressive should collection letters be?

Less than most assume — the largest segment of unpaid invoices is administrative. Assume good faith early, increase formality with age, and use consequence language only where it's accurate.

What phrases create legal exposure in a collection letter?

Threatened legal action you won't take, credit reporting you won't do, garnishment described as automatic, any implication of criminality, and unauthorized fees. Intent to mislead isn't required for exposure.

Should collection messages be email, letter, or phone?

Email for most early B2B stages, text for high open rates with consent, physical letters for formal demand and proof of delivery, and phone for larger balances where a conversation resolves something.

Key takeaways

  • Communicate information, not displeasure — most unpaid invoices are administrative, and specificity resolves them.
  • Every message needs six facts and a working payment link, front-loaded and scannable, with one call to action.
  • The pre-due reminder is the highest-return message in the sequence and the one most businesses skip.
  • Escalate formality, not hostility, and introduce the payment plan option by the middle stages.
  • Say only what is accurate — threatened litigation, credit reporting, and garnishment language create exposure when they aren't true.
  • Review templates as though a regulator were reading them, and measure payment rate rather than open rate.

Every account, every stage, on schedule

Consistency recovers more than intensity. HL Hunt AI Debt Collection works every invoice on a defined cadence with compliance enforced automatically and a complete audit trail — so the pre-due reminder actually gets sent, and the final demand only goes to accounts that earned it.

Get Started with HL Hunt AI Debt Collection


This guide is educational and does not constitute legal advice. Templates are illustrative and must be adapted to your contract terms and to applicable state and federal rules, which differ for consumer and commercial debts. Have collection templates reviewed by counsel.