Recovery Audit Document Checklist

1. Common Business Triggers

• The organization has never conducted a structured AP recovery audit
• AP transaction volume has grown significantly without a corresponding increase in review resources
• An ERP migration or finance-system change has created concern about data integrity during the transition period
• A merger or acquisition has combined AP operations with different vendor master files and payment practices
• A private-equity sponsor or board has requested a historical transaction review as part of a margin-improvement or pre-sale diligence initiative
• A specific vendor relationship has raised concerns about billing accuracy that leadership wants to evaluate systematically

2. Warning Signs Leadership Should Recognize

• AP processes invoices without matching against contract pricing or purchase orders. When invoices are approved for payment without verification against the underlying agreement, overbilling can continue indefinitely.
• Vendor credits and credit memos are not systematically tracked or applied. Credits that sit unapplied represent cash the organization has already earned but not collected.
• Duplicate-payment detection is manual or nonexistent. Without automated duplicate detection, the same invoice can be paid twice — particularly across different entities, departments, or time periods.
• The vendor master file contains duplicate or outdated vendor records. Multiple vendor IDs for the same supplier make it difficult to identify total spend, duplicate payments, and consolidation opportunities.
• No formal recovery audit has been conducted in over three years. The longer the gap, the larger the pool of potentially recoverable transactions — and the more likely that some may exceed lookback limitations.

3. The Recovery Review Workflow

A structured recovery audit follows a defined sequence. Each stage depends on the quality of the data assembled in the prior stage. The diagram below shows the flow from data collection through recovery or correction.

Illustrative Framework

Illustrative framework. Identifying a possible exception is fundamentally different from confirming that money is actually recoverable. Each step reduces the pool of flagged items to those that represent genuine, actionable recovery opportunities.

4. Document Checklist: What to Assemble

A structured recovery audit requires the following data and documents. The more complete the dataset, the more comprehensive the review.

• AP transaction data for 2–4 years. Invoice-level detail including vendor name, invoice number, invoice date, amount, payment date, payment amount, and payment method.
• Vendor master file. Complete vendor records including vendor ID, legal name, tax ID, payment terms, and remittance information.
• Payment records. Check registers, ACH files, wire confirmations, and virtual card payment records.
• Credit memo and adjustment data. All credits issued, including whether they have been applied or remain open.
• Contract terms for top vendors by spend. Pricing schedules, payment terms, discount provisions, and any rebate or volume-incentive agreements.
• Purchase order data for PO-based transactions. PO numbers, amounts, and approval records to match against invoices.

5. How Leadership Should Prioritize Findings

Recovery audit findings should be prioritized by recovery likelihood and collection effort:

• Confirmed duplicate payments first. These are the most straightforward recoveries — the same invoice paid twice to the same vendor. Recovery is typically a matter of notifying the vendor and requesting a refund or credit.
• Unapplied credits and credit memos second. Credits that the organization has already earned but not applied against outstanding balances represent immediate cash-flow improvement.
• Pricing and contract errors third. Overcharges due to incorrect pricing application require more documentation and may require vendor negotiation, but the dollar amounts are often material.
• Tax and freight errors fourth. These typically involve smaller dollar amounts but can be systematic across many transactions.

6. Common Preparation Mistakes

• Assuming that the ERP system will catch duplicate payments. Most ERP systems have basic duplicate detection but miss duplicates across entities, slight invoice-number variations, or payments made in different periods.
• Failing to include credit memos in the data extract. Without credit data, the audit cannot identify unapplied credits — one of the most common recovery categories.
• Limiting the review to a single year. A one-year lookback misses duplicates that span fiscal years and credits that have aged beyond the current period.
• Cleaning the data before extraction. "Cleaning" vendor names or invoice numbers before the review can actually hide the variations that the audit is designed to detect.

7. When a Review Is Relevant — and When It May Not Be

Likely relevant when: The organization processes significant AP volume annually, has never conducted a structured recovery audit, has undergone an ERP migration or acquisition, has decentralized AP operations across multiple locations or entities, or has vendor relationships with complex pricing structures.

May not be the highest priority when: The organization processes very low AP transaction volumes, recently completed a comprehensive recovery audit, operates with highly automated three-way matching that has been independently validated, or is in the middle of an AP-system implementation.

8. What Blackspire Evaluates — and What We Do Not Claim

Blackspire evaluates: AP transaction data for duplicate payments, overpayments, missed credits, pricing errors, and tax or freight inaccuracies; vendor master file integrity; and the organization's AP control environment. Blackspire validates flagged exceptions against source documents to confirm that each finding represents a genuine error.

Blackspire does not claim or guarantee: that any specific recovery amount will be achieved; that all flagged exceptions will be confirmed as recoverable; or that vendors will honor all refund or credit requests. Blackspire identifies and validates exceptions; the client decides which recoveries to pursue and how.

9. Practical Next Steps

1. Assess data accessibility. Confirm that AP transaction data, vendor master files, and payment records can be extracted from current systems.
2. Determine the lookback period. Identify the appropriate review window based on record retention, system migration history, and applicable statutes of limitation.
3. Extract the data without cleaning or filtering. Provide raw transaction data — data cleaning should occur after extraction, not before.
4. Include credit and adjustment records. Ensure the extract includes credits, credit memos, and manual adjustments, not just payment transactions.
5. Schedule a confidential conversation. If AP volumes are significant and a recovery audit has not been conducted, explore the Recovery Review or request a consultation.

10. Frequently Asked Questions