Monday’s cash forecast closes Friday at EUR 10 thousand against a minimum buffer of EUR 50 thousand. The Credit Control team must secure another EUR 40 thousand this week.
The aging report appears to offer an obvious answer: call the customer owing EUR 95 thousand. But that invoice is disputed and no payment has been confirmed. Another customer owes EUR 50 thousand on an accepted invoice and normally pays on Thursday. The CFO must decide who to call first—and how much, if anything, can enter the cash forecast before the conversation produces evidence.
Cash is short, but the aging total is not a cash forecast
An accounts receivable aging report classifies open balances by due date. It identifies exposure, delinquency and potential collection problems. It does not prove that an amount will arrive this week. A disputed EUR 95 thousand invoice, an accepted EUR 50 thousand invoice and a current EUR 30 thousand invoice may all be legally open, yet they require different actions and support different cash assumptions.
| Measure | Amount | Meaning |
|---|---|---|
| Friday closing cash — current base forecast | 10 | Includes Customer D’s expected EUR 30k receipt once |
| Minimum available-cash buffer | 50 | Internal decision threshold |
| Additional cash required by Friday | 40 | Gap to close before further discretionary payment release |
| Total open receivables in the selected aging | 215 | Exposure, not automatically available cash |
The task is therefore narrower than “collect overdue debt.” Management needs a controlled answer to two linked questions: which intervention is most likely to improve cash this week, and which receipt is sufficiently supported to update the forecast?
How do you use an accounts receivable aging report to prioritise collections?
Use an accounts receivable aging report to prioritise collections by validating each open balance, then assessing days overdue, dispute status, payment history, customer payment cycle, existing promises and the evidence for a specific payment date. Rank the next action by urgency, collectability, cash relevance and controllability. Add a receipt to the cash forecast only when its amount and expected date are supported; keep open receivables, customer promises and confirmed bank receipts as distinct states.
- Validate the invoice-level open balance, due date, partial payments, credit notes and dispute status.
- Define the obstacle to payment and the next action capable of changing it.
- Obtain evidence for a specific amount and expected date before updating forecast cash.
- Match the promise to the bank receipt, investigate variance and update the customer assumption.
Days past due measure elapsed delinquency, not collection probability. A long-overdue invoice may demand escalation but contribute nothing to this week’s forecast. A less overdue, accepted invoice with a confirmed payment run may be the first call when the immediate objective is to close a short-term cash gap.
Start with the aging report, then add payment evidence
The following report is entirely synthetic and reflects the position on Monday morning. Amounts are EUR thousands.
| Customer | Open receivable | Aging | Available evidence | Required action |
|---|---|---|---|---|
| A | 95 | 45 days overdue | Open delivery dispute; payment not confirmed | Assign dispute resolution to the delivery owner |
| B | 50 | 12 days overdue | Invoice accepted; Thursday is the usual payment day, but inclusion in this run is unconfirmed | Request amount and date confirmation by Tuesday |
| C | 40 | 62 days overdue | Two missed promises to pay | Escalate under credit policy and demand a specific recovery plan |
| D | 30 | Not yet due | Friday payment confirmed and already included in the base forecast | Monitor bank receipt |
| Total | 215 | — | — | — |
The table contains four different states. A is a dispute-resolution case. B is a near-term confirmation opportunity. C is a broken-promise escalation. D is a monitoring item already represented in forecast cash. Treating all four as one collection queue would obscure both the action and the forecast consequence.
Rank the action separately from the forecast amount
| Priority | Customer | Why act now? | This week’s next action | Incremental forecast treatment |
|---|---|---|---|---|
| 1 | B — EUR 50k | Accepted invoice and established Thursday payment cycle can close the immediate gap | Credit Controller obtains written confirmation of amount, payment-run inclusion and value date by Tuesday | EUR 0 until confirmation; then confirmed expected amount in Thursday receipts |
| Parallel | A — EUR 95k | Largest exposure, but delivery dispute blocks normal collection | Delivery owner resolves evidence gap and agrees dispute path with customer | EUR 0 this week unless dispute and payment date are explicitly resolved |
| 2 | C — EUR 40k | Oldest overdue balance and two missed promises indicate elevated credit risk | Credit Manager escalates under policy and obtains a credible instalment or settlement plan | EUR 0 until a new evidenced promise meets forecast criteria |
| Monitor | D — EUR 30k | Current invoice with confirmed Friday payment | Track value date and match bank receipt | Already in base forecast; no incremental uplift |
B receives the first cash-gap call because the invoice is accepted, the required amount is within the open balance and the customer has a relevant payment cycle. A still requires immediate parallel attention because the exposure is material, but an unresolved delivery dispute makes a same-week cash assumption unsafe. C’s age and missed promises justify escalation, not optimistic forecast inclusion.
This distinction prevents two common errors: allocating collection effort solely by balance size, and filling the forecast with every item the team intends to chase. Action priority answers “where should we intervene?” Forecast eligibility answers “what receipt can the liquidity decision rely on?”
Trace Customer B from open invoice to expected receipt
Customer B’s open balance is not accepted at face value. The controller reconstructs it from invoice and settlement evidence before asking the customer to confirm payment.
| Evidence item | Reference | Amount | Control conclusion |
|---|---|---|---|
| Original invoice | INV-260221 | 60 | Valid invoice issued for accepted delivery |
| Partial payment received | BANK-260304 | (10) | Matched to invoice and cleared from open items |
| Credit notes | None | 0 | No approved reduction of the receivable |
| Unapplied cash | None | 0 | No unidentified receipt available for allocation |
| Confirmed open balance | INV-260221 | 50 | 60 − 10 − 0 = 50 |
| Contractual due date | Friday, 12 days before report date | — | Invoice is overdue |
| Customer’s usual payment day | Thursday | — | Behavioural evidence, not a promise |
| Promise requested | Amount and Thursday value date | 50 | Pending written confirmation |
The Credit Controller checks the customer subledger against the invoice, bank allocation, credit-note register and unapplied receipts. This prevents asking for EUR 60 thousand after a valid partial payment or forecasting EUR 50 thousand when an unprocessed credit note has reduced the claim.
On Tuesday, the customer may confirm the full EUR 50 thousand for Thursday, confirm only EUR 35 thousand, propose another date or fail to respond. Each answer changes the forecast differently. The telephone conversation should be recorded as a contact event; only the customer’s specific amount and date commitment support a promise-to-pay state.
Translate the confirmation into Friday cash
The base forecast already includes Customer D’s confirmed EUR 30 thousand receipt. It is not added again when evaluating Customer B.
| Cash line | Current base | B pays EUR 50k | B pays EUR 35k |
|---|---|---|---|
| Friday closing cash before Customer B | 10 | 10 | 10 |
| Customer D receipt | Included once | Included once | Included once |
| Incremental confirmed receipt from B | 0 | +50 | +35 |
| Friday closing cash | 10 | 60 | 45 |
| Minimum buffer | 50 | 50 | 50 |
| Headroom / (shortfall) | (40) | 10 | (5) |
If B confirms and pays EUR 50 thousand on Thursday, Friday cash reaches EUR 60 thousand and the company restores EUR 10 thousand of headroom. If B confirms and pays only EUR 35 thousand, cash reaches EUR 45 thousand and remains EUR 5 thousand below the buffer. The second scenario requires another collection, payment deferral or authorised liquidity action before discretionary cash is released.
The expected receipt is inserted in the same transaction-level schedule that feeds the 13-Week Cash Flow Forecast. That article identifies when and how much cash is missing; this collections prioritisation determines which invoice action may close the gap and under what evidence conditions.
A usual payment day is not a confirmed promise
The team knows that Customer B normally processes payments on Thursday. It therefore enters EUR 50 thousand into Thursday receipts and releases a supplier payment before speaking with the customer. The assumption feels data-driven, but one critical item is missing: confirmation that INV-260221 is included in the current payment run for a specified amount and value date.
| State | Evidence available | Forecast permission | Management wording |
|---|---|---|---|
| Unconfirmed expectation | Accepted invoice and historical Thursday cycle | Do not treat as committed cash; show as upside or pending confirmation | Customer B is a priority collection opportunity |
| Confirmed promise | Named invoice, amount, payment date and customer confirmation | Include as expected receipt with evidence reference and owner | Customer B confirmed EUR 50k for Thursday |
| Bank receipt | Value-dated bank transaction matched to INV-260221 | Replace forecast with actual cash | EUR 50k received and matched |
| Promise variance | Amount or date differs from confirmation | Reforecast immediately and reopen shortfall | Promise missed or partially fulfilled; escalation required |
Until confirmation, the controller marks the receipt pending customer confirmation, assigns Tuesday as the evidence deadline and prevents it from authorising dependent supplier payments. Historical behaviour informs the probability of collection; it does not create a customer commitment.
Validate both the receivable and the promise
| Control | Question | Failure response |
|---|---|---|
| Open-item integrity | Does invoice less matched payments and approved credit notes equal the open balance? | Correct the subledger before collection or forecasting |
| Invoice acceptance | Has the customer accepted the invoice and underlying delivery or service? | Route dispute to the accountable operational owner |
| Authority and specificity | Does the customer contact identify invoice, amount and value date? | Keep the receipt unconfirmed |
| Duplicate control | Is the same receipt already in the base forecast or another aggregation row? | Remove double counting |
| Bank matching | Did the promised amount arrive on the promised value date and clear the correct invoice? | Record actual, investigate variance and reforecast |
| Decision dependency | Would a supplier payment or other cash action rely on this receipt? | Require stronger confirmation or contingency |
A promise should retain the customer contact, timestamp, invoice reference, amount, expected value date, responsible collector and dependent cash decision. Subsequent edits must preserve the earlier state so management can distinguish a changed promise from an incorrect original forecast.
After Thursday, Treasury matches the bank movement by amount, payer, value date and reference. If EUR 35 thousand arrives against a EUR 50 thousand promise, the remaining EUR 15 thousand stays open, the promise is recorded as partially fulfilled and Friday cash is recalculated rather than reported as “collection completed.”
The CFO record connects the first call to the payment decision
| Decision element | Instruction |
|---|---|
| First call | Customer B regarding invoice INV-260221 and its confirmed EUR 50k open balance |
| Owner | Credit Controller |
| Confirmation deadline | Written amount and Thursday value date by 12:00 Tuesday |
| Forecast update | Insert only the confirmed amount in the 13-week forecast; retain evidence reference and mark as expected until bank receipt |
| Dependent payment rule | Do not release discretionary supplier cash on the basis of B’s habitual payment day alone |
| Escalation | Notify CFO immediately if confirmation is below EUR 40k, value date moves beyond Friday, or no confirmation is received by the deadline |
| Parallel actions | Delivery owner advances A’s dispute resolution; Credit Manager escalates C’s broken promises under policy; Treasury monitors D without double counting |
| Settlement control | Match B and D to bank actuals on value date and refresh Friday cash and remaining open items |
The threshold is decision-specific. B must contribute at least EUR 40 thousand to close the current cash gap if no other action changes. A EUR 35 thousand confirmation is valuable but insufficient; the CFO still needs EUR 5 thousand from another collection or an outflow decision. The forecast must make that residual visible.
Use one repeatable structure in the weekly receivables meeting
| Invoice | Payment obstacle | Next action | Confirmed amount and date | Cash effect |
|---|---|---|---|---|
| Customer / invoice reference / validated open amount | Dispute, approval, payment cycle, documentation, broken promise or no contact | Specific action, accountable owner and deadline | Separate unconfirmed expectation, confirmed promise and bank receipt | Forecast week, buffer impact and dependent decision |
The meeting should start with the cash need and material credit exceptions, not with a line-by-line recital of the aging. Review new receipts against promises, validate changed balances, rank actions, record evidence deadlines, update the cash forecast and escalate dependencies before releasing payments.
Monitor more than total collections. Track promise kept rate by amount and count, timing variance, partial-payment variance, dispute resolution time, overdue migration, concentration, forecast accuracy and the proportion of expected receipts supported by explicit confirmation. These measures reveal whether the team is merely making calls or improving controlled cash predictability.
The operating distinction remains decisive: an open receivable is a claim, a confirmed promise is an evidenced expectation, and a bank receipt is cash. Collections prioritisation becomes decision-useful when the workflow preserves all three states and connects each action to its liquidity consequence.
