In companies that invoice quarterly, the two months without collections are where liquidity thins out before anyone notices. The bank balance stays positive, the annual financial plan approved by the board points to a balanced year, and meanwhile the week in which exposure hits its lowest point passes unobserved. A 13-week cash flow forecast covers precisely that distance: the three months within which a decision can still change the outcome.
The twelve-month plan answers an obligation, cash answers a due date
The annual financial plan documents debt sustainability and feeds a document approved by the board. Long horizon, monthly granularity, demonstrative purpose.
The finance manager of a publicly owned utility put it in terms that work as a diagnosis. The twelve-month plan is required by regulation. The projection she uses every week covers three or four months. That spreadsheet was updated once a month, at the start of the following month, and comparing plan against actuals proved laborious. At that frequency the figure arrives after the decision has been taken. The same company invoices quarterly: in the two months without billing the liquidity line falls, and the fall is as regular as it is invisible on a monthly grid.
What does a 13-week cash flow forecast contain?
It is a weekly projection of collections and payments across the following three months, built on open invoices, recurring contractual commitments and period estimates.
Two things are worth separating before any talk of tools. The method is the weekly grid and the discipline of keeping it current: it can live on a spreadsheet, at the cost of manual work few finance offices sustain beyond two months. The platform exists to pull the data in by itself, from the banks and from the ERP. What follows is about the method; the features explain how it stays current.
In a 13-week cash flow forecast the category grid stays the same as day-to-day treasury, but the weekly step changes the question the figure answers. Seen month by month, an outflow concentrated on the 20th and an inflow expected on the 28th offset each other and disappear. Week by week both remain visible, and with them the week in which the account drops below the safety threshold.
Below thirteen weeks sits the daily view: opening balance and end-of-day exposure per account, with the option to move a payment date or the debit account and see the effect immediately. Above it sits the twelve-month monthly plan.
| Horizon | Question it answers | Who reads it |
|---|---|---|
| Daily | Which account goes into overdraft today and which payment should move | Treasury operations |
| 13 weeks | In which week liquidity bottoms out, and with what headroom | Finance director and CFO |
| Twelve months | Whether debt is sustainable, and on what terms | Board and lenders |
Forecasting a firm commitment before the invoice arrives
A budget line is entered in the matching category: when the invoice arrives the line fills up with the actual amount instead of being added on top of the estimate.
This is the most frequent doubt raised during evaluations, and it has a concrete origin. Anyone who has run cash on a spreadsheet has learned that a recurring estimate and the subsequent invoice produce two rows. Someone then has to remember to delete one. On a treasury platform the forecast line moves through three states that can be read at a glance: dashed while it remains budget, solid and light once an open invoice exists, solid and dark once the transaction has cleared the bank. Next to the amount sits a completion indicator showing how much of the estimate has already become a document.
The same mechanism opens the way to items without a regular invoicing cycle. In a publicly owned company, payment certificates arrive before the invoice and are settled within days. They enter the 13-week cash flow forecast on a historical average and fill up when the document materialises. Estimates start from a recurring amount, from the average of the last three, six or twelve months, or from the same month of the previous year with a variance applied.
When the purchase cycle runs late
The purchase cycle raises a timing problem. A supplier invoice not yet recorded in the accounts produces no due date, and the 13-week cash flow forecast stays incomplete for a reason that is not technical at all: the accounting office is behind. In a wine producer dealing with imports, self-billing and reverse charge, the administrative manager acknowledged it without circumlocution. Connecting to the tax portal recovers due dates without waiting for the bookkeeping entry. The trade-off is the loss of the accounting record returning into the ERP, and it deserves a deliberate decision.
Loans, leases and credit lines inside the 13-week cash flow forecast
Mortgages, leases, intercompany loans and rentals have certain dates and known amounts, and in most companies they live in a separate file that one person updates. Leaving them out of the 13-week cash flow forecast means working on a curve that ignores the most predictable outflows of all.
Across thirteen weeks each contract needs one piece of information: which instalment falls in which week, and how much it weighs. A dedicated loans module derives it from the amortisation schedules, which show principal, interest and outstanding capital month by month. For floating rates the margin and the Euribor index are set, with interest recalculated daily, so the instalment entering the forecast is the current one rather than the one in the original schedule. A company with a dozen active facilities and three credit lines obtains on one screen what previously required reconciling as many files, and the net financial position updates as the difference between treasury and total outstanding capital. Cross-checking the position towards the banking system remains possible through the Central Credit Register held by the Bank of Italy.
Alongside the book balance sits the available balance, which adds self-liquidating facilities and cash credit lines. The distance between the two numbers measures real room for manoeuvre, and monitoring by individual facility shows how much of each bank limit is already used. Salaries, contributions and tax payments enter with the same logic, as a fixed recurring commitment entered once.
A case: a purchasing consortium that always collected late
A purchasing consortium collects from its members and pays suppliers on short terms, within the month or at thirty days. On paper cash is balanced. In practice members pay by bank transfer and many arrive ten or fifteen days late. The pattern is regular enough to rule out an accident and variable enough to make manual estimates pointless.
The finance manager had already considered calculating average collection time member by member and had set the idea aside. With roughly fifteen hundred invoices issued in a year, keeping that figure current for every counterparty is work no office can carry.
In the 13-week cash flow forecast the average delay is calculated by the platform from each customer’s payment history and added to the natural invoice due date. A second curve then appears next to the one built on the ledger. Those two lines do not coincide, and the gap between them measures how optimistic the ledger-based view is. Management began scheduling payments against the prudent curve, keeping the ledger-based one as an upper bound.
Insight: the step change does not come from the volume of data loaded. It comes on the day the due date stops being used as a collection date, and the customer’s actual behaviour takes its place.
What to check before building a first 13-week cash flow forecast
- Which bank accounts feed the projection and how often they refresh: open banking connections return movements between one and four times a day depending on the institution. Credentials need renewing every six months.
- Whether purchase invoices arrive from the ERP or from the tax portal, and which of the two routes returns the accounting entry.
- Where the amortisation schedules for mortgages and leases live today, and who updates them when the index moves.
- Which fixed outflows have no underlying document and need entering as recurring commitments: salaries, contributions, tax payments, subscription fees.
- What average delay emerges from history for each individual customer, rather than as a company-wide average.
- In which weekly meeting the projection is read, and who brings it.
Questions that come up during evaluation
How long before a 13-week cash flow forecast becomes reliable?
Initial loading of a 13-week cash flow forecast typically takes two or three weeks, covering account connections, ledger import and category mapping. Reliability grows with the first comparison between plan and actuals, at the close of the following month. From then on estimates correct themselves against observed behaviour rather than expectations.
What can be exported for auditors and management control?
Data filtered by category or by individual bank exports to a spreadsheet, while dashboards and charts export to PDF for documentation attached to board papers. Payment instructions are generated in SEPA XML format.
How does a treasury platform sit alongside the ERP?
The ERP remains the system of record for accounting and for both the sales and purchase cycles. The treasury platform sits beside it, specialised in liquidity, projections and payments. Aesir is a Gold Partner of NTS Informatica for Business Experience, and with other business software the available connectors are used or new ones are built.
Let’s talk
The starting question about a 13-week cash flow forecast has little to do with the tool. It concerns which decision the company wants to be able to take four weeks in advance rather than in hindsight: postponing an investment, negotiating an extension, requesting an invoice advance before the bank reads it as an emergency. The usual starting point is a review of the cash spreadsheets already in use, which show clearly where the process breaks. On the wider structure of the process, the article on adequate organisational structures and treasury remains a useful reference, while the operational side is covered in the piece on the mistakes made when treasury lives in a spreadsheet.
Aesir Srl works with finance departments on building the first projection and on connecting banks, business software and the chart of accounts. The selected platforms process data in European data centres, holding certifications in the ISO/IEC 27001 family and requirements aligned with NIS2. These are the same standards applied to our own infrastructure, hosted in Tier IV data centres in the European Union with replication.
If you would like to explore the subject or assess the situation in your own company, you can fill in the form at the bottom of this page or write to support@aesir-tech.it: we will arrange a free consultation and start from your numbers.