Sightlines, Not Command Lines: Giving UK Group Boards Cash Visibility Without Central Control

At a recent group board meeting, a director asked a simple question: how much cash does the group have, and where is it? The answer arrived as a spreadsheet compiled four days earlier, with three entities still to confirm their balances. No one in the room was negligent. The finance team had worked diligently. Yet the board was making decisions on a partial, aged picture of its most liquid asset.

This is the treasury blind spot. It is rarely a failure of individual competence. It is a structural consequence of how UK groups grow, how banking relationships are inherited, and how reporting cycles fail to align across entities. Closing it does not require centralising every bank account or turning the group treasury function into a command centre. It requires a deliberate distinction between visibility and control, and a reporting architecture that respects both.

The blind spot is structural, not personal

UK groups are often built through acquisition. A parent company may have a single banking relationship, but its subsidiaries arrive with their own accounts, mandates, platforms and local finance teams. Treasury sees only what is reported to it, and what is reported is often aggregated, lagged and stripped of the detail that matters: which balances are committed, which are restricted, and which will move before the next board meeting.

The problem compounds when reporting calendars diverge. One subsidiary closes its books on the twenty-fifth of the month; another reports weekly; a third provides a quarterly summary. By the time the group finance function consolidates the position, the board is looking at a mosaic of different dates. In a period of volatile interest rates and tighter credit conditions, that lag is not merely inconvenient. It is a governance gap.

Visibility and control are different instruments

Visibility means knowing, with reasonable confidence and appropriate timeliness, what cash exists, where it sits, what it is committed to, and what constraints apply. Control means the ability to direct, sweep or transfer that cash. The two are frequently conflated, and the conflation causes unnecessary friction.

A group board does not need to control every subsidiary bank account in order to govern liquidity prudently. It needs assurance that subsidiary boards and their finance teams are managing cash within agreed parameters, and it needs early warning when those parameters are breached. Centralising control, by contrast, can damage local banking relationships, complicate regulatory compliance, and undermine the accountability of subsidiary directors who are expected to manage their own operations.

For UK groups, this distinction matters under the Companies Act 2006 and the duties set out in section 172. Each director owes duties to the company of which they are a director. A group oversight model that respects entity-level accountability while establishing clear reporting lines is more defensible than one that treats subsidiaries as branches.

A three-layer model for 2026

The alternative to centralisation is a reporting architecture built in three layers.

Layer one: a common entity-level cash standard. Every subsidiary reports against the same template at the same time each week. The template should capture bank balances by account, uncommitted cash, intercompany positions, near-term outflows, and any restrictions or covenants affecting availability. It should be concise enough to complete in under an hour and precise enough to compare across entities.

Layer two: group consolidation with exceptions. The group finance function consolidates the data and produces a short exception report. Most balances will be within expected ranges. The value lies in the outliers: an entity whose cash has fallen below its operating requirement, a significant variance from forecast, a new borrowing facility drawn without prior notification.

Layer three: escalation triggers and board reporting. Triggers are agreed in advance with subsidiary finance directors and reviewed annually. They might include liquidity headroom falling below a stated threshold, a variance from the thirteen-week forecast exceeding an agreed percentage, or any change to banking mandates. When a trigger is breached, the response is a conversation, not an automatic central intervention. The subsidiary explains the position; the group treasury function assesses whether group-level action is required; the board is informed if the matter is material.

Designing escalation triggers that subsidiaries will accept

Triggers fail when they are imposed rather than agreed. A subsidiary finance director who has not been consulted on a threshold will treat it as an intrusion and will find ways to report around it. A trigger that has been discussed and calibrated to the entity's operating reality is more likely to be respected.

The most effective triggers are simple and few. They should relate to outcomes the subsidiary already monitors: cash headroom, covenant compliance, forecast accuracy. They should be reviewed after each quarter to ensure they remain proportionate. And they should be accompanied by a clear statement of what happens when a trigger is breached, so that no one is surprised by the process.

What belongs in the board pack

The board does not need a list of every bank account. It needs a single-page liquidity dashboard showing group cash, committed and uncommitted balances, the rolling thirteen-week forecast, entity-level exceptions, and covenant headroom. A short narrative should explain material movements and confirm the date and time at which the data was captured. Ownership should be explicit: who prepared the report, who reviewed it, and what assurance has been obtained.

This is not a demand for more data. It is a demand for better-shaped data. A board that receives a clear, timely and comparable picture can govern proportionately. A board that receives a delayed aggregation of incompatible formats can only react.

Autonomy as a design constraint

Subsidiary boards should retain authority over day-to-day cash management within an agreed policy. The group sets the reporting standard and the escalation framework; it does not issue operating instructions for each payment run. Treasury acts as an assurance and advisory function, not a command centre.

This model respects the commercial reality of UK groups: local relationships, local knowledge and local accountability remain valuable. It also recognises that the board's role is oversight, not execution. The goal is not a single pot of money. It is a single version of the truth.

Practical steps for the year ahead

Begin by agreeing definitions. What counts as cash? What counts as uncommitted? How is headroom calculated? Then standardise the reporting calendar and test the template with two or three entities before rolling it out. Explore whether open banking APIs can reduce manual effort, but do not let technology dictate the model. Review the triggers quarterly, and report to the board on the quality of the reporting itself, not only on the numbers it contains.

The treasury blind spot is closed not by seizing control but by establishing sightlines. Boards that can see clearly can govern with confidence. Subsidiaries that report clearly can keep the autonomy they need to operate. That balance is the mark of a well-run group.