Master data harmonisation ahead of RISE.

Master data harmonisation is the single largest preparation cost in a RISE with SAP conversion programme and the single largest determinant of post conversion data quality. Buyers that arrive at conversion with harmonised customer, vendor, material, finance, and organisational master data convert faster, integrate cleaner, and produce reporting that the business actually uses from day one. Buyers that defer harmonisation and convert their existing master data as is typically discover within the first quarter post go live that reporting is unreliable, that integration errors consume the support team's bandwidth, and that the target architecture's analytical value is unrealisable until the master data is finally fixed under far worse operational conditions. The harmonisation work is unglamorous and politically demanding, but it is the most consequential pre conversion investment a buyer can make.

01.Defining the harmonisation scope and target model

The first decision in any master data programme is the scope of harmonisation. Some buyers attempt to harmonise every data domain in a single push, which produces an unmanageable scope and almost always fails. Other buyers attempt no harmonisation at all and convert the existing fragmented model, which produces the post conversion data quality problems just described. The right scope is between the two extremes and follows a disciplined prioritisation.

The high priority domains are typically customer master, vendor master, material master, chart of accounts, profit centre and cost centre hierarchies, and organisational structures such as company codes and plants. These domains drive the majority of transactional volume and the majority of cross unit reporting. Each is a candidate for full harmonisation ahead of conversion.

Lower priority domains include conditions, output determination, asset master, and various functional master tables. These domains can often be converted as is and harmonised after go live in a structured cleanup phase. The scope decision should be made explicitly at the start of the programme rather than emerging by accident as harmonisation work is scoped wave by wave.

02.Customer and vendor master harmonisation

Customer and vendor master harmonisation is the most visible harmonisation activity because the records are external facing and the duplicate problem is usually severe. A global enterprise with thirty business units often has eight to ten records for the same customer, each with different addresses, payment terms, tax classifications, and credit limits. The duplicates create reporting noise, prevent consolidated credit management, and complicate compliance such as sanctions screening.

The harmonisation process starts with a match and merge exercise that identifies probable duplicates across the estate and produces a target unified record. The match and merge tooling can be supplied by SAP or by a specialised data quality vendor. The tooling matters less than the governance behind it, since automated matching will always require human adjudication for the edge cases.

The output of the customer and vendor harmonisation is a master data governance policy that defines who can create a new record, what duplicate checks the system enforces, and how the consolidated records are maintained over time. The policy should be in production before the first conversion wave goes live, with a small central team responsible for new record approvals across the enterprise. Without the policy, the harmonised state degrades back to a fragmented state within twelve months of go live.

03.Material master and the product hierarchy decision

Material master harmonisation is the most operationally consequential domain because it touches manufacturing, procurement, sales, finance, and inventory. A fragmented material master with inconsistent product hierarchies prevents consolidated demand planning, makes cross unit transfers expensive to model, and blocks meaningful product profitability analysis.

The harmonisation decision typically requires the buyer to choose a single global product hierarchy that all business units will adopt. The decision is contentious because each business unit has typically built its hierarchy around the way it goes to market. The hierarchy decision should be made at the executive level with explicit trade off analysis between operational simplicity and unit specific reporting flexibility.

Once the hierarchy is set, the material master records need to be mapped to the new structure. The mapping is labour intensive and benefits from automated assistance, but the final mapping decisions should be reviewed by both finance and product management. The post conversion environment should enforce the harmonised hierarchy through master data governance rules that prevent unit specific reversions.

04.Chart of accounts and finance master data

The chart of accounts harmonisation is often deferred to the conversion programme itself rather than addressed as a separate pre conversion activity. That deferral usually produces a difficult conversion. A unified chart of accounts is easier to design and validate in a dedicated preparation phase than in the middle of a wave that is also addressing transactional process changes.

The chart should be designed against the target reporting requirements at the corporate level, with sufficient granularity to support unit level operational reporting. The design should also accommodate statutory reporting requirements in every jurisdiction where the enterprise operates. A common error is to optimise the chart for corporate reporting at the expense of local statutory needs, which produces a post conversion environment that requires extensive local additions to remain compliant.

Profit centre, cost centre, and segment master data should be harmonised alongside the chart of accounts. The hierarchies should reflect the target operating model rather than the historical organisational structure. Buyers that harmonise around the target operating model find the post conversion environment immediately useful for management reporting. Buyers that harmonise around the legacy structure find that the next reorganisation triggers a costly secondary cleanup.

05.Organisational structure decisions

Organisational master data covers company codes, plants, sales organisations, purchasing organisations, and the legal entity structure underneath. These elements rarely change frequently in the source system but they are foundational to the target system architecture. Harmonisation here is a one time decision with multi year consequences.

The typical decision is whether to maintain the legacy structure or consolidate. Consolidation reduces the operational footprint and the licensing footprint, but it can produce statutory or operational complications that are difficult to reverse. The decision should be based on a careful review of the legal and tax implications, the operational implications, and the licensing implications.

When consolidation is chosen, the migration of historical data into the consolidated structure requires careful planning. Transaction history typically needs to be retained in the legacy structure for statutory purposes while the new transactions flow into the consolidated structure. The bridge between the two needs to be designed during the master data programme rather than improvised during the cutover.

06.Governance, cadence, and the post harmonisation operating model

Harmonisation only delivers durable value if it is paired with a master data governance operating model that maintains the harmonised state through the contract life. The governance model defines roles, approval processes, system controls, and data quality metrics. The model should be in production before the first conversion wave to ensure that wave one inherits a well governed master data foundation.

The governance roles include data owners at the domain level, data stewards at the operational level, and a central master data office that resolves cross domain conflicts. The roles need executive sponsorship because the governance enforces decisions that some business units will resist as overly restrictive. Without the sponsorship, the governance erodes within twelve months and the harmonised state degrades.

Finally, the master data programme should deliver a measurement framework that tracks data quality through the conversion and beyond. The framework includes completeness scores, duplicate detection rates, classification consistency, and integration error rates that trace back to master data issues. The metrics should be reviewed monthly at the steering committee, with red threshold breaches triggering remediation. Buyers that measure master data quality continuously preserve the harmonisation investment across the seven year contract life. Buyers that stop measuring after go live typically rebuild the same fragmented state within three years.

Master data is the foundation that every other RISE benefit depends on. Harmonise before conversion or pay later, under worse conditions.

07.Conclusion

Master data harmonisation is the most consequential preparation activity in a RISE conversion programme. The decision to invest in pre conversion harmonisation produces a smoother conversion, a cleaner post conversion environment, and a higher realisation of the analytical and operational benefits the target architecture was designed to deliver. The decision to defer harmonisation almost always trades a manageable pre conversion cost for a much larger post conversion cleanup conducted under operational pressure. The choice between the two paths should not be made by default. Buyers that face the harmonisation decision squarely, scope it carefully, prioritise the high impact domains, and pair the harmonisation with a durable governance operating model deliver RISE conversions that produce business value from the first wave. Buyers that postpone the decision typically deliver RISE conversions that work technically but disappoint commercially because the underlying data quality undermines the architecture. The harmonisation work is unglamorous and contested, but it is the single largest determinant of whether a multi year RISE programme delivers on its promise.