Back to Overview
Executive Decision Systems

When every function has different figures: how CEOs build a reliable basis for decisions

Different figures across functions are not automatically wrong. What matters is whether the definition, cut-off date, data flow and unresolved differences are clear for the management decision in question. A practical starting point with a reconciliation bridge, clear accountability and controlled AI support.

Executive Summary

The essentials in one minute

The management problem

Sales, Finance and Operations calculate figures for different stages of business activity. Without shared definitions, the company may plan capacity for unconfirmed orders or withhold resources that are genuinely needed. A shared interface does not resolve the different meanings.

Why it matters to leadership

A historical supervisory assessment shows how demanding full data aggregation and reporting can be. In the BCBS report published in 2023, based on the assessment as at June 2022, only 2 of the 31 assessed global systemically important banks fully complied with every assessed principle. Most achieved largely or fully compliant ratings across the principles. This is not a data error rate or an SME benchmark. In the article's illustrative example, confirmation status, duplicate records and the cut-off date explain the difference between CHF 1,200,000 in the initial extract and CHF 900,000 for the agreed management metric. The CHF 300,000 difference is not automatically lost revenue.

What management should do

Select a report that informs an important decision. Agree its definition and cut-off date, explain differences down to the individual records and name an accountable business owner. Specify which figures are verified, provisional or blocked for a particular decision. Test the process over 30, 60 and 90 days. AI should provide support only once sources and rules are clear; responsibility for deciding how to use an unresolved metric remains with a person.

Sales reports growth. Finance sees less confirmed business. Operations plans additional capacity. Everyone has done the calculations, but not necessarily on the same basis. The executive meeting then becomes a discussion about where the figures came from, when it should be deciding on staffing, investment or delivery commitments.

This is more than an inconvenience. Mistaking the value of open proposals for confirmed order intake can lead a company to build capacity too early. Failing to see confirmed orders because a system update is delayed can mean withholding the very resources needed to fulfil them. There is no universal loss rate for this. The business question is more specific: which decision are we making and which figure are we using to make it?

I would therefore not start with a new dashboard. First, the functions need to agree what their decision-critical metrics mean, how differences are explained and when a figure is reliable enough to support a particular decision. The definition belongs in the shared operating model, not in the memory of the person preparing the report.

Different figures are not automatically wrong

A sales forecast, a confirmed order, work delivered and an amount invoiced represent different stages of business activity. They can legitimately differ. An order is not yet revenue and an invoice is not yet a cash receipt. These distinctions are particularly important in longer-running projects.

Problems arise when all four figures appear under the same heading or when their boundaries have to be explained in the meeting. A factually correct figure can then support the wrong decision. A more precise presentation will not resolve this if the meaning remains unclear.

A shared order intake metric, for example, needs agreed rules on contract status, cancellations and the cut-off date. International business also requires a consistent currency, exchange rate and allocation within group reporting. A margin comparison needs the same cost basis. One function may include variable delivery costs, while another also includes project management. Initially, these are different questions, not calculation errors.

The first step is therefore to identify differences before trying to eliminate them. Function-specific views that serve a useful business purpose can remain. For cross-functional decisions, however, they must be reconcilable to an agreed management metric.

Why an expensive reporting system cannot solve this on its own

A carefully bounded finding from banking shows how demanding shared data architecture and reporting can be. In the Basel Committee's progress report published in 2023, based on the assessment as at June 2022, only 2 of the 31 assessed global systemically important banks fully complied with every assessed BCBS 239 principle. The assessment was conducted by the relevant supervisors. The report also states that most banks had achieved largely or fully compliant ratings across the principles.1

This is not a data error rate, a claim that banks' reports are unusable or a benchmark for SMEs. The regulatory requirements and the complexity of international banks are exceptionally high. The finding does, however, show why existing systems do not guarantee a fully reconciled data foundation. The same report identifies the absence of common data classifications and incomplete data lineage, meaning the traceability of data from its origin, as obstacles.1

BCBS 239 requires banks to establish, among other things, consistent definitions, traceable reconciliation and accountability on both the business and IT sides. A single physical data model is not mandatory; multiple models require robust reconciliation procedures. This is a useful architectural principle, not a general regulatory obligation for mid-sized companies.2

For a CEO, the implication is clear: bringing data together may be worthwhile. It does not replace the decision about which meaning should apply and who is accountable for it.

A reconciliation bridge instead of another debate

