Your Finance Transformation Has a Blind Spot

In brief:

• Every finance function runs two infrastructures: the systems you govern, and the spreadsheet layer you depend on but cannot see.

• That second layer is the most common reason transformation programs stall midway. The plan accounted for the systems and never for the logic living outside them.

• Regulatory expectations (SOX, IFRS 17, SR 11--7, DORA) already apply to that logic, governed or not.

• You cannot govern logic you cannot see, and you should not scale logic you cannot govern. Visibility is the strategic first move, whatever order the rest takes.

Every CFO operates two financial infrastructures.

The first is the one you govern: the ERP, the general ledger, the financial planning and reporting systems. Each properly architected, audited, and controlled. The second is the one you depend on but cannot see: thousands of Excel workbooks calculating reserves, processing journal entries, reconciling treasury positions, and producing the reports your board reads.

This second infrastructure moves millions of dollars every day — yet it sits outside your financial controls, your system architecture, and your audit frameworks. It is the most common reason finance transformation programs stall midway, because the roadmap accounted for the systems and never accounted for the spreadsheet layer where much of the real work happens.

Until that layer is brought into the transformation conversation, even the most ambitious modernization agenda will underdeliver. Here is why that happens, what the research says about it, and what the path through looks like.

The stall shows up mid-program

Finance transformations rarely fail loudly. They slowly plateau, usually in the middle of the program, and the pattern is consistent:

• Validation steps that took an afternoon start taking a week

• Numbers that should reconcile cleanly need manual explanation before anyone will sign off

• Teams quietly run parallel checks in the old spreadsheets, because that is still where the answers live

What is surfacing is operational logic that never lived in core systems: pricing adjustments, reconciliations, and allocations built in Excel over years, because the platforms of the day could not hold them. The transformation plan covered the systems. It never covered this layer.

Transformation doesn't stall because of Excel. It stalls because the Excel layer was never on the plan.

The research backs this up

EY's 2025 Global Insurance CFO Study, built on interviews with 21 CFOs across global markets, frames finance transformation around six paradoxes:

1. Do more for less
2. Innovate while protecting the business
3. Upgrade technology without disrupting mission-critical systems
4. Move from historical reporting to forward-looking intelligence
5. Maintain stability through constant change
6. Upskill without losing core expertise

The surrounding data underscores the pressure.

Nearly half of surveyed CFOs (47%) named increasing competition as the top disruptive force ahead, and three-quarters said macroeconomic uncertainty had reduced their confidence about the future.

But it is the third paradox, upgrade without disrupting, that gets closest to the structural problem most finance transformation programs miss. One CFO called finance the least understood function an organization can try to transform.

Underneath that leadership challenge sits a visibility gap: the actual mechanics of finance operations — the formulas, manual handoffs, and embedded logic that hundreds of people touch every month — are often invisible to the people trying to change them.

The study covers insurance, but the pattern applies to any finance function with a decade of accumulated end-user computing (EUC), whether the workbooks calculate reserves, loan provisions, or intercompany allocations.

The layer no one can map

The scale of this hidden layer is hard to appreciate until you look. It's not uncommon for hundreds of spreadsheets to feed a single monthly close process, each with its own formulas, assumptions, and manual handoffs. Daily liquidity reporting can depend on dozens of interconnected Excel models spread across multiple teams, with embedded VBA that only a handful of people understand. Management reporting packages often source data from models that haven't been reviewed in over a year.

These files exist because they work. They're flexible, fast to build, and they encode years of domain expertise from actuaries, analysts, and finance professionals who understand the business deeply.

The exposure is what nobody can answer about them:

• How many EUCs exist, and who owns them?

• Which ones carry business-critical logic?

• Which would cause a restatement if they failed?

• Where are the single-person dependencies?

You can commit to doing more for less, upgrading your toolset, and upskilling your teams. But if the foundational layer of your finance operations remains unmapped and ungoverned, you are building on ground you cannot verify.

Why an inventory alone doesn't fix it

The first instinct is to catalogue: count the files, find duplicates, record locations and owners. That produces a registry of metadata, and metadata is not where the risk lives.

