+86 400-623-3007
MTC · Industry Depth, Global Breadth
Scenario · Global Operations · For CEOs / CFOs expanding overseas and MNCs entering China

SAP Business One multi-country deployment:
local compliance, intercompany processes and group reporting

When a China headquarters runs a local ERP and opens a plant in Vietnam, the system architecture should first define HQ governance, data-interface and Vietnam localization requirements. If the HQ platform lacks the required overseas capability, SAP Business One can manage the subsidiary and provide the required data to HQ.

Country coverage↑
70+ countries localised via LinkedWorld network
MTC's global deployment experience since 2009
Deployment speed↑
First overseas entity live in as little as 4–8 weeks
Standardised template + local compliance pre-config
HQ visibility→
Subsidiary data syncs to HQ in real time
Multi-company · multi-currency · unified reporting

SAP Business One Gold Partner MTC · Delivering since 2009 · 760 clients served

ERP requirements for cross-border operations

Local finance teams process country tax requirements manually
Countries use different tax rules, charts of accounts and filing formats, while subsidiary records are maintained outside the group system.Management impact: Headquarters receives delayed data, and tax and audit work requires additional manual reconciliation.
Delayed subsidiary data at headquarters
Subsidiaries use local software or Excel — data can't be sent back to HQ, or arrives weeks late.Management impact: Management decides blind; problems surface only at quarter-end.
Incomplete intercompany and transfer-pricing records
Intercompany transaction prices lack systematic records and traceability — can't produce data when tax authorities ask.Management impact: Back-taxes, penalties, double taxation — profit eroded.
Inconsistent systems, languages and process standards
HQ uses one system, overseas another. Different languages make training and process standardisation impossible.Management impact: Low efficiency, knowledge can't transfer, processes break when people leave.
Business Process and Controls

Subsidiary setup, local compliance and group-consolidation process

The core is SAP Business One's multi-company architecture: each subsidiary has an independent ledger with local compliance pre-configured; intercompany transactions auto-reconcile; and at group level, a unified currency consolidation produces the group report.

Subsidiary setup
New Company DB
Local CoA & Tax
Localization Pack
Daily operations
Multi-Currency Txn
Live Exchange Rate
Intercompany Txn
↓ Intercompany auto-reconciliation · eliminate internal balances
Group level
Multi-Company Consolidation
Unified Group Reporting
Local Compliance Filing
SAP Business One supports 50 country-specific localizations — each subsidiary uses an independent ledger pre-loaded with local chart of accounts, tax rates and statutory reports. Multi-currency transactions include built-in live exchange-rate conversion. Intercompany transactions auto-generate the counterparty entry and reconcile to eliminate internal balances — HQ never consolidates by hand. MTC's LinkedWorld partner network covers 70+ countries, with local teams handling compliance last-mile.
Key control points in global operationsLocal compliance config completenessIntercompany auto-reconciliationExchange-rate update timelinessTransfer pricing audit trailGroup consolidation consistency
Participants: HQ Finance / CFO, Subsidiary Finance, IT, Tax / Legal · Modules used:Financial Management (multi-currency · multi-company)IntercompanyLocalization PacksGroup Reporting
Project Measures

Global-operations outcomes and management measures

Subsidiary go-live cycle

Calendar days from kick-off to subsidiary Go-Live

↓ Lower is better

Group consolidation timeliness

Days from subsidiary close to group consolidated report

↓ Lower is better

Intercompany reconciliation discrepancies

Unreconciled intercompany transaction count · amount

↓ Lower is better

FX gain/loss controllability

Unrealised FX variance ÷ total foreign-currency transaction value

↓ Lower is better

Local compliance pass rate

First-time pass rate on local tax filings / audits

↑ Higher is better

