Roll Out SAP Business One Across Asia
China’s e-Fapiao, Japan’s Qualified Invoice, Korea’s mandatory e-tax invoicing, Southeast Asia’s phased mandates: every market plays by its own rules. MTC rolls B1 out country by country on one group template — with your US headquarters seeing everything.
Last reviewed · July 2026
Asia Isn’t One Market — It’s a Sequence of Them
Each market has its own tax regime, e-invoicing timeline and working habits. These are the blocks that decide whether an Asia rollout lands cleanly — and how each is covered.
China: e-Fapiao & CAS
Fully digitalized e-invoices (e-Fapiao) rolled out nationwide in Dec 2024, and the new VAT law takes effect Jan 1, 2026. Statutory reporting follows Chinese Accounting Standards.
How it’s covered
B1’s China localization covers Tax Code Determination, VAT returns and the GB interface with 16 national-standard financial statements — delivered by MTC’s own China teams.
Japan: Qualified Invoice System
The Qualified Invoice System (effective Oct 2023) ties input tax credits to registered issuers, with the credit transition stepping down from Oct 2026. Monthly closing invoices are standard practice.
How it’s covered
B1 handles consumption tax classification (10%/8%), qualified invoice registration numbers and monthly invoice reports out of the Japan localization.
Korea & Mandate-First Markets
South Korea’s e-tax invoicing is mandatory and live. Getting the sequence wrong in mandate-first markets means rework under deadline pressure.
How it’s covered
MTC sequences each country’s go-live around its e-invoicing mandate dates, so compliance deadlines drive the plan instead of breaking it.
Southeast Asia: Phased Mandates
Singapore (InvoiceNow) and Malaysia (MyInvois) are rolling out e-invoicing in phases; Thailand remains voluntary. Every market is at a different stage.
How it’s covered
The compliance map tracks each country’s current status, and B1 localization packs are configured to the phase your entity actually falls into.
Language & Local Teams
Local staff need the system, documents and support in their own language — and in their own timezone, long after go-live.
How it’s covered
SAP B1 ships 28 native language versions including Chinese, Japanese and Korean; MTC supports them with in-region, native-language teams.
Data Residency & Deployment
Some markets — China in particular — bring data-residency expectations that decide where the system and its data may live.
How it’s covered
B1 supports cloud, on-premise and in-country deployment, so entities with residency requirements deploy locally while the group stays on one template.
Rates, filing cycles and e-invoicing status for all 11 Asia-Pacific markets are on the country compliance map →
Local Books in Every Country. One Picture at Headquarters.
The architecture that makes an Asia rollout governable is the same Two-Tier ERP model MTC uses for multi-country groups — four moving parts, each with a clear job.
One Template
The group’s chart of accounts, processes and controls defined once at HQ — the Two-Tier ERP model.
Local Companies
Each Asian entity runs its own company database: local language, local COA mapping, local statutory books.
Intercompany
Cross-entity trade, allocations and reconciliation handled in-system between the US and Asian entities.
HQ View
Consolidated group reporting back to the US: one picture across currencies and accounting standards.
The governance model — templates, controls, who decides what — is the Globalization track: see Globalization →
Pilot First, Then Replicate
Trying to land every country at once is how Asia rollouts stall. The wave model gets the first country right, then reuses it.
Pilot Country, Done Right
- Pick the pilot by business weight and compliance urgency — often China or Japan
- Build the group template into a working, localized entity
- Prove intercompany flows and HQ reporting end to end
- Document what’s standard vs what’s local, so later waves don’t renegotiate it
Replicate Across the Region
- Subsequent countries reuse the hardened template — localization is the delta, not a redo
- Sequencing follows e-invoicing mandate dates and entity readiness
- MTC in-house teams and LinkedWorld partners deliver in-country
- Each wave shortens: the second country is faster than the first, and the third faster still
On the ground: MTC operates across 8 countries and regions with in-house teams, and connects 70+ in-country partners through the LinkedWorld alliance. For cross-border trade operations specifically, see Cross-Border Trade →
Frequently Asked Questions
Does SAP Business One support China’s e-Fapiao and statutory reporting?
What about Japan’s Qualified Invoice System?
Can our US headquarters see all Asian entities in one place?
China has data-residency requirements. Where does the system live?
Who supports the Asian entities after go-live?
In what order should we roll out countries?
Plan Your Asia Rollout
Tell us which markets are on your roadmap and what you run today — MTC will map the compliance timeline, propose a pilot, and sketch the wave plan back to your US headquarters.