Use a QuickBooks customer statement when the job is to show one customer a selected view of transactions and balances. Use A/R Aging Detail when the job is to review the open transaction population, preserve invoice identity, understand overdue status, or prepare invoice-level actions and forecast assumptions. A statement can help explain a customer balance, but it should not silently replace the dated aging export used for analysis.

Intuit describes three statement types: balance-forward statements list transactions and a current balance for a date range, open-item statements list unpaid invoices, and transaction statements list activity in a chosen period. Intuit also notes that statements update when their underlying transactions change. That makes the statement useful for communication, but it also means a saved or sent version and a newly generated version can represent different source states.

Choose the view by decision

Use a customer statement for questions such as:

  • What balance and transaction activity should this customer see?
  • Which unpaid invoices appear on an open-item statement?
  • Does the statement require parent-customer or sub-customer handling?
  • What exact dated version was sent or reviewed?

Use A/R Aging Detail for questions such as:

  • Which open transaction is past due and by how long?
  • Which invoice row needs an owner, blocker, or next action?
  • Which open amount should enter an invoice-level collections review?
  • Do transaction rows reconcile to the customer and ledger totals?

Intuit's aging-report guide distinguishes the customer-level summary from A/R Aging Detail, which shows individual past-due transactions. That transaction identity is the stronger base for an action list or a four-week forecast.

Reconcile before explaining a difference

When a statement and aging report do not appear to agree, compare the controls before changing any row:

  1. Record the statement date, statement type, and start and end dates.
  2. Record the aging report date, aging method, and filters.
  3. Confirm whether sub-customers are billed with a parent.
  4. Compare invoice numbers, payments, credits, and open amounts at transaction level.
  5. Identify transactions posted after either snapshot.
  6. Preserve the original outputs and route unresolved differences to a named accounting owner.

Do not force the totals to agree by deleting rows from an exported aging report. The difference may be a date scope, statement type, hierarchy, payment, credit, or later posting. The report-date checklist provides a compact control block for keeping those factors visible.

Build the analysis from invoice evidence

For management review, preserve customer, invoice number, invoice date, due date, open amount, and a stable source-row reference. Add disputes, promises, owners, next actions, and forecast weeks in a separate analysis layer. The QuickBooks export columns checklist explains the minimum invoice-level handoff, while the Open Invoices comparison covers another useful report-selection decision.

If the chosen statement is an Open Item statement, check the 365-day statement scope boundary before treating its visible rows as a complete forecast population.

AR Pulse analyzes an authorized customer-provided QuickBooks receivables export and returns a ranked cash-action list plus a four-week collections forecast. It does not request QuickBooks credentials, send statements, contact customers, or change accounting records. View the one-page example to see how source rows, evidence, actions, and timing assumptions remain separate.