How to Plan an Accounts Receivable Transformation
DSO Doesn't Improve From Sending More Reminder Emails
The typical response to a DSO problem is to send more follow-up emails and add another collections headcount. Neither works at scale. DSO is a symptom of upstream problems: invoicing errors that customers dispute, payment processes that create friction, credit terms extended without data, and cash application delays that make it impossible to tell who has actually paid.
An AR transformation project addresses all four root causes. It's not a collections campaign — it's a redesign of the end-to-end order-to-cash process. Here's how to plan it.
Phase 1: AR Diagnostic (Weeks 1–2)
Measure the current state before setting targets.
Key metrics to establish:
- DSO (Days Sales Outstanding): AR balance ÷ (annual revenue ÷ 365)
- CEI (Collection Effectiveness Index): (beginning AR + credit sales − ending AR) ÷ (beginning AR + credit sales − ending current AR) × 100
- Bad debt rate: write-offs as % of revenue (trailing 12 months)
- Cash application rate: % of cash receipts auto-matched vs. requiring manual application
- Invoice error rate: % of invoices disputed or requiring correction
AR aging analysis:
- Total AR by aging bucket: current, 1–30 past due, 31–60, 61–90, 90+
- Stratify by customer: who are the top 10 accounts by past-due balance?
- Stratify by invoice type: which product/service lines have the most disputes?
- Calculate average collection period by customer segment
Process map:
- How are invoices generated and sent?
- What triggers a collections action, and who takes it?
- How is cash applied? Manually or automated?
- How are disputes identified, routed, and resolved?
- How are credit limits set and reviewed?
The diagnostic takes two weeks and produces the most important document in the transformation: a clear-eyed picture of what's broken and why.
Phase 2: Collections Process Redesign (Weeks 3–5)
A collections process that works at scale is systematic, not heroic.
Customer segmentation:
Segment customers into three tiers by strategic value and payment behavior:
- Strategic accounts: high revenue, pay on time → relationship-driven, dedicated AR contact
- Standard accounts: mid-market, standard terms → automated workflow with human escalation
- High-risk accounts: late payers, disputed invoices, or new customers with limited history → proactive management, shorter terms or prepayment required
Collections workflow by tier:
- Day 1 past due: automated email reminder (standard and high-risk accounts)
- Day 15 past due: personal phone call or email from AR team
- Day 30 past due: escalate to sales relationship owner with request to engage customer
- Day 45 past due: escalate to CFO/VP Finance; consider credit hold
- Day 60 past due: legal/collections referral decision
Dispute management:
- Define dispute categories: price discrepancy, quantity discrepancy, quality claim, duplicate invoice
- Route each dispute type to the appropriate resolver: sales for price disputes, operations for quality claims, AP for invoice errors
- Set resolution SLA by dispute type: 5 business days
- Track open disputes: unresolved disputes are always in the oldest aging buckets
Phase 3: Cash Application Improvement (Weeks 3–6)
Manual cash application delays cash visibility and creates reconciliation problems. Target 85%+ auto-match rate.
Current state assessment:
- What percentage of cash receipts can be auto-matched today?
- What prevents auto-matching? Missing remittance information, partial payments, customers paying multiple invoices in one check?
Improvement actions:
- Configure auto-matching rules in ERP: match on invoice number, customer ID, exact amount
- Implement remittance capture: pull remittance detail from customer emails, EDI 820 files, lockbox data
- Enable customer portal for remittance submission: customer logs in, indicates which invoices they're paying
- For mismatches: build exception queue workflow rather than ad hoc manual resolution
Lockbox optimization:
- If using bank lockbox, confirm remittance data is being captured and transmitted
- Consider upgrading to electronic lockbox for OCR extraction of remittance
Phase 4: Credit Policy Update (Weeks 4–6)
Extending credit without a defined policy is one of the most common drivers of bad debt.
Tasks:
- Document current credit limit methodology (if one exists)
- Define credit scoring approach for new customers: credit bureau data, financial statements for large accounts, trade references
- Define credit limits by customer tier: standard limits based on revenue or credit score
- Define enhanced due diligence triggers: limits above $X require additional review
- Configure credit holds: automatic hold trigger at 60 days past due on any invoice
- Define credit hold release process: who can release, what conditions must be met
- Communicate new policy to sales: they need to understand credit hold criteria and timeline
The sales team will resist credit holds on customers they're managing. That's expected. The policy must have CFO support and be applied consistently.
Phase 5: Customer Portal Rollout (Weeks 5–10)
A customer self-service portal reduces calls to the AR team and accelerates payment.
Portal capabilities to enable:
- View and download invoices
- View account balance and aging
- Submit payment: ACH, card, or check initiation
- Submit disputes or inquiries (routed to AR team)
- Submit remittance for unapplied cash
Onboarding:
- Identify top 50 customers by AR balance
- Personal outreach: email from AR manager with portal registration link
- Collect feedback from first adopters and fix friction before broader rollout
- Target: 60%+ of top customers active on portal within 90 days
Phase 6: Technology Implementation (Weeks 6–14)
If the diagnostic revealed technology gaps, this phase implements solutions.
AR automation platforms: HighRadius, YayPay, Versapay, Billtrust, Esker
Core capabilities to implement:
- Automated dunning workflows
- AI-prioritized collections worklist
- Cash application automation with remittance capture
- Customer portal
- Real-time AR analytics dashboard
Integration requirements:
- ERP integration: invoice data in, payment data out
- CRM integration: customer contact data, account history
- Bank integration: payment receipt confirmation
DSO Improvement Tracking
Measure weekly during the transformation:
| Metric | Baseline | Week 4 | Week 8 | Week 12 | Target |
|--------|----------|--------|--------|---------|--------|
| DSO | | | | | |
| CEI | | | | | |
| Auto-match rate | | | | | |
| Past due % of AR | | | | | |
| Dispute resolution days | | | | | |
Track this in gantt-chart.io alongside the project workstreams so the schedule and the metrics are visible in the same place. A DSO that isn't moving by Week 8 is a signal that the collections process redesign or cash application improvement needs to be revisited — not that you need more collectors.