THE ENTERPRISE DATA GOVERNANCE PLAYBOOK — Post 7 of 13
Your GL Redesign Will Fail Without This
By Greg Briscoe, Senior Solution Architect — Enterprise Data Management I’ve seen dozens of GL redesign projects. The ones that succeed have one thing in common: they govern the structural transition. The ones that fail have one thing in common too: they don’t. GL redesign whether it’s a full chart of accounts overhaul, a segment restructuring, or a rationalization driven by cloud migration, it is among the most expensive and risk-laden initiatives in enterprise finance. It touches every downstream report, every consolidation process, every planning model, and every audit trail. And yet, in organization after organization, I see the same pattern: the structural transition itself, the mapping, the validation, the hierarchy management is left to spreadsheets, email chains, and individual heroics. The outcome is as predictable as it is expensive.The 30–40% Problem
Here’s a statistic I share in every GL redesign discovery session. 30–40% of GL transformation budgets are typically consumed by avoidable rework caused by ungoverned structural changes. That’s not a technology cost. It’s a governance cost. Every time someone updates the legacy-to-target COA mapping in a spreadsheet without version control, without validation, without an approval workflow, the project absorbs another cycle of rework. The developer who built a conversion script against version 3 of the mapping discovers that the business team has silently moved to version 5. The test cycle that passed last week failed this week because someone added three new target accounts and didn’t tell the integration team. The go-live checklist that was complete on Monday has six new exceptions by Thursday. This isn’t a failure of competence. The people doing this work are smart, dedicated professionals. It’s a failure of infrastructure. They’re managing a complex, multi-party structural transformation with tools designed for personal productivity. Spreadsheets don’t version. Email doesn’t enforce approval workflows. File shares don’t validate business rules. The tools are wrong for the job, and the cost shows up in rework cycle after cycle after cycle.What Governed GL Redesign Looks Like
When GL redesign flows through EDM Cloud, the structural transition becomes a governed process rather than a collaborative improvisation:- Legacy-to-target COA mapping is maintained as governed cross-references within EDM versioned, validated, and accessible to all stakeholders from a single authoritative source.
- Parallel hierarchies operate during the transition the legacy structure and the target structure coexist within the same platform, allowing side-by-side comparison and gap analysis without maintaining separate files.
- Structural validation rules catch errors before they reach production orphaned accounts, missing mappings, invalid segment combinations, duplicate values all flagged at the point of entry.
- Governed workflows ensure every mapping update, hierarchy modification, and account addition flows through a defined approval process with complete audit trail.
- Automatic distribution pushes approved structures to all consuming applications simultaneously the GL, planning tool, consolidation system, and data warehouse.
| The Difference Ungoverned GL redesign: “Which version of the mapping is current?” “Who approved this change?” “Why doesn’t the test environment match production?” Governed GL redesign is one version, one approval trail, one distribution mechanism, zero ambiguity. |
|---|
The Payoff
Organizations that govern GL redesign through EDM report 30%+ cost savings versus ungoverned approaches. Not because EDM is magic because governed change management eliminates the rework cycle that consumes most of the budget. Think about what 30% means on a large GL transformation. If the project budget is $5 million, that’s $1.5 million in avoided rework. If the timeline is twelve months, that’s three to four months of avoided delay. If the project team is thirty people, that’s the equivalent of ten person-years of effort redirected from rework to value-adding work. Those aren’t theoretical projections. Those are the numbers I’ve seen in organizations that made the transition from spreadsheet-governed to EDM governed structural transformation. The savings are real, they’re measurable, and they show up in the first project that runs through the governed process.Beyond the Redesign
Here’s what most organizations don’t realize until after the GL redesign is complete: the governance capability doesn’t end with the project. The EDM instance that managed the transformation now manages the ongoing maintenance close cycle alignment, alternate hierarchies, regulatory updates, business rule enforcement, new account requests, hierarchy restructuring. The investment compounds. The platform that saved 30% on the redesign project now saves time on every close cycle, every regulatory update, and every organizational restructuring. The skills the team built during the transformation become the governance skills that sustain ongoing operations. The business rules that validated the redesign now validate every structural change going forward. This is the fundamental difference between a project investment and a capability investment. A project delivers value once and depreciates. A capability delivers value continuously and appreciates as more processes and data domains come under governance.| GL redesign is expensive. Ungoverned GL redesign is 30–40% more expensive. The difference isn’t the technology, it’s whether you treat the structural transition as a governed process or a collaborative spreadsheet exercise. |
|---|
Next: The other transformation that keeps CFOs up at night, M&A integration.
Greg Briscoe is a Senior Solution Architect specializing in Oracle EPM, EDM, DRM, ERP, master data governance, and large-scale transformation programs. With experience spanning hundreds of enterprise engagements, he helps organizations design and operationalize data governance capabilities that outlast individual projects and compound in value with every transformation initiative.