An accounts receivable forecast reconciliation bridge explains how the validated open-invoice population changed between two dated snapshots. Build that bridge before assigning collection weeks. It keeps accounting movements—new invoices, payments, credits, reversals, and write-offs—separate from management judgments about when the remaining invoices may turn into cash.
Microsoft documents open customer transactions as one source for cash-flow forecasting alongside upstream items such as sales orders and unposted invoices. Oracle's forecasting documentation separately describes DSO-based drivers that apply an average collection period to outstanding revenue. Those approaches reinforce the need to label the source population and method rather than blend unlike inputs.
Start with a dated AR roll-forward
Use one accounting source, report date, currency basis, and filter scope for both snapshots. Then reconcile:
- Beginning issued open AR
- Plus invoices and debit adjustments issued after the beginning snapshot
- Less receipts applied to those invoices
- Less issued credits, approved write-offs, and other supported reductions
- Plus supported reversals that reopen receivables
- Equals ending issued open AR
Every bridge line should retain the customer, transaction ID, effective date, amount, movement type, and source-row reference. If the calculated ending balance does not equal the validated ending export, stop at an explicit unexplained difference. Do not create a balancing adjustment merely to make the bridge tie.
The QuickBooks AR reconciliation guide covers report-level mismatches. The bridge here has a narrower job: explaining invoice-population movement between two forecast snapshots.
Keep forecast allocations outside the accounting bridge
After the ending open AR is validated, assign supported amounts to Week 1 through Week 4. The accounting bridge says what remains open. The forecast says when some portion might be collected. A promise to pay can change timing without changing open AR. A posted receipt can change open AR and observed cash. A requested credit can weaken a timing assumption without reducing the source balance until the credit is issued.
Use the invoice-level forecast formula to keep lower and upper cases traceable. Then compare both scenarios with the four-week control total so no invoice is allocated twice and no scenario exceeds supported open balances.
Add a compact exception table
For each unreconciled movement, record:
- invoice and customer reference;
- beginning and ending open amounts;
- observed movement and effective date;
- missing or conflicting evidence;
- internal owner and next validation action; and
- next review date.
The same receipt cutoff must apply to the bridge and the forecast. The cash-receipt cutoff guide helps separate receipts already observed from future collection assumptions.
Decision rule
Trust a four-week AR forecast only when its ending source population ties to a dated reconciliation bridge or carries a visible unresolved difference. Do not hide a mismatch inside a collection probability, confidence label, or catch-all week.
AR Pulse analyzes an authorized QuickBooks receivables export and returns a ranked cash-action list plus a four-week collections range. It does not change accounting records or guarantee collections. View the example report to see how source-backed exceptions and timing assumptions stay separate.