NetSuite vs Yonyou for a China Subsidiary: What Changes Locally

The honest headline

NetSuite is an excellent cloud ERP for a mid-market group that wants one system, one chart of accounts, and one consolidation across countries. A China subsidiary is where that model meets its hardest test, not because NetSuite is weak, but because China's invoicing and tax architecture is not an accounting convention you can configure — it is state infrastructure your system has to connect to. Yonyou is the domestic alternative built the other way round: compliance is native and consolidation is the work.

So the comparison is not 'which is better'. It is 'how much consolidation do you need, and how much localization work are you prepared to own forever'. This article answers that by looking at what actually changes locally when a China subsidiary runs one system or the other.

Why NetSuite is the default for many groups — and where it stops

Mid-market groups standardise on a cloud suite for good reasons: a single data model, subscription pricing that scales with headcount rather than servers, fast deployment compared with on-premise enterprise platforms, and consolidation that works out of the box across entities and currencies. For a group with a handful of international subsidiaries, that combination is hard to beat, and it is why the China entity is often told to adopt the same platform as everyone else.

The friction begins with the invoice. In China, the invoice is a tax instrument issued through state-controlled infrastructure, tied to a tax registration, and reconciled against the accounting ledger and the periodic filing. A cloud ERP can record the accounting entry perfectly and still not be able to issue the document. Closing that gap requires a local integration and ongoing maintenance when formats change, and that is a different kind of obligation from the configuration work a global rollout normally involves.

The second point of friction is where the data sits. Cloud products are hosted in a region, and for a China entity the interplay between hosting location, the personal and financial data involved, and what transfers to the parent is a legal question as much as a technical one. We cover that in our guide to China data residency requirements. Many implementations resolve it by keeping the detailed China data in a China region and reporting mapped aggregates upward, which works but has to be designed deliberately.

What Yonyou gives you that a global suite does not

Yonyou is one of China's two largest domestic ERP vendors by common account, with product lines spanning small business through large group platforms and a cloud direction in recent years. For a foreign-owned China entity the relevant point is not its scale but the shape of its capability: Chinese tax, invoicing, statutory reporting, and payroll are part of the product surface, maintained as the rules change, and supported by a domestic partner network that is local by default.

In practical terms this means the flows that take months to build around a global suite are configuration in a domestic one. Issuing an invoice, handling a red-letter invoice, reconciling the invoice pool to the ledger, closing statutory statements on the Chinese calendar, and running payroll with social insurance and cumulative individual income tax are all inside the system's normal operating range.

What Yonyou does not give you is a free bridge into a parent's consolidation under a different framework. If the group consolidates in NetSuite or another global system, that mapping has to be built and owned, and it runs every period. Our guide to HQ consolidation from a China subsidiary describes how to structure that as a report rather than an annual exercise.

The six flows that decide the comparison

Rather than compare modules, compare the flows the China finance team performs. These six cover almost all of the practical difference.

• Invoice issuance and reversal: pushing to the Chinese invoicing infrastructure, including red-letter invoices, from inside the system.
• Supplier invoice verification: pulling the counterparty's invoice record back and matching before payment.
• VAT reconciliation: ledger VAT, the invoice pool, and the filed return tying to one number each period.
• Statutory close: Chinese statutory statements produced from the books, with the annual tax settlement supported.
• Payroll: social insurance, housing fund, and cumulative individual income tax calculated and maintained locally.
• Group reporting: statutory figures mapped to group accounting policies, with the bridge produced from stored data.

The first five are the reason a domestic system is often chosen. The sixth is the reason a global system often is. If you score both vendors across all six with a live demonstration rather than a reference call, the decision usually makes itself.

Scenario: one China subsidiary, foreign parent

This is the most common situation and the one where the tension is sharpest. The parent wants consistency and a reporting package; the subsidiary wants to stop doing compliance work in spreadsheets.

