Skip to content
DueHello
All resources
Playbook Reading time 6 minutes

A cadence that works for relationship-led billing

Most collections advice is written for lenders. When you will see the client again next Thursday, the timing rules change.

The default advice on receivables comes from consumer lending: contact early, contact often, escalate on a fixed ladder. It works when the relationship ends at the invoice. It works badly when the person you are chasing is also the person approving next quarter's scope.

A cadence for relationship-led billing has a different goal. You are not applying pressure until payment arrives; you are removing every excuse for the invoice to sit unread, while keeping the conversation one a colleague could have in person.

Start before the due date

The most valuable message in the whole sequence is the one nobody sends: a short note a few days before payment falls due, confirming the invoice arrived, reached the right person, and carries the right purchase-order reference.

It is not a reminder, so it costs nothing socially. And it catches the single most common failure mode, which is not unwillingness to pay but an invoice that never entered the payer's approval queue.

An invoice that was never approved is not a late payment. It is a filing problem, and it is cheapest to fix before the due date.

Day 3 to day 10: assume administration

The first genuine reminder should read as administrative, because at this stage it almost always is. State the invoice number, the amount, the original due date, and offer to re-send the document. Ask one direct question: is anything holding it up on your side?

Two things matter more than the wording. Send it from a real person at your company, so a reply lands in a monitored inbox. And send it to the accounts-payable contact rather than the person who commissioned the work, unless the relationship tier says otherwise.

Day 18: the tone shifts, the sender does not

By the second cycle, silence has become information. Something is wrong: the invoice is disputed, the approver has changed, the payment run was missed, or the payer has a cash problem. Each requires a different response, and none of them is served by a third copy of the same template.

This is the point where a human should read the account. Not to write the message from scratch, but to decide which of those four situations is most likely, and to name it in the message. "I know the team was mid-handover in July" does more work than any escalation in tone.

Day 30 and beyond: milestones, not moods

After a month, escalation should follow documented steps rather than frustration. Most large payers publish what a supplier should do at 30, 45 and 60 days, and following those steps precisely is what makes a later collection route straightforward.

  • Confirm the invoice was received, matched and approved — three separate states, not one.
  • Contact the payer's creditor administration directly, with the reference and proof of delivery.
  • Inform the relationship owner before the tone hardens, always.
  • Record every step, because at day 60 the previous 30 days become your evidence.

What to cap

Set a maximum number of touches per invoice and hold to it. A sequence with no ceiling eventually sends a fourth reminder to a client who has already paid a different invoice, and that single message costs more goodwill than the cadence saved.

Cap the frequency too. Every 10 days is enough. Weekly reads as pressure, monthly reads as indifference.

Apply this to your own ledger.

A Receivables Leak Audit shows where your follow-up breaks down today.

Book a demo