The Real Cost Structure of IT Staffing in China (Part 3 of 3): Buyer Scenarios, Vendor Selection, and Strategic Recommendations

This is Part 3 of a 3-part industry research series. Part 1 (Commercial Models and Cost Structure Baseline) covers labor dispatch versus IT outsourcing and the full statutory cost baseline. Part 2 (Liability, Compliance, and Termination Risk) covers Article 92 joint liability, de facto employment, overtime/996, non-compete, IP ownership, dispute resolution mechanics, probation, maternity leave, and rebadging. This installment maps six recurring buyer scenarios to the right engagement structure and closes with a vendor-qualification framework and strategic recommendations.

Overview

Parts 1 and 2 of this series established the cost-structure baseline and the liability exposures international buyers inherit under labor dispatch and IT outsourcing. This closing installment is the applied, decision-oriented piece: six recurring buyer profiles mapped directly to the engagement structure the preceding analysis supports, a vendor-qualification framework procurement and legal teams can use in due diligence, and a consolidated set of strategic recommendations.

1. Six Common Buyer Scenarios and the Right Engagement Structure

Part 1 and Part 2 of this series establish the cost and liability mechanics underlying every China IT engagement. This section applies that framework to six recurring buyer profiles encountered in practice. A preliminary point applies to all six: Chinese law does not recognize "Employment of Record" (EOR) as a separate licensing category distinct from labor dispatch. Where a third party holds the labor contract while the buyer directs day-to-day work, that arrangement is, in legal substance, labor dispatch (Part 1, Section 2.1), regardless of the commercial label used to market it — and it is bound by the same 10% headcount cap and temporary/auxiliary/substitute role test. Separately, a foreign company with no PRC legal entity of its own cannot itself sign a PRC labor contract or act as a "user unit" under the Labor Dispatch Provisions; it must operate through a PRC entity — either its own, or a licensed vendor's.

1.1 International IT Service Main Contractor Sourcing Local Vendor Resources

Profile: A global or regional IT service integrator holding an end-client contract, subcontracting China-based engineering delivery to a local vendor, often without a PRC entity of its own.

Recommended structure: Pure outsourcing (Part 1, Section 2.2) — the local vendor delivers a defined scope through its own employees and its own PRC entity, invoicing the main contractor directly. This avoids the "user unit" question entirely, since no PRC entity of the main contractor is directing individual engineers.

Caveat: If the main contractor's project managers direct individual local engineers' day-to-day tasks — common in tightly integrated delivery teams — the arrangement risks re-characterization as disguised dispatch, and, where the main contractor does hold a PRC entity, Article 92 exposure (Part 2, Section 1.1). The main contractor should flow the vendor-qualification checks in Part 2, Section 3 down to the local vendor, and confirm any further subcontracting tier is equally compliant, since liability can travel through multiple layers.

Cross-border payment and foreign exchange settlement risk. This scenario frequently involves a payment structure with three distinct parties rather than two: the paying entity (the international main contractor or its offshore client), the actual end-user of the engineers' work — typically the main contractor's own China-based branch or affiliate, referred to here as the final client — and the Chinese vendor supplying the personnel. This is not a mechanical detail; it is a threshold bankability question. As of 2026, banks processing the domestic conversion (结汇) of cross-border payments for labor dispatch or staff-augmentation services generally require a complete tripartite agreement (三方协议) naming all three parties — the paying client, the final China-based end client, and the Chinese service provider — before they will even consider the settlement. Even where a compliant tripartite agreement is in place, banks frequently decline to approve the foreign exchange settlement for this category of payment: China's exchange-control framework is structured around the presumption that labor dispatch is a domestic RMB transaction between a PRC user unit and a licensed PRC dispatch agency (Part 1, Section 2.1), not a cross-border service payment, and cross-border remittances that functionally resemble dispatch payment routed through an offshore main contractor attract elevated scrutiny for exactly this reason. Main contractors and their China-based affiliates should confirm, before signing any contract, whether the intended cross-border payment flow is bankable at all under current SAFE (State Administration of Foreign Exchange) practice at the receiving bank — treating this as a go/no-go question to resolve upfront, not a payment-processing detail to work out once the engineers are already deployed.

