A four-week accounts receivable forecast should do both jobs: roll forward for current cash decisions and preserve frozen dated snapshots for learning. The rolling view answers what finance believes now. A frozen snapshot records what finance believed at a specific cutoff. Replacing every prior version with the latest view makes the forecast easier to read but removes the evidence needed to explain changes and improve assumptions.

Oracle describes a rolling forecast as a planning view whose periods advance with the current period. Its planning guidance also describes copying working forecast data into milestone or snapshot versions for comparison. Apply that distinction at invoice level: keep one current operating view, and retain each approved weekly snapshot as an immutable comparison point.

Use the rolling view for today's decisions

The rolling view should contain the latest authorized receivables export, current open amounts, newly observed payments or credits, current exception status, owner, next action, and supported collection week or range. As the cutoff advances, remove elapsed periods and add a new period at the far edge.

Update the rolling view when source evidence changes. Examples include a payment application, issued credit memo, corrected invoice, new promise date, dispute resolution, or an invoice moving outside the four-week horizon. Do not wait for the next scheduled review when a material source correction makes the current view misleading.

Use the forecast reconciliation bridge before relying on the updated total. It separates beginning open AR, new invoices, credits, recorded collections, and ending open AR from the timing assumptions layered onto those balances.

Freeze a dated snapshot for comparison

At the review cutoff, preserve the exact source reference and the approved forecast fields. A useful snapshot includes:

  • snapshot date and export identifier;
  • invoice identifier and customer;
  • open amount at the cutoff;
  • expected collection week or unassigned status;
  • confidence or evidence label;
  • exception owner and next review date; and
  • the reason code for any manual timing decision.

The weekly AR snapshot change log shows how to compare successive exports without losing invoice history. The snapshot is not a second live forecast. It is the baseline for explaining what entered, left, moved, or changed.

Compare versions without rewriting history

For each invoice, classify the movement between the frozen snapshot and the current view. Separate observed cash, source-balance changes, timing changes, newly added invoices, and items that moved beyond the horizon. A paid invoice should be recognized as an outcome, while a timing change with no payment remains an assumption revision.

Use the AR forecast variance review to keep operational causes separate. Otherwise a forecast can appear accurate because the team quietly moved dates, removed exceptions, or replaced the baseline.

A simple operating rule

Maintain one clearly labeled current forecast and one frozen snapshot for every formal review date. Never edit the frozen copy. Link corrections and later evidence to a new version, and record why the assumption changed. This produces an auditable sequence without forcing the team to operate from stale data.

AR Pulse analyzes a dated authorized QuickBooks receivables export and produces a ranked cash-action list with a four-week collections range. It does not change the books or predict whether or when a customer will pay. View the example report to see how source facts and forecast judgments remain separate.