Analyze a QuickBooks accounts receivable export in four passes: validate the file, identify invoice-level exceptions, assign an evidence-based collection week, and turn the exceptions into owned next actions. The useful output is not another aging total. It is a short list of invoices that need a decision and a four-week view of cash that may arrive.
Intuit distinguishes the A/R Aging Summary, which groups customer balances, from the A/R Aging Detail report, which shows individual past-due transactions. Use the detail report when the analysis must preserve invoice identity. Intuit also documents how to export QuickBooks Online reports to Excel, allowing the review to happen from an authorized file rather than shared accounting credentials.
Pass 1: validate the export before interpreting it
Start with a copy of the untouched source file. Record the entity, report date, accounting basis, and any report filters. Reconcile the export total to the report total before adding assumptions. Check for missing due dates, duplicate rows, credits, zero-balance items, unapplied payments, and customer totals that do not agree with the invoice rows.
Do not repair the accounting record inside an analysis copy. Flag a suspected data issue for the bookkeeper or controller and keep the original value visible. A clean chain from source row to finding matters more than a cosmetically perfect spreadsheet.
Pass 2: separate routine aging from exceptions
Days past due is a useful sort key, but it is not a complete priority rule. Review each open invoice for evidence that changes the management decision:
- A promised payment date that is confirmed, missed, or unsupported
- A dispute, missing approval, credit, or billing mismatch
- No meaningful follow-up or no clear internal owner
- A large customer-level exposure spread across several invoices
- A due date or payment term that appears inconsistent
- A payment or credit that may not have been applied correctly
The result should be an exception queue, not a list that treats every overdue invoice as equally urgent.
Pass 3: assign a collection week from evidence
For a four-week view, give each invoice an expected week only when there is a reason for the timing. A recent, specific payment commitment can support a different assumption from an invoice with no response. A documented dispute should remain visibly separate from an unblocked invoice. If the evidence is weak, mark the timing as unconfirmed instead of forcing the invoice into a confident forecast bucket.
Keep source facts, review notes, and forecast assumptions in separate columns. That makes it possible to update an assumption without rewriting the accounting data.
Pass 4: publish a compact action list
For each management exception, record:
- Invoice and customer identifier
- Open balance and due date from the export
- Exception or evidence status
- Expected collection week and confidence label
- Internal owner
- Next action and review date
Sort the final list by decision priority, not merely by age. The first items should be the ones where management attention can clarify timing, resolve a blocker, or prevent an assumption from quietly going stale.
What the finished analysis should answer
A finance owner should be able to see which rows are reliable, which invoices need intervention, why each collection week was chosen, and who owns the next step. That is the bridge between a QuickBooks aging report and an operating cash review.
Before ranking the queue, run the duplicate-invoice screen and review voided, deleted, and replacement invoices. These controls prevent a source-population error from becoming a forecast priority or a duplicated expected receipt.
AR Pulse's export checklist describes the invoice and evidence fields needed for that bridge. AR Pulse works from a customer-provided export to produce a ranked cash-action list and four-week collections forecast; it does not request QuickBooks credentials or contact customers, and the forecast is not a promise of an outcome.