For a four-week cash view, use an invoice-level collections forecast as the primary method. A balance forecast can help project ending accounts receivable, and an aging-based method can provide a broad directional view, but neither method by itself explains which open invoices may turn into cash next week or what evidence supports that timing.

Oracle's planning documentation describes several forecast methods because the right method depends on the series and decision being modeled. Microsoft's cash-flow forecasting documentation separately identifies payment terms and the time between an invoice due date and payment date as inputs to cash timing. Those distinctions matter for receivables: forecasting an ending balance is not the same task as deciding which receipts may arrive within four weeks.

The short answer: choose from the decision horizon

| Management question | Best starting method | Main limitation | | --- | --- | --- | | What may collect in the next four weeks? | Invoice-level evidence forecast | Requires current review of each material invoice | | What AR balance may remain at month end? | Balance roll-forward | Does not show which receipts drive cash timing | | What broad collection pattern is plausible with limited detail? | Aging-based assumption | Buckets hide disputes, promises, and approval blockers | | What changes beyond the issued-invoice horizon? | DSO or driver-based model | Too aggregated for the next invoice-level action |

The best method is therefore not one universal formula. It is the method whose unit of analysis matches the decision. For a near-term cash action list, begin at the invoice level and keep the longer-range model as a separate view.

Method 1: balance or roll-forward forecast

A balance forecast starts with accounts receivable as a financial-statement balance and projects how new invoicing, receipts, credits, and other changes may affect a future ending balance. Use it when the main question is how much receivables may remain outstanding at a month or quarter end.

This method is useful for a longer-range cash model, working-capital planning, or a balance-sheet view. Its limitation is resolution. Two businesses can have the same projected ending receivables balance while facing very different near-term collection timing, customer concentration, disputes, and approval blockers.

Method 2: aging-based collections assumption

An aging-based method groups open receivables by age or due status and applies a collection assumption to each group. It is compact and can be useful when invoice-level evidence is unavailable.

Intuit explains that the A/R Aging Summary shows customer balances while the A/R Aging Detail shows individual transactions. The summary can support a portfolio-level view, but a bucket does not show whether one invoice has a current promise, an unresolved dispute, a missing approval, or no recent follow-up. Treat bucket assumptions as broad planning rules, not proof of a receipt date.

Method 3: invoice-level evidence forecast

An invoice-level method starts with one row per open invoice. Preserve the customer, invoice number, invoice date, due date, open balance, report date, and source reference. Then add separate review fields:

  • current payment or approval evidence;
  • dispute, short-pay, credit, or data-quality status;
  • expected collection week;
  • evidence-quality label;
  • internal owner, next action, and review date.

Assign Week 1 through Week 4 only when current evidence supports the timing. Keep later, blocked, and unconfirmed invoices visible outside the weekly expected totals. This method takes more review than applying one percentage to an aging bucket, but it produces the decision layer a small finance team needs: what may arrive, why, what could change it, and who owns the next check.

Choose the method from the decision

Use the following routing rule:

  1. If the decision is an ending balance, start with a balance forecast.
  2. If only summarized aging is available, use a labeled aging-based assumption and expose its limitations.
  3. If the decision is near-term cash timing and invoice-level data exists, use an invoice-level evidence forecast.
  4. If management needs both balance and cash timing, keep the two models linked but separate. Do not force one output to answer both questions.

The balance-versus-collections comparison explains that boundary in more detail. The four-week AR forecast template provides fields for source facts, evidence, assumptions, owners, and later outcomes.

For the specific aggregate-method choice, the invoice-level forecast vs. DSO comparison shows how to separate near-term issued-invoice evidence from longer-horizon driver assumptions.

Translate common forecast searches into a method choice

Terms such as *forecast accounts receivable*, *project accounts receivable*, and *forecast collections* can describe different outputs. Before selecting a model, rewrite the request as a decision: ending A/R balance, expected receipts by week, or invoice actions requiring review. If the answer must name which current invoices may pay within four weeks, use invoice-level evidence. If the answer is a longer-range balance or scenario, use a roll-forward or driver model and keep its assumptions separate from the short-term action queue.

After choosing the method, use the four-week forecast control total to reconcile every open dollar across the weekly, later, and unassigned states. Method choice should not create missing or duplicated receivables.

Keep method changes traceable

Record the method name, data snapshot, assumption source, reviewer, and review date. When actual receipts arrive, compare them with the locked forecast rather than rewriting the prior view. A method should become more useful through observed outcomes, not through silent hindsight edits.

AR Pulse uses an authorized QuickBooks receivables export to create a ranked cash-action list and a four-week collections forecast. It does not require QuickBooks credentials, contact customers, or promise payment outcomes. Finance owners who want an invoice-level decision layer can apply for AR Pulse.