HR software in China must do more than store employee profiles. It should maintain authoritative employee and contract data, feed payroll, support monthly individual income tax withholding, handle city-specific social insurance and housing fund rules, control attendance and leave, produce payslips and reports, and preserve a recoverable audit trail. Buyers must also define the system of record, local-rule owner, data handoffs, payroll approver and contingency process.
This guide covers mainland China employees under an employment relationship and is written for international employers comparing HRIS, payroll software and service-supported HR technology. Information was checked on July 20, 2026. For the complete gross-to-net and statutory workflow, see HROne’s China payroll guide.
What must a China-ready HR system manage?
A global HRIS can remain the group’s employee-data source, but it is not automatically a China payroll engine. Approved data must reach payroll without losing effective dates, location or evidence.
| Process area | China-ready requirement | Buyer test |
|---|---|---|
| Employee and contract records | Chinese and English names, ID or passport, employer, work and payroll city, contract, probation and compensation history | Can it reproduce the effective-dated record used for a past payroll? |
| Payroll inputs | Salary, overtime, absence, variable pay, deductions, joiners, transfers and final pay | Are inputs approved and locked, with late changes logged? |
| Individual income tax | Cumulative withholding, year-to-date data, employee attributes, bonuses, corrections and filing outputs | Can each result be explained and reconciled to filing? |
| Social insurance and housing fund | Participation city, local bases, caps, rates, employer and employee amounts, transfers and adjustments | Are rules versioned by city and effective date? |
| Attendance and leave | Calendars, approved time, overtime, leave and payroll-relevant absence | Does payroll receive approved rather than editable records? |
| Approvals and segregation of duties | Maker-checker, payroll approval, bank authorization and restricted administration | Can one user create, approve and release payroll? |
| Payslips and reporting | Payslips, registers, variance and cost reports, finance entries and statutory outputs | Can each total be traced to approved data and calculation version? |
| Local change management | Rule monitoring, testing, approval, release notes and corrections | Who owns updates, and what proves pre-production testing? |
HRIS, payroll software and service models are not the same
| Model | Primary function | What it does not decide by itself | Legal employer |
|---|---|---|---|
| HRIS | Stores employee, organization, contract, compensation, leave and workflow data | Whether local payroll formulas, filings and benefit settings are current and correctly operated | The client entity |
| Payroll engine | Calculates gross-to-net pay, IIT, statutory contributions, deductions, payslips and payroll reports | Whether source HR, attendance and compensation instructions are lawful and complete | The client entity |
| Attendance and leave software | Captures schedules, time, absence, leave requests and approvals | Final wage, overtime, leave-pay or statutory contribution treatment | The client entity |
| HR outsourcing | A service provider performs selected HR administration for a company that employs its own staff | The employer’s management decisions, legal accountability and final approvals | The client entity |
| PEO support | Broader ongoing payroll, benefits and HR administration for a client with a China entity | A no-entity employment structure; the client ordinarily remains the employer | The client entity |
| EOR | Provides a local legal-employer structure together with payroll and employment administration | The client’s day-to-day direction of work and performance management | The EOR entity |
A license does not guarantee payroll operations, and outsourcing does not remove employer control over policies, approvals, funding and oversight. HROne’s China HR outsourcing guide covers the broader service model for companies with a China entity.
Which operating model fits the China workforce?
| Operating model | Best fit | Main advantage | Main control risk |
|---|---|---|---|
| Global HRIS plus a local payroll solution | Groups needing global records and a China calculation layer | Common HR data with local payroll logic | Unclear ownership, interface failures and mismatched dates |
| Local integrated HR and payroll platform | China teams wanting local HR, time and payroll together | Fewer local handoffs | Weak global integration or difficult exit exports |
| Client HRIS connected to outsourced payroll | Companies retaining their HRIS while outsourcing local payroll | HQ visibility with local execution | Ambiguous RACI, dependency and weak reconciliation |
| EOR-supported technology | Companies without a suitable China entity | Legal-employer and payroll structure | Confusing client HRIS data with controlling EOR records |
The no-entity model is a legal-employment decision, not a software choice. Only that scenario should be directed to China EOR; employers with an entity should compare software and outsourced operations.
China-localization feature matrix
| Localization area | Required capability | Evidence to request |
|---|---|---|
| Multi-city rules | City-specific bases, caps, rates, filings and effective dates | Configuration inventory and recent change release |
| Statutory contributions | Employer and employee calculations, adjustments and transfers | Specification, exceptions and filing reconciliation |
| IIT | Cumulative withholding, tax status, balances, bonuses and corrections | Test cases and filing-output mapping |
| Bonuses and commissions | Effective-dated rules, approvals, tax treatment and payslips | Bonus and retroactive-adjustment tests |
| Allowances and reimbursements | Separate codes, documents and policy-based treatment | Earning-code register and approvals |
| Chinese identifiers | Names, IDs, passports, bank and taxpayer data | Field dictionary, validation and masking |
| Audit trails | Change, calculation, approval, export and correction logs | Read-only log and retention settings |
| Local change management | Named owner, impact analysis, testing and deployment | Recent change ticket and test evidence |
China payroll and statutory benefits vary by city. A provider should explain how changes are identified, tested, approved and applied. The employer is generally the IIT withholding agent and must support monthly calculation, filing and remittance, ordinarily by the 15th day of the following month.
HRIS and payroll integration
A global HRIS and China payroll system should have clearly defined data ownership and handoff rules. Employers should confirm which system owns employee master data, compensation changes, payroll results and finance records, and how approved changes move between systems.
Integration design should also define validation, error handling and reconciliation rather than assuming that automated data transfer guarantees payroll accuracy.
For the complete framework covering APIs, field mapping, system-of-record ownership, approval workflows, employee lifecycle changes and payroll-to-GL reconciliation, see HROne’s guide to HRIS and payroll integration in China.
Employee data, PIPL and cross-border access
China HR and payroll systems process identity, contract, salary, tax and benefit data. Bank accounts, health, biometrics and some identity or location data can be sensitive. Under the Personal Information Protection Law, processing needs a lawful basis, necessary purpose, notice and security controls.
Consent is not a complete strategy. PIPL also recognizes processing necessary for an employment contract, HR management under lawfully established rules or collective contracts, and legal obligations. Identify the basis, minimize data, define retention, and obtain separate consent where required. Processor contracts should cover purpose, term, method, data types, protection, subcontracting and return or deletion; the employer must supervise performance.
Overseas access can be a cross-border provision even when users only view a global platform. The 2024 cross-border data provisions introduced exemptions and thresholds, including certain necessary cross-border HR management. They do not erase PIPL notice, separate-consent, impact-assessment or protection duties where applicable. Important data, sensitive information, volume, infrastructure status and sector rules affect the route.
Use least-privilege access, multi-factor authentication, encryption, controlled exports, logs, access review and deletion workflows. The amended Cybersecurity Law took effect on January 1, 2026. For broader employment-process controls, see HROne’s China HR compliance guide.
Payroll continuity: plan for failure before payroll week
Cloud delivery is not automatically safer, more resilient or compliant. Resilience depends on architecture, access, ownership, tested recovery, usable exports and a workable fallback.
| Failure scenario | Immediate payroll risk | Required contingency |
|---|---|---|
| HRIS outage | Employee changes are unavailable | Controlled extract, emergency change log and validator |
| Payroll-engine failure | Calculations and reports fail | Validated fallback, prior balances, dual review and reconciliation |
| Bank-interface failure | Payment cannot be transmitted | Alternate route, separate authorization and total controls |
| Statutory-portal downtime | Tax or benefit submission fails | Save files and evidence, monitor notices and submit when restored; do not assume an extension |
| Data corruption | Records or balances are unreliable | Stop, isolate, restore a verified copy and reconcile |
| Ransomware | Systems are unavailable or untrusted; data may be exposed | Isolate, activate response, restore clean backups and assess legal/privacy duties |
| Provider unavailability | Staff, access or submissions are unavailable | Backup contacts, exports, procedures, alternate approvers and transition plan |
Use a business impact analysis and set RTO and RPO
A business impact analysis identifies critical payroll activities, dependencies and disruption effects. RTO is the target restoration time; RPO is the maximum tolerable data-loss period. Set both from payroll and statutory deadlines and manual capacity, not vendor marketing. The NIST contingency-planning guide supports BIA, recovery priorities and testing.
Maintain a protected emergency payroll pack
- current employee master and employment-status extract;
- approved salary, bank and payroll-city data;
- year-to-date payroll, IIT and statutory contribution balances;
- current-period approved changes and attendance results;
- last approved payroll register and payslip format;
- calculation rules, earning codes and local configuration references;
- bank and statutory submission procedures;
- approval matrix, escalation contacts and employee communication templates; and
- post-recovery reconciliation and correction checklist.
Encrypt the pack, restrict access, keep a clean offline or isolated copy, record refreshes and test restoration. Recovery planning should include protected backups, clean restoration procedures and evidence that the restored data can support payroll.
Test alternate approvals and manual controls
Contingency processing must retain segregation of duties. Define emergency authorization, independent checks, payment release, logging and production reload. Exercise realistic scenarios, including an unavailable approver or provider, and close identified defects.
If payment or payslips may be delayed, communicate the confirmed impact, action, contact route and next update. After recovery, reconcile every payment, filing, contribution, payslip and ledger entry.
Distinguish an outage from a reportable incident
Not every interruption is externally reportable. An attack, vulnerability, fault, corruption or other event may meet cybersecurity or personal-information incident criteria. The national cybersecurity incident-reporting measures, effective November 1, 2025, require classification; their specified process applies to relatively major or more serious events, subject to operator and sector rules. PIPL notification duties require a separate assessment where personal information may be leaked, altered or lost.
Payroll, HR, finance, security, legal or privacy teams and the provider should preserve evidence, classify the event and meet applicable duties rather than reporting solely because an application was briefly unavailable.
Vendor due-diligence and RFP questions
| Area | Question | Evidence to request |
|---|---|---|
| China localization | Which cities and rules are supported, and who updates them? | Coverage matrix, change log and tests |
| Security and privacy | How are data, privileged access, encryption, logs, retention and incidents controlled? | Architecture, controls, audit evidence and access review |
| Cross-border processing | Where is data stored or accessed, and by which processors? | Data map, processor list and transfer terms |
| Integrations | How are interfaces validated, monitored and retried? | Specification, errors and ownership matrix |
| Availability evidence | What evidence and exclusions support availability claims? | Service reports and contract definitions |
| Disaster recovery | When were recovery and restore last exercised? | Exercise results, scope and remediation |
| Support and escalation | Who supports payroll deadlines and escalations? | Support model, severity, contacts and workflow |
| Subcontractors | Who hosts or processes data, and how are changes notified? | Subprocessor register and change terms |
| Data export | Can complete data and logs be exported in usable formats? | Sample export, dictionary and procedure |
| Exit assistance | How are handover, deletion and residual backups handled? | Exit schedule, fees and responsibilities |
Implementation and cutover
Choosing China-ready HR and payroll technology is only the first step. Before go-live, employers still need to migrate and validate employee data, map payroll elements, establish access and approval controls, test representative payroll scenarios, reconcile opening balances and complete a parallel payroll run.
For the complete project sequence from kickoff through cutover and first live payroll, use HROne’s China payroll implementation checklist.
How HROne can support the operating model
HROne can work alongside a client’s HRIS as an operational payroll and HR service provider. The technology, hosting and interface scope should be confirmed in the proposal rather than assumed to be proprietary HROne software. For companies with a China entity, China payroll outsourcing can support calculation, statutory coordination, reporting and approvals alongside client systems.
Employers can contact HROne to discuss systems, locations, responsibilities, interfaces and continuity. Confirm the exact scope, systems, data duties, recovery procedures and client approvals in the proposal.
Frequently asked questions
What should HR software in China include?
It should maintain employee and contract data, support payroll inputs, monthly IIT withholding, city-specific social insurance and housing fund administration, attendance, leave, approvals, payslips, reports and audit trails. The buyer must also confirm local rule ownership, integrations, data protection and payroll continuity.
Can a global HRIS run China payroll?
It can serve as the global employee system of record, but it should not be assumed to calculate or administer China payroll correctly. The employer may need a localized payroll engine or service layer with city-specific statutory settings, IIT logic, filing outputs and reconciliation back to the global HRIS.
Is cloud HR software automatically safer or compliant in China?
No. Cloud delivery can support access and managed operations, but security, resilience and compliance depend on the actual architecture, permissions, processors, data transfers, local configuration, backups, recovery testing and contractual controls. The employer must review the evidence rather than rely on the deployment label.
What should an employer do if the payroll system fails?
Activate the tested continuity plan, determine the affected systems and data, use a controlled emergency payroll pack and alternate approval or payment process, protect segregation of duties, communicate confirmed employee impacts and reconcile all emergency activity after recovery. Cybersecurity and privacy personnel should separately determine whether incident reporting or notification is required.
Should a company without a China entity buy payroll software or use an EOR?
Payroll software does not create a lawful local employer. A company without a suitable mainland China entity should first decide on the employment structure and may need an EOR. The EOR’s legally controlling employment and payroll records must then be reconciled with any client HRIS used for group reporting.