Residual severance liability for the China-based final client. Where the international main contractor is the contracting party with the Chinese vendor, but the engineers are in fact performing work for a separate China-based final client, termination or non-renewal of the engagement triggers the same statutory severance obligations set out in Part 1, Section 3 — one month's pay per year of service ("N"), or N+1 where proper notice is not given (Part 2, Section 1.1's Article 92 analysis applies in parallel where dispatch is used). If the international main contractor — being outside China, and in some structures deliberately positioned to sit outside the reach of PRC enforcement — refuses or fails to fund this severance obligation, Chinese labor arbitration bodies look past the contractual chain to identify who actually directed the engineers' day-to-day work and benefited from it. In practice this is frequently the China-based final client: present in China, reachable by PRC enforcement, and liable to be found to hold a de facto employment relationship with the affected engineers under the doctrine set out in Part 2, Section 1.2, irrespective of its formal position as a downstream beneficiary rather than the direct contracting party. PRC labor arbitration attaches liability to substance — who controlled the work — not to position in a payment or subcontracting chain. Final clients in this structure should not treat their distance from the paperwork as protection; they should require contractual indemnification from the main contractor for any statutory severance shortfall as a condition of the arrangement, and should independently verify, rather than take on faith, that severance reserves described in Part 1, Section 3 are actually funded. This exposure recurs, often more acutely, whenever the main contractor "rebadges" the engagement to a new local vendor — see Part 2, Section 1.6 on termination mechanics and rebadging risk.

1.2 Local Enterprise Seeking Engineer Supply at a Monthly Rate, Without Labor-Law Liability

Profile: A PRC-domiciled enterprise wanting supplemental engineering capacity billed as a simple monthly rate, explicitly seeking to avoid severance, social insurance, and termination-related liability.

What is achievable: Genuine liability transfer is available only through properly licensed labor dispatch, and only within its statutory boundaries — roles that are genuinely temporary (≤6 months), auxiliary, or substitute, and capped at 10% of total headcount. Within those boundaries, the licensed dispatch agency legitimately carries the salary, statutory contribution, and severance liability, and the enterprise pays a monthly rate that embeds those costs (Part 1, Section 3).

What is not achievable: Using dispatch for a permanent core-team role, or exceeding the 10% cap, does not transfer liability — it creates Article 92 joint-and-several exposure and/or de facto employment risk (Part 2, Section 1), defeating the enterprise's own objective. Buyers in this scenario should size dispatched headcount and role mix against the statutory tests before pricing, not after.

1.3 Local Chinese Enterprise Seeking "Employment of Record" Only

Profile: A PRC-domiciled enterprise that already holds the legal capacity to hire directly, but wants a third party to serve purely as legal employer of record for a given engineer or team.

Legal reality: As noted above, there is no distinct PRC "EOR" category. For a domestic enterprise that can already hire directly, engaging a third party as "EOR" is, in substance, labor dispatch, and is subject to the same constraints as Scenario 1.2 — the 10% cap and the temporary/auxiliary/substitute test. A domestic enterprise cannot use an "EOR" label to place a permanent, full-time, core role outside the reach of the Labor Contract Law's dispatch restrictions.

Practical implication: Local enterprises requesting "EOR only" should be advised transparently that the service will be delivered as licensed labor dispatch, priced and structured as described in Part 1, Sections 2.1 and 3, and confined to roles and headcount that satisfy the statutory test — not marketed as a liability-free alternative to dispatch.

1.4 International Enterprise Seeking Full-Time Onsite Engineers, Accepting Full Labor-Law Liability

