Companies expanding across Asia-Pacific (APAC) often adopt a regional Enterprise Resource Planning (ERP) system for tighter operational control and clearer financial visibility. A template built at headquarters rarely transfers unchanged, however. Accounting, tax, banking, payroll, language and data governance requirements differ considerably between Mainland China, Hong Kong and Southeast Asia, so a rollout that works in one entity may need substantial adaptation before it can support another.
The businesses that gain most decide early what to standardise and what to localise. For companies with a China entity, that starts with tax invoicing and data governance, extends to a cross-border view of Hong Kong and depends on validating every additional market before configuration begins.
Local design requirements in Mainland China
A global template should not be assumed to support local processes in Mainland China. Finance, tax and operational requirements need assessing from the outset, because they shape configuration rather than being added afterwards.
Tax invoicing under the fapiao system
China’s fapiao system governs invoice types, tax codes, customer data, approvals and credit notes, as well as the reconciliation between sales, tax and the general ledger. Microsoft Dynamics 365 Business Central (BC) can support these requirements by connecting its invoice workflows with a dedicated fapiao integration from the Microsoft marketplace, creating an end-to-end compliant tax process.
E-commerce and manufacturing integration
Selling through platforms such as Tmall and JD can unlock growth, but linking these channels to BC through an order management system (OMS) removes manual data tracking and keeps sales, stock and financial records synchronised. In original design manufacturing (ODM) settings, barcode scanning integrated with BC syncs physical inventory with digital records. This speeds up goods receipts, inventory transfers, production tracking and batch traceability, and gives teams real-time visibility.
Payroll, banking and language
A China entity must maintain local salary, allowance and individual income tax (IIT) data while feeding consolidated figures to headquarters. Local banking interfaces, approval steps and payment proofs rarely mirror group standards, so payment processes need local design. A Chinese-language interface also supports adoption and reduces entry errors.
Data migration and governance
China’s cross-border data security and governance laws apply whenever data is collected, stored or transferred, so they need evaluating before migration. Master data in Chinese and English also needs careful cleansing and mapping to keep reporting consistent across entities.
Hong Kong as a cross-border hub
Hong Kong entities often act as regional headquarters, trading companies, procurement centres or distribution hubs. Because Hong Kong has no VAT or fapiao regime, the ERP must separate Hong Kong profits tax reporting from the Mainland China tax configuration while supporting Hong Kong dollars, foreign currency transactions and group reporting.
For trading and distribution businesses, the key requirement is often the link between finance and cross-border operations. Purchase orders, goods receipts, shipments, inventory movements, invoices, intercompany charges and payments need to be tracked from the regional hub through to the Mainland China entity and other group companies. That frequently means interfaces with SAP, warehouse management systems (WMS), OMS platforms, third-party logistics (3PL) providers and local e-commerce channels such as HKTVmall. A Hong Kong rollout is therefore better treated as a cross-border operating model than as a local finance setup.
E-invoicing variation across Asia
Rollouts in Vietnam, Thailand, Malaysia, Singapore, South Korea and the Philippines still benefit from a common framework, but government-connected e-invoicing is the main source of local variation. Each entity should validate its tax documents, reporting, e-commerce and payroll interfaces before go-live.
Malaysia
MyInvois requires the ERP to manage e-invoice validation, submission, rejection and cancellation, while linking the government reference to the underlying accounting transaction.
Vietnam
E-invoices may require an approved service provider, tax authority codes and retained XML or prescribed electronic records. The ERP should therefore connect billing, tax submission and general ledger posting, with Vietnamese-language documents reconciled to group reporting.
The Philippines
The Bureau of Internal Revenue (BIR) sets requirements for electronic invoicing, receipting and sales reporting. These may call for transmission through its electronic invoicing system, compliant data fields and records of registration, permits and submission status.
Thailand
The Revenue Department’s e-Tax Invoice and e-Receipt framework can affect digital signatures, tax certificates, VAT and withholding tax. E-commerce channels such as Lazada may also require connections between a custom order system, a WMS and BC, with tax submission handled directly or through an integrated local provider.
Singapore
Goods and services tax (GST) reporting, the phased InvoiceNow requirement and Central Provident Fund (CPF) payroll obligations all affect integration design. A regional or shared services entity may also need strong multi-entity and intercompany controls.
South Korea
The National Tax Service e-Tax Invoice system links electronic invoice issuance and transmission with VAT reporting. Korean-language records and local payroll withholding should therefore connect to the regional chart of accounts and reporting model.
Dual-language records, such as Vietnamese or Korean alongside a global chart of accounts, keep local teams compliant without obscuring group reporting. Local rules and implementation timelines should be confirmed before system configuration.
Disciplines behind a successful ERP rollout
A system can go live and still fall short if local teams do not trust the data, cannot complete their required processes or keep working outside the ERP. Five disciplines help prevent that:
- Current-state mapping identifies shadow IT (systems used outside formal IT oversight) and manual workarounds, and catalogues legacy systems, spreadsheets and external connections such as head-office ERPs, warehouse platforms, OMS and 3PL interfaces.
- Regional architecture defines how local statutory books feed group reporting through account mappings, adjustment journals and exchange rates, and confirms data hosting, user access, cross-border transfers and cybersecurity controls such as role-based access, multi-factor authentication and audit logs.
- End-to-end testing covers complete scenarios from customer onboarding and order processing to month-end close, including cross-border intercompany flows, customer relationship management (CRM) data and 3PL integrations.
- Data ownership and training are settled before migration, with market-specific training delivered through local super-users to bridge the gap between the regional template and daily tasks.
- Hypercare through the first month-end close watches for a return to spreadsheet workarounds, supported by an escalation matrix linking local teams, regional leadership, implementation partners and ERP support.
Priorities for foreign businesses with a China entity
Foreign businesses can reduce rollout risk by acting on three priorities before configuration begins. The first is to confirm local requirements with the teams that own them. China finance, tax, payroll and IT colleagues should review fapiao workflows, IIT and payroll data, banking interfaces and data obligations against the group template, with the same check repeated for e-invoicing rules and timelines in each additional market.
The second is to record which template elements are standard and which are local, so exceptions are deliberate rather than accidental. Hong Kong and other hubs should be designed as part of the same cross-border flow as the China entity.
The third is to set measures of success beyond the go-live date, such as whether teams complete processes inside the ERP, trust the data and close the first month-end without reverting to spreadsheets. The regional template works best as a controlled framework rather than a fixed design. Standard elements add control where they fit, while local adaptation covers what the rules demand.
Subscribe to our monthly newsletter to stay informed on regulatory and business developments affecting foreign companies in China.











