The short answer: a collection process is a written procedure that names who owns each overdue account, when reminders are sent, what events trigger escalation, where disputes go, and what gets documented at every step. If those five decisions are written down, follow-up happens consistently — even when the usual person is away.
Most small businesses do not have a collection problem so much as a consistency problem. Follow-up happens when someone has a spare hour, the loudest account gets attention, and the same three customers keep appearing on the aging report because nobody formally decided what to do about them. A written process removes the guesswork and the memory dependency.
What the process has to define
Five things, in this order: an owner, a schedule, escalation rules, dispute routing, and documentation standards. Everything else — letter wording, call scripts, channels — is detail you can refine later. If the five above are clear, the process works even with imperfect wording.
1. Name an owner (and a backup)
Every account needs one person accountable for the next action, even when the work is shared. "The finance team" is not an owner; a named person is. Assign a named backup for absences, and decide who approves escalation decisions, since handing an account to a third party or accepting a reduced settlement are business decisions, not administrative ones.
| Role | Responsibility | Who it suits |
|---|---|---|
| Account owner | Sends scheduled reminders, logs every contact, keeps the next action current | Whoever already administers invoices |
| Backup | Covers the schedule when the owner is unavailable | A second person in the same function |
| Dispute route | Answers the substance of a challenge: delivery, quality, pricing, scope | Operations, sales, or the project lead — whoever holds the evidence |
| Decision approver | Approves escalation, write-offs, and external placement | Owner, manager, or controller |
2. Set the reminder schedule
Write the cadence down so it runs the same way every time. The sequence below is a starting structure (hypothetical example) to adapt to your terms, your customers, and your staffing — not a required timeline:
| Stage | Timing | Action | Record kept |
|---|---|---|---|
| Pre-due check | 5–7 days before the due date | Confirm the invoice arrived at the right billing contact and the PO number matches | Short note on the account |
| Gentle reminder | 2–3 days after the due date | One-paragraph email: invoice, amount, due date, how to pay | Email copy in the account file |
| First follow-up | About 7 days past due | Formal reminder with invoice copy and a statement of the balance | Logged contact with date and channel |
| Second follow-up | About 14 days past due | Phone call plus email; ask what is blocking payment and request a specific date | Call note: what was said, what was committed |
| Escalation review | About 30 days past due | Owner and approver review the account against the escalation rules below | Documented decision and reason |
| Final internal notice | 45–60 days past due | Written notice stating the balance, the history, and the intended next step | Copy retained; wording checked for accuracy |
| Handoff decision | 60–90 days past due | Decide: continue internally, change approach, or place the account externally | Decision plus supporting file |
Templates make the schedule sustainable — see our overdue invoice reminder email and final payment reminder email guides, and the collection call script for the phone step. Tone should stay factual and unemotional throughout: state what is owed, what was agreed, and what happens next.
3. Write the escalation rules
Escalation should be triggered by events you can point to, not by a feeling that enough time has passed. Pick the criteria that fit your business and apply them uniformly:
- A broken promise. A customer commits to a date and misses it. Second miss triggers mandatory review rather than another open-ended reminder.
- Silence across channels. No substantive response after reminders by email and phone within your schedule window.
- A dispute that will not close. The claim has been routed, the evidence exchanged, and it still has not resolved — unresolved disputes cap what reminders can achieve.
- Age or balance thresholds. For example, any account crossing your chosen days-past-due mark, or any single balance above an amount your business designates as material.
- Economics. The effort already spent, and the effort next required, are out of proportion to the balance — our evaluation worksheet structures that comparison.
4. Route disputes on purpose
Disputes die in inboxes. Route each type to the person who can actually resolve it, with the evidence attached, and keep the invoice out of the standard reminder cycle while it is genuinely under review:
| What the customer says | Route to | Assemble | Resolve by |
|---|---|---|---|
| "Never received it" / short shipment | Whoever ships or performs the work | Delivery record, bill of lading, signed receipt | Confirm with proof, or credit what is genuinely missing |
| "Wrong price / not what we agreed" | Account owner or sales | Contract, quote, PO, change orders | Reconcile to the agreement; reissue if the invoice is wrong |
| "No PO on the invoice" | Billing | Buyer's PO from the customer's contact | Correct and reissue with the PO number |
| "Quality problem" | Operations | Specifications, correspondence, inspection records | Credit, replace, or document why the claim does not hold |
| "We already paid" | Accounts receivable | Remittance advice, bank posting, unapplied cash report | Apply the payment and confirm the remaining balance |
Every route needs an owner and a "we will come back to you by" commitment — even when the answer is "still checking." The documents you will need are listed in the collection documents checklist.
5. Document every contact the same way
One format, five fields: date, channel, who you spoke to, what was said or committed, next action and its date. Keep it in the account record rather than in individual mailboxes. This does three jobs: any colleague can pick up the account, promise-to-pay commitments become verifiable, and if the account later moves outside your business, the file is already assembled — see what a complete collection file contains.
Record broken promises explicitly. A single missed date is context; a pattern of three is the most useful escalation trigger you have, and it is invisible unless someone wrote it down.
The weekly routine that holds it together
Thirty minutes, same day each week: review the aging report, clear unapplied payments, check that every overdue account has a current next action, confirm disputes are moving, and flag anything that has hit an escalation rule. How to read an accounts receivable aging report covers the review itself. Prevention also belongs in the process — new-customer checks and clean invoicing reduce the size of the list you are working: preventing late payments and building a customer credit policy.
Common failure modes
The process lives in one person's head
When that person leaves or takes a month off, follow-up stops and nobody notices for six weeks. Write it down; a one-page procedure is enough.
Reminders stop when the relationship matters
Important customers get a pass, then a surprise. Consistency is kinder: keep the schedule, adjust the tone, and separate the commercial conversation from the payment conversation.
Everything waits for the "big" escalation
Teams either never escalate or escalate everything. Rules fix both: the account that meets a criterion moves; the account that does not, stays in the schedule.
No distinction between disputed and ignored
These require opposite responses. A dispute needs evidence and a decision; silence needs a firm, documented follow-up. Treating both identically wastes effort on each.
When the process has done its job
A written procedure will not collect every account — some customers stop responding regardless of how well-run your follow-up is. When that happens, you are choosing between channels rather than improvising: how to collect unpaid invoices covers deeper internal effort, in-house vs. a collection agency compares the options, and what happens after you send an invoice to collections explains the handoff. If an account has run through your process without movement, you can submit it for review and we will tell you what fits and what is missing. The wider system — terms, credit policy, invoicing, and measurement — is in the accounts receivable management guide.