13-Week Accounts Receivable Cash Collection Forecast

Published By California Recoveries Editorial

The short answer: a 13-week accounts receivable cash forecast converts open invoices into expected weekly cash receipts. It starts with a reconciled aging report, assigns each invoice to a realistic collection week, adjusts uncertain items using documented evidence, and compares the forecast with actual receipts every week.

An aging report answers how old is the balance? A cash collection forecast answers a different operating question: when is cash likely to reach the bank? The distinction matters. A current invoice due on Friday may not arrive until the following week, while an older invoice with a confirmed payment reference may arrive tomorrow.

The 13-week horizon is short enough for account-level evidence to matter and long enough to reveal a future cash gap. It is not a promise, valuation, or substitute for an organization-wide cash flow forecast. It is a disciplined estimate of receipts from customer invoices.

Download the working structure: use the header-only 13-week AR cash forecast CSV. It contains no customer data, formulas, macros, or hidden assumptions.

What belongs in the forecast?

Begin with customer invoices that remain open as of one documented cutoff date. California's State Administrative Manual describes monthly aging, reconciliation of subsidiary records to control totals, reconciliation of cash receipts, and review of ongoing collection activity. Those controls are a useful foundation even for a private business: a forecast built on unreconciled balances will produce precise-looking but unreliable totals.

IncludeHandle separatelyExclude
Valid open invoicesGenuine disputesPaid invoices not yet cleared from the report
Approved payment plansUnapplied cashDuplicate or canceled invoices
Confirmed partial paymentsPending credits and returnsBalances already written off under policy
Documented customer promisesBankruptcy or legal mattersAmounts unsupported by the contract or ledger

Do not bury disputed or legally sensitive balances inside an ordinary collection assumption. Keep them visible, but use a separate status and obtain qualified advice where necessary.

Build the 13-week forecast step by step

1. Set a cutoff date and week boundaries

Choose the date and time when the open-invoice file was captured. Define Week 1 through Week 13 using actual start and end dates. Consistent week boundaries prevent a Friday payment from moving between versions merely because someone interpreted “next week” differently.

2. Reconcile the starting population

Tie the open-invoice total to the customer subledger and accounts receivable control balance. Remove payments already received, post approved credits, and investigate duplicate or negative balances. Use the monthly reconciliation checklist before forecasting a material balance.

3. Add evidence fields, not just dates

For each invoice, record the due date, current status, last customer contact, promised payment date, dispute status, owner, and next action. A forecast date without its evidence is difficult to review. “Week 3 — customer emailed a remittance date on November 14” is stronger than “Week 3 — probably.”

4. Place each invoice in one expected receipt week

Use the best current evidence:

  1. Clearing evidence: a traceable electronic payment or reliable remittance notice may support the expected bank-receipt week.
  2. Written promise: map the promised payment date to a week and account for normal delivery or settlement time.
  3. Consistent payment behavior: where permitted by your data practices, use the customer's documented payment pattern rather than a general stereotype.
  4. Contractual due date: for a new or current invoice without better evidence, use the due date plus a clearly documented timing assumption.
  5. No reliable evidence: keep the invoice in an uncommitted or downside view instead of forcing it into the base forecast.

5. Assign a confidence category

Confidence should describe evidence quality, not how persuasive the collector feels. A simple policy can use three categories:

CategoryExample evidenceRecommended treatment
CommittedPayment initiated, remittance supplied, or approved plan installmentInclude in the base case and monitor until cleared
ExpectedCredible written promise or stable documented payment patternInclude in the base case with a stated assumption
UncertainNo response, unresolved dispute, missing document, or broken promisePlace in downside or uncommitted view

If your organization uses percentages, define them in a written policy and apply them consistently. Avoid presenting a subjective percentage as a scientific probability.

6. Create base, upside, and downside views

A single number hides uncertainty. Use three transparent views:

  • Base: receipts supported by current evidence and ordinary operating assumptions.
  • Downside: remove or delay uncertain receipts and broken promises.
  • Upside: include plausible early receipts or resolution of specific issues, clearly labeled as contingent.

The difference between the views is a decision range, not an error. Management can compare that range with payroll, supplier, tax, or debt-service needs in the broader cash plan.

A worked example

Assume a business has four open invoices at the Monday cutoff:

InvoiceOpen amountEvidenceBase week
A-104$8,000Customer sent remittance noticeWeek 1
B-219$12,000Written promise for next FridayWeek 2
C-087$6,500Pricing dispute awaiting approved creditUncommitted
D-310$4,000Installment plan: $1,000 per weekWeeks 1–4

The Week 1 base forecast is $9,000: the $8,000 remittance plus the first $1,000 installment. Week 2 is $13,000. The disputed $6,500 does not enter the base case until the valid net amount and timing are established. Its owner and next action remain visible so “excluded” does not become “ignored.”

Run the weekly forecast meeting

A useful review can be completed in 30 minutes when the file is prepared:

  1. Record actual receipts for the week that just ended.
  2. Calculate the variance between forecast and actual receipts.
  3. Explain material misses by reason: timing, dispute, broken promise, posting error, credit, or forecast error.
  4. Move the 12 remaining weeks forward and add a new Week 13.
  5. Review every material uncommitted invoice and every past-due next action.
  6. Assign an owner and date to each forecast-changing task.

The FDIC and SBA Money Smart material treats cash flow management as a core small-business competency. The discipline here is not merely producing a spreadsheet; it is using the forecast to identify and solve timing problems before they become emergencies.

Measure forecast quality

Track forecast accuracy without punishing people for surfacing uncertainty. Two practical measures are:

  • Dollar variance: actual receipts minus forecast receipts for the week.
  • Absolute percentage error: the absolute forecast-to-actual difference divided by actual receipts, when actual receipts are not zero.

Also count the reasons for misses. If “invoice rejected for missing purchase-order number” repeats, fix billing setup. If “payment received but not posted” repeats, fix cash application. Forecast accuracy improves when the underlying process improves.

Common forecasting mistakes

  • Using the invoice due date as certainty. A due date is a contractual reference, not proof of receipt timing.
  • Forecasting the gross disputed amount. Resolve or separately model the valid amount.
  • Counting a payment twice. Reconcile bank receipts, remittance records, and the subledger.
  • Moving misses without explanation. Every rolled receipt should have a reason and a new evidence-based date.
  • Hiding the downside. Management needs to see cash risk early enough to act.
  • Mixing sales pipeline with receivables. Open invoices and unbilled opportunities have different evidence and should not be blended without clear labels.

What a dependable forecast produces

At the end of each review, the business should have weekly base, upside, and downside receipt totals; a reconciled list of invoices behind those totals; a variance explanation for the prior week; and a dated action for every material uncertainty. That output supports the broader cash flow projections recommended in SBA planning guidance while keeping the receivables assumptions visible and testable.

Use the CSV template to create the invoice-level schedule, then connect late or uncertain items to the accounts receivable collection process. Review the forecast every week; do not overwrite old versions, because prior forecasts are the evidence needed to improve the next one.

Editorial review

How this page was prepared

This guide answers a defined operational question, separates general process guidance from legal advice, and links to 3 relevant primary or authoritative sources for verification.

Examples are illustrative, not reported customer outcomes. Advertising does not control our conclusions. Read our editorial and correction standards.