The CFO Architect

How Financial Architecture Shapes What Organizations Can and Cannot See

A book for the people who own the numbers and have to live with what they leave out.

Get an email when it publishes. Palgrave Macmillan

Every serious company produces reliable financial reports. The board packs arrive on time, the consolidation reconciles, the dashboards are precise to the decimal. And capable organizations still act on those reports and get blindsided by their own business. The cause is rarely bad data or incapable management. It sits one level below the numbers, in the inherited definitions, structures, and allocations that determine which signals survive long before they reach a decision. Mark de Haas calls this the Translation Layer: the architecture through which a business becomes visible to itself. Almost no one designs it. It grows the way plumbing grows in an old building, one connection at a time, each addition sensible on its own, until no one can say how the whole thing runs. Management does not build the Translation Layer. Management inherits it.

Who it is for

The people who own the numbers and live with what they leave out. Chief financial officers and finance leaders first, but also the executive who trusts the reporting and cannot say why the decisions keep going wrong, and anyone handed a reporting model built for a company that no longer exists and expected to run today's business on it.

What you will take away

How to understand the architecture behind a report, not just the report. How to see where real signals are lost inside allocation logic and inherited structure, how to tell a number that is reliable from a number that is useful, and how to rebuild the layer so the business becomes visible to the people who run it. By the end, you will not read a financial report the same way again.

Why it matters

A reporting failure never arrives labeled as one. It shows up as a missed forecast, a covenant breach, a portfolio that no longer coheres, or the moment auditors and the board stop trusting the numbers. Underneath a surprising number of them is the same architecture, inherited and never questioned.

Reliable reporting is not the same thing as a business you can see. This book is about the difference.

Mark de Haas has served as CFO through private equity-owned turnarounds, corporate transformations, and international restructurings, and co-founded XBRL Nederland. The CFO Architect draws on two decades spent, as he puts it, rebuilding the same architecture inside different companies.

Publisher: Palgrave Macmillan
Publication: Early 2027
Manuscript ID: 701396

Every number in this report is technically correct

That doesn't mean it tells you what happened

Scroll down

01 · Foundation

Operational Reality

This is where value actually happens: the finished product is shipped to the customer, the engineer records hours on a project, the machine runs at 94 percent instead of the 98 percent assumed in the plan. Nothing here has been translated yet. It is simply what occurred, before anyone decided how to describe it. Every number in every board pack claims to represent this operational reality. The distance between the two is where distortion begins.

02 · Structure

Legacy Plumbing

Finance architecture rarely resembles a blueprint designed once and refined with discipline. It resembles an old house: expanded, repaired, subdivided over years, pipes rerouted when a wall moved, patched when something leaked. Water still comes out of the tap. Nobody fully knows what happens behind the walls. Every plug bought time and avoided a harder conversation. Individually reasonable. Collectively, it's how a visibility problem starts masquerading as a strategy problem.

03 · The Core

The Translation Layer

Between what happens and what management sees sits an architecture: definitions, classifications, timing conventions, consolidation logic, and a long history of judgment calls about what counts. When that architecture can't natively answer a question, finance builds the answer anyway, combining sources, averaging margins, patching the gap. That figure is a ghost number: visually indistinguishable from governed data, dangerous precisely because it looks ordinary.

04 · The Design Question

Designed for Audit versus Designed for Flow

Every finance architecture is optimized for something. Most were designed for audit, and for statutory purposes that is exactly right. Steering a business asks for something else entirely. The two are different disciplines, and they do not automatically coexist.

Designed for audit values Consistency Traceability Reconciliation Defensibility

Designed for flow values Timeliness Relevance Intervention Learning

Most organizations unknowingly optimize for the first while expecting the second.

05 · The Distance

The Resolution Gap

Strategy is written at the resolution of a single customer, a single plant, a single decision. Performance is monitored at the resolution of a consolidated line item. The distance between those two resolutions is where companies lose the thread. The gap does not announce itself. It simply limits what the organization can see, until the limitation becomes expensive.

Many drivers, high complexity → the gap → Few metrics, low complexity

06 · The Output

Financial Representation

By the time a figure reaches a board pack, it no longer presents itself as a designed output. It presents itself as fact. It reconciled, so it passed. It had a line in the report, so it carried authority. But not every number carries the same evidentiary weight. A cash balance is not a provision. An observed fact is not an allocation. The report is correct. That isn't the same as admissible.

07 · The Vantage Point

The Architect CFO

Someone decides what the organization is structurally permitted to see. Usually that decision gets made by accident, by inheritance, by whoever last touched the chart of accounts. It could be made on purpose instead: operational reality, capital allocation, risk and resilience, governance, held together by one deliberately designed layer. The CFO who treats the architecture as a design problem finds the fracture before the covenant breach does.

Outside the Stack

Signals

Signals are not part of the architecture above. They rise on their own, straight out of operational reality, and can often be read directly, a customer call, a shipment delay, a resignation, before any of it reaches a figure. Aggregation has its own sinkholes: points where opposing movements net to zero and the early warning simply disappears. The mistake is waiting for the number. By the time it arrives, the signal has usually been visible for months.

The report can be accurate and still mislead you

The question is whether the architecture behind it lets you see what matters