Learn
EOR Implementation Checklist
You have approval to hire in a new country. The EOR provider is shortlisted.
And now everyone in the room is looking at you to make it actually work:
- Finance wants cost certainty
- Legal wants contract terms nailed down
- IT needs provisioning timelines
- and the hiring manager needed the person started last week
Most EOR implementation guides walk you through the provider’s workflow. This one is different. We built it around what you need to coordinate internally before, during, and after go-live.
The six phases below cover weeks 1 through 6, with the specific sign-offs, data handoffs, and compliance checks that determine whether your first payroll lands clean or triggers a correction cycle.
If you are still selecting a provider, start with our EOR RFP template and best EOR services comparison. This checklist picks up where selection ends.
What should you lock down before engaging your EOR provider?
The two weeks before contract signing determine whether implementation stays on a 6-week track or drifts into month three. Your job here is not procurement.
It is getting Finance, Legal, and hiring managers aligned on scope, cost, and risk tolerance before the provider’s onboarding team starts asking for data you do not have.
Country mapping and structure decision
List every country where you plan to hire in the next 12 months, not just the immediate role. EOR pricing often includes volume tiers, and adding a second country mid-contract can reset your rate.
For each market, document whether you need an EOR, a contractor arrangement, or a local entity.
Get Legal to confirm permanent establishment risk for each jurisdiction. If your team already has customers, offices, or senior decision-makers in-country, an EOR may not eliminate PE exposure.
This is the conversation most teams skip and regret.
Budget alignment with Finance
Your EOR cost is not the provider fee plus gross salary. Statutory employer contributions in markets like France and Brazil add 40-60% on top of gross.
If Finance is modelling on salary alone, your first invoice will trigger an uncomfortable conversation.
Build a per-country cost model that includes: gross salary, employer statutory contributions, EOR management fee, benefits top-ups, and currency conversion margins. Present it to Finance before you sign the MSA.
Contractor conversion audit
If you are converting existing contractors to EOR employment, flag this to Legal immediately.
Between 10-30% of US employers misclassify workers, and misclassification exposure can exceed $135,900 per worker over three years when you combine back taxes, penalties, and benefits owed.
Your EOR provider will not absorb this liability for pre-existing arrangements.
Document each contractor’s current engagement terms, tenure, and exclusivity. This becomes the basis for your conversion risk assessment.
How do you run due diligence on your shortlisted EOR provider?
We reviewed onboarding documentation from providers including Deel and Remote, and the patterns are consistent: the questions most companies forget to ask during selection create the problems that surface at month six.
Your due diligence window is weeks 2-4, overlapping with the pre-implementation work above.
Entity ownership and partner model
Ask whether the provider operates its own legal entities in your target countries or subcontracts to local partners. Owned entities give you a single contractual relationship.
Partner models add a layer between you and the employing entity, which affects response times on payroll queries, contract amendments, and termination processes.
Neither model is inherently better. But you need to know which you are buying, because your escalation paths and SLA enforcement depend on it.
Compliance and data security
Request the provider’s local employment licences for each jurisdiction.
In Germany, operating without an AUG (worker leasing) licence is not just a compliance risk; it converts your arrangement into a direct employment relationship by operation of law.
On data security: confirm SOC 2 Type II certification, data residency policies per jurisdiction, and breach notification timelines.
In 2026, regulators increasingly link labour compliance with data protection and immigration oversight, so a failure in one domain can trigger scrutiny across all three.
Payroll accuracy and error resolution
Ask for the provider’s payroll error rate and their correction SLA. A provider quoting sub-1% error rates should be able to show you the methodology behind that number.
What counts as an error? How quickly is it corrected? Who absorbs the cost of a late statutory filing caused by provider error?
If the provider cannot answer these questions with specifics, that tells you something about their operational maturity.
What does your contract and compliance setup need to cover?
Weeks 3-5 are where Legal earns their keep. The Master Service Agreement is the commercial wrapper, but the documents that protect you are the localised employment contracts and the compliance protocols underneath.
MSA and localised employment contracts
Your MSA should specify: termination notice periods (for the provider relationship, not just the employee), liability allocation for compliance failures, data processing terms per jurisdiction, and fee escalation caps.
Do not accept a template MSA without Legal review.
Localised employment contracts are separate from the MSA and must comply with local labour law. Your provider drafts these, but you own the compensation terms, role scope, and restrictive covenants.
Review each contract with local counsel if the role is senior or the jurisdiction is high-risk.
Right-to-work and compensation structure
Confirm that your provider handles right-to-work verification as part of onboarding. In some jurisdictions, the employing entity (the EOR) bears primary liability for hiring someone without valid work authorisation.
But reputational and operational exposure still lands on you.
Build your compensation packages to include statutory benefits from day one. This is not optional; it is the law in most jurisdictions.
Map each country’s mandatory entitlements: paid leave, sick pay, pension contributions, health insurance, and parental leave. Your provider should supply a benefits matrix, but verify it against current legislation.
Whichapp view
The biggest implementation failures we see are not technical. They are political. Finance discovers the true employer cost after the MSA is signed.
Legal finds restrictive covenant terms that conflict with company policy. A hiring manager promises a start date before right-to-work checks clear.
Run the stakeholder alignment in phases 1-3 as a gate, not a formality.
How do you onboard employees without delaying your start date?
Employee onboarding through an EOR typically takes 5-14 business days, compared to 3-6 months for entity setup.
But that speed only holds if you have your internal coordination sorted before the provider’s onboarding team starts collecting documents.
Classification and document collection
Confirm each hire’s employment classification with your provider before generating contracts. The classification determines tax treatment, benefits eligibility, and termination protections.
Getting this wrong is not a paperwork issue; it is the single largest financial risk in EOR arrangements.
Collect from each employee: signed employment contract, tax identification numbers, bank details for payroll, right-to-work documentation, and benefits election forms.
Missing a single document can delay payroll registration by a full cycle.
IT provisioning and benefits enrolment
Coordinate IT provisioning in parallel with HR onboarding. Your EOR provider does not provision laptops, grant system access, or set up corporate email.
That is your IT team’s job, and they need the same lead time they would need for any new hire.
If your IT provisioning takes 10 business days and you only notify them at contract signing, your new employee will spend their first week unable to work.
Benefits enrolment should happen during the onboarding window, not after. Some statutory benefits in Europe must be active from the employment start date.
Retroactive enrolment creates compliance gaps and employee frustration.
What should your go-live and first payroll process look like?
Your first payroll is the moment of truth. Everything upstream, from cost modelling to contract terms to document collection, either holds or breaks here. Treat go-live as a controlled launch, not a handoff.
Parallel payroll and validation
If you are migrating employees from another payroll provider or converting contractors, run parallel payroll for at least one cycle. Calculate expected net pay independently and compare it against the EOR’s output.
Discrepancies in statutory deductions, employer contributions, or currency conversion are common in the first cycle and easier to catch when you have a comparison point.
Validate every payslip before it reaches the employee. Check gross-to-net calculations, tax withholdings, and any country-specific deductions. Your Finance team should sign off on the first payroll run.
Escalation paths and employee portal
Document your escalation paths before go-live, not after the first problem surfaces. Who does the employee contact for a payslip query? Who in your team handles provider disputes?
What is the SLA for resolving a payroll error that affects an employee’s take-home pay?
Ensure every employee has access to the provider’s employee portal and understands how to retrieve payslips, submit leave requests, and update personal details.
A 15-minute walkthrough during the first week prevents a month of support tickets.
How do you manage ongoing compliance after go-live?
Implementation does not end at first payroll.
Jurisdictions change rules, your headcount shifts, and the EOR arrangement itself has legal time limits in several countries that most teams do not track until it is too late.
Jurisdictional time limits
Germany’s AUG regulations cap EOR-style arrangements at 18 months. France’s Portage Salarial framework allows up to 36 months.
Norway permits up to 5 years. These are not soft guidelines. Exceeding them converts the arrangement into direct employment with the EOR entity, or worse, with your company.
Build a tracking calendar from day one. For each jurisdiction, log the start date, the applicable time limit, and the trigger date for your entity transition decision.
If you are approaching a limit and plan to keep the employee, you need 3-6 months of lead time to set up a local entity or find an alternative structure.
Annual reviews and regulatory monitoring
Schedule annual reviews of your EOR arrangements covering: compensation benchmarking against local market data, benefits compliance with current legislation, provider performance against SLAs, and total cost versus entity setup break-even.
65% of companies use EOR primarily for compliance risk mitigation. That risk mitigation only works if someone in your organisation is actively monitoring regulatory changes.
Assign ownership to a specific person or team, not to “HR” as a department.
Your transition trigger should be concrete: when headcount in a single country exceeds a threshold (typically 5-10 employees) or when time-limit rules force a structural change, begin entity feasibility assessment.
The best EOR services services offer entity transition support, but the decision to transition is yours, not theirs.
Frequently asked questions
How long does EOR implementation typically take from contract to first payroll?
Most EOR implementations take 4-6 weeks from signed MSA to first payroll, with employee onboarding itself taking 5-14 business days. The variable is your internal coordination: if Finance, Legal, and IT are aligned before the provider’s onboarding team engages, you can compress the timeline.
If stakeholder alignment happens mid-implementation, expect 8-10 weeks.
What is the biggest financial risk during EOR implementation?
Underestimating employer statutory costs. In France and Brazil, employer contributions add 40-60% on top of gross salary.
If your budget only accounts for salary plus the EOR management fee, your first invoice will exceed projections significantly.
The second risk is contractor misclassification, where exposure can exceed $135,900 per worker over three years.
When should you transition from an EOR to a local entity?
Two triggers should prompt entity feasibility assessment: jurisdictional time limits (18 months in Germany, 36 in France, 5 years in Norway) and headcount thresholds, typically 5-10 employees in a single country. At that headcount, the per-employee cost of entity maintenance often drops below cumulative EOR fees.
Begin planning 3-6 months before either trigger point.
Can you use this checklist alongside an EOR RFP process?
Yes. This checklist is designed to follow provider selection. Use our EOR RFP template to structure your evaluation, then use this checklist from the point of contract signing onward.
Phases 1-2 here overlap with the final stages of an RFP process.
Compare provider pricing
Open each provider’s official pricing page to compare current plans, setup and contract details.
Some links are affiliate links. We don’t sell these services — they help fund our research.