Project Outcomes & Acceptance Measures
70+ countries
Covered via the LinkedWorld global partner network; MTC has direct on-the-ground teams in 14 countries.
760 group clients
Since 2009 MTC Group has served 760 clients — many involving cross-border multi-company scenarios.
4–8 weeks first site
Standardised global template + local compliance pre-config; first overseas site live in as little as 4–8 weeks.
Group operating visibility
Subsidiary data is consolidated for group analysis by country, region, legal entity and currency.
Implementation priorities for global operations

Global deployment and group-control capabilities

Implementation priorities include country localization and go-live, intercompany transactions and group reporting, and global operating analysis and forecasting.

1

Country localization and go-live

Implementation scope: Configure the local chart of accounts, tax rules, statutory reports and multi-currency processing for the first overseas subsidiary, then test the agreed business processes.
SAP Business One and extensions:
SAP Business One LocalizationMulti-currency · live FX ratesLocal CoA / tax config
Acceptance focus: localization configuration and multi-currency accounting pass the agreed process and reporting tests
2

Intercompany transactions and group reporting

Implementation scope: Configure counterpart postings and reconciliation for intercompany purchases, sales and cost allocations, with supporting records for transfer-pricing review.
SAP Business One and extensions:
Intercompany reconciliationTransfer pricing records1+N BI group reporting
Acceptance focus: intercompany entries reconcile under configured rules, transfer-pricing records are traceable and group reports use consistent data
3

Global operating analysis and forecasting

Implementation scope: HQ can analyze subsidiary revenue, profit and cash flow by country, region and currency. AI can assist with foreign-exchange risk alerts and rolling forecasts.
SAP Business One and extensions:
Global operations dashboardAI FX risk alertingAI cross-border rolling forecast
Further improvement: consolidated global operating analysis · FX risk monitoring · data-supported cross-border decisions
SAP Business One Core1+N SuiteAI Applications
FAQ

Implementation and system requirements for global operations

Our China HQ uses a local ERP and we are building a plant in Vietnam. What should the subsidiary use?

First define the master data, chart of accounts and reports that HQ must control, then verify whether the existing system can meet Vietnam tax requirements and provide a stable interface. If its overseas localization is insufficient, SAP Business One can manage procurement, inventory, production, sales and finance in Vietnam and provide the required group data to HQ. The selection should be based on group governance, local compliance and implementation feasibility rather than software-brand consistency alone.

See the Vietnam tax and compliance entry →
Which countries does SAP Business One support with localisation?

SAP Business One officially provides 50 country-specific localizations (including local chart of accounts, tax rates, statutory reports and e-invoicing). MTC's LinkedWorld global partner network covers 70+ countries, with certified local teams handling compliance configuration.

How does subsidiary data roll up to HQ?

Each subsidiary uses an independent ledger. Intercompany transactions auto-generate and reconcile via the Intercompany module. HQ uses multi-company consolidation to produce group reports in a unified currency — available in real time or on a schedule.

How is transfer pricing managed? How do we handle tax audits?

SAP Business One's intercompany transactions are fully traced (price, quantity, timestamp). Combined with MTC's transfer pricing advisory, compliant documentation can be generated to satisfy tax authorities in any country.

How long does the first overseas site take to go live?

Depends on business complexity and local compliance requirements. With MTC's standardised global template and local compliance pre-config, the first site can go live in as little as 4–8 weeks. Subsequent sites reuse the template for even shorter timelines.

Our team is small — can we manage multiple countries?

Yes. SAP Business One supports multi-language UI — one system, switch language instantly. MTC uses a "HQ blueprint + local execution" model: a small HQ team sets standards, local teams in each country execute. You don't need a large team in every country.

Multi-country deployment scope and rollout assessment

Leave your contact details and an MTC globalisation consultant will help you map out: how to land compliance in your target countries, how to connect HQ and subsidiary data, how to auto-reconcile intercompany transactions, and the steadiest path from first site to multi-site.

  • ✓Compliance landing assessment — how to configure tax and statutory reports in target countries
  • ✓Data connectivity diagnosis — can HQ see overseas operations in real time?
  • ✓Globalisation path planning — fastest, steadiest route from first site to multi-site
Get in touch