Compare weekly accounts receivable exports by invoice identifier and source state, not by total balance alone. A useful change log explains which rows were added, paid, partially paid, reopened, credited, removed, or changed between two dated snapshots. It preserves the old forecast instead of rewriting it with the newest data.

Intuit's AR aging guidance describes summary and detail views of outstanding customer balances. Intuit's audit-log guidance explains how changes to transactions can be reviewed. Together they support a simple control: retain dated invoice detail, then investigate material changes against the approved source rather than inferring their cause.

Lock the two populations

Record the entity, report name, report date, export time, aging basis, filters, currency, and preparer for both snapshots. Preserve the original files. If the report settings differ, mark the comparison as blocked until the scope is made comparable.

Use a stable invoice key when the source provides one. If it does not, combine customer, invoice number, invoice date, and original amount, then flag collisions for human review. Never silently choose one of two ambiguous rows.

Classify each row change

Give every material difference one status:

  • **Added:** issued and open in the new snapshot, absent from the prior one.
  • **Paid or closed:** present before, no longer open, with supported payment or closure evidence.
  • **Partially paid:** open balance decreased while the invoice remains open.
  • **Reopened:** previously closed or absent, now open again.
  • **Credited or adjusted:** the source balance changed through a documented credit or correction.
  • **Removed without support:** the row disappeared but the reason is not yet traceable.
  • **Unchanged:** key source fields and open amount match.

An amount change is not its own explanation. Link it to a payment, credit, replacement, correction, or current audit record where the authorized system supports that evidence.

Keep forecast changes separate

After source changes are classified, compare forecast fields: prior expected week, current expected week, evidence date, confidence label, owner, and next review. This separates a source event from a management-assumption change.

For example, a partial payment can reduce the remaining balance without proving a new date for the residual. A reopened invoice can return to the action list while remaining unconfirmed. A removed row should not disappear from the audit trail merely because it contributes no current expected cash.

The forecast variance review compares prior assumptions with observed receipts. The cash-receipt cutoff guide keeps actuals on the correct side of the snapshot date, and the void/delete guide covers unsupported removals and replacements. When an invoice remains open but its fields change, use the edited-invoice bridge. If the changed field is the payment term, preserve both dates with the due-date version guide.

Use a compact review table

Retain prior and current open amounts, change type, evidence reference, change date, source owner, prior and current forecast treatment, reviewer, and review date. Reconcile both snapshot totals to their own control balance before explaining the bridge between them.

When the changed source is a customer statement, use the statement version-control checklist because the live statement can reflect later transaction edits.

Decision rule

A weekly AR change log should make every material row movement reviewable and reversible. Preserve both exports, explain source changes before forecast changes, and leave unknown causes explicit. Do not overwrite the prior forecast or manufacture a reason for a disappearing balance.

Use the AR forecast update cadence to combine this locked weekly snapshot with event-driven reviews for material payments, reversals, disputes, and source corrections.

AR Pulse analyzes an authorized QuickBooks receivables export to produce a ranked cash-action list and four-week collections forecast. It does not request QuickBooks credentials, change accounting records, contact customers, or promise an outcome. Finance owners can view the example report after the snapshot population is reconciled.