What a Monthly Cash Bridge Should Explain in a Founder Cash Review

April 24, 2026 · 8 min read

A monthly cash bridge should not only explain where cash went.

It should explain what the cash movement means.

That is the point.

A founder cash review does not need a long list of every inflow and outflow. It needs a clear read on how opening cash became closing cash, what moved differently from plan, and what that movement changes about the next few months.

The bridge is useful when it helps the team answer one practical question:

What should we change because of what cash did this month?

Who this is for

This article is for founders, CFOs, and finance leads who already review cash every month, but still feel one of these problems:

• the team reports cash movement, but does not explain what it means
• the month-end balance is clear, but the reason behind it is not
• forecast misses are discussed, but not tied back to actual cash movement
• finance spends time preparing the bridge, but founder decisions do not change
• the review becomes a list of inflows and outflows instead of a management discussion

If that sounds familiar, the issue is usually not that the cash bridge is useless.

The issue is that it is being used too narrowly.

What a monthly cash bridge is for

A monthly cash bridge explains how cash moved from the beginning of the month to the end of the month.

In simple terms, it answers:

• what cash came in
• what cash went out
• what was expected
• what was different
• what was timing-related
• what was one-off
• what should change in the next forecast

That sounds basic.

But it matters.

Without this bridge, a founder may see the closing balance and miss the real story. Cash may be higher because collections improved. Or because a payment slipped. Or because investment was delayed. Or because cash was pulled forward from the next period.

Those situations can produce the same ending balance.

They do not mean the same thing.

The purpose is not reporting. It is interpretation.

The purpose of a monthly cash bridge is not to make the cash report look complete.

It is to make cash movement harder to misuse.

A weak bridge says:

Cash started here, moved by these amounts, and ended here.

A better bridge says:

Cash started here, moved this way, differed from plan for these reasons, and now changes how we should read the next few months.

That difference is important.

Founders do not need every transaction.

They need the explanation behind the movement.

The bridge should help separate:

• normal operating movement
• timing differences
• one-off inflows or outflows
• collection issues
• delayed payments
• spend that is becoming more fixed
• changes that should update forecast assumptions

That is when the bridge becomes useful.

Start with opening cash and closing cash

The first step is simple.

Fix the opening cash balance.

Fix the closing cash balance.

Then explain the difference.

At a high level, the cash movement can be grouped into a few major categories:

• operating cash inflows and outflows
• investing cash inflows and outflows
• financing cash inflows and outflows
• total cash movement

For a founder cash review, the exact format can be simple. What matters is that the bridge explains the material movement clearly enough for management to understand what happened.

A practical starting structure might include:

• customer collections and revenue-related inflows
• payroll and people costs
• vendor and contractor payments
• taxes, debt, and statutory payments
• capex or major one-off spend
• financing-related inflows and outflows
• timing items
• other material movements

The goal is not perfect classification on day one.

The goal is to make the movement explainable.

The bridge should answer “what created the change?”

The first useful question is not:

How much did cash move?

The better question is:

What created the change?

If cash finished better than expected, the review should ask:

• did collections improve?
• did a large customer pay early?
• did vendor payments move into next month?
• did hiring or investment slip?
• was spending actually reduced?
• did the forecast also improve?

If cash finished worse than expected, the review should ask:

• was revenue collection delayed?
• did payroll or contractor cost rise?
• did a large planned payment hit earlier?
• was the miss one-off or recurring?
• does the next forecast need to change?

This is the bridge doing its job.

It turns cash movement into management questions.

Compare the bridge with plan or forecast

Actual cash movement is not enough by itself.

The bridge becomes much more useful when it is compared with plan or forecast.

That comparison shows what changed between what the company expected and what actually happened.

This matters because a one-month variance can reveal several different things.

It may show that the cash forecast was built poorly.

It may show that a major assumption changed.

It may show that collections moved differently from expected.

It may show that a large payment shifted timing.

It may show that management is still using old assumptions that no longer fit reality.

That is why the variance matters.

