Table of Contents
China payroll runs on a monthly RMB cycle with IIT withholding and city-specific social insurance and housing fund bases calculated in Chinese-language statutory filings — none of it maps cleanly onto a global HRIS's default country template. Treat your China Employer of Record as the system of record for China-specific compliance data, and design a deliberate, minimal, cadence-based data feed into headquarters covering headcount, cost, and compliance status — not a real-time mirror of every field. Granular employee personal information generally should not flow cross-border without a PIPL-compliant legal basis (security assessment, certification, or standard contract, plus a PIPIA and often specific consent). Currency translation, FX mechanics, and China's July contribution-base reset and March–June annual IIT reconciliation all need to be planned around your HQ close calendar rather than assumed to align with it.
Table of Contents
- The Integration Challenge: Why China Payroll Doesn't Just "Plug In"
- How Global HRIS Platforms Handle Multi-Country Payroll — and Where China Breaks the Model
- What Data Should Flow From Your China EOR to Global HQ
- What Should Stay in China: PII, PIPL, and the Limits of "Export Everything"
- Currency and FX: From RMB to Your Consolidated Reporting Currency
- Reporting Cadence Mismatches: China's Calendar vs. Your Close Calendar
- A Practical Integration Model: EOR as the System of Record for China
- Data Flow at a Glance: A Comparison Table
- Building the Integration: A Step-by-Step Approach
- Knit Client Snapshot: Integrating China Headcount Into a Global HRIS
- Common Pitfalls When Connecting China to a Global System
- Governance: Who Owns What Between HQ, the EOR, and IT/Legal
- Frequently Asked Questions
- Glossary of Key Terms
- Related Reading
1. The Integration Challenge: Why China Payroll Doesn't Just "Plug In"
Most global HRIS and payroll platforms are built around a "core plus country extension" model: a standard data schema for employee records, compensation, and org structure, with country-specific fields layered on top for local variations. For many markets, that layering is manageable — a few extra tax fields, a local benefits code, a different pay frequency. China is not one of those markets.
China's payroll and HR compliance system runs on assumptions that simply do not exist in a typical global HRIS default configuration:
- Individual Income Tax (IIT) is withheld monthly on a cumulative basis within the calendar year, using tax tables and deduction rules that reset annually and reconcile the following spring — a structure most global systems have no native field for.
- Social insurance and housing fund contributions China's "five insurances and one housing fund, are calculated against city-specific contribution bases, which are capped and floored by local government notices that change annually, typically each July. Shanghai's bases differ from Shenzhen's, which differ from Beijing's — a level of localization far below what a country-level configuration field can capture.
- Statutory filings are submitted in Chinese, to local tax bureaus and social insurance administration systems, in formats that do not export cleanly into an HQ system's standard payroll register template.
- Employment contracts, work permits (for expatriate staff), and union-related documentation carry compliance weight that a global HRIS's generic "contract type" dropdown was never designed to represent.
The result: adding "China" as a country in a global HRIS is rarely a matter of flipping a toggle. It requires a deliberate data-mapping exercise — deciding what China-specific data actually needs to reach headquarters, in what form, on what schedule, and through what legal mechanism. Companies that skip this step tend to end up with one of two failure modes: a China entity (or EOR engagement) that operates as a disconnected silo HQ can't see into, or an attempt at full data replication that creates compliance exposure under China's data protection law. Neither is a data problem you want discovered during a board reporting cycle or an audit.
This is precisely the design question a well-run Employer of Record engagement in China should answer before day one of hiring, not after the first payroll cycle surfaces a reconciliation gap.
2. How Global HRIS Platforms Handle Multi-Country Payroll — and Where China Breaks the Model
Global HRIS and payroll orchestration platforms typically fall into two categories relevant to this discussion: platforms that run payroll calculations natively per country, and platforms that serve as a system of record while payroll execution happens through in-country providers (whether a local payroll vendor, a PEO, or an EOR). For companies hiring in China without a wholly owned local entity — a very common structure given China's entity-registration timelines and capital requirements — the second model is the norm, and the EOR effectively becomes the "local payroll engine" whose outputs need to be summarized and fed upward.
The friction shows up in three places:
Field-level mismatches. A global HRIS's compensation module usually expects a single "gross pay" and "net pay" figure per pay period, sometimes with a handful of statutory deduction categories. China payroll output naturally decomposes into IIT withheld, employee-side social insurance and housing fund contributions (which reduce net pay), and employer-side social insurance and housing fund contributions (which sit on top of gross as an employer cost, not a deduction from the employee). Mapping that decomposition into a generic global schema without losing information takes explicit design, not a default template.
Currency and unit mismatches, covered in more depth in Section 5, where RMB figures need translation into a reporting currency using a defined rate convention.
Cadence mismatches, covered in Section 6, where China's monthly filing cycle and annual reset events don't automatically line up with a global close calendar built around US, European, or other market timelines.
None of this means China should be excluded from global reporting — quite the opposite, since leaving China's headcount and cost data out of consolidated reporting creates its own blind spot for finance and HR leadership. It means the integration has to be designed rather than assumed, with a clear view of which system is authoritative for which data element. For background on how EOR structures work generally before diving into the China-specific mechanics, see Knit's guide to what an Employer of Record is and the executive guide to EOR total cost of ownership and compliance.
Knit practical tip #1: Before your China EOR processes its first payroll run, get IT, finance, and HR together to agree on the exact field-level mapping between China payroll outputs and your global HRIS's compensation schema. Doing this once, deliberately, is far cheaper than reconciling twelve months of mismatched categories at year-end.
3. What Data Should Flow From Your China EOR to Global HQ
Not all China HR and payroll data needs to travel to headquarters, and — as Section 4 explains — much of it legally shouldn't without a specific basis. But a defined subset should flow upward on a reliable cadence, because HQ genuinely needs it for global planning, consolidated reporting, and risk oversight. Three categories cover the vast majority of legitimate use cases:
Headcount and org-chart data. Global workforce planning, budget headcount tracking, and org-chart tools need to know how many people are employed in China, their reporting lines, job titles or levels (mapped to a global job architecture where one exists), start dates, and department or cost-center assignment. This is largely structural data — it supports global reporting without requiring granular personal detail.
Cost data — gross-to-net summaries translated into the reporting currency. Finance needs consolidated labor cost data for budgeting, board reporting, and — increasingly — ESG and workforce-cost disclosures. What typically flows here is a summarized gross-to-net breakdown per employee or per cost center: total employer cost (gross pay plus employer-side social insurance and housing fund contributions), net pay disbursed, and the statutory deduction totals, translated into USD, EUR, GBP, or whichever currency HQ consolidates in. The underlying calculation detail — city-specific contribution base tables, IIT bracket application — generally stays with the EOR as the specialist system.
Compliance-status data for global HR risk dashboards. HQ legal and HR risk functions typically want status flags rather than underlying documents: is the employment contract current and correctly renewed, is any required probation period documentation in place, and — critically for companies with expatriate staff in China — is the work permit and residence permit status current and within its validity window. A "green/amber/red" status feed serves this purpose without transmitting the underlying permit numbers or personal identifiers that created the status.
The pattern across all three categories is the same: aggregate, summarize, or status-flag the data before it crosses the border, rather than exporting the underlying record-level detail wholesale.
Knit practical tip #2: Build your China data feed around three output files or API objects — headcount/org, cost summary, and compliance-status — rather than trying to sync every field in the China EOR's system in real time. A narrower, well-defined feed is both easier to maintain and easier to defend to a regulator or auditor.
4. What Should Stay in China: PII, PIPL, and the Limits of "Export Everything"
The most common mistake foreign companies make when connecting a China EOR engagement to a global HRIS is treating it like any other country: pointing the global system's standard data-sync connector at China and letting it pull everything — full employee records, ID numbers, bank account details, home addresses, health information, dependent data — into the same HQ database that holds every other country's employee file.
This is a real compliance risk under China's Personal Information Protection Law (PIPL), which governs cross-border transfers of personal information originating in China. PIPL does not prohibit cross-border data transfer, but it conditions it on meeting one of several legal mechanisms, generally depending on the volume and sensitivity of the data and the nature of the data handler:
- A security assessment organized by the Cyberspace Administration of China (CAC) — required for higher-volume or more sensitive transfers, or for transfers by operators meeting certain thresholds.
- Certification by a CAC-recognized professional institution for cross-border processing.
- A filed standard contract for cross-border transfer of personal information, executed between the China data exporter and the overseas recipient, and filed with the local provincial cyberspace authority — the mechanism many mid-sized employers use for routine HR data flows.
Whichever mechanism applies, PIPL also generally requires a Personal Information Protection Impact Assessment (PIPIA) — an internal risk assessment of the transfer — before the transfer takes place, and in many cases separate, specific consent from the employee for the cross-border transfer itself, distinct from general consent to data processing. Employee personal information collected for domestic HR administration in China was not, by default, collected with a cross-border transfer already in view.
The practical implication: "just export everything to the global HRIS so we have one system" is a common instinct but a risky default. It converts what should be a scoped, purpose-limited data flow (headcount counts, cost summaries, compliance status) into a bulk transfer of sensitive personal information that may trigger the higher-threshold PIPL mechanisms, requires a PIPIA that likely was never performed, and may lack the specific employee consent PIPL expects.
This connects directly to a broader theme in cross-border hiring: data compliance risk doesn't stop at the employment contract. Knit's guide on hiring abroad without a foreign entity covers the related permanent-establishment and data-compliance questions that arise whenever headcount data crosses a border without a deliberate legal basis.
Knit practical tip #3: Treat "what data does this specific HQ system actually need, for what specific purpose" as the first question — not "what data can we technically pull." A purpose-limited data flow is both the PIPL-compliant approach and, in practice, the easier one to maintain, since it doesn't require re-mapping personal data fields every time the China EOR's local systems change.
5. Currency and FX: From RMB to Your Consolidated Reporting Currency
China EOR payroll is run, disbursed, and filed in RMB — Chinese law requires domestic wage payment and statutory filings in RMB regardless of where the employing company is headquartered. Global HQ finance, however, typically consolidates labor cost reporting in a single reporting currency: USD, EUR, GBP, or another currency depending on where the parent entity reports.
A few conventions matter here, at a general level (exact treatment should follow your company's own accounting policy and current guidance from your finance and audit function):
- Translation timing. Most companies translate monthly payroll cost figures using either the exchange rate on the payroll disbursement date or an average rate for the reporting period, applied consistently period over period. Using a spot rate on an arbitrary date, inconsistently, is a common source of unexplained variance in consolidated labor-cost reports.
- Rate source consistency. Whatever rate source is used (a central bank reference rate, a corporate treasury rate, or a payroll provider's own quoted rate) should be documented and applied consistently, so month-over-month cost trends reflect actual labor cost changes rather than FX-source noise.
- Realized vs. reporting-only translation. Translating RMB payroll cost into USD for a management report is different from actually moving funds cross-border. The former is a reporting exercise; the latter requires a licensed mechanism for compliant fund movement.
On that second point, this is where Knit's own Money Services Business (MSB) license becomes directly relevant to the integration question, not just a back-office detail. Moving client funds cross-border to cover in-country payroll disbursement — and doing so in a way that's licensed, auditable, and compliant with both China's foreign exchange controls and the client's home-jurisdiction requirements — depends on holding the right regulatory status for cross-border payment activity. Knit holds MSB License No. M23187879, which is the mechanism that allows client payroll funds to move compliantly between a client's home-country account and the RMB disbursement required for China payroll, without the client needing to independently navigate China's foreign exchange approval process for each payroll cycle.
Knit practical tip #4: Ask your China EOR provider two separate questions, because they have separate answers: (1) what exchange rate convention will be used to translate RMB cost figures into your reporting currency for HQ dashboards, and (2) what licensed mechanism moves your actual payroll funding cross-border. A provider should be able to answer both clearly and specifically — a vague answer on the second question is a signal worth following up on before you commit.
6. Reporting Cadence Mismatches: China's Calendar vs. Your Close Calendar
Even with data mapping and currency translation solved, timing remains a structural mismatch that's easy to underestimate. China's statutory HR calendar runs on its own rhythm, and it doesn't reliably line up with a global HQ's monthly or quarterly close:
- Monthly IIT withholding and social insurance/housing fund filings happen every month, generally with filing deadlines in the following month — a cadence that's usually compatible with a monthly HQ close, but the exact filing and reconciliation dates in China may fall after your close date has already locked, meaning a given month's China cost figure delivered to HQ may be a close estimate rather than a fully reconciled final number.
- The annual social insurance and housing fund contribution-base reset, which most Chinese cities apply each July, changes the base against which contributions are calculated for the coming twelve months — sometimes materially, depending on how local average wage benchmarks have moved. This creates a cost step-change in the July or August reporting period that has nothing to do with headcount growth or compensation decisions, and can look like an anomaly on an HQ dashboard if it isn't flagged in advance.
- Annual IIT reconciliation, which typically runs March through June of the following year, true-ups each employee's actual annual tax liability against what was withheld monthly, and can produce either a refund or an additional payment obligation. This reconciliation event has no direct equivalent in most other countries' payroll cycles and doesn't map onto a standard global HRIS's year-end payroll close process.
- Chinese public holidays (notably Spring Festival, which shifts dates each year on the lunar calendar) can shift both payroll processing and filing timelines by several business days in ways a Gregorian-calendar-based global close schedule doesn't anticipate.
None of this is a reason to avoid integration — it's a reason to plan for it. A workable approach is to treat the first China cost figure delivered each month as provisional, with a defined reconciliation step (for example, a quarterly true-up) that catches any adjustment from late filings, the July base reset, or the annual IIT reconciliation cycle. Building that reconciliation step into the HQ finance calendar up front avoids the alternative — quietly absorbing small China variances into a miscellaneous line item, which erodes the reliability of consolidated labor-cost reporting over time.
For a deeper look at how China's statutory wage-base calculations actually work — relevant background for anyone setting up the cost-data feed described in Section 3 — see Knit's explainer on what counts as "wages" for social insurance purposes in China.
7. A Practical Integration Model: EOR as the System of Record for China
The single most useful mental model for this entire integration question is deciding, deliberately, which system is the system of record for which data element — rather than defaulting to "the global HRIS should have everything" or "the China EOR should just send us whatever we ask for."
A workable division of responsibility looks like this:
- The China EOR is the system of record for China-specific compliance data: employment contract terms and status, statutory withholding calculations, city-specific social insurance and housing fund base determinations, work permit tracking for expatriate staff, and the underlying Chinese-language filings themselves. This is where the specialist compliance expertise lives, and where it should stay authoritative — a global HRIS has no mechanism to independently verify a Shenzhen social insurance base calculation, and shouldn't be asked to.
- The global HRIS/finance system is the system of record for global reporting outputs: consolidated headcount by country and department, consolidated labor cost by reporting currency, and a compliance-status dashboard aggregating risk flags across every country the company operates in, China included.
- A defined, minimal, one-directional (or scheduled two-directional) data feed connects the two, populated on an agreed cadence — commonly monthly, aligned as closely as practical to the HQ close calendar, with the reconciliation buffer described in Section 6.
This is a meaningfully different design goal from full real-time two-way synchronization of every field, which is both technically harder to build reliably (given the cadence mismatches above) and legally riskier (given the PIPL considerations in Section 4). It's also, in practice, the model most companies converge on once they've worked through the alternative and found it doesn't hold up — whether that's discovered proactively during integration planning or reactively after a data-flow problem surfaces.
Knit practical tip #5 (bonus, beyond the core four): Document the system-of-record decision in writing — a one-page data governance note naming which system owns which data element — and share it with both your HQ IT/data team and your China EOR's implementation contact. This single document resolves the majority of "wait, which system is right?" disputes that otherwise surface months into an engagement.
Knit's own approach to this is built into how our HR software and compliance management tools structure client-facing exports: designed to hand off exactly the headcount, cost, and compliance-status data categories described in Section 3, rather than exposing the full underlying China HR record for bulk extraction.
8. Data Flow at a Glance: A Comparison Table
The table below summarizes how the main categories of China EOR data typically should be handled when connecting to a global HRIS or finance system.
Knit practical tip #6: Use this table as a starting checklist in your own integration kickoff meeting — but confirm the specific legal basis and consent language for any PII flow with qualified counsel before implementation, since the right PIPL mechanism depends on your specific data volumes and sensitivity, which this general guidance cannot determine for your situation.
9. Building the Integration: A Step-by-Step Approach
A practical sequence for setting up a China-to-HQ data integration, once you've engaged a China EOR:
- Inventory HQ's actual reporting needs first. Ask finance, HR, and legal/risk teams separately what China data they actually use today, and for what decision. This usually produces a shorter list than "everything the global HRIS has a field for."
- Map that list against the three legitimate flow categories (headcount/org, cost summary, compliance status) from Section 3, and explicitly exclude anything that falls into granular PII without a confirmed legal basis.
- Confirm the PIPL mechanism with your China EOR and legal counsel for any data element that does involve personal information crossing the border, however summarized — even aggregated data can sometimes be re-identifiable at low headcounts, which is worth flagging to counsel specifically for small China teams.
- Agree on the FX translation convention and cadence with finance/treasury, and confirm how the EOR's cross-border fund movement mechanism (its MSB license or equivalent) interacts with your treasury's own banking setup.
- Set the data feed cadence against your HQ close calendar, building in the reconciliation buffer described in Section 6 rather than assuming a same-day match every month.
- Pilot with a defined file or API feed for one or two cycles before treating the numbers as final inputs to board-level reporting, so any mapping errors surface on a low-stakes cycle rather than a high-visibility one.
- Document the system-of-record split (Section 7) in a shared governance note, and revisit it annually — particularly around the July contribution-base reset and the March–June IIT reconciliation window, when China cost figures are most likely to need HQ-side context.
10. Knit Client Snapshot: Integrating China Headcount Into a Global HRIS
The following case study is anonymized and details have been generalized to protect client confidentiality.
A mid-sized industrial technology company headquartered in Europe, with an existing global HRIS covering roughly fifteen countries, engaged Knit as its China EOR to hire a small technical team in Shenzhen — initially six employees, growing to just under twenty over eighteen months. The company's global HRIS had a generic "add country" workflow that its regional HR lead initially assumed would work the same way it had for other Asia-Pacific markets.
Two issues surfaced quickly. First, the global HRIS's standard payroll import template expected a single net-pay figure per employee per month, with no field structure for China's employer-side social insurance and housing fund contributions as a distinct employer-cost line — the initial import materially understated true China labor cost in the company's consolidated headcount-cost dashboard. Second, the regional HR lead had initially requested a full employee data export, including ID numbers and home addresses, to populate the same employee-master fields used for other countries — a request Knit's implementation team flagged against PIPL cross-border transfer requirements before it was executed.
Working with Knit's implementation team, the company redesigned its China data feed around three elements: a monthly headcount/org-chart export mapped to the company's existing global job-level framework; a monthly cost summary breaking out gross pay, employee-side deductions, employer-side social insurance and housing fund contributions, and total employer cost, translated into EUR at a documented average-rate convention; and a quarterly compliance-status flag covering contract renewal status (no expatriate staff were involved in this case, so work-permit tracking wasn't part of the feed). Granular employee PII remained in Knit's China-specific systems as the system of record, accessible to the client's HR team through a secured portal rather than bulk export into the global HRIS.
The company's finance team also built a standing quarterly reconciliation step into its close calendar specifically for the China cost line, anticipating the July contribution-base reset and the following spring's IIT reconciliation period as expected — not anomalous — adjustments. Eighteen months in, China headcount and cost data now flows into the company's global workforce dashboard on a predictable monthly-with-quarterly-reconciliation cadence, with the underlying compliance detail retained where it has to be: with the EOR that has the specialist capability to manage it correctly.
11. Common Pitfalls When Connecting China to a Global System
- Treating China as a standard "add country" configuration, without a dedicated mapping exercise for IIT, social insurance/housing fund bases, and the gross-to-net decomposition described in Section 2.
- Bulk-exporting employee PII into the global HRIS's standard employee-master fields, without confirming a PIPL cross-border transfer legal basis first — the single most common compliance exposure in this integration pattern.
- Assuming a same-month reconciled close, when China's filing and reconciliation timelines routinely run a cycle behind, and building no buffer into the HQ close calendar for that gap.
- Missing the July contribution-base reset and spring IIT reconciliation in forecasting models, leading finance to misread a routine annual adjustment as a cost anomaly or a payroll error.
- Applying an inconsistent FX rate convention month to month, which makes genuine labor-cost trends indistinguishable from currency-translation noise in consolidated reporting.
- No documented system-of-record agreement, leaving HQ IT, finance, and the EOR each assuming a different system is authoritative for a given data field — a gap that typically surfaces during an audit or a leadership data request, at the least convenient moment.
12. Governance: Who Owns What Between HQ, the EOR, and IT/Legal
Sustainable integration depends on clear, written ownership — not just at implementation, but as an ongoing operating model, since personnel turnover on both the HQ side and the EOR side is where undocumented arrangements tend to break down. A workable governance split typically assigns:
- HQ HRIS/IT team: owns the receiving-side data schema, the import/mapping logic, and access controls on whatever China data does land in the global system.
- HQ finance/treasury: owns the FX translation convention, the reconciliation calendar, and the relationship with the EOR's cross-border fund-movement mechanism.
- HQ legal/data privacy function: owns the PIPL legal-basis determination for any personal information in the flow, in coordination with the EOR's China compliance team and, where the volumes or sensitivity warrant it, outside PRC counsel.
- The China EOR: owns the underlying China compliance system of record, the statutory calculations and filings, and the design of the defined data feed described in Section 3 — and should be able to explain, specifically, what data it does and does not send onward, and why.
The bullets above describe ownership in prose; in practice it's often more useful to have the same split laid out function-by-function, so a specific decision — "who signs off on the PIPL legal basis for this particular data element" — has one clear answer rather than three plausible ones. The table below is meant to sit alongside the data-flow table in Section 8, not repeat it: Section 8 answers what moves and how it should be handled, while this one answers who is accountable for each governance decision along the way.
As with the ownership list above, this table is a starting template rather than a fixed allocation — the right split depends on how a given company's IT, finance, and legal functions are actually structured, and it's worth walking through each row explicitly with your China EOR's implementation contact rather than assuming the default holds for your organization.
This governance clarity matters beyond China integration specifically — it's the same discipline that protects a company against misclassification exposure when contractor relationships are involved, a related risk area covered in Knit's global contractor misclassification audit guide. The common thread across both is that clear, written ownership of compliance-sensitive data and decisions is what actually reduces risk — not the sophistication of the integration technology layered on top of it.
13. Frequently Asked Questions
Can our global HRIS run China payroll calculations natively?
Most global HRIS platforms are not built to independently calculate China's city-specific social insurance and housing fund bases or apply current IIT withholding tables — this calculation work is generally best left to a specialist system, such as a China EOR's payroll engine, with summarized results feeding the global HRIS rather than the reverse.
How often should China cost data be updated in our global system?
Monthly is the most common cadence, aligned as closely as practical to your HQ close calendar, with a quarterly (or at minimum annual) reconciliation step to true up any figures affected by China's own filing timelines, the July contribution-base reset, or the spring IIT reconciliation period.
Do we need employee consent to send China payroll data to our HQ system?
Often yes, in addition to whichever PIPL cross-border transfer mechanism applies (security assessment, certification, or filed standard contract) — PIPL generally expects separate, specific consent for cross-border transfer of personal information, distinct from general HR data-processing consent. Confirm the specific requirement with qualified PRC counsel based on your data volumes and content.
What's the difference between a security assessment, certification, and a standard contract under PIPL?
These are three distinct legal mechanisms for cross-border personal information transfer under PIPL, generally applying based on data volume and sensitivity thresholds and the nature of the data handler. A CAC security assessment is the most stringent, typically required for higher-volume or more sensitive transfers; certification is conducted by a recognized professional institution; a filed standard contract is a template agreement filed with the relevant provincial cyberspace authority, commonly used for more routine HR data flows. Which applies to your situation should be confirmed with counsel.
Should expatriate employee data be treated differently from local Chinese employee data in this integration?
Both are subject to PIPL when the data originates from processing within China, but expatriate work-permit and residence-permit status is often specifically relevant to HQ's global mobility and immigration risk tracking, so it's commonly included as a compliance-status flag (not underlying document data) even where other granular PII is excluded from the flow.
How does currency translation affect month-over-month labor cost comparisons for China?
If the FX rate convention isn't applied consistently, month-over-month changes in the RMB-to-reporting-currency rate can make China labor costs appear to rise or fall independent of any actual change in headcount or compensation — a common source of confusion in consolidated dashboards until a documented, consistent rate convention is adopted.
What happens to the China data feed if we later set up a wholly owned entity in China?
The data-mapping and PIPL considerations largely persist regardless of employer-of-record structure, since they stem from Chinese law governing personal information originating in China, not from the specific employment vehicle. Many companies that transition from EOR to a wholly owned entity keep a similar system-of-record split, simply moving the "China compliance system of record" role from the EOR to an in-house or locally contracted payroll function.
Can Knit help design this integration, not just run China payroll?
Yes — this is a standard part of onboarding for clients connecting China into an existing multi-country HRIS. Contact Knit's team to scope a data-mapping and cadence plan specific to your existing global systems.
14. Glossary of Key Terms
HRIS (Human Resources Information System): The core software system a company uses to store and manage employee data, org structure, and (often) payroll and benefits administration across its global workforce.
PIPL (Personal Information Protection Law): China's comprehensive data protection statute, which governs how personal information collected in China may be processed, stored, and transferred — including cross-border transfer to a company's headquarters or global systems outside mainland China.
System of Record: The single authoritative source for a given category of data — the system whose values are treated as correct when other systems disagree, used in this context to describe which platform (the China EOR vs. the global HRIS) owns which data element.
PIPIA (Personal Information Protection Impact Assessment): A risk assessment required under PIPL before certain personal information processing activities, including most cross-border transfers, evaluating the necessity, scope, and risk of the proposed data handling.
Five Insurances and One Housing Fund: China's mandatory social insurance and housing fund contribution system, comprising pension, medical, unemployment, work-related injury, and maternity insurance, plus the housing provident fund — calculated against city-specific contribution bases that are reset annually, commonly each July.
IIT (Individual Income Tax) Reconciliation: China's annual process, typically running March through June of the following year, in which an employee's actual annual tax liability is calculated and compared against amounts withheld monthly, resulting in either a refund or an additional payment.
About Knit
Knit is a Canada-founded global HR and payroll company with 11 years of experience serving over 4,000 clients across 172 countries and regions, processing more than USD 600 million in annual payroll through a network of 60+ owned entities worldwide. Knit operates a dedicated China operations hub in Shenzhen and holds MSB License No. M23187879, enabling compliant cross-border payroll fund movement for clients hiring in China and beyond. To discuss how to integrate a China Employer of Record engagement into your existing global HRIS and finance systems, contact Knit's team or explore Knit's Employer of Record services.
15. Related Reading
- What Is an Employer of Record? A Guide to Global Expansion
- Global Employer of Record (EOR) Executive Guide: TCO & Compliance
- Hiring in China: What to Know and Why Use an EOR?
- China EOR Guide: What Counts as "Wages" for Social Insurance? A 2026 Compliance Explainer for Foreign Employers
This article is for general informational purposes only and does not constitute legal, tax, financial, or IT security advice. Integrating China EOR data into a global HRIS or finance system involves fact-specific legal considerations (including PIPL cross-border transfer requirements, which depend on your specific data volumes and sensitivity) as well as IT security and system-design considerations that vary by company. Before designing or implementing a specific data integration, confirm current PIPL, tax, and foreign exchange requirements with Knit's team and with qualified legal, tax, and IT security professionals licensed in the relevant jurisdictions.





