EOR vs recruitment agency, what blue-collar employers should choose

Two words get conflated and a buyer signs the wrong contract. Employer of Record (EOR) and recruitment agency (RA) are not interchangeable categories. They sit at different points in the workforce stack, they carry different legal weight, and they invoice for different things. This piece names both, runs a decision matrix, and is explicit about where Werklist sits in the model split.

The short version: an EOR legally employs the worker on the buyer's behalf and holds the payroll, the contract, and the in-country compliance. A recruitment agency sources, vets, and delivers the worker, but the worker is employed by the end-buyer or by a labour-hire entity downstream. For most cross-border blue-collar deployments into the EU and the Gulf, the right answer is a recruitment agency plus a destination-country employer that is either the end-buyer directly or a licensed labour-hire entity. Werklist is the recruitment agency in that stack. We are not an EOR.

What an EOR is, precisely

The clean single-sentence definition of an EOR is this: an EOR steps in as the legal in-country employer, so the buyer can deploy workers in compliance with local employment law without standing up a local entity. The definition does two jobs at once. First, it names the legal substance: the EOR is the employer of record, on the labour contract, with the regulator, on the tax return. Second, it names the buyer benefit: the buyer can deploy workers into a country without standing up a local entity, taking a payroll registration, or learning the local labour code.

The seven scope items inside a typical EOR engagement:

1. Payroll and tax administration in the destination country
2. Employee benefits aligned to local statutory minimums
3. Foreign exchange and in-country money movement
4. Employment contracts compliant with local labour law
5. Insurance, including workmen's compensation and occupational health
6. Compliance with local employment law, including termination and severance
7. Immigration, visa, and work-permit processing

Each line is a legal responsibility that has to land somewhere. If the buyer has no local entity, those responsibilities go to the EOR by contract. If the buyer has a local entity, the responsibilities sit there.

The operator's nuance: a workforce has to be mobilised quickly and legally. That is the EOR proposition.

What a recruitment agency is, precisely

A recruitment agency sources, screens, and delivers candidates to an end-employer. The agency does not employ the worker in the destination country. The end-employer (or a labour-hire entity engaged by the end-employer) signs the destination-country contract and holds the legal employer relationship. The agency holds the candidate relationship up to the point of contract signature and, in cross-border deployments, frequently runs the document attestation, visa filing, and pre-departure orientation as a paid scope.

A cross-border recruitment agency operating in the labour-export regulator framework will typically also be licensed in the origin country, DOFE Nepal, DMW Philippines, the Protector of Emigrants office in India, NSZ Serbia, HZZ Croatia. The licence regulates the agency's conduct in the origin country, including the no-fee-to-worker rule, the contract attestation requirement, and the recordkeeping obligations.

A useful disclaimer pattern: Werklist is a licensed cross-border recruitment operator. We are not a staffing agency, not an EOR, not a PEO; destination-side visa filings sit with our partner counsel. The disclaimer is positioning, not legal hedge. Each clause excludes a category and clarifies the channel.

The model categories named precisely

Before the decision matrix, the categories. Blue-collar buyers see at least five distinct models on the market, and a procurement team that conflates them ends up comparing offers that are not comparable.

• Recruitment agency (RA). Sources and delivers the candidate. End-employer holds the destination-country contract.
• Labour hire / staffing. A destination-country licensed entity employs the worker and seconds them to the end-employer for the duration of the assignment. The operator vocabulary calls this "labour hire", and the term is worth surfacing.
• Employer of Record (EOR). Legally employs the worker on behalf of a foreign principal that has no local entity. Holds the labour contract, payroll, tax, and statutory benefits.
• Professional Employer Organisation (PEO). Co-employs alongside the buyer's existing local entity. Shares the employer relationship rather than substituting for it. Common in US payroll.
• Recruitment Process Outsourcing (RPO). Operates the buyer's internal recruitment function as a managed service. Typically white-collar; rare in blue-collar workforce.
• Managed Service Provider (MSP) / Vendor Management System (VMS). Coordinates multiple recruitment vendors under one buyer-side governance layer. Used by large enterprises with high-volume contingent-workforce needs across many countries.

Cross-border blue-collar work most often sits in the RA + labour hire stack. The recruitment agency runs the origin-side scope; the destination-side labour-hire entity holds the local contract; the end-employer directs the work. EOR is the pattern when the buyer has no destination entity at all and is unwilling to engage a labour-hire partner directly.

Decision matrix, which model wins, by scenario

The matrix is not a substitute for legal advice on the specific corridor. It is a starting position for a procurement team to refine on a scoping call.

Cross-border nuance, where the model split bites

The model decision changes when the workforce is crossing a border, and that is where most buyers get caught.

