An old invoice status or collection note should stop supporting a four-week receipt assumption when its stated review date passes, its underlying condition changes, or newer source evidence contradicts it. Do not assign one universal expiration period. Instead, record an evidence date, a next-review trigger, and the event that would upgrade, downgrade, or invalidate the assumption.

Oracle's receivables review documentation describes collections information such as disputes, promises, and customer activity as separate review inputs. Intuit's AR aging guidance provides a current snapshot of outstanding balances and past-due status. A forecast needs both a current source row and current support for timing.

Distinguish source freshness from assumption freshness

The invoice row can still be current while the note behind its expected week is stale. Conversely, a recent note cannot rescue an export with the wrong report date or unresolved balance. Track these separately:

  • source snapshot date and scope;
  • current open amount and status;
  • evidence type and observation date;
  • expected week or unconfirmed state;
  • owner and next-review date;
  • invalidation trigger.

If any material component is missing, preserve the invoice but lower the support assigned to its receipt timing.

Use event-based expiration

A promise-to-pay can expire when its date passes without an observed receipt. An approval note can expire when the approval is rejected, changed, or still pending at the agreed check date. A dispute update can expire when a new deduction, credit, or resolution appears. Historical timing evidence can expire when the current customer, contract, amount, or process is no longer comparable.

Age alone does not refresh evidence. Repeating last week's forecast week in a new column is not a new observation.

Route stale evidence explicitly

  • **Still supported:** source and condition remain current; retain the week and set the next check.
  • **Conditional:** a named event remains unresolved; retain the condition, owner, and review date.
  • **Unconfirmed:** the old support expired and no current evidence replaces it.
  • **Source blocked:** the invoice balance or status itself is not reconciled.

Do not delete the prior note. Preserve when it was last valid and why the current classification changed. This creates a usable record for later forecast-variance review.

The promise-to-pay guide shows how dated commitments should be tracked. The confidence-label framework separates evidence quality from payment probability. The forecast variance review compares locked assumptions with observed outcomes.

Add a weekly freshness test

Before publishing the next four-week range, sort assumptions by next-review date and materiality. Check expired items first, then rows changed in the new AR snapshot, then supported items whose conditions approach the cutoff. Record the reviewer and outcome. Leave blank fields blank when no new evidence exists.

Decision rule

Evidence remains usable only while its source, condition, and review window remain current. When support expires, keep the invoice visible and move its timing to conditional, unconfirmed, or blocked. Never extend a prior collection assumption merely to keep the forecast populated.

AR Pulse analyzes an authorized QuickBooks receivables export to produce a ranked cash-action list and four-week collections range. It does not contact customers or guarantee collections. Finance owners can apply for AR Pulse to make evidence dates and review triggers explicit.