An invoice collection assumption should record the expected week, the evidence supporting that week, the confidence in the evidence, the blocker or condition, the internal owner, and the next review date. Keep those fields separate from the invoice amount and due date. That separation makes the forecast reviewable instead of turning a planning judgment into an apparent accounting fact.
The starting data can come from an invoice-level aging report. Intuit's QuickBooks guidance explains that the A/R Aging Detail report shows customers' individual past-due transactions. The collection-assumption fields belong in a working analysis layer, not as silent edits to that source report.
The minimum assumption fields
Create one working row per open invoice and add these columns:
- Expected collection week: Week 1, Week 2, Week 3, Week 4, later, or unconfirmed
- Evidence type: promise, approval, historical pattern, dispute status, or no current evidence
- Evidence detail: the specific fact a reviewer can verify
- Evidence date: when the supporting fact was observed
- Confidence: supported, conditional, or unconfirmed
- Blocker or condition: what must happen before payment is plausible
- Internal owner: the person responsible for the next internal action
- Next action: the smallest concrete step that could clarify or change timing
- Review date: when the assumption must be checked again
Also preserve the source-row identifier, customer, invoice number, due date, and open balance so the assumption remains traceable.
A simple confidence framework
Use labels that describe evidence quality rather than promising an outcome.
Supported means recent and specific evidence points to the assigned week. A dated payment commitment or completed approval may qualify, but the label still does not guarantee receipt.
Conditional means the assigned week depends on a named event. Examples include approval of work, resolution of a billing discrepancy, a purchase-order correction, or confirmation from the customer's accounts-payable process.
Unconfirmed means the invoice is open but current evidence does not support a collection week. Do not hide these rows. Their absence from a weekly total is itself a management signal.
Rules that keep the template honest
- Never use the contractual due date as the only evidence for an overdue invoice.
- Never carry a missed promise forward without noting that it was missed.
- Never assign a probability merely to make the total look more precise.
- Never remove a disputed or blocked invoice from view; separate it from unblocked expected cash.
- Never overwrite a source fact with a forecast assumption.
- Never leave a material exception without an internal owner and review date.
These rules make uncertainty visible instead of pretending it has been eliminated. For disputed balances, use the disputed-invoice forecast framework to separate the ledger amount, disputed portion, evidence, owner, and supported timing.
Review the template as a decision queue
At the weekly review, begin with assumptions whose evidence changed: new commitments, missed dates, resolved approvals, new disputes, partial receipts, or unexplained silence. Then check concentration: several individually reasonable assumptions may create a fragile weekly total when they depend on one customer.
Compare actual receipts with the prior assigned week. Mark whether the invoice collected as expected, earlier, later, or remains open. Record the reason for a change so the team can improve its evidence rules without inventing a benchmark from a small sample.
Example without invented numbers
An invoice can be labeled Week 2, conditional, because customer approval is expected before a named review date. The next action is assigned to the internal account owner to verify approval status. If approval is not confirmed, the row returns to unconfirmed rather than rolling forward automatically.
AR Pulse's aging-versus-forecast guide explains why overdue age and expected cash timing are different decisions. AR Pulse uses explicit, reviewable assumptions to turn a customer-provided QuickBooks export into a four-week collections forecast and ranked action list; the forecast is not a promise of an outcome.
Include current invoices that can affect the four-week window even before they become overdue, while keeping due date and expected date separate. At each review, apply the stale-evidence test so an expired note or missed condition returns to conditional, unconfirmed, or blocked instead of rolling forward automatically.
Treat a sent or viewed event as delivery evidence, not a cash date. The invoice-viewed status framework connects status changes to the next review action without converting a platform event into a payment promise.