An accounts receivable exceptions report is a short management queue, not a reformatted aging report. It should isolate the invoices, customers, and collection assumptions that require a decision now. Every row needs a reason it is exceptional, a materiality signal, an owner, and a next action.
QuickBooks describes aging reports as a view of outstanding balances, who is behind, how much remains due, and how long balances are past due. That is the factual base. The exception report adds an operating layer so the weekly meeting does not spend equal time on every open invoice.
Recommended report columns
- Priority and exception type
- Customer and invoice number
- Open balance and customer total open AR
- Due date and days past due
- Last meaningful follow-up
- Promise date and promise status
- Dispute or blocker
- Expected collection week and confidence
- Internal owner
- Next action and due date
- Evidence note or source-row reference
Keep the original balance, invoice date, and due date separate from judgment fields. Expected collection week, confidence, and priority are management assumptions; they should be visible and reviewable rather than blended into accounting facts.
Six useful exception types
Missed promise
The customer gave a payment date and that date passed without verified receipt. A missed promise deserves a clear owner and a new evidence-gathering action; it should not remain in the forecast merely because the old promise was specific.
Unresolved dispute
A product, service, procurement, or documentation issue is preventing normal payment. Record the blocker, the internal person able to resolve it, and the next decision date. “Customer dispute” without a named blocker is not actionable.
Missing follow-up
No meaningful activity has occurred within the company’s chosen review window. Automated reminder delivery alone may not count as meaningful evidence. The exception is the absence of a current collection signal.
Material concentration
One customer represents a large share of open AR or the expected cash for a near-term week. Concentration can matter even when none of that customer’s invoices is the oldest.
Data-quality conflict
The due date, balance, credit, payment application, or invoice identity appears incomplete or contradictory. Resolve data quality before turning the row into a confident forecast assumption.
Timing-risk change
New evidence makes the existing expected collection week too optimistic or too conservative. Record what changed and when the next reassessment should occur.
A priority rule that avoids “oldest first”
Use age as one input, then combine it with balance materiality, customer concentration, evidence strength, broken commitments, active disputes, and forecast impact. Intuit's explanation of aging buckets clarifies that current and past-due placement depends on due dates. It does not imply that every invoice in the same bucket deserves the same action.
A simple high-attention test is: would a change in this row alter a management action or the expected cash range? If not, it probably belongs in the underlying aging detail rather than the exception queue.
The open-invoice-list versus AR action-queue comparison explains why the complete reconciled population and the smaller owned work queue should remain linked rather than being treated as interchangeable reports.
Weekly meeting sequence
- Reconcile the source total and confirm the review date.
- Review new and materially changed exceptions first.
- Resolve data-quality conflicts before debating timing.
- Assign one owner and one dated next action per material exception.
- Update forecast timing and confidence only when evidence changes.
- Close resolved exceptions without deleting the decision history.
The output should be concise enough to review, but complete enough that someone can understand why a row was prioritized. AR Pulse applies this exception-first structure to a customer-provided QuickBooks export, producing a ranked cash-action list and a four-week collections forecast. It is an analysis layer, not reminder automation, bookkeeping, or a guarantee that an invoice will be paid.