Profile: An international company that wants engineers embedded full-time, onsite, functioning as ordinary employees, and is willing to assume the full statutory cost and liability position of a direct PRC employer in exchange for maximum control and the cleanest legal structure.

Recommended structure: Direct employment through the international company's own PRC legal entity (WFOE, joint venture, or equivalent), issuing PRC labor contracts directly and funding the full statutory stack in Part 1, Section 3 — salary, five insurances and one housing fund, 13th-month pay, severance reserve — without an intermediating dispatch or outsourcing layer. Where the company does not yet hold a PRC entity, establishing one, or engaging a licensed payroll-processing/HR-administration provider that performs administrative payroll and compliance functions while the company remains the named contracting employer, is preferable to a dispatch or EOR structure that reintroduces the third-party employer of record the company is explicitly trying to avoid.

Advantage: Because the international enterprise is itself the sole legal employer, there is no Article 92 joint-liability question and no de facto employment risk — the company already holds the employment relationship it would otherwise be found to hold in substance. The trade-off is that it must build or contract for proper PRC payroll, tax withholding, and HR compliance capability, and bears the full fully loaded cost in Part 1, Section 3 directly, without a vendor absorbing any portion of the statutory or severance risk.

1.5 International Enterprise Building a Captive Global Capability Center (GCC)

Profile: An international company establishing its own China-based engineering center at scale — a "captive center" or GCC — rather than sourcing individual engineers, typically anticipating a headcount trajectory of dozens to hundreds of engineers over a multi-year horizon.

What is different from Scenario 1.4: The individual cost and liability mechanics are the same as direct employment (Section 1.4), but scale changes which questions matter most. Entity-setup lead time (typically several months for a WFOE, longer where the business scope requires specific approvals) should be sequenced against hiring plans, not treated as a formality that runs in parallel. Buyers should make an explicit build-versus-buy decision on payroll, tax withholding, and HR-compliance infrastructure — building in-house capability is rarely justified below a headcount threshold in the low hundreds, and a licensed payroll-processing/HR-administration provider (Section 1.4) is typically the more capital-efficient choice below that scale even where the buyer intends to be the direct legal employer.

Downsizing exposure: A GCC's headcount can move in both directions, and a reduction crossing 20 employees, or 10% of total workforce, whichever is lower, is treated under Article 41 of the Labor Contract Law as an economic layoff, not a series of individual terminations. This triggers a distinct procedural regime — advance consultation with the labor union or employee representatives, a required filing with the local labor authority at least 30 days ahead of implementation, and specific statutory priority-retention criteria for certain categories of employees (including, relevantly here, employees within the "three periods" discussed in Part 2, Section 1.7, who cannot be selected for economic layoff at all) — layered on top of, not instead of, the ordinary severance obligations in Part 1, Section 3 and Part 2, Section 1.6. Buyers planning for the possibility of downsizing at GCC scale should build this consultation-and-filing timeline into any restructuring plan from the outset, since it cannot be compressed after the fact by paying more severance.

1.6 Main Contractor Transitioning Engineers from Dispatch or Outsourcing onto a Direct WFOE

Profile: An international main contractor that has been sourcing engineers through a Chinese dispatch agency or outsourcing vendor (Scenario 1.1) and now wants to "flip" the existing team onto its own newly established PRC entity's direct payroll — commonly to gain control, to exit a rebadging cycle (Part 2, Section 1.6), or in response to the Article 14 open-ended-contract question becoming live for long-tenured engineers.

The question this report has not yet addressed: does the transition reset the severance clock? Generally, no. Where the transfer is arranged by the employer side — the engineer is moved to the new entity as a condition of the engagement continuing, rather than freely choosing to resign from one employer and separately apply to another — and the engineer continues performing essentially the same job, PRC practice treats the engineer's prior years of service as continuous for severance-calculation purposes even though the legal employer of record has changed. A main contractor that assumes a "clean start" WFOE transition zeroes out the accumulated severance exposure discussed in Part 2, Section 1.6 is very likely wrong, and should size its severance reserve on the engineer's full original tenure, not on the shorter period since the WFOE was established.