The pattern that works most often is a split: a China-native system for statutory compliance, invoicing, and tax, with mapped and aggregated figures reported into the group's platform. The split is cheap to run if the mapping is designed once and owned; it is expensive if it is rebuilt each period, which is the usual failure mode. The alternative — NetSuite with a localization layer — is entirely workable, and is the better choice when the parent consolidates in it and the China entity is material to group reporting, provided the localization is funded properly and has a named owner after go-live.

The failure mode to avoid is a global template bent to fit China through one-off customisations. It passes go-live, and then becomes unmaintainable when the person who built it leaves. Our article on why global ERP templates break in China sets out the four patterns behind that outcome.

Scenario: China as a manufacturing base for export

When the China entity manufactures for group customers or third parties abroad, the compliance stack deepens. Export tax refunds, foreign-currency settlement, customs documentation, and in some cases processing-trade arrangements all become relevant, and they touch operations as much as finance.

This scenario shifts the balance further toward a domestic system, because the export stack is deep, recurrent, and rule-driven, and global templates do not carry it natively. It is the same logic as Scenario 3 in our SAP vs Kingdee comparison: the more export-specific the operation, the more the local product's depth matters relative to the global platform's consistency.

Integration architecture: three patterns that work

If you adopt a split, or even if you adopt one system with a localization layer, the integration architecture determines whether the arrangement survives contact with an audit.

• Pattern A — single global suite plus a local compliance layer: NetSuite for the ledger and group reporting, with invoicing and tax connected through a maintained local integration. Works when the localization is funded and owned.
• Pattern B — dual systems with an owned bridge: a China-native system for statutory purposes, reporting mapped aggregates upward, with the statutory-to-group reconciliation produced as a standard report. Works when the mapping is stable and documented.
• Pattern C — dual systems with a one-way data push: local system exports a file the group imports. Works only for small entities with simple structures, and fails as soon as the mapping changes.

Pattern A and Pattern B are both defensible. Pattern C is the one that quietly accumulates risk, because it has no owner and no control, and the mapping drifts without anyone noticing until an audit asks a question the file cannot answer.

Total cost shape

The licence comparison is the least informative part of the exercise. What differs between the two options is where the recurring cost sits.

• With NetSuite: subscription per user plus a localisation integration build, recurring connector maintenance, and internal finance time owning the reconciliation.
• With Yonyou: domestic licensing and implementation, plus a reporting bridge to the group and the internal capacity to maintain it.
• Either way: parallel running during implementation, where the old and new processes must agree before the manual route is retired.
• Either way: the cost of the person who owns compliance after go-live. This is the line most often left blank and most often decisive.

A practical evaluation script

If you are running this selection now, these are the steps that produce a decision rather than a shortlist.

• Map the parent's actual consolidation requirement: full consolidation, or mapped aggregates? The answer removes about half the options.
• Write down the six flows above and score both vendors on demonstrated capability and on evidence, weighting per your business.
• Ask each vendor who fixes the connector when the tax authority changes a format, how fast, and at whose cost.
• Model the three-year cost including localisation maintenance, internal reconciliation time, and parallel running.
• Name the person who will own China compliance after go-live. If there is no name, treat that as a finding rather than a detail.
• Run a trial close with real data on the preferred option before signing, and compare the result with your current process.

The last step is the one teams skip and the one that changes decisions. A trial close on your own numbers will surface more about localization quality than any amount of reference checking, and it is far cheaper than discovering the same gap in the first month of live operation. For the underlying requirements list, see our ERP checklist for foreign companies in China.

Verdict

If the group consolidates in NetSuite and the China entity matters to group reporting, stay on NetSuite and fund the localization as a real product workstream rather than a configuration task. If the China entity operates largely independently, files Chinese taxes monthly, and the parent needs mapped summaries rather than a full consolidation, a Yonyou-based solution is usually the lower-risk choice, with the reporting bridge designed and owned from day one. Neither decision is wrong; the wrong decision is making it without naming who owns the gap between them.