Palgrave Macmillan · March 2027

The CFO Architect

Name: The CFO Architect
Author: Mark de Haas
ISBN: 9783032420954

How Financial Architecture Shapes What Organizations Can and Cannot See

The numbers reconcile and the auditors are satisfied, yet the board still cannot see what is happening in the business. That is not a reporting problem. It is a design problem.

Pre-order

Amazon.com

Or get an email on publication day

Financial reality is constructed, not discovered. Dashboards and board reports do not simply reflect events. They show what a financial architecture, built up over years, allows executives to see. Consolidation logic, data models, validation rules, systems, escalation mechanisms, and reporting routines together form what Mark de Haas calls the Translation Layer, which stands between raw economic activity and managerial visibility. Management rarely builds the Translation Layer. Management inherits it.

Mark has spent decades in the trenches of accounting and corporate governance. This book shares real, hard-won experience from large enterprises, working at scale, not on theory. He highlights a crucial need: keeping the finance function aligned with the actual shape of the business. Especially in the AI age, this is a rare, must-have guide for anyone reading (or preparing) management packs or sitting on a board.
John Turner, CEO, XBRL International

What it covers

The book develops a practical framework for understanding how financial architecture influences management information, capital allocation, risk visibility, governance, and decision making. Each chapter dissects a structural component of this architecture, demonstrating how design choices determine what becomes visible, comparable, and actionable at group level. It examines how reporting systems can produce technically correct numbers while obscuring strategic drift, weakening operational visibility, and masking emerging problems in cash flow, working capital, project performance, and organizational resilience. It also considers the implications of digital finance, ERP systems, XBRL, analytics, and AI for financial reporting and control.

Who it is for

Bringing together financial management, corporate reporting, management control, and digital transformation, the book is written for CFOs, controllers, board members, and executive education audiences seeking a deeper understanding of how financial representation shapes corporate judgment, as well as scholars and advanced practitioners in accounting, finance, governance, and business administration.

Why it matters

A reporting failure never arrives labeled as one. It appears as a missed forecast, a covenant breach, a portfolio that no longer coheres, or the moment the board and auditors stop trusting the numbers. Beneath many of these failures lies the same inherited architecture, rarely questioned.

Publisher: Palgrave Macmillan
Publication: Early March 2027
ISBN: 978-3-032-42095-4
Pre-order: Amazon.com

The Structure

Four parts. Nine chapters.

Part I Understanding the Problem

01 The Resolution Gap
02 Financial Reality Is Constructed
03 Strategy in a Leaky House

Part II Designing Financial Architecture

04 Blueprints of Reality
05 The Wrong Question Correctly Answered
06 When Aggregation Kills the Signal

Part III From Architecture to Value

07 The Four Pillars of Financial Reality
08 Jet Engine on a Bicycle

Part IV The CFO Architect

09 The CFO Mandate

About

Mark de Haas

CFO · Author · Lecturer

Mark de Haas is a Dutch Chartered Accountant (RA), CFO, financial executive, author, and lecturer with more than 25 years of experience in financial transformation, reporting, control, governance, and restructuring. He has held senior finance roles at KPMG, Wolters Kluwer, Nielsen, Fairstar Heavy Transport, and Strukton, and teaches Financial Management at the Amsterdam Business School, University of Amsterdam. His work focuses on financial architecture, reporting, governance, and the evolving role of finance. He treats financial reporting as a structure to be designed, not one that already is.

Ventures & writing

Entrepreneur and co-founder of XBRL Netherlands. Author of The CFO Architect (Palgrave Macmillan, 2027) and, previously, Infrastructuur voor Sturing. He maintains a professional profile through dHare B.V. and writes regularly on financial architecture and reporting design.

A career spent, as he puts it, rebuilding the same architecture inside different companies.

LinkedIn →

de-haas.nl · More articles →

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 board pack figure claims to describe this 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