ERP Migration & SelectionFree templatePDF, Excel, Word exportChina

China ERP Implementation Statement of Work Template

A vague statement of work is the usual root of ERP disputes. This template pins down scope, localization, timeline, assumptions and acceptance for an ERP project in China, whether you use a local or global package.

Fill in

Live preview
Download:

China ERP Implementation Statement of Work Template

Statement of Work

Customer: Hengda Machinery Co., Ltd. Partner: Example Systems Integration Ltd. ERP: Kingdee Cloud Galaxy Legal entities: 2 legal entities, 1 plant Named users: 120

1. Scope

Modules in scope: Finance, Procurement, Sales, Inventory, Production, Quality

Anything not listed is out of scope and handled through change control.

2. China localization

The project covers statutory requirements agreed in the design phase, including: VAT and fapiao integration with the tax platform in use, bilingual master data, Chinese language reports and statutory financial reporting formats. Details are recorded in the design document.

3. Timeline

PhasePlanned dateDeliverable
Start2027-01-11Project charter and plan
Design sign-offBusiness blueprint
Data migration trial loadsTwo completed trial loads
User acceptance testingSigned test scripts
Go-live2027-07-01Cutover complete

4. Assumptions

Customer provides subject matter experts for each module. Legacy data is available in an agreed extract format. Fee basis: Fixed price with change control. Changes to scope require a signed change request.

5. Acceptance

Each deliverable is accepted when it meets the criteria agreed in the design document and the customer signs the acceptance form within an agreed number of business days.

Approvals

Customer project sponsor / Date
Partner project director / Date

A starting point, not legal advice. Have the final statement of work reviewed by your legal counsel and align it with the master services agreement.

Independent SOW review

Optional: an expert read of your ERP statement of work.

Optional. The tool and every export work without this. No spam.

How to use it

Fill the fields, export to Word and edit the text to suit your situation. Keep module scope explicit and list entities, plants and named users, because licences and effort follow those numbers. Attach the detailed requirements and the data migration approach as appendices so they have the same contractual weight as this document.

What to be explicit about

In China projects the most disputed items are the tax platform integration, bilingual data, report formats and who supplies each integration endpoint such as bank, e-fapiao service or MES. Name the responsible party for each. State what happens when a regulation changes between signature and go-live.

  • Interfaces with the tax and bank platforms
  • Number of mock loads and who runs them
  • Training scope and language
  • Hypercare duration after go-live

Common mistakes

Scope described only by module name leaves room for argument. Use process lists. Another mistake is acceptance without criteria, which lets either side delay sign-off. Define criteria per deliverable. Finally, do not leave change control to a sentence; add a simple request, estimate and approval flow.

Frequently Asked Questions

Is this tied to Kingdee or Yonyou?

No. The ERP name is a field. The structure suits any ERP project, including SAP, Oracle, Dynamics or Infor in China.

Should fees be fixed price?

Fixed price needs a tight scope and change control. Time and materials suits unclear scope. Many projects blend both.

How long should hypercare be?

Commonly a few weeks to a quarter depending on size. Set it in the SOW so support expectations are clear.

Is this legal advice?

No. Have counsel review the final document.

If you need a second opinion on scope or want an independent view of an ERP SOW, Netray is happy to look at it.