Practical sequencing: Because this is functionally the same seniority-carryover and outgoing-liability-settlement question addressed for rebadging in Part 2, Section 1.6, the same discipline applies — resolve, in writing, whether the outgoing dispatch agency or outsourcing vendor or the new WFOE bears any pre-transition severance shortfall, before treating the transition as complete, rather than assuming the question resolves itself simply because the new entity is under the buyer's own control.

1.7 Scenario Summary

• 1.1. Buyer profile: International main contractor sourcing local resources  Recommended structure: Pure outsourcing via the vendor's own PRC entity  Who holds statutory/labor-law liability: Local vendor, provided arm's-length management is preserved — but reverts to the China-based final client as de facto employer if the main contractor defaults on severance, and cross-border FX settlement may itself be refused by the paying bank
• 1.2. Buyer profile: Local enterprise wanting engineer supply, monthly rate, no liability  Recommended structure: Licensed dispatch, within the 10% cap and temporary/auxiliary/substitute test  Who holds statutory/labor-law liability: Dispatch agency, within statutory scope only — reverts to the enterprise if the scope is exceeded
• 1.3. Buyer profile: Local enterprise wanting "EOR" only  Recommended structure: Same as 1.2 — no separate EOR category exists in PRC law  Who holds statutory/labor-law liability: Dispatch agency, within statutory scope only — reverts to the enterprise if the scope is exceeded
• 1.4. Buyer profile: International enterprise, full-time onsite, accepts full liability  Recommended structure: Direct employment via the company's own PRC entity  Who holds statutory/labor-law liability: The company itself, by design
• 1.5. Buyer profile: International enterprise building a captive GCC at scale  Recommended structure: Direct employment via own PRC entity, with build-vs-buy HR infrastructure decision  Who holds statutory/labor-law liability: The company itself — plus Article 41 consultation/filing obligations if headcount is later reduced past the economic-layoff threshold
• 1.6. Buyer profile: Main contractor flipping dispatched/outsourced engineers onto a direct WFOE  Recommended structure: Direct employment via new PRC entity, with pre-transition severance settlement resolved in writing  Who holds statutory/labor-law liability: The new WFOE going forward — but on a severance clock that generally continues from the engineer's original hire date, not from the transition date

Frequently Asked Questions

How should procurement teams evaluate a below-market quote?

A below-market quote should trigger diligence on the specific items in Part 2, Section 2 of this series, particularly the social insurance contribution base and whether a severance reserve is genuinely funded. In the majority of cases, below-market pricing reflects deferred statutory liability rather than genuine cost efficiency.

Can Chinese banks refuse to settle cross-border payments for IT staff dispatch?

Yes, and as of 2026 this is a common outcome rather than an edge case. Where an international main contractor pays a Chinese vendor for staff supplied to a separate China-based final client, banks typically require a complete tripartite agreement naming the paying client, the final client, and the Chinese vendor before processing the domestic foreign exchange settlement (结汇) — and frequently decline to approve the settlement even when that agreement is provided, since China's exchange-control framework treats labor dispatch as a domestic RMB transaction rather than a cross-border service payment (Section 1.1). This should be verified with the receiving bank before contracting, not after engineers are deployed.

If an international main contractor refuses to pay severance, who is liable?

Where engineers sourced through a China vendor are performing work for a separate China-based final client, and the international main contractor that contracted with the vendor refuses or fails to fund statutory severance (N or N+1) on termination, PRC labor arbitration will typically look past the contractual chain to the party that actually directed the engineers' work. This is frequently the China-based final client, which can be found to hold a de facto employment relationship and bear the liability directly, regardless of its formal position as a downstream beneficiary rather than the contracting party (Section 1.1).

