Aged A/R playbook

Turn an aging report into a recovery action plan.

Old invoices do not all need the same follow-up. The useful first move is to separate accounts that are ready to work from accounts that need proof, owner review, dispute cleanup, or no further action.

Published by RevRecoup. Updated June 12, 2026.

This playbook is for B2B teams reviewing commercial invoices that have moved beyond ordinary billing reminders. It is designed for first-party workflows where the original creditor or merchant remains in control of communications, payment terms, and escalation decisions.

Fast definition

Aged A/R recovery is the process of sorting overdue receivables by workability, evidence quality, dispute status, payment route, and next action before deciding whether to keep working the account, settle, hold, or escalate.

1. Triage the batch

Start with a single export or CSV. Avoid trying to solve every account at once. Add account-level columns that explain why an invoice is stuck, not just how old it is.

  • Invoice number, debtor name, amount, due date, and age bucket.
  • Last meaningful contact and current owner.
  • Dispute status: none, pricing, delivery, scope, quality, duplicate, or unknown.
  • Proof status: complete, partial, missing, or needs review.
  • Payment route: ACH, card, wire, portal, check, or unknown.

2. Segment by next action

Useful recovery work usually begins with segmentation. RevRecoup recommends five plain-language lanes.

LaneUse whenNext action
Work firstProof exists, contact route is known, and no unresolved dispute blocks payment.Send targeted first-party follow-up or call the AP owner.
Needs proofThe invoice is valid, but the file lacks contract, delivery, service, or communication evidence.Collect missing proof before further pressure.
Dispute cleanupThe debtor has raised a scope, quality, delivery, pricing, or duplicate-invoice issue.Route to the internal owner who can resolve the issue.
Payment promiseThe debtor has acknowledged the balance and needs tracking for a promised date or plan.Record promise terms and follow up on the promised date.
Escalation reviewThe file is complete, first-party work has stalled, and leadership approves outside review.Prepare a clean evidence timeline for approved escalation.

3. Build the evidence timeline

A messy file slows every recovery path. For each invoice, create a simple sequence: contract or order, invoice, delivery or completion proof, communications, dispute notes, payment attempts, and approvals.

The goal is not to overwhelm the debtor. The goal is to make sure the team knows what happened and what can be stated accurately.

4. Use a narrower follow-up cadence

For aged commercial receivables, broad reminder blasts are often less useful than specific account-level asks. Examples:

  • "Can you confirm whether invoice INV-1048 is approved for payment?"
  • "We have delivery confirmation and need the correct AP route for payment timing."
  • "Your team noted a scope issue. Who should review the attached proof?"
  • "The payment promise date passed on June 10. Can you confirm the revised date?"

5. Measure movement, not only money

Recovered revenue matters, but early signal comes from account movement. Track response rate, proof completion, resolved disputes, payment promises created, promises kept, payment plans started, and accounts moved to hold or escalation review.

Where RevRecoup fits

RevRecoup helps teams import aged invoices, assign recovery lanes, organize proof, track payment promises, preserve the evidence timeline, and decide when a file is ready for approved escalation.