A bridge without plan comparison explains the month.

A bridge with plan comparison explains whether the company is learning from the month.

Separate timing, one-off, and structural changes

This is one of the most important parts of the review.

Not every cash movement should be treated the same way.

A timing item is different from a structural change.

A one-off payment is different from a rising fixed cost base.

A delayed collection is different from a permanently weaker collection pattern.

A planned investment is different from uncontrolled spend.

If the team does not separate these, the forecast will become noisy.

For example, if cash looks better because a vendor payment moved into next month, that should not be treated as improved cash safety.

If cash looks worse because a planned investment happened on time, that may not be a problem.

If cash looks worse because collections are repeatedly slipping, that is more serious.

The bridge should help identify which movements should change the future view.

The bridge should feed the updated forecast

A monthly cash bridge should not sit beside the forecast.

It should feed the forecast.

If the bridge shows that collections are slower, the forecast should reflect that.

If it shows that a payment moved into next month, the next forecast should include that pressure.

If it shows that fixed costs have increased, the downside case should become more realistic.

If it shows that a one-off item created a better balance, management should avoid treating that as recurring strength.

This is where many reviews get weak.

The team explains what happened, but the next forecast barely changes.

That means the bridge did not become management learning.

A useful founder cash review should move from:

cash balance → cash movement → variance → cause → forecast impact → decision

That is the sequence.

Without the forecast impact, the bridge is only reporting.

What finance should prepare

Finance should own the bridge.

That does not mean finance owns all of the meaning.

Finance should prepare the numbers, reconcile the movement, and identify the material differences from plan.

At minimum, finance should bring:

• opening cash
• closing cash
• major inflows
• major outflows
• plan or forecast variance
• timing items
• one-off items
• upcoming obligations
• updated forecast assumptions
• fixed versus flexible spend signals

Finance should also make the bridge easy to compare month to month.

The format matters here.

A consistent format is better than a perfect one that changes every month. If categories keep moving, the review becomes harder to follow and harder to compare. A fixed format also makes it easier for the person explaining the bridge to spot differences from prior months.

In practice, this may mean using a simple workbook, a fixed cash movement template, or a standard export from the accounting system.

The tool is less important than the habit.

The key is consistency.

What founders should focus on

Founders do not need to inspect every line.

They should focus on the movement that changes judgment.

The founder’s questions should be:

• did cash move differently from plan?
• why did it move differently?
• is the difference temporary or structural?
• does this change cash safety?
• does this change spending direction?
• does this reduce downside control?
• what should change before the next review?

That is the right level.

A founder cash review should not become a transaction review.

It should become a decision review.

Where other teams should be involved

Cash movement often needs context from outside finance.

Finance can show that collections were delayed.

Sales or customer success may need to explain why.

Finance can show that vendor spend rose.

Operations may need to explain whether it was planned, temporary, or recurring.

Finance can show that payroll or contractor cost increased.

People, hiring, product, or engineering may need to explain the reason.

The goal is not to invite every department into a long finance meeting.

The goal is to get the cause of material cash movement right.

A simple operating rule works well:

Finance prepares the bridge. Founder reviews the decision points. Other teams explain only the material movements that need business context.

That keeps the review useful without making it heavy.

The most common failure: too much detail, not enough meaning

A monthly cash bridge can fail by becoming too detailed.

That sounds strange, but it happens often.

The bridge becomes a long list of inflows and outflows. The team explains every movement. The meeting is full of accurate detail. But by the end, nobody has clearly answered what should change.

That is not a good founder cash review.

The bridge should not try to show everything with equal weight.

It should highlight the movements that changed the cash read.

The most useful bridge answers:

• what was materially different from plan?
• why was it different?
• does it repeat?
• does it affect forecast?
• does it change a decision?

If the bridge does not answer those questions, it may be accurate but still not useful.

The practical difficulty: building the bridge can be harder than it looks

There is also a very practical problem.

Building a cash bridge can be time-consuming.

