Accounts Receivable Collection Process Steps

Standard Operating Procedure: accounts receivable collection process steps

1. Document Control & Revision History

---

2. Executive Summary & Scope

2.1 Purpose

This Standard Operating Procedure (SOP) defines the institutional workflow for the Accounts Receivable (AR) collection lifecycle. It establishes rigorous, auditable operational steps designed to optimize cash conversion cycles, minimize Days Sales Outstanding (DSO), mitigate bad debt exposure, and ensure strict compliance with global accounting standards.

2.2 Operational Boundaries & Scope

This SOP applies globally to all operating entities, business units, and shared service centers handling enterprise B2B and high-value B2C accounts receivable portfolios. It governs operations from the point of invoice issuance through cash application, dispute resolution, dunning execution, and pre-write-off legal escalation.

2.3 Regulatory & Accounting Framework

All collection operations must strictly adhere to:

• Generally Accepted Accounting Principles (GAAP) / International Financial Reporting Standards (IFRS): Specifically ASC 606 (Revenue from Contracts with Customers) and IFRS 9 (Financial Instruments: Expected Credit Losses).
• Consumer Financial Protection Bureau (CFPB) Regulations & Fair Debt Collection Practices Act (FDCPA): For applicable consumer accounts.
• General Data Protection Regulation (GDPR) & California Consumer Privacy Act (CCPA): Regarding the handling and retention of debtor Personally Identifiable Information (PII).
• Internal Control Frameworks: Sarbanes-Oxley (SOX) Section 404 internal controls over financial reporting.

---

3. Prerequisites & Tool Requirements

3.1 Software & System Access

• Enterprise Resource Planning (ERP): SAP S/4HANA, Oracle Cloud Financials, or Microsoft Dynamics 365 (Write, Read, and Reconciliation access).
• Accounts Receivable Automation Suite: HighRadius, Tesorio, or Quadient AR (Full collection workflow access).
• Customer Relationship Management (CRM): Salesforce Enterprise or HubSpot (Account health, contract terms, and communication log visibility).
• Payment Gateway & Banking Portals: SWIFT access, ACH processing platforms, and lockbox feed interfaces.

3.2 Hardware & Security

• Multi-Factor Authentication (MFA) hardware token or secure authenticator application.
• Encrypted enterprise workstation with Virtual Private Network (VPN) connectivity for remote operations.

3.3 Certifications & Qualifications

• Personnel executing this SOP must hold internal certification in Enterprise Credit and Collection Management (ECCM) or equivalent professional credentials (e.g., Certified Credit Executive - CCE, or Certified Global Business Accountant - CGBA).
• Annual mandatory compliance training completion regarding FDCPA, GDPR, and anti-bribery/anti-corruption (FCPA/UKBA) policies.

---

4. Roles & Responsibilities (RACI Matrix Table)

• Definitions:
  • Responsible (R): The operational role that performs the specific activity.
  • Accountable (A): The sole role with final approval and audit accountability.
  • Consulted (C): Subject matter experts and stakeholders providing critical input.
  • Informed (I): Parties updated on progress, milestones, and exception events.

---

5. Step-by-Step Operational Procedure

Phase 1: Pre-Dunning & Invoice Hygiene (Days 0 to 15 Post-Invoice)

• 1.1 Verify electronic invoice delivery via the EDI/Invoicing portal within 24 hours of generation.
• 1.2 Confirm complete billing data alignment: PO numbers, tax IDs, banking remittance details, and correct corporate legal entity names.
• 1.3 Monitor automated ERP bank feeds daily for early payment cash applications against open line items.

Phase 2: Active Dunning & Communication Cadence (Days 16 to 45 Overdue)

• 2.1 Day 16 Post-Due: Execute automated soft-reminder statement dispatch via the AR automation platform.
• 2.2 Day 30 Post-Due: Initiate direct phone/email contact by the assigned Collections Specialist. Log all communication attempts within the CRM and AR subledger within 2 hours of interaction.
• 2.3 Day 45 Post-Due: Issue formal Demand Letter (Escalation Level 1) featuring explicit payment due notices and hold-status warnings.
• 2.4 Notify the Account Executive (Sales Owner) of delinquency status to freeze outgoing shipments or service renewals pending resolution.

Phase 3: Dispute & Exception Management (As Triggered)

