Use one exact collection date only when the evidence is actually date-specific. Otherwise assign a bounded week range or leave timing unassigned. An invoice due date, aging bucket, or habitual customer pattern can inform judgment, but none automatically proves the day cash will arrive. A range makes that uncertainty visible without discarding the invoice from the action plan.
Match precision to evidence
Oracle's promise-to-pay workflow records a committed date, amount, status, and linked transactions. That is stronger date evidence than an invoice merely being overdue. Microsoft describes cash-flow forecasting as a configurable process drawing on multiple inputs. Together they support a practical rule: the forecast representation should be no more precise than the underlying evidence.
An exact day may be reasonable when a current written commitment names the date and amount, an initiated payment has a documented settlement window, or another verified workflow event creates a specific timing point. Even then, keep the assumption distinct from observed cash.
A week range is more honest when the customer has acknowledged the invoice but not committed to a date, approval is expected within a bounded interval, or historical behavior is relevant but not decisive. Leave timing unassigned when the invoice is disputed, undelivered, linked to the wrong payer, or missing a current owner.
Use a simple decision framework
For each invoice ask:
- Is the open amount reconciled to the source?
- Is there current evidence of payer acceptance?
- Does the evidence name a date or only a stage?
- What event could invalidate the assumption?
- Who will review it and when?
Record the earliest supported week, latest supported week, included amount, reason code, and evidence date. The invoice collection assumptions template provides a durable row structure. Use confidence labels to describe evidence quality rather than disguising a range as a probability claim.
Avoid common false precision
Do not copy the due date into expected collection date by default. The due date versus expected collection date guide separates the contractual date from the forecast assumption. Do not place every uncertain invoice in week four merely to keep it inside the model. Do not shift a missed date forward without recording the broken assumption.
At the weekly review, replace assumptions with observed payment and deposit facts when available. Compare the previous range with actual receipts, then update the reason rather than only changing the date. This creates evidence for later calibration without pretending that one invoice proves a general rule.
AR Pulse analyzes an authorized QuickBooks receivables export and produces a ranked action list with a four-week collections range. It does not promise exact payment dates or assure a cash outcome. View the example report to see how bounded timing supports decisions.