How to Build a Collection Routine

Before You Start

The current position needs measuring before the routine gets built.

Calculate your average collection period

How many days pass between invoice date and payment date? That single figure shows both the size of the problem and the effect of any correction you make.

Classify the delays

Separate receivables into not yet due, overdue within a month, and outstanding longer. Three groups require three approaches.

Distinguish the cause

Forgetting, cash pressure and refusal to pay are different things. The implementation data indicates the large group comes from forgetting. Treating everyone with the same firmness pushes the majority unfairly.

Name who does it

If it is not written down who sends reminders, the task belongs to nobody. Whether accounting or sales handles it should be settled at the outset.

Step 1 · Build the Calendar

Collection is entirely a matter of timing.

Work backwards from the due date

Place the first contact not on the due date but a few days earlier. At that point the customer is not yet the late party, so the message reads as convenience rather than warning — and response rates rise from there.

A second notice on the day

A short note on the due date itself largely eliminates forgetting, and because nothing is late yet the relationship stays intact.

Escalate in stages once overdue

Reminder in week one, a call in week two, written notice in week three. Having the stages written in advance ends the need to decide afresh at every delay.

Leave gaps

Messages sent back to back lose effect and become irritation. A few working days should separate each step.

Step 2 · Write the Message

Content matters more than frequency.

Everything needed in one place

The sum owed, the date, where to send it and — if you have one — a link that opens the payment screen. A message that requires the recipient to go and find something else has already lost a day.

Keep it short

Long explanatory texts go unread. Two sentences and a link is the format producing the highest response in most cases.

Write it as help, not as a demand

The programme’s own framing was assistance ahead of sanction, and the numbers backed it. Firmer wording buys nothing on the payment side while costing something on the relationship side.

Turn the text into templates

A message rewritten each time costs time and loses the tone. Three templates for three stages is enough.

Step 3 · Make Paying Easy

What happens after the reminder determines the response.

Count the steps

How many actions does completing payment take for someone who received your message? Past three, response falls noticeably; the same reminder performs very differently on a short path.

Offer more than one method

Transfer, card and link-based payment offered together remove the obstacle of preference.

Do not make them search

A customer who has to dig through months-old correspondence postpones payment to the next day, and that day usually does not arrive. Keeping the information at a fixed address closes that loss.

Define the confirmation process

Where it is unclear how payment should be notified, reconciliation slows and unnecessary correspondence follows.

Step 4 · Measure and Sustain

Whether the routine works shows only through measurement.

Prove it on your own numbers

Send reminders for one billing cycle and skip the next, then set the two collection periods against each other. Whatever the sector average says, this is the figure that will convince your own finance team.

Track overdue receivables

The share of overdue amounts within total receivables is the single indicator of the routine’s health. Monthly review suffices.

Record the exceptions

Where it is not written why a particular customer received extended terms, that exception becomes permanent.

Review annually

Terms policy should update as the customer base changes. A static policy eventually becomes either too tight or too loose.

A Solid Digital Foundation

Most businesses that build a customer portal never consider how that area should be managed.

Login-protected areas need separate handling

Invoice viewing and payment sit behind a login. Those sections should stay out of the index while the login page itself remains findable; how login-protected content should be handled is described in the Google Search Central documentation. Building the portal is not enough; the customer has to find the way in.

Password reset must work

A customer logging in a few times a year does not remember their password. When the reset step fails, payment fails with it — and it is the flow most businesses never test.

A portal is not always necessary

At small scale, putting the invoice and payment details directly into the message does the same job. Portals become worthwhile once transaction volume rises.

Setup happens once

A reminder calendar, templates and a payment route, defined once, run every period. We connect that to our guide to the period and handle the setup within process and e-commerce consulting.

Frequently Asked Questions

I worry my customers will dislike this

Reactions in practice tend to run the other way: a customer relieved of tracking their own calendar treats it as convenience. Complaints start when frequency is overdone and the message turns into a demand.