A useful accounts receivable export needs to answer four questions at the invoice level: who owes the money, how much remains open, when it became due, and what evidence changes the expected collection date. A summary by customer or aging bucket can show exposure, but it cannot reliably support an invoice-by-invoice action queue.

Intuit's QuickBooks documentation distinguishes the A/R Aging Summary from the A/R Aging Detail report. The detail view is the better starting point when the goal is to review individual overdue transactions. QuickBooks also supports exporting reports to Excel, so a finance owner can work from an authorized file without sharing accounting credentials.

The minimum invoice identity fields

  • Customer or account name
  • Invoice number
  • Invoice date
  • Contractual due date
  • Original invoice amount
  • Open balance
  • Currency if the file can contain more than one currency

These fields establish a stable row identity and the basic aging calculation. Keep invoice number and customer name as separate columns. Do not combine multiple invoices into one customer total if the output needs owners, next actions, or different collection dates.

The fields that improve prioritization

Add days past due, aging bucket, customer total open AR, and any existing collection status. Days past due helps sort, but it should not become the only priority rule. A younger large invoice with a broken promise can deserve attention before an older small invoice with a confirmed payment date.

Customer-level total matters because concentration changes the management question. Several individually modest invoices can create a material exposure when they belong to one customer. A decision-ready review should preserve both the invoice row and the customer rollup.

The evidence fields that improve a cash forecast

The most valuable fields often live outside the standard aging export. Add them as explicit review columns rather than silently overwriting source data:

  • Last meaningful follow-up date
  • Promised payment date
  • Promise status
  • Dispute or blocker
  • Internal owner
  • Next action
  • Expected collection week
  • Confidence label
  • Evidence note

A promise date should not be treated as cash merely because it exists. Mark whether the promise is new, confirmed, missed, or unsupported. Likewise, a forecast date should remain an assumption linked to evidence—not a change to the accounting record.

What to remove before external analysis

Use the minimum data needed for the purpose. Remove bank details, tax identifiers, payment-card information, attachments, free-text notes with unrelated personal information, and credentials. Customer names may also be replaced with stable IDs when identity is not needed for the analysis. Never send a financial export through a public application form or ordinary email merely because the file is convenient.

A practical preflight before using the file

  1. Confirm the report date and entity.
  2. Reconcile the exported total to the QuickBooks report total.
  3. Check that open balance is invoice-level rather than customer-level.
  4. Confirm due dates exist and use the intended payment terms.
  5. Look for credits, unapplied payments, duplicates, and zero-balance rows.
  6. Preserve the untouched source export and work from a copy.
  7. Record any added assumptions in separate columns.

The result is not simply a cleaner spreadsheet. It is a traceable bridge between an aging report and a management decision. AR Pulse uses this principle to turn one authorized QuickBooks receivables export into a ranked cash-action list and a four-week collections forecast without requesting QuickBooks credentials or contacting customers.

After the first clean export, retain each dated snapshot and compare invoice rows before replacing the working file. The weekly AR snapshot change log classifies added, paid, reopened, credited, removed, and changed rows. Use the negative-customer-balance diagnostic for credit or unapplied-payment exceptions, and keep Undeposited Funds separate from bank-available cash.

Also preserve transaction type, manual-entry context, currency, and exchange-rate fields when they are relevant. Keep invoices separate from paid-at-sale sales receipts, route manual AR journal entries through a reconciliation review, and retain a dated foreign-currency invoice and home-value bridge.

Before an AI-assisted review uses the export, run the source-schema drift checklist for missing, renamed, duplicated, or type-shifted fields and require a named reviewer for mapping changes.

Preserve both the source customer identifier and display name. When one payer appears under multiple profiles, use the duplicate-customer profile checklist to add a reversible management mapping without changing the dated export.

The short version

Start with A/R Aging Detail, preserve one row per open invoice, keep the original financial fields intact, and add evidence fields for promises, disputes, ownership, expected timing, and confidence. That is enough structure to move from “what is late?” to “what needs attention, and what might arrive when?”