China is usually not the first stop in a global Dynamics 365 rollout. By the time a multinational reaches the China wave, the template has often been built, tested, and deployed in other markets. The program has established its governance model, delivery rhythm, and design principles.

China should still be treated as a distinct rollout wave, with its own assumptions, dependencies, and risk profile.

The gap between a global Dynamics 365 template and the requirements of a China legal entity is often larger than expected. It can surface across finance, tax, local integrations, infrastructure, supply chain, and day-to-day operations. Many of these issues are not visible in the original global template or risk register.

Identifying them early is one of the most important parts of planning a successful Dynamics 365 rollout in China.

Protecting the global template

The first discipline in a China rollout is protecting the global template.

Every local deviation that is not legally or operationally necessary adds complexity, weakens standardization, and creates a precedent for future rollout waves. A well-governed program establishes clear rules for local changes and supports those rules with an effective decision-making process at headquarters.

In practice, local requirements usually include a combination of statutory obligations, genuine operational gaps, and established working habits. The fit-gap analysis needs to separate them carefully.

A useful principle is:

• Requirements driven by Chinese laws, statutory reporting, tax regulations, or mandatory local integrations belong in the localization scope.

• Requirements that materially affect the operation of the China business require a formal design decision.

• Requirements based mainly on existing user habits should generally be addressed through process alignment, training, or change management.

Making these distinctions requires more than product knowledge. The project team needs people who can work directly with China finance, IT, supply chain, and operations teams in Chinese, understand the local process detail, and translate it into structured decisions for the global program.

Without that capability, local concerns are often misunderstood or raised too late. The result is usually scope creep, delayed sign-off, and design decisions being reopened during testing.

What China localization actually includes

The term “China localization” is sometimes used too broadly. In a Dynamics 365 project, it usually refers to a defined set of statutory, financial, technical, and operational capabilities required by the China legal entity.

China entities must comply with Chinese Accounting Standards and local requirements for bookkeeping, vouchers, audit trails, tax processing, and statutory financial reporting. These requirements affect the initial setup of the legal entity, including the chart of accounts, financial dimensions, voucher management, reporting formats, and mapping to the group accounting structure.

The project also needs to determine how China statutory reporting will coexist with headquarters reporting and consolidation requirements. In many cases, the same transaction data must support both local statutory outputs and group management reporting.

VAT invoicing introduces another important workstream. Dynamics 365 provides China-specific tax and reporting capabilities, but companies often require additional configuration or local integration to connect sales and finance processes with the applicable invoicing and tax platforms.

The design may need to cover:

• Invoice request and approval

• Customer and item tax information

• Invoice data transmission

• Invoice number and status updates

• Red-letter invoice and cancellation processes

• Incoming invoice matching and reconciliation

• Electronic invoice storage and archiving

China’s continued transition toward digital electronic invoicing also means that the integration approach needs to remain adaptable as platforms, interfaces, and operating requirements evolve.

Local banking adds another layer. Domestic banks may use payment files, statement formats, communication protocols, and security requirements that differ from the global banking model. E-banking integration must therefore be designed and tested against the specifications of the selected bank rather than treated as a standard global interface.

These requirements should be identified during fit-gap analysis, included in the solution blueprint, and validated before development begins.

The architecture decision that deserves more attention

The deployment architecture should be evaluated early.

The main question is whether the China operation should run as a legal entity within the existing global Dynamics 365 environment or require a China-hosted environment operated by 21Vianet.

For many multinational programs, adding the China entity to the global environment is the preferred starting point. It supports common governance, group reporting, master-data alignment, and closer control of the global template.

The main practical consideration is cross-border performance.

Access to cloud infrastructure hosted outside mainland China may introduce latency. This may be manageable for finance and office-based users, but it can create difficulties for warehouse scanning, manufacturing execution, shop-floor transactions, or local systems that require frequent real-time communication with Dynamics 365.

The decision should therefore be based on actual transaction volumes, response-time requirements, user locations, and integration patterns.

Some organizations address performance through network optimization. Others use a hybrid operating model in which Dynamics 365 manages finance, planning, procurement, and group reporting, while a local warehouse or manufacturing system handles high-frequency execution.

A 21Vianet-operated deployment should be evaluated when local data residency, regulatory, contractual, or industry requirements justify a China-hosted environment. Cross-border data transfer requirements under China’s data protection framework may also need to be assessed, particularly where personal or sensitive data is involved.

The China cloud is physically separated from the global environment and may involve differences in available functionality, release timing, integrations, and operating processes. The final choice should therefore come from a formal architecture, security, and compliance assessment rather than a general assumption about the China market.

Supply chain does not simplify at the border

Finance and tax usually dominate the early planning discussion. Supply chain and manufacturing gaps often become visible later, during workshops with local operations teams.

China manufacturing entities may support several business models within the same facility, including domestic sales, exports, subcontracting, sample orders, spare parts, repair services, and intercompany transactions. Each flow can involve different documentation, tax, inventory, and invoicing requirements.

Outbound logistics may include split shipments, customer-designated carriers, proof-of-delivery requirements, local transportation platforms, and third-party warehouses. These details can affect warehouse processes, invoicing, revenue recognition, and customer service.

Local procurement may also involve different supplier settlement practices, advance payments, invoice matching, quality inspection, and approval processes. Sales operations may require support for distributors, customer credit controls, rebates, marketplace orders, or local e-commerce channels.

The objective is not to redesign the entire global supply chain template for China. The project team needs to determine:

• Which global processes can be adopted without change

• Which processes require local configuration

• Which gaps require integration or controlled extensions

• Which local practices should be replaced through process standardization

These decisions should be made with both global process owners and China business users involved. A design approved only by headquarters may overlook critical operational details, while a design driven entirely by local preferences may weaken the global template.

Planning the rollout as a coordinated program

A China rollout cannot be designed by one team in isolation.

Headquarters typically owns the global template, architecture, security standards, and program governance. The China business understands local finance, tax, customers, suppliers, banking, and operating practices. The global implementation partner brings template knowledge, while the local partner provides China-specific regulatory, technical, and operational expertise.

The project design should clearly define ownership across these groups.

Key decisions include:

• Who approves deviations from the global template

• Who owns China localization requirements

• Who coordinates local banks, tax platforms, and third-party vendors

• Who signs off statutory reporting and financial processes

• Who validates local data and migration rules

• Who supports the China business after go-live

Clear ownership is especially important in bilingual and cross-border programs. Requirements may be understood differently depending on language, business background, and familiarity with the global template.

A strong local delivery team helps close this gap by translating local requirements into the language of the global program and explaining global design decisions in a way that the China team can act on.

Before design sign-off

Before the solution design is approved, the program should have clear decisions on:

• Global template deviations

• China statutory and tax requirements

• Local banking and invoicing integrations

• Deployment architecture and network performance

• Supply chain and operational gaps

• Data ownership and reporting rules

• Responsibilities across global and local teams

Any major item left unresolved will usually reappear during testing, cutover, or go-live preparation, when changes are more expensive and more disruptive.

A successful Dynamics 365 rollout in China begins with a disciplined design process: protect the global template, identify genuine local requirements, involve the right stakeholders, and make architecture and integration decisions early.

Part 2 will cover delivery execution, including project governance, testing, data migration, cutover, user adoption, go-live, and post-go-live support.

Huamei Soft is the Asia-Pacific headquarters of Sunrise Technologies, a Microsoft Inner Circle partner. We help multinational companies deliver Dynamics 365 projects in China through local compliance expertise, bilingual consulting, system integration, and cross-border project coordination.