The origin-country regulator does not recognise an EOR as a substitute for the recruitment licence. A Nepali worker leaving Kathmandu for Croatia goes through DOFE attestation against a demand letter signed by a destination-country employer, which may be the end-buyer, a labour-hire entity, or an EOR with a local entity in Croatia. The EOR does not eliminate the DOFE permit; it just sits as the employer of record on the destination side of the document trail. The recruitment scope in Nepal, sourcing, trade test, document attestation, pre-departure orientation, is regulated separately and sits with a DOFE-licensed recruitment agency. An EOR contracting directly with a Nepali worker without going through a licensed recruitment agency in Nepal is, in most readings, operating outside the framework.

Destination-country labour law sets the floor. Croatia's jedinstvena dozvola system, the German AÜG temporary work agency law, and the UAE MOHRE Tasheel contract framework each impose specific employer obligations. An EOR has to be licensed and compliant in the destination country. A recruitment agency operating cross-border partners with destination-country entities, labour-hire, EOR, or end-employer, that already hold the licence.

The "active customers" framing applies. A serious EOR publishes its active-customer count by country and a serious recruitment agency does the same by corridor. The disclosure is a trust artefact, not a marketing line.

Where Werklist sits

Werklist is a licensed cross-border recruitment operator. We are not an EOR. We do not legally employ workers on the destination side. Our scope is the recruitment, document attestation, and mobilisation stack on the origin side, plus partnership with a destination-country employer that holds the labour contract.

Visa filings at the destination sit with our partner counsel; the "not a law firm" disclaimer pattern applies to us as well. We brief candidates and employers on the process and we run the operational scope. We do not represent the worker or the employer legally in the destination jurisdiction.

When the buyer has a destination entity, Werklist plus the buyer's entity is the cleanest stack. When the buyer has no destination entity, Werklist will partner with a licensed labour-hire entity in the destination country or, in some corridors, with an EOR vendor selected for the engagement. The recruitment scope is ours; the employment scope is held downstream.

Common employer confusion points

Three confusions show up repeatedly in scoping calls.

"Can the recruitment agency just employ the worker for us?" Not in most jurisdictions, not without crossing into staffing-licence territory in the destination country. The agency that sources the worker is rarely the same legal entity that employs the worker on the destination payroll. The buyer that asks the question usually wants an EOR and is using the wrong word for it.

"Doesn't the EOR handle the recruitment too?" Some EORs offer a recruitment service as an add-on, but the regulatory framework in most origin countries requires a separately licensed recruitment entity for the origin-side filings. An EOR running recruitment in Nepal without a DOFE licence is a compliance risk the buyer's CSR team will not want to underwrite.

"What about a PEO?" PEO is co-employment alongside an existing local entity. It is a US-rooted model. Outside the US it shows up rarely in blue-collar workforce and frequently in white-collar tech. For a cross-border blue-collar deployment, the buyer is usually choosing between RA + end-employer, RA + labour-hire, and EOR.

The compliance enumeration, what each model owes you

The full abuse-enumeration pattern below names what the buyer should expect each model to commit to in writing.

The buyer's CSR team should require a written commitment that the model in use, whether EOR or RA + labour-hire, prohibits recruitment-fee charging to workers, passport retention, contract substitution, debt bondage, dormitory confinement, retaliation against complainants, and deception in the recruitment process. The IOM IRIS framework and ILO Convention 181 set the floor for the prohibited conducts. A model that cannot enumerate the floor is not the model to sign.

How to decide, the scoping questions

The scoping call that produces a clean model decision asks five questions.

1. Does the buyer have a destination-country legal entity that can employ the worker?
2. What is the assignment duration, under 12 months, 12-24 months, 24+ months?
3. What is the headcount, under 10, 10-50, 50-200, 200+?
4. Is the workforce rotational, fixed-term, or open-ended?
5. Does the buyer's CSR audit framework require the workers to be on the buyer's payroll, or is a labour-hire entity acceptable?

The five answers narrow the decision matrix to one or two cells. The remaining choice is between a single-vendor stack (Werklist plus one labour-hire partner per corridor) and a vendor-management stack (Werklist plus multiple labour-hire partners under MSP/VMS governance). For headcounts under 50 in one corridor, single-vendor wins. For headcounts above 200 across multiple corridors, vendor management is usually the right governance layer.

Where to go next

For the cost dimension that pairs with the model decision, see Cost-per-hire calculation for blue-collar workforce, 2026 benchmarks. For the retention numbers that determine whether the model survives month six, see Turnover and retention in industrial workforce. For the structural choice between full-scope and partial-scope engagement, which interacts with the EOR/RA split, see End to end vs partial-service recruitment. For the partner-selection checklist that follows from the model decision, see Cross-border recruitment agency, selection guide for employers.

Send the brief, corridor, trade, headcount, destination, target start date. We come back inside one business day with a model recommendation, a corridor fit, and the labour-hire or EOR partner that fits the deployment. Talk to a corridor lead.