An inventory can tell you that 50 pricing spreadsheets exist, but not that they are variants of one core model plus a few that silently diverged, because that answer sits in formula structures, dependency chains, and version lineage, none of which appear in a static file list.

The questions that determine risk are behavioral:

• Which spreadsheets are fundamentally doing the same thing?

• Where did logic diverge, and was it intentional?

• Which files are genuinely risky, and which merely look complex?

• Which are essential, and which persist out of habit?

Answering them means reading the logic inside the workbooks, across thousands of files, and keeping that picture current as copies multiply. A manual catalogue can do neither: it stops at the file's surface, and it is stale the first time someone saves a new version.

That is why teams with complete inventories still freeze.

Governance feels risky because no one knows what might break; replacement feels reckless because too much institutional knowledge sits in files no one fully understands.

Regulators aren't waiting

There's a dimension EY's study touches on but doesn't fully develop:

Regulatory pressure around off-system data is accelerating faster than most transformation timelines can match.

SOX and IFRS 17 both place strict requirements on data integrity, model calculation governance, and auditability. Those requirements don't distinguish between logic that lives in an enterprise system and logic that lives in an uncontrolled spreadsheet on someone's desktop. The standard is the same. The gap in controls is not.

In banking, SR 11-7 and BCBS 239 extend the same expectations to EUCs feeding risk and regulatory reporting. DORA in Europe and CPS 230 in Australia extend similar expectations to operational resilience, making this a global trend rather than a jurisdictional exception.

Exposure is already on the books, and it compounds for as long as the transformation timeline runs.

From visibility to control to scale

EY's own recommendation for navigating the upgrade-and-sustain paradox points in a specific direction: add capability to existing systems via interfaces users already know, and wrap legacy processes with new controls where full replacement is unrealistic. 

The Coherent platform is built on that principle.

Start by seeing what you have. Coherent Insights scans Excel files across teams and systems to map the full estate — surfacing dependencies, complexity, ownership patterns, VBA risks, and sensitive data exposure. The output answers questions CFOs can rarely answer today: How many spreadsheets touch my financial close? Which models would cause a restatement if they failed? Where are the single-person dependencies that create fragility at the worst possible time? With that picture, transformation planning shifts from guesswork to evidence-based prioritization — and CFOs can direct investment where it will actually reduce risk and accelerate the close.

Then govern it without forcing a platform change. Coherent Control applies version control, maker-checker workflows, audit trails, and change tracking directly on top of existing Excel-based processes. Teams keep working where their expertise lives, but every change is logged, every approval is enforced, and every formula modification is traceable. The business impact is direct: fewer audit findings, faster regulatory response, and a control framework that covers the off-system processes where journal entries, treasury reconciliations, and regulatory reports are actually assembled. For CFOs who've spent cycles explaining spreadsheet-related control gaps to auditors, this closes that conversation.

Then put governed logic to work everywhere it's needed. Coherent Spark takes the models your teams already trust and runs them as production-grade services — the same logic, executing consistently across every system that depends on it, deployable via REST API to close, planning, and reporting workflows alike. The result is a shorter close cycle, fewer reconciliation errors, and models that are reused across business lines instead of rebuilt from scratch. Finance professionals who were spending their time maintaining manual processes shift toward variance analysis, scenario modeling, and strategic business partnering. That's the move from cost center to value creator that most transformation programs promise but struggle to deliver.

Entry point varies. A team absorbing an acquisition may need Insights first; one fielding audit findings can start with Control; one facing a calculation backlog can enter at Spark. The modules compound in whichever order the business needs them.

Where this leaves finance leaders

Leaders who understand their actual financial infrastructure, the spreadsheet layer as much as the systems on the architecture diagrams, make better decisions about what to automate, what to govern, and where to invest. They move faster, with fewer false starts, and they walk into audits with evidence instead of reconstruction.

Brought under governance, that layer shortens the close, strengthens the control environment, and returns your best people to analysis. It also gives the board confidence in the numbers every CFO is ultimately accountable for.