How to structure a 13-week cash flow forecast
Most conversations about 13-week cash flow forecasting focus on what goes into the model. Fewer people talk about how to structure a 13 week cashflow forecast itself.
That matters more than you might think. The right structure depends on how your business is set up, and getting it wrong creates either unnecessary complexity or dangerous blind spots. In my experience, there are three structures I see used in practice.
Structure 1: single entity
If your business operates through one legal entity, this is the straightforward case. All of the cash flows live in one place, and one person can build and maintain the entire forecast.
That person is typically the finance manager, CFO, or someone in FP&A. But even in a single entity business, building the forecast isn't a solo job. The finance team still needs inputs from other parts of the business: HR for employee costs and headcount plans, supply chain or operations for purchasing schedules and production planning, sales for expected order flow.
The model itself can cover the whole business in one view. Opening cash, weekly inflows, weekly outflows, closing balance. Clean and manageable.
Structure 2: multi-entity, centralised
When a business is made up of multiple entities, the forecast needs to account for each one individually and then roll them up into a group view. Otherwise you risk missing entity-level cash gaps that don't show up at the consolidated level.
In some multi-entity businesses, this is still done centrally by one person or a small central finance team. This works when the financial data for all entities is accessible in one place, whether that's through a shared ERP system, a group accounting platform, or simply because the entities are small enough that a central finance manager can pull the numbers without needing local input.
The central finance team builds individual entity forecasts and consolidates them into a group model. One important detail here: intercompany cash movements (transfers between entities within the group) need to be handled carefully in the consolidation. They should net to zero at the group level, otherwise you're effectively double counting cash that's just moving between your own accounts.
The output is two things: the individual entity forecasts, which show each subsidiary's liquidity position, and the group forecast, which shows the consolidated picture.
How to structure a 13-week cash flow forecast for a multi-entity, decentralised group
The third structure is the most complex, and it's the one you'll typically see in larger businesses with entities spread across multiple countries or regions.
In this model, central finance doesn't have easy access to the raw data sitting in each entity. Local finance managers are closer to the numbers, and they're the ones who need to build the forecast for their piece of the business.
The process works like this. Central finance designs a standardised template and sends it out to the finance managers in each local entity. The template needs to be consistent across all entities — same structure, same line items, same weekly format — so that when the completed forecasts come back, they can actually be consolidated without a rebuild.
Local finance managers populate the template with their entity's cash flow forecast and return it to central finance. Central finance then aggregates everything into the group model.
Getting the template design right is critical in this structure. If each entity is using a slightly different format or labelling line items differently, consolidation becomes a manual, error-prone exercise. Standardisation upfront saves a significant amount of time every single week.
There's also a governance dimension. Someone needs to own each entity forecast, someone needs to own the consolidation, and someone needs to have authority over decisions like intercompany transfers when one entity is heading for a shortfall. Those roles should be defined before the process starts, not figured out mid-crisis.
Which structure is right for your business?
The honest answer is that your business structure largely dictates it.
Single entity: one model, one owner, done.
Multi-entity with accessible centralised data: centralised structure, one person consolidates.
Multi-entity with local data ownership or geographic spread: decentralised structure with standardised templates.
The thing I'd add from experience is that businesses sometimes default to the decentralised model because it sounds more rigorous, when actually a centralised approach would work fine. Decentralised forecasting introduces coordination overhead, version control challenges, and dependency on local finance managers hitting their deadlines. If you can avoid it, do.
What you can't avoid is making sure the structure you choose gives you proper visibility at the entity level as well as the group level. A group 13WCF that only shows the consolidated number can mask serious liquidity problems sitting inside individual subsidiaries. You need both views.
At 13WEEKS, getting the structure right is always the first conversation. The model is only as useful as the process behind it.
If you're not sure which structure fits your business, or if you've got a multi-entity group and the current forecasting process isn't giving you the visibility you need, I'm happy to have a conversation. Grab my free 13-week cash flow forecast template to get started, or get in touch directly.
Comments