This is Part 2 of a two-part series on rolling out Microsoft Dynamics 365 in China. [Part 1] covers planning and design, including global template governance, China localization scope, deployment architecture, and supply chain fit.

A successful Microsoft Dynamics 365 rollout in China depends on how well the project moves from design into execution. Governance, bilingual collaboration, China-specific testing, cutover readiness, user adoption, and post-go-live support all shape the final outcome.

The second half of a China D365 deployment is where a well-designed project either holds together or begins to lose control.

Governance across teams, time zones, and languages

A Dynamics 365 rollout in China typically involves three core groups: the global ERP program team or headquarters IT, the global implementation partner, and the China business and IT teams.

Each group works with different priorities and may have different assumptions about the project’s status, scope, and outstanding decisions. The governance model should therefore define decision rights early.

Who approves a deviation from the global template? Who has final authority over China statutory requirements? Who resolves conflicts between global standards and local operational needs?

When ownership is unclear, decisions are often deferred until user acceptance testing, increasing pressure on the delivery team and creating additional go-live risk.

Another common issue is that China teams may not fully surface local requirements during global project meetings conducted in English. Language is only one factor. Communication styles, organizational dynamics, and the difficulty of explaining detailed local compliance or operational concerns in a global workshop can all limit participation.

Requirements that remain unspoken during design often reappear during testing or after go-live.

Running dedicated Chinese-language workshops gives local finance, supply chain, operations, and IT teams more room to examine processes in detail. The outputs can then be translated into structured requirements, risks, and decisions for the global program.

This requires a delivery team that understands both sides of the project. Direct translation alone is not enough. The team needs to understand the China process, explain its business impact, and present it in a format that global stakeholders can evaluate and approve.

Testing how the China business will actually operate

User acceptance testing for a China rollout should validate complete business processes, including global template functionality and China-specific requirements.

Testing only the configuration differences from the global template can leave important gaps undiscovered.

China test scenarios may include digital invoicing and Golden Tax integration, local bank payments and reconciliation, statutory financial reporting, voucher numbering and continuity, domestic procurement, supplier settlement, warehouse processes, manufacturing transactions, and local third-party integrations.

These scenarios should be tested by the finance, operations, and IT users who will own them after go-live.

Bilingual test materials also play an important role. China users working only with English-language scripts may need more time to understand the scenarios, document defects, and explain process concerns.

Chinese or bilingual test cases, expected results, defect templates, and operating procedures improve test coverage and make issue resolution more efficient across local and global teams.

The same principle applies to UAT sign-off. Approval should come from users who understand both the statutory requirement and the actual operating process. A technical test result alone does not confirm that the business is ready.

Planning the China cutover

Cutover follows the same core mechanics as other Dynamics 365 go-lives, but several China-specific dependencies require explicit planning.

Opening balances in D365 must reconcile with the China statutory ledger. This usually requires sign-off from the China CFO, financial controller, or another locally accountable finance leader. The review may need more time than the global project schedule originally allows.

Digital invoicing or Golden Tax integration should also be validated end to end in the production environment. Successful testing in a non-production environment does not confirm that production certificates, permissions, external connections, and platform configurations are ready.

Local bank integrations create similar dependencies. Payment files, statement formats, security certificates, communication protocols, and approval workflows may need to be confirmed directly with the bank or its technical service provider.

These activities often sit partly outside the ERP project team, which makes early coordination essential.

The China cutover plan should clearly cover opening balances, master data, inventory, open transactions, bank accounts, invoicing, user access, local interfaces, scheduled jobs, and production readiness sign-off.

Hypercare also requires local coverage. Headquarters teams can manage platform-level incidents, but China financial closing, invoicing, banking, and local integration issues often need rapid support in Chinese.

Building user adoption before go-live

For many China finance and operations teams, the rollout may be their first experience with Microsoft Dynamics 365.

Training models that work for experienced global users may therefore be insufficient. Short refresher sessions or self-service learning modules provide limited support when users are learning a new platform, new global processes, and new responsibilities at the same time.

A practical adoption plan should include role-based training in Chinese, bilingual standard operating procedures, realistic business scenarios, and hands-on system practice.

A structured super-user program is equally important. Super users should be selected and trained before go-live so they can support end users, reinforce process adherence, and retain knowledge within the China organization.

Without internal capability, routine questions continue to flow back to the implementation partner long after the project has ended. This increases support costs and makes it harder for the business to maintain consistent processes.

User adoption should therefore be treated as part of delivery readiness, alongside data migration, testing, and cutover.

Keeping China localization current after go-live

A Dynamics 365 configuration that meets China requirements at go-live will still need to evolve.

Digital invoicing platforms, tax requirements, statutory reporting, banking interfaces, and data protection obligations can change over time. Microsoft Dynamics 365 releases and updates may also affect local extensions and integrations.

Post-go-live support should therefore cover more than break-fix incidents.

The support model should include regulatory monitoring, localization updates, interface maintenance, release impact assessments, regression testing, statutory reporting support, and Chinese-language user assistance.

There should also be a controlled process for moving localization updates into production without disrupting the global template or local operations.

This requires a support provider with both Dynamics 365 expertise and an active understanding of China’s regulatory and business environment.

Managing China as one connected delivery program

What makes China different from other rollout waves is the concentration of dependencies within one legal entity.

Statutory accounting, tax and invoicing, local banking, supply chain processes, bilingual governance, user adoption, cross-border architecture, and ongoing compliance maintenance all affect the same implementation.

Teams achieve better outcomes when these workstreams are managed as one connected delivery program.

Clear decision rights keep the project moving. Local-language workshops surface requirements earlier. Complete process testing improves readiness. China-specific cutover planning reduces production risk. Strong user adoption and post-go-live support help the system continue to operate effectively after the implementation team leaves.

Together, these disciplines allow multinational companies to protect their global Dynamics 365 template while giving the China business a system it can use, support, and maintain over time.

Huamei Soft is the Asia-Pacific headquarters of Sunrise Technologies, a Microsoft Inner Circle partner supporting multinational companies with Dynamics 365 delivery and localization in China.

Planning a Dynamics 365 rollout in China? Contact our team to discuss your project scope or request a localization fit-gap assessment.