1
Define scope and responsible roles
Specify which invoice types and customer segments the procedure covers. Name the roles responsible for each escalation stage β AR clerk, finance manager, CFO β so accountability is clear.
π‘ Assign a single named owner for each escalation stage rather than a team or department. Shared ownership means no one acts.
2
Set specific day thresholds for each escalation stage
Replace any vague language with exact day counts from the original invoice due date. A typical cadence: Day 7, Day 14, Day 30, Day 60, Day 90+.
π‘ Run your last 12 months of invoice aging data before setting thresholds β match escalation triggers to where your DSO typically stalls.
3
Write or adapt the communication scripts
Draft an approved email and phone script for each escalation stage. Scripts should escalate in firmness β from friendly reminder to formal demand β while remaining professional throughout.
π‘ Have a manager review tone before finalizing. Language that sounds appropriately firm to a finance person can read as aggressive to a customer who intends to pay.
4
Document the late fee and interest policy
Enter the late fee rate, the day it begins to accrue, and how customers are notified. Confirm the rate matches what is stated in your invoice terms and any signed contracts.
π‘ Cross-check your late fee clause in every active customer contract before applying fees β mismatched terms create disputes that delay payment further.
5
Set payment plan authorization limits
Define the minimum balance, maximum plan duration, and the approval level required for payment arrangements. Record the form customers must sign before any plan takes effect.
π‘ A 90-day plan with three equal installments works for most SMB customers and resolves more accounts than a hard demand for full immediate payment.
6
Fill in legal and agency referral thresholds
Enter the dollar amount and age that trigger escalation to external collections or legal action. Name the person who must approve each referral and the documents they need to receive.
π‘ Set a calendar reminder to review accounts at the 45-day mark β catching borderline accounts before the 60-day threshold gives you more recovery options.
7
Specify record-keeping requirements and the system of record
Name the specific system (accounting software, CRM, shared folder) where all contact logs and documents must be stored, and set the 24-hour logging requirement for all contact attempts.
π‘ If your team uses both an accounting system and a CRM, designate one as the single source of truth for collections activity to avoid conflicting records.
8
Define the bad debt write-off approval chain
State the conditions that make an account eligible for write-off, the dollar approval thresholds for each management level, and the accounting entry required.
π‘ Separate write-off approval from collections responsibility β the person chasing payment should not be the same person who can approve writing it off.