China payroll is a compliance process wearing a payroll costume

In many countries, payroll is a calculation: gross pay, minus tax and deductions, equals net. In China it is a compliance process with several moving parts that a generic payroll module does not model. Social insurance and the housing fund — collectively the five insurances and one fund, 五险一金 — are administered locally, with bases and contribution rules that vary by city. Individual income tax is withheld monthly using a cumulative method, so the amount withheld changes through the year even at constant salary. And the tax authority now administers much of the system, so payroll data has to reconcile with tax filings. An ERP that treats China payroll as 'the standard payroll engine with a local tax table' will produce an answer that is arithmetically fine and operationally wrong.

The five components an ERP must handle

These are the pieces that separate a China-capable payroll from a generic one. Each is a real requirement, not a nicety.

  • Social insurance: pension, medical, unemployment, work-injury, and maternity contributions, computed on a local base with employer and employee shares.
  • Housing fund (住房公积金): contributions on a locally defined base, with city-specific caps and rates.
  • Individual income tax: monthly withholding using the cumulative method, with special additional deductions and year-end settlement reconciliation.
  • Local variation: bases, caps, and rules that differ by city and are updated periodically, so the configuration must be maintainable, not hard-coded.
  • Filing reconciliation: payroll data that ties to the tax and social-insurance filings, with a visible audit trail.

Why the cumulative method matters to system design

Under the cumulative withholding method, the tax withheld in a given month depends on cumulative income and cumulative deductions to that point in the year, not just that month's salary. The practical effect is twofold. First, net pay for a constant salary can change as the year progresses, which surprises employees and payroll teams who expect a flat number. Second, the calculation needs full historical data for the year, so it cannot be reconstructed month by month in isolation. An ERP must therefore hold the year's cumulative position and recalculate reliably, including for joiners, leavers, and mid-year adjustments. Systems that compute tax month by month on that month's figures will be wrong, and the error compounds.

Where global and China-native systems diverge

The split is familiar from tax and invoicing. Global HR and payroll systems often provide a China payroll 'localization' that handles the tax table but requires local configuration and manual upkeep for social insurance and housing fund bases. China-native platforms and dedicated payroll services build the five components in as the default, because Chinese companies use them from day one. For a foreign-invested entity with a small China headcount, a dedicated local payroll service integrated with finance is frequently the pragmatic answer; for a large manufacturing entity with hundreds of employees across sites, a system that models social-insurance variation by city is worth real money.

Cost and control considerations

Payroll carries sensitive personal data, which links it back to the data-residency question: employee records are exactly the kind of data the cross-border rules are most concerned about, so keeping payroll in a China region and reporting only aggregates to a foreign parent is the usual pattern. Beyond compliance, the cost question is upkeep. Social-insurance bases and caps change, special deductions change, and a payroll system that is not maintained produces silent errors that surface as employee complaints or filing mismatches. When you evaluate a system, ask who maintains the local rules and how changes are delivered — that answer tells you more than any feature list. For the wider China compliance picture, see the ERP checklist for foreign companies in China.

Year-end reconciliation and the annual settlement

Because income tax is withheld on a cumulative basis through the year, the year-end position has to be reconciled rather than assumed. The settlement process compares what was withheld with what was ultimately due, and employees with additional income, multiple employers, or changes in deductions may need to settle a balance. For the finance team, the important consequence is that the payroll system must be able to reproduce the year's figures and explain them employee by employee, because questions at year-end are personal and specific. A system that can only produce monthly totals makes the settlement a manual reconstruction, and one that cannot reconcile makes it a source of disputes.

Foreign employees and assignees

Expatriates add a layer of complexity that generic payroll configurations handle poorly. Their social-insurance treatment may differ, their income tax position depends on residence status and treaty provisions, and their compensation often includes housing, schooling, and other benefits whose tax treatment is specific. For a foreign-invested enterprise with even a handful of assignees, this is a strong argument for a system — or a service — that has genuinely modelled the expatriate case rather than approximating it with the domestic calculation. Ask a prospective vendor to walk through an assignee's monthly calculation, not just a local employee's; the difference in maturity is usually obvious within minutes.

Build or buy: how to decide

Payroll in China is a genuine build-or-buy decision, and the answer depends on headcount and complexity rather than on a preference for owning software. For a small entity, a specialist local payroll service that delivers a validated result each month is usually cheaper and safer than configuring a module and maintaining it in-house. For a larger entity with multiple sites, city-specific rules, and an integration requirement into finance, an in-system capability earns its place because it links payroll to the ledger and removes a recurring reconciliation. The deciding question is not which is more powerful but which produces fewer errors per month for the effort it requires — and for most organisations that is a straightforward calculation once the maintenance burden is counted honestly.

How to test a payroll system in a demo

Payroll demos are easy to stage and easy to see through, if you insist on your own data. Bring three employee cases and require the vendor to run them live: a standard local employee with a mid-year salary change, a new joiner who starts partway through a month, and an assignee whose compensation includes housing and schooling benefits. A system that handles the cumulative tax method correctly will produce month-by-month figures that change as the year progresses, and will recalculate cleanly when you alter an earlier month. A system that approximates will produce a constant monthly tax figure or fail when you change history. Ask, finally, who maintains the city-specific bases and caps and how often updates are delivered — the answer tells you whether the localisation is a product or a promise.