Overdue invoice audit: review a minimized CSV
An overdue invoice is a record to review, not proof that cash was lost. Payments, credit notes, disputes and export timing can change what is actually owed.
Start with the source record
Export a current invoice list from your billing system. Keep a private mapping of invoice IDs to customer records. CAVOA needs only id, status, balance, currency, due_date and last_payment_date. Omit names, emails, bank details and free-text notes.
What the current CSV checker does
The supported scan flags overdue unpaid balances and stale part-paid balances using the supplied fields. It shows matched rows and rule explanations. An old balance can be a reconciliation issue; confirm payments and credits in the source system. It does not inspect failed card payments or establish collectibility.
A practical review sequence
Confirm the invoice is still open, check its due date, match payments and credits, then record whether the finding is true, false or uncertain. Do not chase a customer from a CSV flag alone. Use the Action Center to track your review and next step.
Try the zero-data check first
The free Revenue Leak Check asks about your process. It does not read invoices or estimate money found. A minimized CSV audit is optional and subject to the First Five participation workflow.
See the synthetic example · Prepare a minimized CSV · Supported checks
Related guides
- Stale partial payment: review the remaining invoice balance
- Revenue Health, review actions and verified recovery
Source-system guidance
Stripe Invoicing documentation · Stripe pilot status · QuickBooks CSV and pilot status · Xero CSV and pilot status
CAVOA. Product scope reviewed . No customer results or recovery claims are implied.