Global Rollout
The same template can go live in Hanoi and Hamburg on the same day — tax IDs, invoice shapes and approval culture cannot. Rollout is not copy-paste; it is template plus localization plus governance.
Who it is for
Groups that already have a hub template and are opening a new country or company code. Cosmetics, FMCG, manufacturing and holding structures — especially when local obligations such as German DATEV / XRechnung enter the picture.
Rollout steps
- Template inventory: what is global, what is local — in writing.
- Country gap: tax, e-invoicing, language, banking, approval matrix.
- Localization: statutory reports and integrations without breaking the template.
- Data and authorization: master data, roles, company-code cut.
- Go-live orchestration: time zones, hypercare window, hub–country rhythm.
What a rollout engagement includes
A rollout takes the SAP template built at the centre into new countries and adapts it to each country’s local regulations. On multi-country, multi-language, multi-regulation projects we take this on from the design of the template to the go-live of the last country. A rollout engagement consists of the five work items below.
- Template design: building the central process template that stays common to every country.
- Rollout execution: taking the template live country by country, in a planned order.
- Localization: compliance with each country’s local regulations, tax rules and reporting obligations.
- Multilingual delivery: project management across different languages and time zones.
- Top-management visibility: a reporting structure designed for what top management needs to see.
Localization: meeting local rules
Meeting local regulations and local business requirements is at the centre of our rollout service. Group headquarters usually reports under IFRS, while each country company answers to its local tax authority and keeps its books under local rules. Localization meets both needs in the same system while keeping the common structure of the template. The work falls under four headings.
- IFRS-compliant localization: local postings are set up so they also meet the IFRS needs of group reporting.
- Country-specific tax and reporting: that country’s tax rules and statutory reports are built into the system.
- Multi-currency: transactions are kept in local currency and tracked in group currency as well.
- Multi-company consolidation: country companies produce their data in a structure ready for group consolidation.
Treasury and cash management across countries
As the number of countries grows, two finance topics come forward: treasury and cash. In multi-currency groups, foreign-exchange transactions and hedge accounting are managed in TRM, and each company’s cash position and liquidity forecast in CM. We can bring these modules into the rollout scope: Borusan Birleşik Boru’s five-country programme included CM and TRM alongside FI, CO and PS.
From the field: five rollout engagements
We have worked on SAP implementation and rollout projects in 50+ countries on 6 continents. The five examples below differ in country count, sector and module scope; the common job is rolling out a central template adapted to each country’s regulations. After a rollout, support can continue under AMS; we also provide AMS to Hayat Kimya and Farmasi.
- Borusan Birleşik Boru: greenfield S/4HANA and rollout in five countries (Türkiye, USA, Germany, Italy, Romania); FI, CO, PS, CM and TRM.
- Hayat Kimya: S/4HANA rollout in Russia, Indonesia, Vietnam, Thailand and Malaysia; IFRS-compliant localization; FI, CO, MM and SD.
- Arçelik: S/4HANA rollout in Thailand, Bangladesh, Vietnam, Malaysia, Indonesia and Dubai.
- Farmasi: S/4HANA rollout and AMS covering Türkiye and the USA.
- Flormar: the Germany rollout has had its kickoff; FI, CO, SD and MM are in scope.
Case pages
Frequently asked questions
Do you change the template in every country?
No. Local legal musts are added; ‘this is how we do it here’ habits are not promoted into the hub. Otherwise you have no template by country three.
Can IFRS and the local book travel together?
Yes — parallel ledger or account approach is designed per country. Forcing a single book tires the auditor, not the rollout.
Can several countries go live together?
Yes, if readiness is actually the same. If one country is hollow, it waits. A risk calendar, not a hero calendar.
What stands out on a German rollout?
DATEV, XRechnung/ZUGFeRD, multi-site logistics and bank formats. The public scope we described at the Flormar Germany kickoff was FI, CO, SD, MM plus those local integrations.
How do you handle language and training?
The template can stay English/Turkish; screens and training go local. A multilingual team is insurance, not a luxury line.