Update a four-week accounts receivable forecast on a fixed weekly cadence and whenever a material invoice event makes the current view misleading. Preserve each dated snapshot. A small finance team does not need to rebuild every assumption after every email, but it should not wait for month end when a large receipt, dispute, credit, or missed promise changes the near-term cash picture.

The right cadence has two layers: a scheduled full review and event-driven exceptions. Recent accounting-practitioner guidance commonly describes weekly aging review as the minimum operating rhythm for a small team. AR Pulse uses the same practical boundary because a four-week forecast needs enough stability for comparison and enough freshness for cash decisions.

Run one controlled weekly refresh

Choose a consistent report date and receipt cutoff. Export the same QuickBooks receivables detail, reconcile the population, compare it with the prior snapshot, and update evidence fields only from observed sources. Lock the finished version before the next review.

The weekly review should answer:

  • Which forecasted receipts became observed cash?
  • Which invoices moved because of a payment, credit, dispute, approval, or source correction?
  • Which promises or scheduled events are now stale?
  • Which material invoices still have no defensible collection week?
  • Which owners and review dates need to change?

Use the weekly AR snapshot change log to preserve source changes. Use the forecast variance review to compare the locked expectation with observed outcomes.

Trigger an interim update for material events

Do not rebuild the entire portfolio for routine notes. Update or flag the affected rows when one of these events would materially change the current four-week view:

| Event | Immediate response | | --- | --- | | Material payment observed | Record actual cash under the cutoff and reduce the supported open amount | | Payment returned or reversed | Reopen the supported balance and remove stale receipt timing | | Large dispute or credit request | Separate the supported and unresolved amounts | | Promise missed | Expire the old week and request fresh dated evidence | | Buyer approval completed or failed | Change the blocker state; assign timing only if new evidence supports it | | Source correction changes scope | Reconcile the population before relying on totals |

`Material` is a company-defined review threshold, not a universal percentage. Document the threshold, owner, and reason so the cadence is repeatable.

Avoid continuous silent rewriting

A forecast that changes every time new information arrives but never preserves a snapshot cannot be evaluated. It hides misses and makes improvement impossible. Keep the prior version, timestamp the event, and create a revised current view. The rolling forecast vs. frozen snapshot guide explains how to use both without losing history.

Do not confuse update frequency with certainty. A daily refresh cannot turn a vague promise into a reliable cash date. Conversely, a weekly cadence should not delay a known material reversal until the next meeting.

A practical rule

For most small B2B service teams, use one full weekly refresh, a consistent cutoff, and event-driven updates for material changes. Review owners and unresolved exceptions between cycles without rewriting the locked baseline.

AR Pulse turns an authorized QuickBooks receivables export into a ranked cash-action list and four-week collections range. It does not require QuickBooks credentials, contact customers, or promise collection outcomes. Apply for AR Pulse when the team needs a repeatable evidence-based review cadence.