HRIS and payroll integration in China should do more than move employee data from one system to another. A reliable integration needs to define which system owns each field, how approved employee changes reach payroll, what happens when data is rejected, and how payroll results reconcile back to HR and finance.
This becomes especially important for multinational companies that use a global HRIS while China payroll is processed through a local payroll engine or outsourced payroll provider.
The HRIS may contain the employee’s job, salary and organizational information, while the China payroll process maintains local payroll inputs, statutory records, calculation results and payroll history. If ownership is unclear, the same employee can end up with different salary, start-date, location or status information in different systems.
This guide focuses on the integration layer between HRIS, China payroll and finance. It does not compare HR software products or explain how to choose an HRIS. For technology-selection questions, use HROne’s China HR technology guide.
If you are implementing a completely new payroll process and preparing for the first live payroll, use the separate China payroll implementation guide.
Key Takeaways
- The HRIS should not automatically become the source of truth for every China payroll field.
- Each employee and payroll field should have one defined system of record and one owner.
- APIs can automate data exchange, but validation, approvals, error handling and reconciliation remain necessary.
- Salary changes should be effective-dated and approved before they become payroll inputs.
- New hires, terminations and employee transfers require more than a simple active/inactive status sync.
- Payroll outputs should reconcile with HRIS headcount, employee payments and finance or general-ledger records.
- Manual files can still form part of a controlled integration where direct APIs are unavailable, provided ownership, version control and reconciliation are clear.
What Does HRIS and Payroll Integration Mean in China?
HRIS and payroll integration connects the company’s employee system of record with the process used to execute payroll in China.
A typical multinational structure may look like this:
- the global HRIS manages employee master data, organization structure and approved compensation;
- a local China payroll system or payroll provider performs local payroll execution;
- attendance or leave systems supply payroll-relevant time information;
- finance or ERP receives payroll accounting results;
- banking processes execute employee payments; and
- local statutory systems maintain required tax and benefit records.
Integration connects these systems without making them interchangeable.
The HRIS may be authoritative for an employee’s position and approved salary, for example, while payroll remains authoritative for the final payroll calculation. Finance may own the accounting entry, while the bank record provides evidence of the actual payment.
The objective is therefore not to create one database that owns everything. It is to create a controlled chain in which each system owns the information it is responsible for and passes the required data to the next process.
Start by Defining the System of Record
One of the most important decisions in an HRIS-payroll integration is identifying the authoritative source for every data object.
If two systems can independently change the same field, payroll teams may not know which value should be used.
| Data object | Possible system of record | Integration rule |
|---|---|---|
| Employee legal name | HRIS or controlled employee master | Changes should follow an approved identity-update process |
| Employee ID | HRIS | Use one stable identifier across HRIS and payroll |
| Employment status | HRIS | Payroll should receive effective-dated joiner, leave and termination events |
| Job title | HRIS | Payroll receives the field only where it is required for payroll or reporting |
| Department and cost center | HRIS or finance master | Must map consistently into payroll accounting output |
| Approved base salary | HRIS or compensation system | Only approved and effective-dated salary changes should enter payroll |
| Attendance | Attendance system | Payroll receives approved payroll-relevant results rather than uncontrolled raw records |
| Leave | HRIS or leave system | Only leave with payroll impact needs to flow into payroll calculation |
| Payroll calculation | China payroll system | Calculated payroll results should not be overwritten by HRIS |
| Payroll history | Payroll system or controlled payroll archive | Historical values should remain traceable by payroll period |
| Accounting entry | Finance / ERP | Payroll output should map to approved GL accounts and cost centers |
| Salary payment | Bank record | Final bank payment should reconcile to approved payroll |
The system-of-record matrix should become part of the payroll operating documentation rather than remaining only in the original implementation project.
Which Data Should Flow From HRIS to China Payroll?
The integration should transfer the fields payroll actually needs rather than copying the entire HRIS employee profile.
Common HRIS-to-payroll fields may include:
- employee ID;
- legal name;
- identity information required for payroll administration;
- employment start date;
- employment status;
- termination date where applicable;
- work location;
- payroll location;
- department;
- cost center;
- job title where required;
- base salary;
- recurring allowances;
- approved compensation changes;
- working-time arrangement;
- approved payroll-relevant leave;
- approved variable-pay inputs where maintained in the HRIS; and
- other fields agreed during payroll setup.
China payroll may also require local fields that a global HRIS does not maintain in a usable format. These should be identified during field mapping rather than added informally after payroll begins.
Some of these fields support statutory payroll administration rather than ordinary HR reporting. For example, China’s IIT withholding rules require employers or other applicable withholding agents to maintain employee information and apply cumulative withholding to resident employees’ salary and wages. HRIS-to-payroll mapping should therefore preserve the employee identifiers, effective dates and year-to-date information needed by the local payroll process.
Build a Field-Mapping Dictionary Before Connecting Systems
The same piece of information may have different names, formats and allowed values in the HRIS and payroll system.
For example, one system may record employment status as:
- Active
- Leave
- Terminated
while another system may require several local payroll statuses.
A field-mapping dictionary should define:
| Mapping item | What to document |
|---|---|
| Source field | The HRIS field supplying the information |
| Destination field | The corresponding field in the China payroll process |
| Data type | Text, number, date, code, Boolean or another accepted format |
| Allowed values | Permitted codes or classifications |
| Transformation | Any conversion required between systems |
| Required / optional | Whether payroll can process the employee without the field |
| System owner | The system allowed to originate or change the value |
| Business owner | The function responsible for approving the information |
| Effective-date rule | When a change should affect payroll |
| Validation | What conditions must be satisfied before the record is accepted |
| Error treatment | What happens when the record fails validation |
The mapping should also identify fields that deliberately do not move between systems.
For example, a global HRIS may need an employee’s payroll status and total compensation result for reporting but may not need employee bank-account information, detailed medical leave documentation or every statutory payroll field.
API, File Transfer or Portal: Which Integration Method Should You Use?
There is no single integration architecture that is appropriate for every China payroll.
The right method depends on employee volume, frequency of changes, system capabilities, internal IT resources, security requirements and how much automation the business actually needs.
Direct API integration
An API can allow approved employee data to move between systems automatically.
It may be appropriate when:
- employee volumes are significant;
- changes occur frequently;
- the HRIS is expected to remain the long-term employee system of record;
- the payroll environment supports stable interfaces; and
- the organization has resources to maintain and monitor the integration.
An API does not remove payroll controls. The design still needs validation, approvals, logging, rejected-record handling and reconciliation.
Secure structured file exchange
Many payroll integrations can operate effectively through controlled CSV, Excel or other structured data files exchanged through an approved secure channel.
This may be appropriate when:
- employee volume is moderate;
- payroll changes are concentrated around a monthly cutoff;
- a direct API would add unnecessary development complexity;
- the payroll provider uses a defined input template; or
- the company wants stronger human review before data enters payroll.
A file-based process should still define one source file, version control, required fields, approved users, submission deadlines and reconciliation totals.
Middleware or integration platform
A middleware layer can transform data between HRIS and payroll when the two systems use different formats or when several local payroll providers connect to one global HRIS.
The integration layer should not become an undocumented place where business rules are hidden. Transformations, field ownership and error handling should remain visible to HR and payroll teams.
Portal-supported payroll workflow
Where a direct system-to-system integration is not required, a payroll portal can provide a controlled interface for data submission, review and payroll reporting.
The key question is not whether the process is fully automated. It is whether employee changes move through a controlled, traceable and reconciled workflow.
Do Not Let Automation Bypass Payroll Approval
One common integration mistake is assuming that an approved HRIS record should immediately become a live payroll instruction.
Payroll often needs a controlled cutoff and review process.
A safer workflow may look like:
- HR enters the employee change in the HRIS.
- The required business or HR approval is completed.
- The approved record becomes eligible for payroll transfer.
- The integration validates required fields and effective dates.
- Payroll reviews accepted and rejected changes.
- The approved payroll population is frozen for the payroll period.
- Payroll calculation begins.
- Finance or another authorized reviewer approves the final payroll result.
This prevents an HRIS correction made during payroll week from silently changing salary after the payroll population has already been reviewed.
Salary Changes Need Effective Dates, Not Just New Values
Compensation integration should preserve both the value and the date from which the value becomes effective.
For every salary change, payroll should receive:
- employee ID;
- old salary where needed for validation;
- new salary;
- effective date;
- change reason;
- approval status;
- approval reference where applicable; and
- the date the change entered the payroll process.
Without an effective date, payroll cannot reliably determine which payroll period should use the new salary or whether a retroactive adjustment is required.
Do not overwrite payroll history
If an employee’s salary changes from RMB 20,000 to RMB 25,000, the integration should not make it appear that the employee was always paid RMB 25,000.
HRIS and payroll records should preserve the historical effective period of each compensation change.
New-Hire Integration Requires More Than Creating an Employee Record
A successful new-hire sync should tell payroll not only that an employee exists, but also when and how the employee should enter payroll.
The integration should confirm:
- employee ID;
- legal name;
- employment start date;
- legal employer;
- work and payroll location;
- base salary;
- recurring allowances;
- working-time arrangement;
- department and cost center;
- bank information where handled through the integration;
- required payroll identifiers;
- benefit information relevant to payroll; and
- whether the employee is ready for the next payroll cycle.
The integration should also distinguish between:
- an employee record that has been created;
- an employee who has accepted employment;
- an employee whose start date is confirmed; and
- an employee who is ready to enter live payroll.
These statuses should not be treated as identical.
Payroll onboarding also needs to connect the employee to the employer’s statutory administration. China’s Social Insurance Law requires employers and individuals in China to participate in and contribute to the applicable social insurance system. Integration design should therefore distinguish ordinary HRIS fields from the local information required to support payroll and statutory administration.
Housing fund administration is a separate process. The Housing Provident Fund Regulations establish the framework for employer and employee housing fund contributions. Where the payroll provider supports housing fund administration, the HRIS-payroll design should identify which employee and contribution fields are required locally rather than assuming that the global HRIS already contains them.
Offboarding Must Sync the Right Dates and Final-Payroll Instructions
Terminations are another high-risk integration point.
Simply changing an HRIS status from Active to Terminated is not enough.
Payroll may need:
- last working day;
- employment termination date;
- final payroll period;
- approved final salary treatment;
- unused leave information;
- bonus or commission instructions;
- approved expenses;
- approved deductions;
- severance or settlement instructions where applicable;
- cost-center treatment;
- system-access end date; and
- other approved final-payroll inputs.
The employee should not disappear from payroll merely because an HR administrator closed the HRIS record before final payroll was completed.
Handle Other Employee Changes as Structured Events
Payroll-relevant employee changes should be transferred as controlled events rather than arbitrary field updates.
Examples include:
- salary increase;
- promotion;
- department change;
- cost-center change;
- work-location change;
- payroll-location change;
- recurring allowance start or stop;
- extended unpaid leave;
- return from leave;
- bank-account change;
- bonus eligibility change; and
- termination.
Each event should have an effective date, source, approval status and audit trail.
Define What Happens When Integration Data Fails
An integration should never silently discard an employee record.
Typical validation failures may include:
- missing employee ID;
- duplicate employee ID;
- invalid effective date;
- missing salary;
- unsupported work or payroll location;
- unknown cost center;
- invalid bank information;
- missing required payroll field;
- unexpected employment status; or
- duplicate change event.
The integration design should define:
| Control | Required outcome |
|---|---|
| Validation | Identify invalid records before they affect payroll |
| Reject queue | Keep failed records visible rather than silently dropping them |
| Error reason | Explain which field or rule caused the failure |
| Owner | Assign the correction to HR, payroll, finance, IT or the provider |
| Resubmission | Allow corrected records to be processed without duplication |
| Audit log | Record the original submission, correction and final result |
A successful file transfer does not necessarily mean a successful payroll integration. The company needs evidence that every expected record was accepted or deliberately rejected.
Use Control Totals to Check HRIS-to-Payroll Data
Individual field validation should be combined with population-level reconciliation.
Before payroll calculation begins, compare control totals such as:
- active employee headcount;
- new hires;
- terminations;
- salary changes;
- total base salary;
- total recurring allowances;
- employees by legal entity;
- employees by payroll location;
- employees by department or cost center; and
- rejected integration records.
For example, if HRIS shows 148 active employees but payroll contains only 147, the difference should be explained before payroll is approved.
What Data Should Flow Back From Payroll?
Integration does not always need to be one-way.
After payroll is processed, selected information may need to flow back to HRIS, finance or reporting systems.
Possible payroll outputs include:
- payroll period;
- payroll processing status;
- gross salary;
- variable earnings;
- employee deductions;
- net salary;
- employer payroll cost;
- payroll correction status;
- payslip availability;
- YTD values where required for reporting; and
- other approved reporting fields.
Not every downstream system needs every employee-level payroll field. The output should follow the reporting purpose and applicable data-access rules. China’s Personal Information Protection Law requires personal information processing to have a clear and reasonable purpose and to remain within the scope necessary for that purpose. A global HRIS or finance system should therefore receive the employee-level payroll information it actually needs rather than automatically receiving the complete payroll dataset.
For the detailed privacy framework affecting salary data, bank information, payroll providers and overseas headquarters access, see HROne’s payroll data privacy guide for China.
Connect Payroll to Finance and the General Ledger
HRIS-to-payroll integration solves only one side of the data flow. The payroll result must also reconcile with finance.
The payroll-to-finance mapping should define how payroll elements are posted to:
- salary expense accounts;
- bonus and commission accounts;
- allowance accounts;
- employer contribution accounts;
- employee deduction liabilities;
- tax liabilities;
- benefit liabilities;
- net salary payable;
- department or cost-center dimensions; and
- other required accounting categories.
Create a payroll-to-GL mapping
| Payroll element | Finance mapping | Control |
|---|---|---|
| Base salary | Salary expense | Reconcile employee and cost-center totals |
| Bonus | Bonus expense | Match approved variable-pay population |
| Employer statutory contributions | Employer benefit expense | Reconcile payroll calculation to liability |
| Employee deductions | Payroll liability | Confirm deduction totals |
| IIT withheld | Tax payable | Reconcile payroll output to reporting process |
| Net salary | Salary payable | Reconcile to approved bank-payment total |
The accounting export should use the same approved payroll result that generated the employee payment. Finance should not rebuild payroll expense from a separate spreadsheet after payroll has been finalized.
Reconcile HRIS, Payroll, Bank and Finance
Integration is complete only when the systems can be reconciled end to end.
A monthly reconciliation should connect:
| Comparison | What to verify |
|---|---|
| HRIS vs payroll population | Joiners, active employees, leavers and approved employee changes |
| HRIS compensation vs payroll input | Approved salary and recurring compensation |
| Payroll input vs payroll result | All approved changes were processed |
| Payroll result vs bank payment | Approved employee net-pay population and total |
| Payroll result vs finance | Gross expense, employer cost, deductions, liabilities and net pay |
| Payroll result vs downstream reporting | Employee and management reporting uses the finalized payroll result |
Automation can reduce manual reconciliation work, but it should not eliminate independent control totals.
Keep an Audit Trail for Every Payroll-Relevant Change
A reliable integration should make it possible to answer:
- Which system originated the change?
- Who entered it?
- Who approved it?
- What was the previous value?
- What is the new value?
- When does the change become effective?
- When was it transmitted to payroll?
- Was it accepted or rejected?
- Which payroll period processed it?
- Was the payroll result later corrected?
This is particularly important for salary, bank, work-location, employment-status and variable-compensation changes.
The audit trail should survive the integration itself. If the HRIS shows only the newest salary and payroll shows only the final result, the employer may lose evidence of how a change entered payroll.
What Should You Test Before Activating an HRIS-Payroll Integration?
Integration testing should focus on data flow and controls rather than duplicating the entire payroll implementation process.
Representative scenarios should include:
- new hire;
- future-dated new hire;
- salary increase;
- retroactive salary change;
- department change;
- cost-center change;
- work-location change;
- bank-account change;
- leave affecting payroll;
- employee termination;
- rejected employee record;
- duplicate change event;
- integration interruption;
- corrected and resubmitted record; and
- payroll-to-GL output.
The test should confirm that:
- the correct records leave the source system;
- required approvals are preserved;
- effective dates arrive correctly;
- valid records are accepted;
- invalid records are visible in the exception process;
- resubmitted records do not create duplicates;
- employee changes reach the correct payroll period; and
- downstream payroll and finance totals can be reconciled.
For full payroll implementation testing, parallel payroll, cutover and first-live-payroll controls, use the China payroll implementation checklist.
Common HRIS and Payroll Integration Mistakes in China
Assuming the global HRIS should own every field
Some China payroll and statutory fields belong in the local payroll process. The integration should define ownership instead of forcing every local field into the global HRIS.
Building an API before defining the business process
An API can automate a bad workflow just as effectively as a good one. Define field ownership, approvals, effective dates and error handling before development begins.
Sending every HRIS field to payroll
Payroll should receive the information it needs. Unnecessary employee data increases complexity and privacy exposure.
Letting unapproved salary changes flow directly into payroll
Integration should preserve the company’s compensation approval and payroll cutoff controls.
Using employee name as the integration key
Names can change or be entered differently across systems. Use a stable employee identifier for matching records.
Ignoring effective dates
A new value without its effective date can create incorrect current-period or retroactive payroll treatment.
Silently dropping rejected records
Every expected record should be accepted or appear in a visible exception process.
Integrating onboarding but not offboarding
Joiners receive significant integration attention, but leavers can create greater payroll risk if termination dates and final-payroll instructions do not synchronize correctly.
Stopping reconciliation because the interface is automated
Successful transmission does not prove that the employee population, salary, payroll result, bank payment and GL posting are correct.
Building excessive China customization into the global HRIS
Local requirements should be supported, but the company should first determine which fields genuinely belong in the global HRIS and which can remain within the local payroll execution layer.
What Good HRIS and Payroll Integration Should Look Like
A well-designed integration should make payroll easier to control, not harder to understand.
The company should be able to identify:
- one authoritative source for each important field;
- a stable employee identifier across systems;
- a documented field-mapping dictionary;
- effective-dated employee changes;
- visible approval status;
- controlled payroll cutoffs;
- clear rejected-record handling;
- traceable joiner and leaver events;
- reconciled payroll outputs;
- defined payroll-to-GL mapping;
- role-based data access; and
- an audit trail from HR change to payroll result.
The goal is not maximum automation. The goal is reliable automation with visible controls.
How HROne Can Work Alongside Your Existing HRIS
Companies do not necessarily need to replace their global HRIS to operate China payroll effectively.
Where the company has its own mainland China employing entity, HROne’s China payroll outsourcing service can provide the local payroll execution layer while the client continues to maintain its chosen HRIS for employee and group-level data.
During payroll onboarding, the parties can align on:
- employee master-data requirements;
- payroll input templates and data flows;
- salary and payroll-element mapping;
- monthly cutoff dates;
- client approvals;
- employee onboarding and offboarding updates;
- payroll reports;
- finance outputs;
- data handover responsibilities; and
- payroll portal access.
HROne’s payroll portal can support payroll visibility, employee-data submission and reporting alongside the client’s existing HR systems. The exact technical interface—including whether information is exchanged through structured files, portal workflows, APIs or another agreed method—should be confirmed during project scoping rather than assumed.
This allows the client’s HRIS to remain part of its global HR architecture while China payroll is executed through a locally supported operating process.
Companies planning to connect an existing HRIS with China payroll can contact HROne to review the system architecture, data fields, payroll workflow, approval requirements and reporting needs.
This article provides general payroll and systems-integration information and does not constitute legal, tax, cybersecurity or data-protection advice. The appropriate integration architecture depends on the systems involved, employer structure, employee population, payroll scope, data flows, security requirements and technical capabilities of the parties.
Frequently Asked Questions
Can a global HRIS integrate with a China payroll provider?
Yes. A global HRIS can remain the employee system of record while a local payroll provider executes China payroll. The parties need to define field ownership, data format, approval rules, effective dates, error handling and reconciliation.
Does HRIS and payroll integration require an API?
No. Integration may use APIs, middleware, secure structured files, controlled portal workflows or a combination of methods. The appropriate method depends on system capabilities, employee volume, frequency of changes and the organization’s control requirements.
Which system should own employee salary?
The approved compensation record may sit in the HRIS or a separate compensation system, while payroll should own the calculated payroll result. The company should define one authoritative source for the approved salary value and its effective date.
Should payroll update the HRIS automatically?
It can, where useful. Selected finalized payroll information may flow back into HRIS or reporting systems, but the company should define which fields are required and avoid returning unnecessary employee-level payroll data.
How should new hires move from HRIS into payroll?
The integration should transfer the employee’s stable identifier, start date, employment status, payroll-relevant personal information, compensation, location, cost center and other required fields. It should also distinguish between a record being created and the employee being ready for live payroll.
How should terminations be synchronized?
Payroll should receive the relevant employment and last-working dates together with approved final-payroll inputs. The employee should not simply disappear from payroll when an HRIS status changes to terminated.
How should salary changes be integrated?
Salary changes should include an effective date and approved value. The integration should preserve the approval status and ensure the change reaches the appropriate payroll period without overwriting historical compensation records.
What happens when an HRIS record fails payroll validation?
The record should enter a visible exception process with an error reason and named owner. After correction, it should be resubmitted in a way that prevents duplicate payroll changes.
How should HRIS and payroll be reconciled?
Compare employee population, joiners, leavers, compensation changes and other payroll-relevant records between HRIS and payroll. After calculation, reconcile payroll with bank payments, finance outputs and downstream reporting.
Can payroll integrate with the general ledger?
Yes. Payroll elements can be mapped to finance accounts and cost centers so the finalized payroll result produces a controlled accounting output. The GL totals should reconcile with the approved payroll register.
Does HROne provide a payroll portal?
HROne’s China payroll service can use an online payroll portal to support payroll data submission, visibility and reporting. The exact portal functions and technical integration scope should be confirmed for the specific project.
Do we need to replace our HRIS to use HROne payroll?
Not necessarily. HROne can support local China payroll alongside a client’s existing HRIS. The parties should first agree on the data handoff, payroll inputs, approval process, reports and technical interface required for the specific project.