Consider an explicitly illustrative example, not a client case. A CRM extract purportedly shows CHF 1,200,000 in order intake. For capacity planning, however, the company wants to use only net confirmed new order intake up to an agreed cut-off date. Assume that all the following amounts are in CHF, exclude VAT and have been calculated without overlap.

The review finds that CHF 100,000 relates to business not yet confirmed. CHF 50,000 comes from duplicate records. A further CHF 150,000 was confirmed only after the cut-off date and belongs in the next period.

The reconciliation is as follows:

CHF 1,200,000 in the initial extract, less CHF 100,000 of unconfirmed business, CHF 50,000 of duplicate records and CHF 150,000 outside the period, gives CHF 900,000 for the agreed management metric. This is an illustrative calculation, not an observed company result.

The CHF 300,000 difference is not automatically lost business. Some of it may be confirmed later. The duplicate records, by contrast, are a data error. Calling the entire difference lost revenue would create the next misleading metric.

Nor is CHF 900,000 alone enough to authorise a staffing decision. Operations needs to know when the orders will be fulfilled, which skills they require and how much existing capacity is available. The shared figure enables this next step. It does not determine the decision in advance.

A reconciliation bridge of this kind should be traceable to the affected records. Otherwise, it is merely another explanation on a slide. If a difference remains unresolved, its amount, possible cause and responsible person must be visibly documented. A new total must not conceal the unresolved balance.

A metric specification jointly owned by the functions

I would start with a small number of metrics that genuinely inform a management decision. Each gets a short specification. There is no need for a hundred-page data manual before the first useful result.

First, the decision it supports. Is the figure intended to support capacity approval, a pricing decision or a liquidity measure? The same data source may need different analyses for different purposes. A forecast is useful when its uncertainty is disclosed. Presenting it as business already secured would be misleading.

Then, the definition. What is counted and what is excluded? Which period, currency and unit apply? How are cancellations, partial orders and subsequent changes handled? Ratios need a clear numerator and denominator. A win rate based on the number of orders is not the same as one based on order value.

Next, the data flow. Where does the relevant business transaction originate, which source is authoritative for each stage and which calculation produces the management figure? A manual adjustment needs a reason, a traceable approval and a date. The original data must be retained.

Finally, accountability. A named business owner confirms the definition and fitness for use. IT ensures that technical processing and controls work. Users of the metric provide feedback on requirements and identifiable problems. A data owner can resolve a question about a figure; the business decision remains with the executive authorised to make it.

The UK's Government Data Quality Framework, published in 2020, supports this use-based approach. It calls for critical data to be prioritised, quality to be documented clearly and accountability to be established. It was developed for UK central government and is not a mandatory corporate standard.3

When a decision can proceed despite uncertainty

Insisting on fully reconciled figures can also cause harm. An operational decision may be needed today, while a final accounting entry will only be available later. That calls for a visibly provisional figure, not a pretence of finality.

The UK framework distinguishes, among other dimensions, consistency, accuracy, completeness and timeliness. Data can be internally consistent yet still misrepresent reality. It also describes the trade-off between timely availability and completeness. Quality must be assessed against the intended use.3

I would distinguish three usage statuses. A verified figure is approved for its stated purpose. A provisional figure may be used only for explicitly specified, limited decisions. A blocked metric must not be used to justify the affected decision until the material uncertainty has been resolved.

Materiality is not simply about the size of a discrepancy. Even a small unexplained difference can matter if it changes whether a minimum margin is met or a capacity bottleneck exists. Conversely, an immaterial, explained rounding difference need not bring all operational planning to a halt. The test is whether it could change the decision.

In practice, Finance and the affected function should explain how sensitive the decision is to the unresolved difference. If the proposed action remains sensible under plausible scenarios, limited approval with a review date may be justified. If the decision changes depending on the interpretation, further clarification is needed before approval. Reversible actions and long-term commitments warrant different requirements.

What AI can usefully take on

Once the underlying questions are resolved, AI can help prepare reports and explain identifiable discrepancies. It can consult approved definitions, summarise a data flow or consolidate points for business review. Recurring duplicate-record and cut-off checks can often be automated with rules alone. They do not necessarily require a language model.

An AI assistant should certainly not decide for itself which of two conflicting definitions is the official one. Nor should it replace a missing reconciliation with a plausible-sounding explanation. A paper submitted for a management decision must retain traceable sources, an as-at date, the definition used and any unresolved limitations.

