Overdue invoice cash forecast: a two-week worksheet
Key facts
Check two totals. First, reconcile the overdue opening balance to the ledger. Then split that balance between expected receipts inside the forecast and balances carried beyond it. Keep disputes and unsupported dates visible in the carry-forward.
This guide is not legal advice and laws/rules may change; consult a qualified professional for personalized assistance. Use at your own risk.
Build the forecast from open invoice balances
- Freeze an as-of date and check applied payments and authorised credits. Use the remaining overdue amount in the invoice currency.
- Enter an expected receipt date and the evidence behind it, such as a confirmed payment run plus expected bank timing. Split a promised partial payment from the remainder. Record a next review date for the remainder or an unresolved dispute.
- Convert each foreign-currency amount into your reporting currency using a dated planning rate. Keep the invoice currency and rate alongside the converted value. Record actual cash from the bank as it comes in and explain any difference in timing or conversion.
Oracle’s cash forecasting documentation includes unpaid and partly paid invoice balances among forecast inputs. Use the accounts receivable aging audit if you need to reconcile the opening list first.
Work through a fictional overdue invoice book
A euro-reporting supplier has four overdue balances on Friday 6 November. Week 1 is 9–13 November and Week 2 is 16–20 November. For this exercise it uses EUR 1.16 per GBP 1 at the as-of date in both scenarios. GBP 5,000 therefore enters the worksheet as a planning value of EUR 5,800.
- INV-107: EUR 7,500 with a confirmed run and expected Week 1 receipt. In the downside scenario, the receipt slips to Week 2.
- INV-112: The buyer confirms GBP 5,000 is included in its scheduled run, with bank timing that puts the expected receipt in Week 2. In the downside scenario, a missed run pushes it beyond Week 2.
- INV-119: EUR 4,200 in dispute with no confirmed receipt date. It stays in the outstanding balance in both scenarios.
- INV-124: EUR 3,500 open, including EUR 2,000 promised for Week 2. Carry forward the unconfirmed EUR 1,500 in both scenarios.
Both scenarios start with EUR 21,000 at the same planning rates. The base case expects EUR 15,300 in two weeks, leaving EUR 5,700. The downside expects EUR 9,500, leaving EUR 11,500. Each receipt appears in one bucket; a delayed receipt moves between buckets.
Copy the two-week scenario table
| Line | Base | Downside |
|---|---|---|
| Opening overdue | 21,000 | 21,000 |
| Week 1 receipts | 7,500 | 0 |
| Week 2 receipts | 7,800 | 9,500 |
| Still open | 5,700 | 11,500 |
Keep a separate source row for each invoice or partial receipt with the currency, balance, planning rate, evidence, expected week, owner and review date. The projected receipts are planning assumptions. Replace them with cleared amounts you can match to the invoices, then rebuild the remaining schedule from the open ledger. Review an unconfirmed date with the buyer before relying on it.
For an overdue and undisputed invoice that stays unpaid after follow-up, see the options for an unpaid B2B invoice.


.webp)