04GLOBAL STANDARD · LOCAL FIT
Rollout Project Consulting
We turn global SAP templates into controlled, repeatable rollout programmes that meet Türkiye’s localization, tax and e-Transformation requirements.
1template
ONE PROCESS LANGUAGE
Every country uses the same process, data and reporting model.
3layers
GLOBAL · REGIONAL · LOCAL
What never changes and what gets adapted is clear from the start.
Pilot
VALIDATE FIRST
The template is proven in a single country before it is rolled out to the rest.
Wave
PLANNED ROLLOUT
Countries go live in waves, ordered by risk and similarity.
CONCEPT
Why do you need a Global Template?
In a multi-country group, letting each company build its own SAP system with its own rules means different processes, data that does not talk to each other and manual consolidation at every month end. A Global Template solves this with a single reference model. Common processes, data standards, report definitions and control points for the group are designed once.
Rollout is the country-by-country implementation of this reference model. Nothing is designed from scratch in each country. The template is shown to the country team, only the legal and genuinely necessary differences are adapted, data is migrated and the system goes live. This way the second country goes live faster than the first, and the third faster than the second.
The template is not a frozen document; it is versioned with the lessons from each wave. But this evolution has to be controlled. Otherwise every country adds its own exceptions and the template erodes over time.
Design once, validate in the pilot, roll out to every country under control
The success of a rollout project depends less on the number of countries than on how well the template is designed. In the Negzel approach the Global Template has three layers: an unchanging global core, shared regional adaptations and only the local extensions that are truly needed. Every country goes live in planned waves with the same methodology, and the template matures with each wave.
- TRe-Invoice · e-Ledger
- DEGoBD · Intrastat
- PLJPK / SAF-T
- USSales & Use Tax
- AEVAT · Arabic
- SGGST
TEMPLATE ANATOMY
What is global and what is local?
The strength of the template depends on placing every area in the right layer from the start. Fixed global areas are never changed in any country. In parametric areas the structure stays the same and the value is entered per country. Local areas live only in the country concerned.
LAYER 1
Global · Fixed
Process flows, data model, control points and reporting definitions. Only the Design Authority decides on changes.
Target: the vast majority of the scope
LAYER 2
Global · Parametric
Fields with a global structure and country-specific values: organisation values, approval limits, tax rates, language.
The country team enters values, not the structure
LAYER 3
Local
Legal requirements and country-specific integrations. Built outside the template as controlled extensions.
The smallest area possible
Layer classification, area by area
Global fixed: the same in all countries. Global parametric: same structure, value per country. Local: only the country concerned.
| Area | Layer 1Global · Fixed | Layer 2Global · Parametric | Layer 3Local |
|---|---|---|---|
| Organisation structure | Naming rules for company code, plant and sales organisation; corporate structure model | The country’s company code, plant and warehouse values | Additional country-specific organisational units (if needed) |
| Master data | Material, customer and vendor data model; numbering; group chart of accounts | Country chart of accounts mapping, currency, language | Local tax number fields, statutory additional fields |
| End-to-end processes | O2C, P2P, R2R, Plan-to-Produce process flows and control points | Approval limits, tolerance values, document type assignments | Exception steps required by local business practice |
| Tax and statutory | Tax determination logic and tax code structure | Tax rates and code values | Statutory reports, e-documents (e-Invoice, SAF-T, JPK…), tax returns |
| Finance and reporting | Consolidation, group reporting, KPI definitions | Fiscal year variant, period calendar | Local GAAP reports, statutory ledgers |
| Forms and outputs | Corporate form design and logo standard | Language, address and bank details | Legally required form content |
| Integration | Integration architecture, SAP Integration Suite standards, interface catalogue | Connection parameters, country endpoints | Local bank, customs and tax authority interfaces |
| Authorisations | Role design and segregation of duties (SoD) rules | Role derivation from organisation values | Roles specific to local audit requirements |
The classification is an example; the final split is made in the template design phase together with the group and country process owners.
TEMPLATE CHANGE MANAGEMENT
How does a country request enter the template?
During rollout every country brings new requests. What protects the template is that all of them go through the same decision flow. A legal requirement is met with a local extension. An improvement that concerns the whole group goes into the next template release. Everything else is solved with the standard process.
From request to decision
Template change request flow
- Country requestlocal team · fit-gap
- Legal requirement?YES · LEGAL → Local extensionNO → Design Authority
- BENEFITS ALL COUNTRIESGlobal changeenters the next template release
- Rejected · solve with standardprocess adapts, system stays
- THIS COUNTRY ONLYLocal extensioncountry-specific · template intact
Global changes are published with release notes and activated in live countries after regression testing
COUNTRY ROLLOUT LIFECYCLE
Every country goes through the same six steps
Once the template is ready, a country’s rollout is an adaptation and deployment project, not a design project. Duration varies with the size of the country, local requirements and the state of its data.
Preparation
Country kick-off, naming the local team and Key Users, approving scope and schedule.
OUTPUT · COUNTRY PROJECT PLAN
Template Demo & Fit-Gap
The template is shown to the country team in the live system; differences are classified as Global / Parametric / Local.
OUTPUT · FIT-GAP LIST
Local Realisation
Parametric values are entered, local extensions are built, country integrations and data migration are prepared.
OUTPUT · COUNTRY CONFIGURATION
Testing
Local scenarios, integration testing, template regression and user acceptance testing.
OUTPUT · ACCEPTANCE SIGN-OFF
Cutover & Go-Live
Training, trial loads, an hour-by-hour cutover plan and the go/no-go decision.
OUTPUT · LIVE COUNTRY
Hypercare & Handover
An intensive support period, feeding lessons back into the template and handover to AMS.
OUTPUT · LESSONS LEARNED REPORT
WAVE PLANNING
In what order do countries go live?
The pilot country validates the template. Later waves use what the pilot taught, and run faster and with less risk. After each wave the template is published as a new release.
Template, pilot and two waves
Example wave plan
- Template design & buildGLOBAL
- Pilot · TRPILOT
- Wave 1 · DE · PLWAVE 1
- Wave 2 · US · AE · SGWAVE 2
- AMS · live countriesOPERATIONS
Template release: v1.0 (MONTH 9), v1.1 (MONTH 13), v2.0 (MONTH 16)
Indicative plan · durations depend on the number of countries, their size and local requirements
Six criteria that shape the waves
Risk and size
PILOT SELECTION
The pilot is chosen to be representative enough to genuinely test the template, yet small enough for the risk to stay manageable.
Regulatory similarity
LOCALISATION
Countries with similar tax and statutory structures are grouped in the same wave, and local extensions are built together.
Time zone and geography
SUPPORT MODEL
Countries that the hypercare and support teams can serve at the same time are planned together.
Business calendar
CLOSING · SEASON
Go-live is not planned for fiscal year end, peak sales seasons or audit periods.
Current system status
LEGACY · LICENCE
Countries whose legacy system support or licence is ending are brought forward.
Resource capacity
TEAM · KEY USER
How many countries the global team and country Key Users can carry at the same time is planned realistically.
SYSTEM AND TRANSPORT STRATEGY
How do you add new countries while protecting live ones?
From the moment the first country goes live, two jobs run in parallel: supporting live countries and developing new waves. If both run on the same development line, unfinished rollout development can leak into production. The answer is a two-track structure and disciplined retrofit.
Maintenance track, project track and a single production system
Two-track system structure
MAINTENANCE TRACK · LIVE COUNTRIES
DEV-M hotfix → QAS-M regression → PRD
RETROFIT ↓Live fixes flow back to the project track
PROJECT TRACK · NEW WAVE / TEMPLATE
DEV-P rollout development → QAS-P integration testing → PRD WITH CUTOVER
PRD · single global production system
A single global production system is recommended; regional systems can also be considered depending on the number of countries and data residency requirements
GOVERNANCE
Who protects the template, and who carries the country?
Rollout governance has two axes. The global axis protects the integrity of the template, and the country axis manages local delivery. The PMO is where the two axes meet.
Steering Committee
GROUP MANAGEMENT
Approves the wave plan, the budget and go-live decisions; resolves priority conflicts between countries.
Design Authority
TEMPLATE OWNER
Made up of the global process owners and the architect. Decides on template changes and local exceptions.
Global PMO
PROGRAMME MANAGEMENT
Consolidates the schedule, risk and resource status of all country projects in one view.
Global Process Owners
O2C · P2P · R2R
Responsible for the template design of their end-to-end processes and for consistency across all countries.
Country Project Lead
LOCAL DELIVERY
Manages country scope, the local team, data migration and cutover; represents the template in the country.
Local Process Owners & Key Users
COUNTRY TEAM
Take part in fit-gap, test local scenarios and own end-user training.
RISKS
The six most common risks in rollout projects
An early warning sign and a countermeasure for each risk. The PMO tracks these items in every country’s weekly status report.
Template erosion
- Signal
- Each country accepts a few more local exceptions.
- Action
- The local deviation rate is tracked as a KPI; every exception goes through the Design Authority.
Lack of local ownership
- Signal
- Country teams see the template as “the head office’s system”.
- Action
- Local process owners join the design demos early; Key Users are chosen from the country.
Data quality differences
- Signal
- Each country’s legacy system has a different data standard.
- Action
- A global data standard and a country-specific cleansing plan; at least two trial loads.
Retrofit leaks
- Signal
- Urgent fixes made in the live system are not carried to the project track.
- Action
- The retrofit list is checked every sprint; transports are tracked in SAP Cloud ALM.
Regulatory change
- Signal
- A local tax or e-document rule changes while the project is running.
- Action
- The country regulatory calendar is tied to the wave plan; legal packages are planned in advance.
Cutover clashes
- Signal
- One country’s go-live coincides with another’s month-end close.
- Action
- A global cutover calendar; no go-live during financial closing periods.
SUCCESS METRICS
Is the template healthy?
The success of a rollout programme is not measured by go-live dates alone. We also track whether the template is being protected and whether each wave is more efficient than the last.
01TEMPLATE COMPLIANCE
Local deviation rate
The share of objects in a country’s configuration that sit outside the template. The aim is to keep it low.
02LEARNING CURVE
Duration per country
Rollout duration and effort per country are expected to fall with each wave.
03QUALITY
Hypercare incident count
The number of incidents in the first weeks after go-live and the share of critical incidents.
04EVOLUTION
Template release discipline
Approved changes are published in planned releases and pass regression testing.
WHY NEGZEL
The team that designs the template also carries the countries
In rollout programmes, Negzel runs template design, country rollouts, integration and post-go-live AMS with the same team. Having the consultants who designed the template also work on the country projects keeps the spirit of the template intact in every country.
Thanks to our SAP Integration Suite (CPI) expertise, the integration architecture is designed as part of the template. This way every new country starts from a ready integration catalogue instead of building interfaces from scratch.
COMMON QUESTIONS
Frequently asked questions
Can a global template be used in Türkiye as it is?
Core processes are kept as far as possible, but legal requirements such as tax, finance, e-Transformation and statutory reporting need controlled localization. Every difference is managed with a gap and decision record.
When does the local team join a rollout project?
Local process owners join the programme from discovery and gap analysis onwards. Joining late means critical needs surface during testing or cutover.
How does a multi-country rollout scale?
Through shared governance, reusable assets, a wave plan and a rollout playbook fed by every go-live.
How is the pilot country chosen and how are the waves planned?
The pilot country is where the template is first proven in real operations, so the choice is a company whose process scope represents the template well and whose team can give the project time. The remaining countries are grouped into waves by regulatory calendar, business workload and shared system dependencies. However many countries you operate in, the wave plan is written at the start of the programme and reviewed after every go-live.
LET’S START TOGETHER
Let’s start your rollout journey with the template
It does not matter how many countries you operate in. Let’s design your Global Template together, choose the pilot and take every country live under control with the right wave plan.
THE COMPLETE JOURNEY
Other areas of expertise
- 01ENTERPRISE CORESAP S/4HANA Consulting
- 02DATA FLOWIntegration Consulting and Architecture
- 03CONTINUITYSAP AMS Support
- 04You are hereRollout Project Consulting
- 05FULL CONTROLProject Management Services
- 06DIGITALIZATIONNegzel n-Solutions
- 07CLOUDRISE with SAP
- 08EXPERIENCEOur Expertise
- 09FUTURER&D and Artificial Intelligence
- 10SAP MODULESSAP Consulting