Accounts Receivable Collections SOP
Accounts Receivable Collections SOP template for reviewing aging, contacting customers, escalating overdue balances, and preparing write-off approvals. Use it to standardize follow-up, reduce missed promises, and keep collection actions documented.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: B2b Saas · Wholesale Distribution · Manufacturing · Professional Services
Overview
This Accounts Receivable Collections SOP template defines how a finance or credit team reviews overdue invoices, prioritizes accounts, contacts customers, confirms dispute status, escalates delinquent balances, issues final notices, and prepares write-off documentation. It is meant for recurring collections work where timing, ownership, and documentation matter more than improvisation.
Use this template when you need a consistent process for aging review, customer outreach, promise-to-pay tracking, and approval-based write-offs. It is especially useful when multiple people touch the same account, when disputes need to be separated from true delinquency, or when management wants a clear escalation path for balances that exceed a threshold. The structure helps the team record what was done, who did it, and what the next action is.
Do not use this SOP as a substitute for legal advice, credit policy, or a contract-specific collection clause. If your organization has jurisdiction-specific debt collection rules, regulated customer classes, or attorney-led recovery steps, those requirements should be added to the procedure. It is also not the right template for active litigation, fraud recovery, or one-off exception handling unless those paths are explicitly added. The value of the template is in making routine collections work repeatable, traceable, and easy to audit.
Standards & compliance context
- This template supports ISO 9001-style documented information practices by defining controlled steps, responsibilities, and records for collections activity.
- It helps create an auditable trail for approvals, escalation, and write-off decisions, which is useful for internal control and financial review.
- If your organization follows formal credit policy, GAAP-oriented close procedures, or jurisdiction-specific debt collection rules, add those requirements to the workflow before use.
- Where customer disputes affect payment timing, the SOP should preserve evidence of the dispute and the resolution path to support non-conformance handling.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Steps
This section matters because it turns collections work into a repeatable sequence with clear ownership, verification, and escalation points.
-
Review the current aging report
The Accounts Receivable Specialist reviews the current aging report and confirms all open balances are grouped by current, 1-30, 31-60, 61-90, and 90+ days past due. The specialist verifies that the report date, customer names, invoice numbers, and outstanding amounts are accurate before starting collections activity.
-
Prioritize accounts by risk and delinquency
The Collections Specialist ranks accounts by days past due, balance amount, dispute status, and customer payment history. The specialist flags any account over the internal escalation threshold, any account with repeated broken promises to pay, and any account with a known dispute that may delay payment.
-
Contact customers according to the cadence
The Collections Specialist contacts each prioritized customer using the approved cadence for the invoice age and customer segment. The specialist sends a courteous reminder by email, follows up by phone when required, and records the date, time, contact method, person reached, and summary of the conversation in the contact log. The specialist requests a payment date or dispute details and confirms the next follow-up date.
-
Verify dispute status and promised payment dates
The Finance Manager verifies whether each overdue account is unpaid due to a valid dispute, missing documentation, or non-response. The manager confirms that any promised payment date is recorded, that supporting evidence is attached where applicable, and that unresolved disputes are routed to the appropriate internal owner for resolution.
-
Escalate accounts that exceed the threshold
The Accounts Receivable Specialist escalates any account that meets the escalation criteria, including balances beyond the defined days past due limit, repeated missed commitments, or unresolved disputes with no customer response. The specialist notifies the Finance Manager, sales owner, or account owner according to the escalation matrix and documents the escalation date, reason, and assigned owner.
-
Issue final notice for long-overdue balances
The Collections Specialist sends a final notice for accounts that remain unpaid after prior reminders and escalation attempts. The notice states the outstanding amount, the deadline for payment, and the next action if payment is not received, such as suspension of service, referral to a collection agency, or write-off review, according to company policy.
-
Prepare the write-off package
The Accounts Receivable Specialist prepares a write-off package for accounts that meet the company write-off criteria. The specialist includes the invoice details, aging history, collection attempts, dispute notes, customer response history, and the reason the balance is considered uncollectible.
-
Obtain approval before writing off the balance
The Finance Manager or other authorized approver reviews the write-off package and confirms that collection efforts were completed, the amount is within approval limits, and the documentation supports the request. The approver signs or electronically approves the write-off before the accounting entry is posted.
-
Record the final action and archive documentation
The Accounts Receivable Specialist updates the account status in the accounting system, records whether the balance was collected, escalated, disputed, or written off, and archives the supporting documentation in the approved repository. The specialist confirms the record retention period is followed and that the final disposition is visible in the collections tracker.
How to use this template
- 1. The collections owner reviews the current aging report and confirms which invoices are open, overdue, disputed, or already in escalation.
- 2. The collections owner assigns each account a risk priority and contact cadence based on balance size, delinquency age, customer history, and known dispute status.
- 3. The assigned collector contacts the customer using the approved cadence, records the contact attempt, and logs any promised payment date or dispute update.
- 4. The collector verifies whether the balance is valid, whether a dispute is active, and whether the promised payment date is realistic before moving the account forward.
- 5. The manager escalates accounts that exceed the threshold, issues the final notice for long-overdue balances, and prepares the write-off package for approval when recovery is no longer likely.
Best practices
- Keep the aging report source consistent so the team is working from the same invoice status, due date, and balance data each cycle.
- Separate disputed invoices from undisputed delinquency so collectors do not chase balances that require resolution before payment.
- Record the exact promised payment date and the person who made it, then compare that date against the next follow-up step.
- Use a clear escalation threshold tied to balance age, amount, or customer risk so exceptions do not depend on memory.
- Send final notice only after the required contact attempts and internal review are complete, not as a first response.
- Attach supporting documents to every write-off package, including aging history, contact log, dispute notes, and approval routing.
- Escalate repeated broken promises to a manager or account owner early so the account does not drift past recovery windows.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What does this Accounts Receivable Collections SOP template cover?
It covers the full collections workflow from aging review through customer outreach, promise-date verification, escalation, final notice, write-off preparation, and approval. The template is designed for recurring use by finance or credit teams that need a repeatable process for overdue invoices. It also creates a documented trail for disputes, deviations, and non-conformance handling.
How often should this SOP be run?
Most teams run the aging review on a weekly or biweekly cadence, then use the contact cadence defined in the SOP for each delinquency bucket. High-volume businesses may review daily for critical accounts or large balances. The right cadence depends on invoice volume, customer terms, and how quickly balances tend to age.
Who should own the collections process?
The process is usually owned by accounts receivable, credit and collections, or finance operations, with escalation to sales, customer success, or a manager when needed. A competent person should handle dispute review and approval routing so promises, exceptions, and write-offs are recorded consistently. If your organization separates customer communication from accounting approval, this SOP helps define those roles clearly.
How does this template support compliance and audit readiness?
It supports ISO 9001-style documented information practices by keeping the collection steps, verification points, and approvals in one controlled procedure. It also helps maintain an auditable record of customer contact, dispute status, escalation, and write-off authorization. If your business operates under stricter controls, you can add internal approval thresholds and retention rules without changing the core flow.
What are the most common mistakes this SOP helps prevent?
The most common issues are skipping the aging review, contacting the wrong customer contact, failing to verify whether a dispute is open, and missing promised payment dates. Teams also often escalate too late or write off balances before approval is complete. This template reduces those failures by making each step, role, and verification point explicit.
Can this SOP be customized for different customer segments or invoice types?
Yes. You can set different cadence rules for strategic accounts, small business customers, government accounts, or high-risk balances, and you can add separate paths for disputed invoices or installment plans. Many teams also customize thresholds, escalation owners, and final notice timing by region or contract type.
What systems can this SOP be integrated with?
It can be paired with ERP, accounting, CRM, ticketing, and document management systems so aging reports, contact logs, disputes, and approvals stay aligned. Common integrations include invoice status updates, email logging, task assignment, and approval workflows. The SOP should define what gets recorded in each system so the process does not depend on memory or spreadsheets alone.
How is this better than ad-hoc collections follow-up?
Ad-hoc follow-up usually depends on individual habits, which leads to inconsistent timing, weak documentation, and uneven escalation. This SOP gives the team a repeatable sequence with clear ownership, verification, and approval steps. That makes collections easier to manage, easier to audit, and easier to improve over time.
Related templates
Ready to use this template?
Get started with MangoApps and use Accounts Receivable Collections SOP with your team — pricing built for small business.
