A successful ERP transformation with a Target Operating Model(TOM)
A successful ERP transformation with a Target Operating Model(TOM)
Cloud ERP Transformation From Legacy Systems to a Unified Platform

Each business unit operated under its own local Target Operating Model, with no shared process catalogue, common data definitions, or unified governance. This made it impossible to establish a consistent operating baseline or enforce organisation-wide standards.
Finance and procurement teams relied heavily on spreadsheets and offline tools for routine transactional activities including invoice processing, reconciliation, and month-end reporting. This created significant processing delays, increased error rates, and consumed high volumes of staff time on low-value work.
There was no common data model across the organisation. Vendor master records, cost centre structures, and chart of accounts definitions varied by entity, resulting in duplicate records, poor data quality, and an inability to produce reliable consolidated reporting.
Legacy ERP platforms operated in isolation with minimal interoperability. Finance and procurement functions were disconnected, preventing end-to-end process visibility and making it difficult to track spend, commitments, or supplier performance across the organisation.
The existing systems and operating structures were not designed to support centralised service delivery. Transactional processes were duplicated across entities, creating unnecessary cost and preventing the organisation from realising the efficiency benefits of a consolidated model.
With multiple stakeholder groups, varying levels of readiness, and no central design authority, the risk of fragmentation during transformation was significant. Ensuring consistent adoption of a standardised model while accommodating legitimate local requirements required a structured and evidence-based governance approach.
Used existing documentation including finance and procurement SOPs, local operating models, benchmarking data, and previous advisory reports — alongside structured stakeholder interviews to build a credible, multi-entity baseline. This avoided duplication of discovery work and grounded the TOM design in facts rather than assumptions.
Ran Fit-to-Standard workshops using a pre-configured SAP S/4HANA environment to co-design a common process catalogue and shared data model across all business units. Workshops were scenario-based, running live in the system to demonstrate standard processes before any configuration decisions were made.
Designed a hub-and-spoke SSC model comprising a central transactional hub for high-volume processing, supported by local finance business partners and strategic procurement cells embedded within each entity. Standardised service catalogues and SLAs were defined to govern the operating relationship between the SSC and individual business units.
Produced a six-layer TOM covering process, organisation, service delivery, technology and data, performance and insights, and governance. This was accompanied by a Shared Services Handbook and a governance blueprint establishing a Partnership Committee, Management Board, and Operational Service Review cadence to maintain oversight and drive continuous improvement.
.png)
This experience directly informs our approach to complex, multi-entity ERP and shared services programmes particularly in SSC operating model design, governance layering, and the balance between organisation-wide standardisation and necessary local flexibility.