It is similar to building a cash flow view using the direct method: actual cash movements have to be gathered, classified, and explained. That sounds simple until the company has many bank accounts, multiple currencies, intercompany movements, and unclear payment descriptions.

Even deciding whether a payment is an operating expense, inventory-related payment, contractor cost, tax payment, or financing movement can take time.

This is one of the quiet reasons cash bridge reviews fail.

The problem is not that founders dislike the idea.

The problem is that the actual update work can become heavy.

For companies with several accounts or foreign currency balances, the bridge may need to be prepared by account as well as in total. In stressed cash environments, knowing that the company has enough cash overall may not be enough. The team may need to know whether a specific account, currency, or entity will be short next week.

That is why the bridge should start simple, but not pretend the work is always easy.

A good process respects the workload.

How simple should the bridge be for a small team?

For a small team, the first version should be simple enough to keep using.

A good minimum version has five parts:

1. opening cash
2. major inflows
3. major outflows
4. closing cash
5. what changed in the next forecast

That is enough to create a useful monthly review.

The categories can also stay simple at first:

• customer collections
• financing inflows
• payroll
• vendors and contractors
• tax and debt
• one-off items
• other material movement

A small team should avoid building a perfect finance pack that nobody can maintain.

The review should be good enough to answer:

What moved cash, what was temporary, and what should change next month?

If it can answer that, it is useful.

When to review it

For most companies, the monthly cash bridge should be reviewed after month-end close, once actual cash movement is known.

It should happen before the forecast is finalized.

That order matters.

If the forecast is updated before the bridge is reviewed, the team may miss the meaning of actual cash movement.

A practical monthly rhythm is:

• close the month
• confirm opening and closing cash
• build the cash bridge
• compare with plan or forecast
• identify timing, one-off, and structural movements
• update the cash forecast
• decide what changes

This should usually happen before a founder monthly review, board update, or stakeholder update.

The bridge should shape the message, not sit behind it.

When monthly is not enough

Monthly review is the normal rhythm.

But it is not always enough.

If cash safety is weak, the view needs to zoom in.

A company may start with an annual cash view.

Then pressure increases, and the discussion becomes monthly.

Then weekly.

Then daily.

That is not theoretical.

When cash is tight, the real question can become:

How do we get through the payments due in the next few days?

At that point, a monthly bridge is too slow.

The company may need a weekly cash watch or even a daily cash forecast by account. That can feel excessive when the business is healthy, but it becomes necessary when the timing of specific payments matters.

The goal is not to live in daily cash management forever.

The goal is to avoid getting forced into it too late.

What a good bridge changes

The value of a monthly cash bridge is not that it explains the past.

The value is that it changes the next decision.

A good bridge might lead the company to:

• update collection assumptions
• change payment timing controls
• delay a hire
• reduce lower-return spend
• re-check a large vendor commitment
• adjust the next forecast
• explain cash movement differently in a board or stakeholder update

If nothing changes after the review, the bridge may not be doing enough.

The best question to end with is:

What should change next month because of this bridge?

That one question keeps the review practical.

How to explain this internally

A clear internal explanation could sound like this:

The cash bridge is not just a record of cash in and cash out. It explains what moved cash, why it moved, whether the movement is temporary or structural, and what the updated forecast or next decision should change as a result.

That explanation keeps the review focused.

It also prevents the bridge from becoming either too shallow or too detailed.

The goal is not more reporting.

The goal is a better cash read.

What to check next

If you want the broader monthly review structure, read:

What a good monthly cash review should actually look like

That article explains the full monthly review habit.

This article is narrower.

It focuses on what the monthly cash bridge should explain inside a founder cash review.

Where RunwayDigest fits

RunwayDigest takes your inputs, processes them, and returns a structured runway, burn, and cash direction report by email.

The goal is not to replace judgment.

It is to make the current cash read clearer, faster, and easier to act on.

The free version is monthly free use.

Once per month per email.

It returns a simplified text report by email.

The paid version adds updated inputs during the month, updated reports by email, compare input cases, monthly reminder, and stakeholder update draft.

← Back to Insights