Build a four-week accounts receivable cash forecast invoice by invoice. Start with open receivables, assign a collection week only when evidence supports the timing, keep uncertain invoices visible, and review actual receipts against the prior forecast every week. An aging bucket alone cannot tell you when cash will arrive.

QuickBooks' A/R Aging Detail report provides the transaction-level starting point: open invoices, outstanding balances, and how long transactions are past due. A forecast adds a separate layer of expected timing. It should never change the accounting record or present an estimate as certain cash.

Start with one row per open invoice

Keep the source columns intact: customer, invoice number, invoice date, due date, original amount, and open balance. Add review columns next to them rather than overwriting them:

  • Current evidence or status
  • Promised payment date, if any
  • Dispute or approval blocker
  • Expected collection week
  • Confidence label
  • Internal owner
  • Next action and review date

Reconcile the invoice rows to the source report before forecasting. If the report contains unapplied payments, unexplained credits, or missing due dates, mark those rows as data exceptions instead of guessing. Keep uninvoiced billable expenses in a separate upstream schedule so they are not counted as open receivables.

Use evidence rules for each week

Define the four forecast columns as Week 1 through Week 4 using actual date ranges. Then apply a consistent rule:

  • Put a row in a week when a specific payment commitment, established payment pattern, completed approval, or other documented evidence supports that date range.
  • Lower the confidence or leave timing unconfirmed when a promise is stale, a dispute is open, approval is missing, or no meaningful follow-up exists.
  • Keep invoices beyond Week 4 in a visible later or unconfirmed group rather than dropping them from the review.

This approach avoids the common shortcut of treating every current invoice as near-term cash and every old invoice as equally unlikely.

Turn open AR into forecast cash receipts

Treat the conversion as a controlled bridge rather than a single percentage calculation. Begin with validated open AR. Exclude amounts that are not issued receivables, identify receipts already observed before the snapshot cutoff, and place only the remaining supported invoice amounts into Week 1 through Week 4. Microsoft's cash-flow forecasting documentation likewise separates open customer transactions from the timing rules used to estimate their cash impact.

The bridge should always reconcile:

`validated open AR = forecast inside four weeks + later amounts + unassigned amounts + documented exclusions`

That equation explains where the source balance went without claiming every open dollar will be collected. Use the invoice-level forecast formula for weekly lower and upper totals, and keep the reconciliation beside the action list.

Separate amount, timing, and confidence

These are three different judgments. The open balance comes from the accounting export. The expected week is a planning assumption. The confidence label summarizes the strength of the evidence. Do not multiply an invoice by an invented probability simply to make the forecast look precise.

A useful confidence scheme can stay qualitative:

  • Supported: recent, specific evidence points to the assigned week
  • Conditional: timing depends on a named approval, dispute, or other blocker
  • Unconfirmed: the invoice is open, but evidence does not support a week

Write the evidence beside the label so another reviewer can challenge it.

Roll the forecast forward every week

At the next review, compare actual receipts with the invoice-level forecast. Mark paid rows, move slipped rows only when new evidence supports the change, and record why the prior assumption missed. The variance is useful because it improves the rules for future reviews; it is not proof that a forecast was guaranteed.

Track at least four outcomes: collected in the assigned week, collected earlier, collected later, and still open. Review repeated misses by customer, evidence type, and blocker type without turning a small sample into a broad benchmark.

Connect the forecast to decisions

The output should show both expected weekly collections and the exceptions that could change them. A finance owner should be able to see which timing assumptions deserve attention before relying on the total.

When an invoice includes tax, the QuickBooks sales-tax cash bridge explains how to reconcile the gross customer receipt while keeping its components separately classified.

Before assigning weekly timing, use the AR forecast reconciliation bridge to explain how beginning open AR became the current issued-invoice population.

AR Pulse's comparison of aging and forecasting explains why the two views serve different decisions. AR Pulse converts an authorized QuickBooks receivables export into a ranked cash-action list and a four-week collections forecast. It does not contact customers, and the forecast is not a promise of payment.

For management teams starting from a broader working-capital metric, the cash conversion cycle vs. AR action review comparison explains why aggregate trends still need invoice-level evidence and owners.