Financial Planning & Analysis in the AI Era: Governing Data Before Automating Decisions

Today, a financial controller still spends close to 60% of their time consolidating and reconciling data, and only 40% actually analyzing it. That ratio should be reversed — and that’s exactly the promise of AI applied to finance. But before automating a forecast or plugging a predictive model into your numbers, there’s an older problem to solve first: the reliability and governance of the underlying financial data itself.

This guide is for CFOs, FP&A leads, and data leaders who want to modernize their reporting without reproducing, at greater speed, the definitional and governance errors that already exist in their current systems.

1. The real bottleneck isn’t the tool, it’s the data

Most finance functions already have the tools: Power BI, a modern ERP, sometimes even a dedicated data warehouse. The problem is almost never technological. It’s structural: sales data flows from a CRM, cost data from an ERP, payroll from an HRIS, and no one has ever formally decided who owns the definition of « net revenue » or « contribution margin » at group level.

The result: three different versions of the same KPI circulate in the executive committee, and FP&A spends its time arbitrating discrepancies rather than informing decisions. This pattern shows up identically across very different sectors — retail, banking, distribution — confirming it’s a structural governance problem, not a sector-specific one.

2. Mapping financial data flows across the enterprise

Before any automated reporting project, you need to map precisely where each piece of financial data actually comes from: does revenue come directly from the billing ERP, or does it pass through a CRM before consolidation? Are production costs fed automatically or entered manually at month-end? Does payroll come from the HRIS in real time or from a monthly export from the payroll provider?

This mapping almost always reveals invisible flow breaks: a timing gap between two systems, an undocumented manual transformation in an intermediate spreadsheet, or a different data source per subsidiary for what is supposed to be the same consolidated KPI.

3. Building a financial data dictionary

A financial data dictionary documents, for each key KPI (net revenue, EBITDA, contribution margin, working capital…), a single definition validated by group finance, the exact calculation formula, the identified source of truth, and the owner responsible for keeping it current. Without this reference, automation simply spreads errors faster and at greater scale than before.

Best practice is to build this dictionary KPI by KPI, validating each definition with the different subsidiaries or business units involved — this is often when you discover definitional divergences that have existed for years without anyone formally identifying them.

4. Governing flows between ERP, CRM, and HRIS

ERP, CRM, HRIS, billing tools: every interface is a potential breakpoint. Solid governance documents who feeds what, at what frequency, and with what automated consistency checks (reconciliations, alert thresholds). In a multi-entity group, this governance must also specify how local data rolls up to group consolidation, and what conversion or harmonization rules apply (currencies, local charts of accounts, closing periodicities).

5. The financial RACI matrix

Who validates a figure before close? Who has the right to correct it? Who is informed in case of a significant variance? These questions, often left informal, need to be formalized — particularly in multi-entity groups where each subsidiary may have its own practices. A typical financial RACI matrix identifies the local controller (responsible for entry and first-level validation), the group CFO (accountable for consolidated consistency), IT (consulted on any change to technical flows), and the executive committee (informed of significant variances).

6. Fix reliability before automation: the method

The most common mistake is trying to automate reporting before resolving the underlying definitional inconsistencies. The method that works on the ground always follows the same order: first document existing definitions as they are actually used (not as they should be), then reconcile discrepancies with business stakeholders, and only then formalize the shared reference before connecting it to an automation tool.

7. What AI actually changes in FP&A

Once the data is reliable, AI genuinely changes the FP&A function: continuous forecasting recalculated automatically, anomaly detection before close rather than after, automated variance narratives enriched by humans, and real-time simulation scenarios for investment committees. But each of these use cases assumes data whose definition and freshness are under control.

8. Continuous forecasting vs. the frozen annual budget

The traditional annual budget freezes an assumption that becomes obsolete by the second quarter in a volatile environment. Continuous forecasting, fed by reliable and current data, allows projections to be recalculated with each significant new data point rather than on a fixed quarterly schedule. This change in rhythm requires data governance capable of guaranteeing freshness and consistency at every recalculation, not just at official closes.

9. Anomaly detection and automated narrative

A well-governed anomaly detection model can flag a suspicious budget variance before close rather than after, leaving time to correct or explain it. Automated narrative generates a first draft of management commentary from the numbers, which the controller then enriches with business context — a genuine time saver, provided the underlying figures are reliable.

10. A realistic implementation roadmap

On the ground, the trajectory that works best follows this order: first a data maturity audit to map sources and existing discrepancies; then building the shared reference and financial RACI; and only then deploying forecasting or predictive BI tools. Skipping the second step is the most common mistake I see in engagements — and the most expensive one to fix after the fact.

Expert perspective

On multi-country programs, I’ve seen groups invest hundreds of thousands of euros in a BI tool before even harmonizing their definition of EBITDA across subsidiaries. The software wasn’t the problem: it was the missing data governance upstream. The rule I give clients systematically: never automate a calculation whose logic you can’t explain to an executive committee in one sentence.

FAQ

Do we need a data warehouse before modernizing FP&A?
Not necessarily first. The priority is governing definitions and flows; the technical infrastructure comes after, once the real need is clarified.

How long does this kind of alignment take?
For a single-country mid-size company, expect 2 to 3 months for the reference dictionary and RACI. For a multi-entity group, the trajectory often extends to 6-12 months.

Should FP&A lead this initiative alone?
FP&A should be the business sponsor, but success depends on close collaboration with IT and the data function, otherwise the reference dictionary remains theoretical.

Which KPIs should be prioritized in the data dictionary?
Start with the KPIs that reach the executive committee and are subject to recurring disagreements between subsidiaries or business units — that’s where clarification delivers the most immediate value.

Next steps

If your financial reporting still relies on different definitions across subsidiaries or business units, the priority isn’t a new tool — it’s a governance diagnostic. Check out our Data Governance in the Age of Agentic AI e-book, which includes a RACI template directly applicable to finance, or contact us for a maturity audit.

References

Notoriti — field experience from financial transformation and data governance engagements across multi-entity environments.