Hope, Email, and Spreadsheets Are Not a Governance Strategy

By Greg Briscoe, Senior Solution Architect — Enterprise Data Management

 

I’ve sat in hundreds of discovery sessions with enterprise finance teams. The words change. The company names change. The industries change. The pain doesn’t.

Every session starts the same way: a room full of smart, experienced professionals who know their data is broken, know the workarounds are unsustainable, and know that something has to change. People who’ve been told so many times that “the new EPM, or BI reporting system will fix it” and they’ve stopped believing in the press. And I honestly don’t blame them. Because in most cases, the new system didn’t fix it. The new system inherited the same structural mess, dressed it up in a modern UI, and handed it back. The problem was never the system. The problem was the absence of governed enterprise data.

What I Keep Hearing

“We’re too dependent on IT for every structural update.”

This one comes up in nearly every session. Business teams own the data conceptually, they understand the reporting structures, the cost center logic, and entity hierarchies but can’t touch the system. Every change requires an IT ticket, a developer, and a deployment window. By the time the change is live, the business has moved on to the next quarter’s workaround.

“We maintain the same dimensions in five different systems and they never match.”

This is the parallel maintenance problem, and it is staggeringly common. The same chart of accounts exists in the GL, the planning tool, the consolidation system, the data warehouse, and at least two spreadsheets maintained by people who don’t know the others exist. Each version drifts. None reconciles. Everyone blames everyone else.

“Our spreadsheets are our system of record for master data.”

I hear this without irony from billion-dollar organizations. The spreadsheet that Linda in accounting maintains on her desktop is the authoritative source for the legal entity hierarchy. Linda is wonderful. Linda is also a single point of failure with no version control, no audit trail, and no backup plan.

“M&A is killing us, every acquisition takes months to integrate.”

Months for structural integration. Not business integration, not cultural integration, just getting the chart of accounts to align and the entities to map. Organizations that acquire regularly absorb this cost as a given, like weather. It isn’t. It’s a solvable problem.

“No process, no standards, no accountability.”

When I ask who owns the chart of accounts, I get three different answers in the same room. When I ask about the change request process, I get shown an email chain. When I ask about approval workflows, I get silence. Governance without ownership, process, and accountability is just a word on a slide deck.

“Reconciliation nightmares every close cycle.”

Close cycles that should take five days take fifteen, because the first ten are spent figuring out why the reporting hierarchies in the consolidation system don’t match the ones in the GL. The numbers are probably right. The structures definitely aren’t. And no one knows which version is current, or correct.

“We can’t trust the numbers because we can’t trace who changed what.”

Audit trail? What audit trail? When master data lives in spreadsheets, governed by email, and maintained by tribal knowledge, traceability is a wonderland fantasy. And when the auditors come asking, the fire drill and blame game begins.

The Real Cost

30–40%	of GL transformation budgets consumed by avoidable rework caused by ungoverned structural changes
5–10 days	per close cycle spent reconciling misaligned hierarchies across systems
3–7 times	duplication of effort maintaining the same dimensions in parallel across applications
Zero audit trail	when spreadsheets and email govern master data creating material compliance risk

Add it up across a fiscal year and you’re looking at millions of dollars, not in software licenses or consulting fees, but in pure waste. Rework. Reconciliation. Remediation. The kind of cost that hides in operational budgets because it’s been normalized. “That’s just how close works.” No, it isn’t. That’s how an ungoverned financial close works.

The Question Isn’t Whether… It’s When

I’m not going to pretend that enterprise data governance is simple or that it happens overnight. It isn’t, and it doesn’t. But I will tell you this: the question isn’t whether your organization needs governed enterprise data. Every organization that runs more than one financial application already does. The question is how long you can afford to keep paying the hidden cost of not having it.

Every quarter you delay, you absorb another round of reconciliation rework, another close cycle stretched by misalignment, another transformation initiative that overruns its budget because nobody governed the structural transition. The cost, risk, and organizational patience for “we’ll fix it in the next system” wears a little thinner.

Over the next twelve posts in this series, I’m going to walk through what enterprise data governance actually looks like in practice, not in theory, not in vendor demos, but in the organizations that have done it. We’ll cover the frameworks, the operating models, the use cases, the organizational design, and the business case methodology that separates organizations that get it right from those that keep rebuilding the same spreadsheets every quarter.

The cost of ungoverned enterprise data isn’t a line item. It’s an invisible tax on every close cycle, every transformation, and every acquisition. The organizations that eliminate it gain a strategic advantage that grows with every initiative.

Next: What exactly is “enterprise data” and why does everyone define it differently?