Standardized Divisional Reporting Without Eliminating Legitimate Business Differences For A Multi-Billion-Dollar MedTech Company
Standardization is often treated as the natural objective of Enterprise Performance transformation. But for complex organizations, making every business unit plan, report, and operate in exactly the same way can create as many problems as it solves. For a division within a multi-billion-dollar MedTech company, two business segments operated with different ERP systems, stakeholders, revenue models, cost structures, and planning requirements. Those differences reflected genuine business realities rather than process inefficiencies.
Divisional leadership nevertheless needed a single, consistent financial view across both businesses. The challenge was therefore not to make the two segments identical. It was to determine where standardization created management value and where preserving business-specific planning logic was essential.
UVID designed a divisional FP&A framework that maintained segment-level planning models while standardizing the financial structures, definitions, and reporting required at the divisional management layer.
The Problem
The two business segments had legitimate reasons to operate differently. Each segment had its own ERP environment, stakeholders, revenue model, cost structure, and planning requirements. Applying one generic planning model across both businesses would have risked removing the business logic and ownership structures that made each segment’s planning meaningful.
At the same time, divisional leadership needed to manage performance across the businesses through a common financial view.
The challenge involved several competing requirements:
- Different ERP environments: Each segment operated within its own systems and data structures.
- Different revenue models: Revenue planning needed to reflect the commercial reality of each business.
- Different cost structures: OpEx and cost planning could not simply be replicated using a common template.
- Different ownership models: Employee and departmental planning needed to remain aligned with how each segment was managed.
- Need for consolidated visibility: Divisional leadership required one standardized financial view across both segments.
- Need for consistent reporting: Shared reporting requirements, definitions, and calculations needed to be established where they created management value.
- Disconnected CapEx planning: Capital investment needed to be connected to planned spend, assets, depreciation, and financial statement impact.
- Date: August 17, 2026
- Client: Division of a Multi-Billion-Dollar MedTech Company
- Location: North America
- Category: Case Study, Med-Tech
- Website:
The Solution
UVID designed the FP&A architecture around a clear distinction:
Preserve what is different → Standardize what matters → Consolidate for leadership
This allowed the organization to achieve consistency at the management layer without forcing uniformity into the underlying planning processes.
Preserving Business-Specific Planning
Where business ownership and operating requirements genuinely differed, UVID maintained separate planning models for each segment.
The architecture preserved:
- Two employee-planning models
- Two OpEx planning models
- Two revenue planning models
- Separate structures and data where business ownership required them
This meant each segment could continue planning according to the way its business was actually managed. The objective was not to standardize for the sake of standardization. It was to standardize only where doing so improved enterprise visibility and management control.
Standardizing the Divisional Management Layer
At the divisional level, the underlying differences were brought together into a common financial structure.
Both business segments rolled into:
- Common divisional structures
- A standardized P&L
- Consolidated financial reporting
- Common reporting requirements
- Consistent definitions and calculations where appropriate
This created a deliberate architectural separation:
Business-specific underneath → Standardized at the management layer
Divisional leadership could therefore work from one consolidated financial view without requiring either segment to abandon its legitimate planning model.
Connecting the CapEx Investment Lifecycle
UVID extended the architecture beyond core P&L planning by incorporating the CapEx investment lifecycle into the financial model.
The process connected:
Approved CapEx Projects → Planned Capital Spend → Assets → Depreciation → Financial Statements
This meant capital investment was no longer treated simply as an input into an expense or planning line. The investment could be followed through its financial lifecycle and connected to the resulting financial statement impact. The asset-related structures established through the transformation also created a foundation for extending integrated planning into adjacent areas such as inventory planning.
Business Outcomes
The transformation created a divisional FP&A environment in which business-specific planning and standardized management reporting could coexist.
Business-Specific Planning Preserved
Each segment retained the planning structures and processes appropriate to its ownership and operating model.
Divisional Standardization Achieved
The different underlying planning models rolled into a common divisional financial structure, giving leadership a consolidated view of performance.
Stakeholder-Specific Planning Enabled
Different teams could work at the level and structure relevant to their responsibilities while leadership received a consistent enterprise-level view.
Common Reporting Without Uniformity
Shared reporting requirements, definitions, and calculations were standardized where they created management value without unnecessarily redesigning legitimate business differences.
Connected Investment Planning
Approved CapEx projects, planned capital spend, assets, and depreciation were incorporated into the forward-looking financial model.
Scalable Planning Architecture
The underlying design established a foundation for extending integrated planning into adjacent areas such as inventory planning.
Reduced Manual Effort
Automation, reconciliation, and data integration reduced manual effort across the two business segments, reinforcing the broader transformation.
