Investing in China? Roll out a compliant B1 for your China entity
A suitable China-based SAP partner should be able to preserve the HQ template, implement China tax and local integrations, and govern the project bilingually. MTC applies a Template-Rollout approach: retain the group template, implement the China requirements for e-invoicing, VAT, Golden Tax filing, accounting standards and interfaces, and return the required business and finance data to HQ.
SAP Business One or a local Chinese ERP?
The selection should be based primarily on the required depth of integration with HQ. If HQ requires its SAP template, unified master data, group reporting or integration with S/4HANA, SAP Business One can reduce interface and data-standard differences. If the China entity will remain operationally independent, provide only summary data to HQ and operate within a simpler scope, a local ERP may also meet the requirements.
| Decision factor | When to favour SAP Business One | When a local ERP may work |
|---|---|---|
| HQ template and group standards | Prefer B1 when HQ requires the SAP template, a common chart of accounts and unified master data. | A local ERP may be sufficient when the China entity operates independently and HQ receives summary reports only. |
| HQ system integration | B1 normally reduces interface variation when the China entity must exchange master data, transactions or consolidation data with S/4HANA or B1 at HQ. | Evaluate local systems when only limited summary data is transferred and no deep process integration is required. |
| Business complexity | B1 is a stronger fit where multi-entity, multi-warehouse, production, batch, bilingual and group-reporting requirements must be managed in one system. | A single entity with basic finance, purchasing, sales and inventory requirements may be adequately served by a local ERP. |
| Future roll-outs | A shared SAP architecture is easier to extend when more countries, entities or group-governance requirements are planned. | If operations will remain China-only and independent, local functionality, adoption and total cost may carry more weight. |
| Long-term cost | Assess the cost of maintaining HQ interfaces, converting data standards and reconciling duplicate records in addition to the initial implementation fee. | Initial software cost may be lower, but future HQ interface development, upgrade adaptation and maintenance must be included in total cost. |
How to choose an SAP Business One implementation partner for a China subsidiary
Partner assessment should extend beyond the software quotation. Each candidate should substantiate these six capabilities with its proposed team, delivery approach and relevant case evidence.
SAP credentials and delivery record
How MTC meets it: SAP Gold Partner with continuous SAP Business One implementation and service experience since 2009
An established China delivery team
How MTC meets it: Shanghai headquarters and seven directly operated service centers in mainland China, with remote and on-site delivery defined in the project plan
China tax and local integrations
How MTC meets it: CAS, VAT, fully digitalized e-invoicing, banking, statutory reporting and local filing configuration
HQ template and system integration
How MTC meets it: HQ template adoption plus Two-Tier ERP, master-data and group-reporting integration with S/4HANA or B1
Relevant industries and named cases
How MTC meets it: Evidence from comparable industries, operating complexity and publicly verifiable customer cases
Bilingual governance and support
How MTC meets it: Chinese-English coordination between HQ and China teams, followed by ongoing service through 14 support centers
Template-Rollout: adopt the HQ template, change only what China needs
When a global group rolls ERP out across countries, the usual pattern is: get the first country right, distil it into a reusable template, then adapt the differences and roll out the rest. The China subsidiary works the same way — you don’t start each country from scratch and HQ keeps one protocol. The catch: China’s tax and statutory differences are bigger than most countries’, so the adaptation step takes more work.
As a SAP Business One Gold Partner, MTC delivers the China localization in four steps: adopt the HQ template, adapt for China, go live, then connect back to HQ for consolidation. What SAP Business One supports natively versus what MTC delivers — this page sets out item by item.
Adopt the template
If HQ already has a Global Template — a unified chart of accounts, reporting protocol and master-data rules — we start the China go-live from that template. If there is no template yet, we work with HQ to define a repeatable China baseline first.
Adapt for China
On top of the template, we add only what China requires: Chinese Accounting Standards (CAS) accounts, VAT and fully-digitalized e-invoicing, Corporate Income Tax, individual income tax and withholding, statutory report formats, RMB functional-currency accounting and a Chinese interface. Whatever the template already covers, we keep.
Go live
Configure the agreed blueprint, migrate data, build and test interfaces, train end users and provide go-live stabilization support. SAP Business One manages the China subsidiary’s local finance and operations and integrates with the headquarters system under defined group rules.
Connect to HQ
Bring the China entity into one group management language: unified master data, account mapping and reporting protocol, integrated with the overseas B1 or S/4HANA so HQ keeps a single set of books.
What you have to get right in China
These four blocks are unavoidable for a China subsidiary. The content shares its source with the “China” entry of our 50+ countries and regions compliance map, which is reviewed against current rules on a schedule.
VAT & fully-digitalized e-invoicing
- Standard rate 13%, reduced 9% / 6%, 0% for exports; filed monthly or quarterly, split between general and small-scale taxpayers
- Fully-digitalized e-Fapiao rolled out nationwide from 1 Dec 2024; paper special / general invoices are being phased out
- New VAT Law implementing rules take effect from 1 Jan 2026, unifying the VAT framework
Corporate Income Tax & statutory reports
- Standard CIT rate 25% (preferential rates apply to qualifying small/low-profit and high-tech enterprises)
- Statutory statements: balance sheet, income statement, cash-flow statement, statement of changes in equity, profit distribution statement
- Financial data export per the GB/T 24589.1-2010 national standard (Golden Tax / fiscal interface)
Individual income tax & withholding
- Individual income tax withheld monthly with annual reconciliation
- Withholding tax (WHT) summarized by tax code and business partner, supporting multiple tax types
- Withholding income tax on payments to non-resident enterprises per the rules
China-specific delivery details
- Tax Code Determination (TCD) rule engine: auto-determines tax by item group, business-partner group, warehouse and more
- Output / input VAT grouping and tax filing period management
- Bank integration: connect to major Chinese banks for payment and reconciliation
Rolling out beyond China too?
If your group also rolls out in other countries, open the “50+ countries and regions compliance map” to understand each market’s tax differences before planning the local rollout sequence.
See the compliance map for 50 countries and regionsWhat B1 does natively, and what MTC does
SAP Business One ships with a China localization — but “ships with localization” is not “compliant out of the box.” SAP provides the foundation: tax rules, statutory reports and multi-currency accounting. Connecting to the e-invoicing platform, integrating with banks, configuring to local filing practice and consolidating with HQ all need a local partner. Below is the split, capability by capability — laid out plainly, with nothing glossed over.
| Capability | SAP B1 native | MTC delivers |
|---|---|---|
| Accounting standards & ledger | China CAS localization, RMB functional-currency accounting, Chinese interface and language pack | CAS chart-of-accounts templates and mapping rules to group reporting (IFRS / group GAAP) |
| Tax codes & calculation | Tax Code Determination (TCD) rules, output / input VAT grouping | Configured to match real-world local filing practice |
| Statutory reports & filing | GB interface wizard (16 reports), VAT / withholding-tax filing, extended tax reporting | Real-world rollout of reporting and Golden Tax filing |
| e-invoicing (e-Fapiao) | — (B1 does not connect natively to China’s e-invoicing platform) | e-invoicing platform connection, issuing and receiving directly with the tax platform (via the 1+N suite) |
| Bank integration | — | Connect to major Chinese banks for batch payment, e-receipts and auto-reconciliation |
| Multi-currency · multi-entity | Multi-currency, multi-ledger (multi-entity) accounting across the group | Unified group master data and reporting protocol |
| Consolidation with HQ | Official Two-Tier integration framework with S/4HANA | Account mapping, currency translation, standards adjustments and interface delivery |
| Data compliance · cross-border | Supports on-prem / private-cloud deployment — data can be retained and governed in-country | Plans data residency and cross-border transfer compliance per CSL / DSL / PIPL |
| Delivery & ongoing compliance | — | Blueprint, data migration, integration, training, hypercare and policy tracking |
“Native” = the foundation in SAP’s official China localization; “MTC delivers” = taken all the way to a compliant go-live by MTC’s Gold-Partner team. The data-compliance row is what overseas HQs care about most.
How to consolidate with the overseas B1 or S/4HANA
The China entity has to satisfy China statutory filing and roll up into the group — two different protocols. Consolidation comes down to four concrete things: how the architecture is set up, how accounts map, how currencies translate, and how standards differences are adjusted.
Two-Tier ERP architecture
HQ runs S/4HANA or SAP Business One for group consolidation and unified master data; the China subsidiary runs B1 for local compliance and operations. This widely adopted Two-Tier ERP model is backed by SAP’s official S/4HANA-to-Business One integration.
Account mapping
The China entity books under Chinese Accounting Standards (CAS), then a mapping ruleset aligns local accounts to the Group Chart of Accounts — keeping data comparable across countries at consolidation.
Multi-currency translation
The China entity books in RMB as its functional currency; at consolidation, balances are translated into the group reporting currency (e.g. USD, EUR), with rates and translation differences handled per group policy.
Standards-difference adjustments
Differences between Chinese Accounting Standards (CAS) and the group’s IFRS or group GAAP are handled through adjusting entries at consolidation — satisfying both China statutory filing and group reporting.
Already running SAP Business One at HQ and want the full picture of multi-country deployment and group control? See the Two-Tier ERP, template-rollout methodology and group consolidation on the Global Deployment sub-page.
Review the implementation teams and on-site support arrangements for Shanghai, Suzhou, Guangzhou and other mainland China locations.
See mainland China service coverage →FAQ
Should a China subsidiary use SAP Business One or a local Chinese ERP?
How should we choose an SAP Business One implementation partner for a China subsidiary?
Who should a foreign company use to roll out and localize SAP for a new China operation?
SAP Business One ships with a China localization — why do we still need MTC?
What is Template-Rollout?
Our China entity runs B1 and HQ runs S/4HANA — can we consolidate?
What are the China-specific compliance challenges?
How long does a China subsidiary localization take?
Does data have to stay in China? Can it be sent back to overseas HQ?
Talk to us about your China entity
Tell us whether HQ runs B1 or S/4HANA and what your China subsidiary does — MTC will map out the localization and consolidation path.
Talk to us about China