Before comparing or exporting a QuickBooks accounts receivable aging report, lock four things: the report date, aging configuration, included scope, and reconciliation result. Save those settings with the file. Two exports with different snapshot rules are not a reliable trend, even when both files are individually valid.

Intuit's AR aging documentation distinguishes the summary report, which shows total outstanding balances and how long they are past due, from the detail report, which exposes the underlying transactions. It also lets users customize aging periods. That flexibility is useful, but it means the export needs a small control record before anyone analyzes changes.

Lock the snapshot settings

Record these fields beside every export:

  • **Snapshot date:** the date the report represents, not the date someone happens to review the file.
  • **Report type:** AR Aging Detail or AR Aging Summary. Use detail when invoice-level review is required.
  • **Aging configuration:** the periods and aging options shown in the saved report.
  • **Entity and customer scope:** any filters, exclusions, classes, locations, or customer selections applied.
  • **Accounting source:** the QuickBooks company and report name, without sharing credentials.
  • **Export timestamp and owner:** who created the file and when.

Do not infer a comparison period from a filename alone. Put the snapshot date inside the review record so a renamed file cannot silently change the meaning of the data.

Reconcile before comparing

A comparison should start only after each snapshot passes the same checks. Intuit's AR reconciliation guidance explains that report settings and transaction treatment can contribute to differences between the AR balance and AR reports.

Use this preflight:

  1. Confirm the expected customers and transactions are present.
  2. Confirm the aging-detail total agrees with the intended AR control view for the same date and scope.
  3. Check unapplied payments, credits, and zero-net customer balances before treating changes as new collection risk.
  4. Confirm invoice identifiers, open balances, due dates, and customer names survived the export.
  5. Save the settings record with the exported file.

If the totals do not reconcile, label the snapshot **held for review**. Do not repair the books from an analysis copy or force the difference into a forecast assumption.

Compare like with like

Once both snapshots use the same rules, compare invoice-level changes rather than only bucket totals. Mark new invoices, payments, credits, balance changes, and invoices that moved buckets. Keep operational evidence—such as a dispute or dated payment commitment—separate from the accounting facts.

| Comparison item | Source fact | Review question | |---|---|---| | Open balance changed | Exported invoice balance | Was cash or a credit applied? | | Aging bucket changed | Due date and snapshot date | Did the settings also change? | | Invoice disappeared | Prior and current export | Was it paid, credited, excluded, or corrected? | | Customer total changed | Sum of open invoices | Which source rows explain the movement? |

The QuickBooks AR export column checklist covers the minimum invoice fields, while the Open Invoices versus AR Aging Detail comparison helps choose the starting report. Review unapplied payments in AR aging when the ledger and operational view disagree.

When a saved or customized view is reused, apply the filtered aging-report scope control so hidden customer, date, status, or transaction filters do not silently change the invoice population.

AR Pulse analyzes an authorized QuickBooks receivables export and traces findings to supplied source rows. It does not request QuickBooks credentials or change the books. See the one-page example for the output structure.