Budget, Forecast, and the Thirteen Weeks That Actually Matter

Cash forecasting in a PE-backed multi-entity platform, and why the consolidated view is the one entity with no bank account.

A budget is a commitment. A forecast is a projection. A thirteen-week cash flow is a countdown.

Most finance teams treat these as three versions of the same document. They are not. They answer three different questions, they are read by three different people, and in a multi-entity platform only one of them tells you whether you can operate next month.

I have rebuilt this discipline at more than one portfolio company. The pattern is the same every time.

Three documents, three jobs

The budget is a commitment. It is set with the sponsor at the start of the year. It is the basis for the operating plan, often for management compensation, and sometimes for the covenant package. It is not supposed to move. That is the point of it. A budget revised every quarter is not a commitment. It is a running excuse.

The forecast re-underwrites the commitment. It says what the business will actually do given what has happened since. It is where you learn that the plan is short, and how short, while there is still time to act on it.

The thirteen-week cash flow is neither. It does not measure performance. It measures liquidity. It answers one question: on any given Friday over the next quarter, is there money in the account the obligation is drawn on.

Companies with a healthy P&L run out of cash. That is not a paradox. That is what happens when nobody owns the third document.

Why the standard rolling forecast breaks in a multi-entity structure

Consolidated cash is not available cash.

In a platform with multiple management companies and multiple operating entities, cash sits in specific legal entities, in specific accounts, under specific credit agreements. The consolidated balance sheet nets it into one line. The bank account does not.

A consolidated position can look comfortable while the entity carrying next week’s payroll holds a fraction of it. Moving the difference is not a journal entry. It is an intercompany funding transaction with an agreement behind it, a timing lag, and a documentation trail that has to survive an audit and a buyer’s counsel three years later.

That is what a generic rolling forecast template does not model. It forecasts the consolidated entity, which is the one entity in the structure with no bank account.

Build it by entity first

The order matters.

1.      Forecast receipts and disbursements at the entity level. Every entity that holds a bank account gets its own thirteen weeks.

2.      Layer intercompany funding as its own explicit line, in and out, with the counterparty named. It should net to zero across the platform. When it does not, you have found something worth finding.

3.      Consolidate last, and only for the summary page.

Build it the other way around and you get a number that is correct in total and useless in practice.

What goes in the lines

Receipts come off the aging, not the revenue forecast. Revenue recognition and cash collection are different events, separated by payer or client behavior, contract terms, and billing performance. If you model receipts as a percentage of forecast revenue, you have rebuilt the P&L under a different title. Model from what is billed, what is billable and unbilled, and how those specific payers have actually paid over the last two quarters.

Disbursements start with what is committed. Payroll on its actual dates, not a monthly average. A semi-monthly cycle puts three payrolls inside some months, and a forecast built on averages will miss the week that matters. Then debt service, rent, insurance, taxes, and anything under contract. Discretionary spend comes last, because it is the part you can still control and therefore the part the forecast exists to inform.

Two lines carry the most weight: the balance at the end of the tightest week, and the balance at the covenant test date. Everything else is supporting detail.

An descriptive example

The figures below are illustrative. They are not from any engagement.

A platform holds $4.2M in cash against $3.0M of obligations coming due in week three. On the consolidated view, that is comfortable.

It is not. The management company holds $0.4M and owes $2.1M in payroll. Operating entity A holds $2.9M and owes $0.3M. Operating entity B holds $0.6M and owes $0.2M. Holdings sits on $0.3M against $0.4M of debt service.

The money is real. It is in the wrong entity. The company that has to pay people in seventeen days is the one holding almost none of it.

The fix is a funding transfer from operating entity A. That requires an approval, a signatory on that entity, and an agreement that permits the transfer. If the agreement does not permit it, the fix is not a transfer. It is a call to the lender, and you want to be making that call in week one, not week three.

A consolidated forecast shows none of this. It shows $4.2M and a comfortable balance.

That version has no lists, no table, no image. Four sentences carry the four entities and the shortfall still lands, because the reader does the subtraction themselves on the payroll line.

The discipline is the deliverable

Same day every week. Same format every week. Delivered whether the news is good or not.

Each file carries the variance to the prior week’s forecast, with an explanation for every material line. That variance history is the asset.

A lender is not grading your forecasting accuracy. They know you will be wrong. They are grading whether you knew you were wrong before they did.

The week you skip because the number is ugly is the week you spend the credibility it took nine months to build.

What each reader is actually looking for

The lender reads liquidity and covenant headroom, and reads the variance file as evidence that the borrower has command of its own position.

The sponsor reads runway and the decision it forces. Not the cash number. The decision. Fund, slow the build, accelerate collections, or do nothing.

You read the tightest week, and then you go work on it.

Where the three documents reconnect

The budget sets the commitment. The rolling forecast re-underwrites it. The thirteen-week tells you whether you get to execute either one.

When the forecast says the year holds and the thirteen-week says week nine is tight, that is not a contradiction. That is the meeting.

Profitable and illiquid is a real state, and it is the one that closes companies.

Run all three. Know which question each one answers. And never let the person who owns the budget be the only person who owns the cash.

Georgeta Elena Precup, CPA, CGMA, MBA is a strategic CFO advisor and operating partner working with private equity sponsors and healthcare platforms. All Seasons Consulting.