2. Strategic Recommendations for International Buyers

Based on the foregoing analysis, the following practices are recommended for procurement, legal, and finance functions overseeing China IT staffing and outsourcing relationships:

1. Model cost on a fully loaded basis from the outset, including expected annual escalation. Build internal benchmarks around the 30–45% statutory contribution range and the 35–50% fully loaded cost range set out in Part 1, Section 3, and budget the roughly 5% annual compounding increase in Part 1, Section 3.3 for any engagement running beyond a year, rather than anchoring evaluation to a headline monthly rate.
2. Align management practice with the chosen legal model. Where outsourcing is the contracted structure, route task assignment and day-to-day direction through the vendor's management layer, not directly to individual engineers, to preserve the liability separation the model is intended to provide.
3. Treat below-market pricing as a diligence trigger, not a negotiating win. Request the itemized cost disclosure in Part 2, Section 3 before accepting a quote materially below the benchmarks in this report, and confirm the vendor's financial standing and licensing position as part of that review, not as a substitute for it.
4. Fund and document severance liability before it is needed. Confirm that a severance reserve is genuinely funded, and — before any vendor transition or "rebadging" — resolve who bears the outgoing vendor's accumulated severance obligation and how the engineer's years of service carry forward (Part 2, Section 1.6), rather than leaving the question to be settled mid-dispute.
5. Reassess vendor arrangements periodically, particularly where headcount has grown organically over time, to confirm continued compliance with the 10% dispatch cap and the temporary/auxiliary/substitute role restriction.
6. Coordinate procurement, legal, and tax functions on China vendor selection, given the interaction between labor law liability, IIT withholding accuracy, and VAT/Corporate Income Tax treatment of the vendor relationship.
7. Verify working-hour classification and overtime practice before assuming "unlimited hours" is free. Confirm any comprehensive or non-fixed working-hour approval actually covers the specific positions deployed, and that overtime is recorded and paid where standard hours apply (Part 2, Section 1.9) — silent non-compliance here compounds the same way underfunded social insurance does.
8. Route IP assignment and non-compete instruments through the entity in actual control, not just the nominal employer. Confirm IP-assignment paperwork is enforceable by whichever party directs the engineer's work, and confirm any non-compete template includes the statutory compensation obligation rather than being repurposed from a plain confidentiality clause (Part 2, Sections 1.5, 1.11).

Putting the Vendor Qualification Framework to Work: An RFP Checklist

Part 2's vendor qualification framework identifies what to check; the table below translates it into a document request list procurement teams can attach directly to an RFP or vendor onboarding packet, organized by which scenario in Section 1 it most applies to.

• Itemized monthly cost breakdown (gross salary, statutory contributions, bonus accrual, severance reserve). Applies most directly to: All scenarios  What a weak or missing response signals: A blended "rate card" with no breakdown is the single most common precursor to the underfunding pattern in Part 2's illustrative cases
• Social insurance and housing fund contribution base, confirmed against actual gross salary. Applies most directly to: All scenarios, especially 1.2/1.3 (dispatch)  What a weak or missing response signals: A declared base below actual salary is the leading indicator flagged throughout Part 2
• Current Labor Dispatch Business License and registered capital confirmation. Applies most directly to: Scenarios 1.2, 1.3  What a weak or missing response signals: Absence compounds Article 92 exposure if a dispute arises, though this is a secondary signal, not the primary one
• Headcount ratio calculation (dispatched staff as % of total workforce). Applies most directly to: Scenarios 1.2, 1.3  What a weak or missing response signals: Undisclosed or unverifiable ratios often mean the 10% cap has already been exceeded
• Working-hour system classification and overtime policy, with evidence of government approval where "unlimited hours" is claimed. Applies most directly to: All scenarios, especially 1.1, 1.5  What a weak or missing response signals: No approval on file means standard-hours overtime premiums apply regardless of internal policy
• IP assignment and non-compete templates, reviewed for PRC enforceability. Applies most directly to: All scenarios, especially 1.1, 1.5, 1.6  What a weak or missing response signals: Templates translated from Western boilerplate frequently omit the non-compete compensation obligation or misroute IP assignment to the wrong entity
• Severance reserve funding confirmation and rebadging/transition liability allocation, in writing. Applies most directly to: Scenarios 1.1, 1.6  What a weak or missing response signals: An unwillingness to commit this to writing before a transition is itself a risk indicator
• Entity-setup and payroll-infrastructure plan, with build-vs-buy analysis. Applies most directly to: Scenario 1.5 (GCC build-out)  What a weak or missing response signals: Absence of a sequencing plan against hiring targets often produces avoidable compliance gaps during scale-up