• 3.1 Upon client notification of short-payment, pricing discrepancy, or service defect, flag the specific line item as "Disputed" in the AR subledger.
• 3.2 Issue an internal workflow ticket to the Billing/Revenue Operations Lead within 24 hours of dispute identification.
• 3.3 Ensure undisputed portions of the invoice remain active and subject to standard collection cadences.
• 3.4 Execute root-cause analysis on recurring billing errors; issue Credit Memos or rebills only upon documented managerial approval.

Phase 4: Restructuring, Settlement & Legal Escalation (Days 60+ Overdue)

• 4.1 Evaluate accounts reaching 60+ days overdue for formal Payment Plan Agreement (PPA) eligibility under Credit & Collections Manager oversight.
• 4.2 For accounts exceeding 90 days overdue with unresponsiveness, compile the complete collection file (contracts, invoices, communication logs) and transfer to Legal Counsel.
• 4.3 Initiate third-party collection agency placement or legal litigation protocols based on enterprise bad debt risk policies.
• 4.4 Process bad debt write-off provisioning strictly in accordance with IFRS 9 / ASC 326 Expected Credit Loss (ECL) frameworks, following sign-off from the CFO.

---

6. Quality Assurance & Verification Criteria

6.1 Audit Checklist

• Every customer contact, promise-to-pay (PTP), and dispute must be immutably logged in the ERP/CRM within the same business shift.
• Bank reconciliations must occur daily; unapplied cash balances must not exceed 2% of total monthly cash receipts.
• Credit memos must be cross-referenced with original invoices and bear dual-authorization sign-off for amounts exceeding $10,000 USD.

6.2 Tolerance Thresholds & Benchmarks

• Days Sales Outstanding (DSO): Must remain within $\pm 5$ days of the industry benchmark or rolling 12-month historical target (Target: $< 45$ days for enterprise B2B).
• Collection Effectiveness Index (CEI): Must maintain a monthly performance benchmark of $\ge 85%$.
• Bad Debt Write-off Rate: Must not exceed $0.5%$ of total annual gross credit sales.
• Aging Portfolio Concentration: Maximum of $5%$ of total AR balance permitted in the $> 90$ days overdue bucket.

---

7. Practical Troubleshooting Scenarios

Scenario A: Unapplied Cash Received Without Remittance Advice

• Symptom: Wire transfer or ACH payment lands in the bank clearing account, but no associated invoice number or customer identifier is provided in the remittance metadata.
• Immediate Corrective Action Protocol:
  1. Post the transaction immediately to the suspense/unapplied cash ledger account.
  2. Issue an immediate system-generated inquiry to the originating banking institution via the lockbox/treasury portal requesting full originating entity details.
  3. Cross-reference the exact incoming cash amount against open invoices across all business units matching the exact numerical value within a $\pm 3$-day billing window.
  4. If unresolved within 48 hours, contact the suspected client via the business development or sales channel to secure remittance data before reallocating the funds.

Scenario B: Client Refuses Payment Due to Unresolved Service Dispute

• Symptom: Debtor states they will withhold 100% of payment for an active invoice because a separate, unrelated project phase or product delivery is delayed or defective.
• Immediate Corrective Action Protocol:
  1. Validate the validity of the service complaint via the CRM ticket logs.
  2. Invoke "Segmented Collection" protocols: Isolate the undisputed invoice amount from the disputed line items.
  3. Require the client to remit payment for the undisputed portion immediately as a condition for ongoing dispute mediation.
  4. Establish a joint resolution meeting with the Service Delivery Lead and Account Executive, setting a strict 10-business-day resolution window for the disputed component.

Scenario C: Systemic ERP/Automation Integration Failure

• Symptom: Automated dunning emails fail to dispatch due to an API synchronization timeout between the CRM and the AR collection automation software.
• Immediate Corrective Action Protocol:
  1. Immediately notify the IT Enterprise Applications Helpdesk and log a Severity-2 incident ticket.
  2. Switch to manual operational mode: Extract the affected aging report directly from the ERP database via secure SQL query or flat-file export.
  3. Manually review and dispatch critical high-value dunning notices ($> $50,000$) via secure corporate email within 4 hours of the system failure detection.
  4. Reconcile all communication logs manually once automated system integration and data integrity are restored.