Evaluation method
What Happens to Cash When a Customer Pays Late?
Moving a receipt by fourteen days changes cash timing, not necessarily revenue. This walkthrough explains a bounded scenario on a 13-week forecast. It is a sensitivity exercise, not a prediction that a customer will pay late.
Keep an unchanged baseline
Record the opening cash, Monday start, currency, forecast window and expected receipt source row. Keep the original schedule and approved profile revision so you can compare the same forecast before and after one changed assumption.
A baseline is not a bank-confirmed outcome. Label expected receipts and known payments according to their source. Changes in payment probability and changes in payment date are separate assumptions.
Inspect an actual one-receipt sensitivity run
In the public synthetic pack, only receipt-1 was moved from 3 November to 17 November 2026. All amounts and other dates stayed unchanged. The same source-bound application service ran the revised CSV against the unchanged opening control. No language model or customer data was involved.
The minimum baseline balance fell from PLN 24000.00 to PLN 12000.00 while week-13 closing cash stayed PLN 88000.00. This demonstrates why an unchanged final balance can hide a temporary shortage. It is distinct from the pack’s combined cautious scenario.
| Measure, PLN | Original | One receipt delayed 14 days |
|---|---|---|
| Minimum weekly balance | 24000.00 | 12000.00 |
| Closing cash, week 13 | 88000.00 | 88000.00 |
| Minimum cash threshold | 20000.00 | 20000.00 |
Move the selected receipt exactly once
Remove the receipt from its original week and place it in the delayed week. Adding it to the new week without removing the old value creates cash that does not exist. Retain the same source identifier in the audit trail.
In Braio’s dedicated cautious scenario, the approved receipt-delay setting applies to the scoped receipts rather than selecting an arbitrary individual customer. To test a single receipt in a separate workbook, create a clearly labelled scenario source revision. Do not claim the global setting edits only one invoice.
Check boundaries and overdue treatment
A delayed receipt can leave the 13-week window. Do not force it into the last week to keep total receipts unchanged. Show the out-of-window exclusion and distinguish it from a missing row. An overdue opening item also needs explicit treatment, such as week one or exclusion with a warning.
After the change, recalculate every affected weekly balance. The lowest balance, first week below the approved floor and closing cash can change differently. Do not reduce the scenario to one final balance.
| Check | Expected behaviour |
|---|---|
| Original week | Receipt removed once |
| Delayed week | Receipt included once if inside the horizon |
| Beyond week 13 | Excluded with an explicit reason |
| Threshold comparison | Use the same approved minimum cash |
| Other changes | Keep baseline assumptions fixed |
Do not bundle unrelated assumptions silently
Receipt reduction and payment increase are additional stress settings. If you change them with the delay, the difference is a combined cautious scenario, not the isolated impact of a late payment. Show each setting beside the result.
A minimum-cash breach is a signal for a human review. The workflow does not decide to borrow, move money, defer payments or contact a customer. Those decisions need business context and authority.
Run and review the source-bound scenario
Use the synthetic template and inspect its profile assumptions, canonical weekly output and XLSX/DOCX. Then prepare a new scenario deliberately rather than editing a reported total. The downloadable output is a snapshot; a new calculation requires a new run or a separately verified workbook model.
Keep the comparison and unresolved data issues with the decision. This public page describes the method and an available workflow; it is not an interactive cash calculator.
Sources
Continue with your workflow
- How to Verify Numbers in an AI Financial Report
- Rolling Cash Flow vs Monthly Budget: Choose the Right View
- Financial Data Quality Checks Before AI Analysis
- 13-Week Cash Flow Template and Verifiable Example | Braio
- Braio help - first workflow, QA and SEO/GEO reports
- AI agent security - access, approvals and costs | Braio