Buyers should treat reluctance to produce any of the above — not just an outright refusal — as the material risk signal Part 2 describes: hedged, partial, or verbally-promised-but-undocumented responses carry the same underlying risk as an outright refusal, since they leave the buyer with nothing enforceable if the vendor's practice diverges from what was represented.

3. Conclusion

From a cost-structure perspective, the distinction between labor dispatch and IT outsourcing in China is largely immaterial: both models operate within the same statutory framework governing salary, social insurance, housing fund, tax, and severance, and a compliant vendor's fully loaded cost converges to a similar range regardless of label. The material distinction is legal — where employer status and associated liability sit — and the material differentiator between vendors is whether the underlying statutory cost is genuinely funded or deferred onto a future dispute in which the client may be implicated.

For international buyers, the appropriate analytical question is not why a compliant vendor's quote appears high relative to the market, but what a below-market quote is failing to fund, and which party ultimately absorbs that cost. Once the full cost structure is disaggregated, the pricing of a properly licensed, fully compliant China IT provider reflects the actual, unavoidable cost of lawfully employing skilled engineers in China — not a premium above it.

This analysis is provided for general informational purposes and reflects a general understanding of Chinese labor law and market practice as of 2026. Social insurance rates, contribution base ceilings and floors, and tax brackets vary by city and are updated periodically by local authorities. International buyers should confirm current figures and obtain local legal and tax advice before finalizing any China IT staffing or outsourcing arrangement.

Sources and Regulatory References

1. Labor Contract Law of the People's Republic of China (中华人民共和国劳动合同法), adopted June 29, 2007, effective January 1, 2008; amended December 28, 2012 — statutory basis for the dispatch and EOR analysis in Section 1, the 10% headcount cap, and the "Employment of Record" non-recognition discussed throughout this installment. See Part 1 and Part 2 of this series for the full cost-structure and liability-specific provisions of this same statute.
2. Interim Provisions on Labor Dispatch (劳务派遣暂行规定), Ministry of Human Resources and Social Security (MOHRSS) Order No. 22, effective March 1, 2014 — statutory basis for the 10% dispatched-headcount cap and the temporary/auxiliary/substitute position test referenced throughout Section 1's buyer scenarios.
3. Labor Law of the People's Republic of China (中华人民共和国劳动法), adopted July 5, 1994, effective January 1, 1995; most recently amended December 29, 2018 — statutory basis for the economic (mass) layoff consultation and filing requirement referenced in Scenario 1.5.

Note on citation approach: statutory instruments above are cited by official title, promulgating authority, and effective date rather than by URL, since government portal links are frequently restructured; readers should retrieve current consolidated texts directly from the National People's Congress (npc.gov.cn), the State Council (gov.cn), or MOHRSS (mohrss.gov.cn) official publication channels, or through qualified PRC legal counsel. For the complete regulatory citation list underlying this 3-part series, see the Sources sections of Part 1 and Part 2.

---

This concludes the series. Read Part 1 – Commercial Models and Cost Structure Baseline · Part 2 – Liability, Compliance, and Termination Risk