Recruitment outsourcing models, the operator taxonomy for blue-collar employers

A procurement team typing "recruitment outsourcing" into search will surface five acronyms inside the first page, EOR, PEO, RPO, MSP, VMS, plus labour hire and staffing as common synonyms for two of them. The acronyms are not interchangeable. Each names a specific scope, a specific commercial model, and a specific set of conditions where it fits. This guide names the full taxonomy in operator-grade detail and walks the model decision for blue-collar workforce.

The short version: the five models split into two groups. EOR and PEO are employment-of-record models, who legally employs the worker. RPO, MSP, and VMS are recruitment-process or vendor-governance models, who runs the recruitment function and the vendor relationships. The two groups can stack, an EOR engagement under an MSP governance layer is common. The model taxonomy is the vocabulary procurement teams need before the RFP.

The five models, named precisely

Employer of Record (EOR). A third-party legal employer in the destination country, employs the worker on the buyer's behalf when the buyer has no destination entity. Holds the payroll, the labour contract, the statutory contributions, and the in-country compliance.

Professional Employer Organisation (PEO). A co-employer alongside the buyer's existing destination entity. Shares the employer relationship rather than substituting for it. Common in US payroll for SMEs.

Recruitment Process Outsourcing (RPO). A third-party operator running the buyer's internal recruitment function under the buyer's brand. Often co-located on site. White-collar enterprise default; rare in blue-collar.

Managed Service Provider (MSP). A governance layer over a multi-vendor recruitment supply chain. Onboards vendors, routes demand, monitors KPIs, consolidates invoices, runs compliance audits.

Vendor Management System (VMS). The software platform an MSP uses to run the work. Holds the demand pipeline, the candidate submissions, the dashboards, the invoice reconciliation. Often quoted together as MSP/VMS.

Plus two operator-vocabulary synonyms that frequently confuse:

Labour hire. APAC and Australian vocabulary for staffing or temporary agency work. The labour-hire entity employs the worker (often under destination-country temporary-work licence regimes like AUG in Germany or ustupanje in Croatia) and seconds them to the end-buyer. Functionally adjacent to a domestic EOR-light arrangement, with operating-cycle vocabulary.

Recruitment agency (RA). Sources and delivers candidates to an end-employer. The agency does not employ the worker on the destination side. The end-employer or a labour-hire entity holds the contract.

The taxonomy table

The table is the starting point. Most real engagements stack two or three of the models. A cross-border blue-collar engagement under an MSP governance layer typically has Werklist (RA) plus a destination labour-hire entity, all running on the MSP's VMS, with the MSP routing demand and consolidating invoices.

The stacking patterns, what real engagements look like

Three common stacks for blue-collar workforce.

Stack A, single corridor, single vendor. Werklist (RA) plus the end-buyer's destination entity holds the labour contract. No MSP layer. No EOR. Fits headcounts under 50 in one corridor.

Stack B, single corridor, labour-hire partner. Werklist (RA) plus a destination-country labour-hire entity employs the worker. The end-buyer pays the labour-hire entity hourly. No MSP. Fits buyers that prefer no destination payroll obligation.

Stack C, multi-corridor, MSP governance. Werklist (RA) for one or more corridors, additional corridor RAs for other origins, destination labour-hire entities for each route, all under an MSP that holds the buyer relationship and consolidates KPI reporting and invoicing through a VMS. Fits enterprise multinational accounts with placements above 200 per year.

The stacks combine across the taxonomy. The labelling matters because the RFP and the contract paper sit on the labels. A buyer issuing an RFP for "RPO services" against Stack C will receive non-fit proposals. A buyer issuing for "MSP with cross-border labour-hire corridor partners" will receive proposals matched to the work.

The decision matrix, by scenario

The matrix simplifies. Real engagements often blend stacks across business units inside the same buyer.

The commercial models, briefly

Each outsourcing model carries a different commercial structure.

EOR. A monthly per-worker fee on top of the destination payroll and statutory cost. Typically EUR 200-600 per worker per month depending on country, often with a setup fee per worker.

PEO. A percentage of payroll (US market norm 5-10%) or a per-worker per-month fee.

RPO. A management fee plus a per-hire fee, or a bundled cost-per-hire. Often 12-18% of first-year salary for white-collar; structured differently for industrial bundles.

MSP. A percentage of total managed spend, typically 3-8%, sometimes a fixed annual fee with volume tiers.

VMS. Often bundled into the MSP fee or charged per transaction (per submission, per timesheet, per invoice line).

Labour hire. An hourly margin over the direct wage and statutory contributions, typically 15-30% depending on country and trade.

Recruitment agency. A fixed sum per placement plus, on cross-border deployments, the cost-per-hire stack across sourcing, screening, permit, mobilisation, onboarding, and replacement reserve.

A buyer evaluating the total cost has to add the commercial layers across the stack. Stack C carries the recruitment agency cost plus the labour-hire margin plus the MSP fee. The combined load is meaningful and is the trade-off against the governance discipline the stack provides.

Cross-border industrial, where the taxonomy bites

The cross-border industrial context exposes taxonomy assumptions other contexts hide.

The EOR has to be licensed in the destination country. The labour-hire entity has to be licensed under the destination country's temporary-work statute. The recruitment agency has to be licensed in the origin country under DOFE, DMW, e-Migrate, NSZ, or HZZ depending on origin. The MSP is generally licence-light but is expected to verify the licences of every downstream vendor.

A buyer running cross-border industrial workforce should expect the procurement contract to name every licence and every regulator in the stack. A contract that hedges on "vendor will hold all necessary licences" without naming them is a contract the inspection team will not respect.

The CSR and compliance dimension

Each outsourcing model interacts with the buyer's CSR and modern-slavery compliance framework differently.

The IOM IRIS framework, ILO Convention 181, and the no-fee-to-worker principle apply across the stack. A buyer that has signed the modern slavery statement obligations needs every model in the stack to commit, in writing, to the same prohibited-conducts enumeration. The standard line, "Workers are never charged fees for our services, employers pay for recruitment," should appear in the contract paper of every recruitment-side vendor.

The MSP layer often runs the consolidated due diligence. Stack A and Stack B engagements run the due diligence directly between the buyer and the recruitment partner. In either case, the receipt the auditor will ask for is the same.

Where to go next

For the EOR vs recruitment agency split that sits at the structural centre of the taxonomy, see EOR vs recruitment agency, what blue-collar employers should choose. For the RPO model in industrial contexts specifically, see Industrial RPO model explained. For the MSP/VMS governance layer in detail, see Vendor management for blue-collar staffing.

Send the brief. Corridor mix, headcount target, current vendor stack, compliance framework. We come back inside one business day with a stack recommendation against the taxonomy and the corridor partner identities that fit. Talk to a corridor lead.