Multi-Entity Runway: Why One Consolidated Burn Rate Hides the Real Picture

Executive summary

• A consolidated runway number can be mathematically correct while hiding an entity with only a few months of cash left.
• Group cash and group burn are useful for the board headline, but they do not show where liquidity risk actually sits.
• Multi-currency groups need one consistent FX basis before entity runway can be compared meaningfully.
• A defensible view shows group runway and entity runway together, along with the funding assumptions behind both.

Fourteen months for the group, four months for the entity

The board deck says the group has fourteen months of runway. The number is correct: consolidated cash divided by consolidated monthly burn produces fourteen months.

But the UAE entity holds most of the cash, while the KSA entity has only four months left at its current burn rate. The KSA business is hiring, paying local suppliers, and funding payroll from its own bank accounts. Unless the group plans to move cash across entities, the headline runway does not describe the risk facing that operation.

That is the problem with multi-entity runway. A blended number can be true and misleading at the same time. It answers how long the group could survive in aggregate, but not whether each legal entity can fund its own obligations as they fall due.

Why consolidated burn rate becomes the default

The blended calculation is attractive because it is simple. Finance takes total available cash across the group, divides it by total monthly net burn, and produces one number for the board pack.

For a single entity, that can be a useful shorthand. In a group, it assumes cash can move freely between entities, in the required currency, at the required time, with the right approvals and documentation. Those assumptions are often left unstated.

One entity may be cash-rich because it collected customer balances early. Another may be burning faster because it is funding expansion, hiring, or local setup costs. A third may have cash that is restricted, committed to tax, or operationally unavailable to the rest of the group.

The consolidated number smooths those differences into one average. It shows the total capacity of the group, but it does not show which entity will need support first.

A worked example: one group number, three different risks

Consider a simplified group with three entities:

The board headline is ten months of runway. Yet two entities face a funding decision within four months.

The group figure becomes defensible only when finance can explain what happens next. Will the UAE entity fund KSA and Qatar? Are those transfers legally and operationally possible? Have intercompany loans been approved and documented? Does the cash forecast include transfer timing, FX conversion, bank cutoffs, and repayment expectations?

Without those answers, the group runway is not wrong. It is incomplete.

This is also why cash flow forecasting and cash flow management should not be treated as the same workflow. Forecasting estimates when each entity will need cash. Management determines what action the group will take when that need appears.

Multi-currency runway needs one measurement basis

GCC groups often plan and report across AED, SAR, USD, and sometimes QAR or other currencies. That creates a second problem: the runway can change depending on the FX basis used.

An entity may forecast local payroll and supplier spend in SAR, while group reporting converts the result into AED or USD. If one entity uses a budget rate, another uses the current spot rate, and the board pack uses a month-end accounting rate, entity burn rates are no longer comparable.

Finance should define one basis for the runway view. That may be a planning rate for the forecast period, with a separate sensitivity for material currency movement. The important point is consistency: cash and burn must be translated using an agreed method, and the rate assumption should be visible.

The same FX discipline also applies to multi-currency consolidation in the GCC, because consolidated actuals, forecasts, and runway reporting all depend on a controlled translation basis.

What a defensible runway view should show

A useful runway report should not force finance to choose between a group number and an entity breakdown. It should show both.

The group view remains useful for the board headline. It indicates the total cash capacity of the business under the assumption that liquidity can be allocated where needed.

The entity view shows where the actual pressure sits. It should include local available cash, monthly burn, committed payments, expected collections, and the point at which support is required. It should also make funding assumptions explicit: which entity will transfer cash, when, in what currency, and under what intercompany arrangement.

Finance should also separate current runway from supported runway. Current runway shows how long the entity can operate using its own available cash. Supported runway shows the position after approved group funding is included. That distinction prevents a proposed transfer from being treated as if it has already happened.

A post-accounting layer such as Kudwa can help by connecting bank balances, entity structures, forecast assumptions, currencies, and intercompany context into the same reporting view. It does not replace bank portals or treasury approvals; it gives finance a clearer way to see group capacity and local exposure together.

Runway is a group metric and an entity metric at the same time. Reporting only the consolidated number tells leadership how much cash exists in total. It does not show where the next funding problem will appear.

See runway at the group and entity level together with Kudwa’s cash flow management, or book a demo.

‍