A limited test could use completed reporting periods. The team introduces known duplicate records, inconsistent cut-off dates and missing confirmations into separate test data. Does the assistant identify these cases? Does it distinguish a documented difference from a supposition? Does it refer unresolved issues to the named person rather than assert a definitive figure?

NIST's AI Risk Management Framework, published in 2023, calls for documented business context, suitable data, known limits to knowledge and defined human oversight. It is a voluntary US framework, not a certification or a guarantee of safety.4

Several layers of the Fassbender AI Operating System work together here. Strategy & Value determines which decision matters commercially. Processes & Decisions establishes the decision process. Data & Knowledge anchors definitions and sources. Technology & Integration provides the reconciliation. Governance & Evaluation assesses fitness for use and changes. People & Operating Model ensures that those involved can fulfil their responsibilities. Connecting systems without making these decisions leaves the work incomplete.

A realistic start over 30, 60 and 90 days

In the first 30 days, I would select one decision-critical report and limit the associated metrics. Finance, an affected business function and IT document definitions, data flows and current differences. The last completed period provides the starting point. The team also records the actual reconciliation effort and the decisions delayed as a result. The aim is a baseline, not retrospectively constructed savings.

By day 60, the reconciliation is applied in at least one new reporting period. Manual steps remain visible. Recurring errors are corrected at their source wherever possible, for example through a clearer confirmation process in the CRM. Changes to definitions receive an effective date and the old and new analyses are explained. Otherwise, a change in definition can be mistaken for growth or decline.

By day 90, the executive team reviews whether the report is sufficiently reliable for its purpose. It compares unresolved material differences, timeliness, total manual effort and the time taken to reach the relevant decision. This includes any new review and maintenance work. Less effort initially means available capacity, not automatically a cost reduction.

Only then should the company decide on the next function and further automation. Applicable statutory reporting and accounting requirements remain in force. A pragmatic internal management definition cannot replace them.

When an Executive AI Transformation Blueprint is appropriate

A single faulty export usually needs a targeted repair. I would not recommend a transformation engagement for that.

The situation is different when several functions rely on different sources, commercially important decisions are blocked as a result and AI is already expected to work with these figures. Priorities, data architecture, responsibilities and investment then need to be decided together.

The Executive AI Transformation Blueprint provides a decision-ready foundation in three weeks. It combines management interviews with a Management Value Case, the Target AI Operating System, prioritised workstreams and a 90/180/365-day roadmap. The executive team receives a standalone two-page Executive Summary and a 30–45-page Executive Deck. The three-week process is for planning, not a claim that every data problem will be resolved in that time.

For this use case, the Value Case would need to show specifically which decisions are currently delayed, how much reconciliation effort is required and which change can be tested with proportionate effort. Where the baseline is missing, the benefit remains a hypothesis to be tested. Transformation investment and the consulting fee are shown separately.

Management FAQ

Must every function use exactly the same figures?

No. Function-specific views can serve different purposes. For shared decisions, however, their meaning and scope must be clear. Where the same management metric is intended, there needs to be a traceable reconciliation and documentation of any remaining differences.

Is a central data platform a prerequisite?

Not always. A limited start can build on existing systems. What matters is approved sources, shared definitions and verifiable processing. A platform investment makes sense when its additional capabilities are needed to meet specific requirements.

Who has the final say when figures conflict?

The accountable business owner clarifies the definition and the relevant functions check the data. If an interpretation materially changes the business decision, the authorised executive must decide. IT or an AI assistant should not silently resolve an unresolved conflict between objectives.

How do we recognise useful initial progress?

When a selected report discloses its definitions, cut-off date and limitations, differences are explained in a traceable way and the responsible decision-maker can use it to make the intended decision. A better-looking dashboard alone is not evidence of this.

Sources

  • ◆Basel Committee, 2023 progress report: supervisory assessment of major international banks as at June 2022.1
  • ◆BCBS 239, 2013: consistent definitions, data reconciliation and business accountability in the banking context.2
  • ◆UK Government Data Quality Framework, 2020: quality for the specific intended use and transparent limitations.3
  • ◆NIST AI RMF 1.0, 2023: business context, data and human oversight.4

Related Insights

Strategic Advisory

From insight to a decision you can stand behind.

We translate AI potential into clear architecture, measurable priorities and an executable roadmap for your organization.