Before a U.S. company opens or acquires an overseas entity, assign all nine localization responsibilities
Use the country explorer to prepare questions—not to replace local advice. Scope the local books, tax and e-invoicing, currency, banking, payroll handoff, hosting, industry records and ongoing ownership alongside the U.S. group-reporting design.
Last reviewed · July 2026
Nine decisions that need a named U.S. and local owner
SAP supplies part of the product layer; MTC, local partners, specialist providers, company teams and professional advisers own other parts. Record the boundary and local sign-off for each block.
Local Tax & E-Invoicing
Which taxes, withholding rules, mandated invoices and filing interfaces apply to the subsidiary?
Local Books & Statutory Reports
How will local accounts and statutory outputs map into the U.S. headquarters reporting structure?
Language & Documents
Which users, customer documents and statutory reports require a local language?
Currency, Rates & Revaluation
Who owns exchange-rate sources, revaluation policy and translation into the U.S. management view?
Country Banking & Payments
Which local bank formats, payment methods, approvals and reconciliation feeds must connect?
Payroll & Employment Systems
What remains in a local payroll provider, and which postings and dimensions return to B1?
Hosting & Cross-Border Data
Where will production data and backups reside, who can access them, and what transfer restrictions need review?
Industry, Customs & Records
Do local product, customs, traceability, retention or regulated-industry rules change the process?
Local Ownership & Support
Who signs off locally, supports the timezone and monitors regulatory or provider changes after launch?
The explorer covers 50 countries and regions as a starting point for the local tax and fiscal block. select the target subsidiary country below ↓
50-Country Localization Explorer
Select the country where the subsidiary will operate. Use the tax system, rates, e-invoicing status and B1 support notes to prepare a verification list for local finance, implementers and advisers.
Showing 50 countries/regions · Click a card for details
Planning reference only. Local authorities, SAP release documentation and qualified advisers control the final design.
Record production, backup, access and transfer locations separately
Do not assume in-country hosting alone resolves privacy, security or cross-border-transfer duties. Map the data, users, subprocessors, integrations, backups and support access, then obtain the legal and security review required for the jurisdictions involved. Use the deployment page to define technical ownership after the legal data-flow review.
U.S. program ownership with local-country execution
MTC USA coordinates the headquarters blueprint and cross-country dependencies. MTC service centers and LinkedWorld partners provide local delivery coverage; company owners and qualified advisers retain approval responsibility.
MTC Support Service Centers
MTC’s support footprint spans 8 countries and regions for regional delivery coordination.
LinkedWorld Country Reach
Local partners support country requirements, providers, language and implementation work.
SAP B1 Languages
Confirm the required user interface, customer documents and statutory output for each entity.
A new subsidiary and an acquired entity start from different facts
A greenfield entity can adopt the group blueprint from day one. An acquisition already has data, providers, controls and obligations that must be inventoried before migration.
U.S. Headquarters Opens a Subsidiary
- Separate the U.S. group blueprint from the country-specific statutory layer
- Map local accounts and reporting dimensions into the headquarters view
- Configure local tax, e-invoicing, currency, banking and document language
- Define paired intercompany documents, exceptions and reporting cutoffs
- Obtain local finance and qualified-adviser sign-off before go-live
U.S. Parent Inherits a Local System
- Inventory the existing local ledger, providers, custom reports and open obligations
- Choose what migrates to B1 and what integrates during a controlled transition
- Preserve required local history, documents, tax evidence and access
- Create account, master-data and entity mappings for U.S. group reporting
- Assign country support, provider and regulatory-change ownership
This page scopes one country at a time. For account mappings, intercompany flows and portfolio reporting across entities, see U.S. HQ Global Operations →
Questions U.S. headquarters should resolve before country design
How should a U.S. headquarters use this compliance map?
Does an SAP localization pack make the subsidiary compliant?
Can U.S. headquarters force its chart of accounts into every subsidiary?
Who owns payroll and employment-related filings?
How do we keep country requirements current after go-live?
Can U.S. and overseas entities share one reporting model?
Build the country checklist from the U.S. headquarters view
Share the target country, legal-entity plan, operating model, local providers and headquarters reporting needs. MTC USA will organize the nine work areas and identify where local verification is still required.