Your group runs SAP. Your subsidiaries can run lighter.
Most large groups run headquarters on SAP S/4HANA, and the same big system is too slow and costly to roll out to every small company. A spreadsheet or a local accounting package leaves headquarters blind. Two-tier ERP puts each subsidiary on SAP Cloud ERP, connected to headquarters by SAP's prebuilt integrations. Orders, invoices, master data and financials move between them without anyone typing them in twice.
Standard where the subsidiaries are. Connected where it counts.
A small sales office in a new country doesn't need the full weight of your headquarters system. It needs to sell, buy, invoice and close its books in a way headquarters can see and trust.
SAP Cloud ERP shares its data model with SAP S/4HANA: the same business partners, products, document types and accounting logic. That's what makes the connection between the two tiers standard work, not a custom project.
Open a company in months
A new subsidiary starts from your group template on a ready-to-run cloud system, not a rollout of the HQ system.
Lower cost per entity
Subscription per user, run by SAP. No local servers, upgrades or IT team in each country.
Headquarters sees everything
Financials, cash and intercompany activity flow to HQ in a structure it already understands.
Local rules, handled locally
Tax, invoicing and statutory reports are dealt with in the subsidiary's own system.
Easier acquisitions and exits
An acquired company goes live on its own system first. A business you sell can leave without untangling the HQ system.
New features land first
Subsidiaries get SAP's cloud releases twice a year, so they can pilot ideas before HQ adopts them.
What role does each subsidiary play?
SAP provides ready-made business scenarios for the most common relationships between a headquarters and its subsidiaries. We start every design by agreeing which pattern each company follows, because that decides what has to flow between the two systems.
Sales and distribution office
Sells the group's products in its market. It buys from headquarters and sells to local customers.
Manufacturing plant and internal supplier
Makes finished goods or components for headquarters or for other group companies.
Service and installation company
Sells, installs and maintains equipment that the group makes or distributes.
Served by central functions
Uses services run once for the whole group, such as purchasing, payments or accounting.
One intercompany order, two systems, zero re-keying.
Here is how a sales office buys stock from headquarters. Every document on one side automatically creates the matching document on the other side, using standard SAP messages that both systems already understand.
- SUBSIDIARY · SAP CLOUD ERP1Purchase orderBuyer orders stock
- HEADQUARTERS · SAP S/4HANA2Sales orderCreated and confirmed
- HEADQUARTERS · SAP S/4HANA3DeliveryTo subsidiary or customer
- SUBSIDIARY · SAP CLOUD ERP4Goods receiptFrom the shipping notice
- HEADQUARTERS · SAP S/4HANA5BillingIntercompany invoice
- SUBSIDIARY · SAP CLOUD ERP6Supplier invoicePosted and matched
Close the group, not just the companies.
The second half of two-tier ERP is financial. Headquarters needs each subsidiary's results quickly, in one structure, with intercompany balances that agree.
Consolidation with Group Reporting
Each subsidiary's figures flow into SAP's Group Reporting. Currency translation, intercompany matching, eliminations and group statements run there.
One group ledger with Central Finance
Where HQ runs Central Finance, subsidiary postings are copied into it in near real time, giving one ledger view across the group.
Cash visibility and planning
Group treasury sees subsidiary bank balances and forecasts. Group planning can run in SAP Analytics Cloud on the same numbers.
One customer, one product, one set of accounts.
Integration only works if both tiers mean the same thing by "product 4711" or "customer Lanka Retail". We agree which data headquarters owns and sends out, and which data each subsidiary keeps for itself.
Products
Created once at headquarters and sent to the subsidiaries that sell or make them, including configurable products and their variants.
Customers and suppliers
Group customers and suppliers are governed centrally, for example with SAP Master Data Governance, so every company uses the same record.
Chart of accounts
Every subsidiary posts to accounts that map to the group chart, while also meeting its own country's statutory reporting.
Data moves through SAP's standard replication: SAP Master Data Integration on SAP BTP, SAP Master Data Governance, or the IDocs an older ECC headquarters already uses.
Is two-tier right for your group?
Two-tier isn't always the answer. Some groups are better served by one system for everyone. Here's how the three common options compare.
| Question | One system for the whole group | Two-tier with SAP Cloud ERP | Non-SAP system in subsidiaries |
|---|---|---|---|
| Time to open a new company | Long. Every change touches the central system. | Short. Starts from the group template. | Short locally, then long to integrate. |
| Cost for a small company | High for its size | Proportionate. Per user, run by SAP. | Low licence, high integration cost |
| HQ visibility | Complete | High. Prebuilt financial and process flows. | Limited. Often month-end files. |
| Local flexibility | Low | Good, within SAP's standard | High, but every company differs |
| Best when | Companies share most processes and IT is central | Many smaller or fast-changing companies around an SAP core | A very small entity with a light link to HQ |
Two-tier works whichever side Sri Lanka is on.
Your headquarters is abroad. Your Colombo company joins in.
Headquarters runs SAP in Europe, India or Asia. The Sri Lankan company runs SAP Cloud ERP with our Sri Lanka layer for VAT, SSCL, withholding tax and RAMIS, and stays connected to the group's processes and close.
Your headquarters is in Colombo. Your group is growing abroad.
Headquarters runs SAP S/4HANA. New companies in India, the Gulf, the Maldives or Bangladesh run SAP Cloud ERP, using SAP's own local versions where they exist and a local layer where they don't.
Design the group once. Add companies in waves.
Map the group
Every company, its role and its pattern.
We: agree which flows each company needs with HQ.
Design the template
Processes, accounts and master data ownership.
We: build the group template on SAP Cloud ERP.
Connect HQ
Messages, partner set-up and monitoring on both sides.
We: work with your HQ SAP team or provider.
Pilot company
One subsidiary goes live first.
We: test complete flows across both tiers.
Roll out
Further companies in waves.
We: reuse the template, tests and training.
Run
Releases, new companies and changes.
We: support both tiers and test each release.
See it from SAP.
Short videos from SAP’s official YouTube channels on two-tier ERP and group consolidation.
Published by SAP on its official SAP and SAP Community YouTube channels. Older videos use the earlier product name, SAP S/4HANA Cloud Public Edition.
© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice
Straight answers.
Does our headquarters have to run SAP?
It works best when it does, because SAP's prebuilt two-tier scenarios assume SAP on both sides. That includes SAP S/4HANA on-premise, SAP Cloud ERP Private and older SAP ECC systems. If headquarters runs something else, the subsidiaries can still run SAP Cloud ERP, but the connection is built with APIs and takes more work.
Our headquarters is still on SAP ECC. Is that a problem?
No. ECC connects through the same IDoc messages it already uses. Keep in mind that ECC mainstream maintenance ends in 2027, so we design the subsidiary side to keep working when headquarters moves to SAP S/4HANA.
Can a subsidiary work differently from headquarters?
Yes, within SAP's standard processes. The group template fixes what has to be the same: accounts, master data and the intercompany flows. Each company then adds what its country and business need.
How is it licensed?
Each subsidiary subscribes to SAP Cloud ERP per user, by what each person does. SAP also has commercial options for subsidiaries of groups that already use SAP. We look at both as part of licensing advisory.
What if we sell a subsidiary later, or merge it into headquarters?
A subsidiary on its own system is easier to sell, because its data and processes are already separate. If you later want it inside the headquarters system, its data can be migrated across.
How long does it take to add a subsidiary?
The first company takes longest, because the template and the connection to headquarters are built with it. After that, each company is mostly local set-up, data and training. We give you a plan for each wave after mapping the group.
Map your group in one workshop.
Bring your list of companies. We'll come back with the pattern for each one, what needs to flow to headquarters, and a rollout sequence.
- Pattern for each company
- Integration flows with headquarters
- Master data ownership
- Consolidation approach
- Rollout waves
SAP, SAP S/4HANA and SAP Cloud ERP are trademarks of SAP SE. Screens and diagrams shown are illustrations.
We call our approach to Two-Tier ERP for Subsidiaries the Henwyn Method: advice that stays on your side of the table.