Onboarding a remote employee across borders means settling three things before day one, in order: compliance — are they employed legally where they live; logistics — can they actually work on day one; and belonging — do they feel part of the team. It is not the generic "send a laptop and a welcome email" checklist. This guide walks each phase.
A remote hire in the city you were founded in is straightforward. A remote hire in another country is a different job. The person is subject to the employment law, tax rules, and data rules of the place they sit in, not the place your company is registered. Get the order right — legal footing first, working setup second, human welcome third — and the first week runs smoothly. Get it wrong and you find out weeks later, when a payroll registration is missing or a contract does not hold up locally.
The checklists below are illustrative. They show the shape of a cross-border onboarding, not a template to copy — every country and every role changes the detail. Treat them as a starting point for your own runbook.
Last updated July 18, 2026. Jump to: What is different · Before the offer · Offer to day one · Week one · 30/60/90 · Failure modes · FAQ
What makes international onboarding different?
Standard remote onboarding assumes one thing your international hires break: that everyone shares your legal and payroll setup. A colleague in the same country as your entity slots into a system that already exists. A colleague in France, Brazil, or Japan does not — until you have built the legal and payroll footing to employ them there, they cannot be paid or protected properly.
So international onboarding adds a layer the domestic version never has to think about. Before you get to buddies and welcome calls, you have to answer three questions the local country asks: are they allowed to work here, who is their legal employer, and how do they get paid and covered. Those are settled long before day one, and they shape everything that follows.
- Compliance comes first. The right to work, the employing entity, the contract, and payroll registration all have to be in place before a start date is real. This is the part that cannot be rushed at the end.
- Logistics comes second. Equipment crossing a border, system access, and security setup take longer than they do down the hall — plan them as lead-time items, not day-one errands.
- Belonging comes third — but is planned first. A remote hire cannot absorb the culture by sitting near people. The welcome, the buddy, and the first-week structure have to be deliberate, because nothing happens by accident.
Before the offer: get the footing right
The most expensive onboarding mistakes are made before anyone signs. Two decisions here set up everything else, and both are hard to reverse once an offer is out.
Confirm the right to work and identity
Before you commit to a hire, confirm the person is legally allowed to work in the country they will work from, and verify who they are. What counts as proof, and who is allowed to check it, varies from country to country, so keep this at the category level and follow local rules rather than a single global process. The point is simple: the right to work is a precondition, not a formality you tidy up later.
Choose the correct engagement vehicle
Decide how you are actually engaging this person, because the answer sets the entire onboarding path. There are two broad routes.
- Employee. If you want an employee, someone has to be their legal employer in that country. If you have a legal entity there, you employ them directly. If you do not, an employer of record becomes the legal employer on your behalf, so the person is properly employed under local law while they work for your team day to day.
- Contractor. If the work genuinely suits a contractor relationship, the path is different — a services agreement, not an employment contract, and no payroll registration. Get this classification right from the start; treating an employee as a contractor to skip the setup is the misclassification risk our guide to contractor management walks through.
This choice is not a detail you settle during week one. It determines who issues the contract, whether there is payroll to register, what the person is owed, and how you onboard them. Make it before the offer goes out.
From offer to day one: the compliance and logistics runbook
Once the offer is accepted, the window to day one is where most of the real work happens. Run these items in parallel — several have lead times you cannot compress at the end.
A locally compliant contract
The employment contract has to satisfy the law of the country the person works in. Required terms, language, notice, and probation all differ. Who issues it depends on your setup. If you employ directly through your own entity, you issue it. If you use an employer of record, the EOR issues the contract as the legal employer, and you approve the commercial terms. Either way, do not reuse your home-country template unchanged. It rarely fits.
Payroll registration and pay cutoffs
A new employee usually has to be registered for local payroll and social contributions before they can be paid. That registration takes time, so line it up early. Note the local pay-run cutoff dates too, so the first paycheck lands on schedule. Miss a cutoff by a day and someone can wait a second month to be paid. Our guide to global payroll explains how these cycles and registrations differ from place to place.
Equipment across borders
Shipping a laptop to another country is not the same as sending one across town. Customs, import duties, and delivery times all come into play, and hardware can sit at a border for days. So plan equipment as a lead-time item. Order early. Decide who handles any customs charges. And have a fallback, such as a local purchase or a stipend, for places where shipping is slow or costly. Keep the specifics category-level and check the route for each country.
Access provisioning and security
Map out the accounts, tools, and permissions the person needs. Have them ready to switch on for day one, rather than scrambled together during it. Set up their identity, multi-factor authentication, and access before they start. Then the first morning is spent working, not waiting on IT tickets. A short, ordered access list per role saves the same fire drill on every hire.
Data handling
A remote hire works from a home network and a personal space, which changes how company and customer data is protected. Set the rules for devices, connections, and where data can be stored before they start, and make sure they line up with your remote work policy and your data-protection obligations. Onboarding is the moment to establish good habits, not to discover a gap after a device goes missing.
Benefits enrollment
Two kinds of benefits need sorting before or around day one: the statutory ones the country requires, and the company ones you choose to offer on top. The statutory set is not optional and differs sharply by country — our guide to statutory benefits by country shows how much. Enroll the person in both, and be clear with them about which is which, so the offer they accepted matches what actually shows up.
Week one: turning a legal hire into a teammate
By day one the compliance and logistics should be invisible — done, working, forgotten. Week one is where belonging is built, and for a remote hire none of it happens on its own.
Give the first week an owner
A new remote employee should never spend day one wondering who to talk to. Name a manager and a buddy before they start. Give the week a structure: who they meet, what they read, and a small, real task they can finish by Friday. A named buddy answers the quiet questions a new hire will not raise in a group call. And a first win builds confidence faster than a week of reading.
Put the record in one place
The contract, the role, the goals, the policies the person has acknowledged — these should live in one system of record. Not scattered across inboxes and spreadsheets. When employment details sit in an AI-native HRIS from day one, the person, their manager, and HR all see the same source of truth. Nothing about a remote hire then depends on someone remembering where a file was saved.
Respect the time zones
A hire several hours ahead of or behind the team cannot join every live call, and should not be expected to. Set rituals that respect the spread. Write decisions down so they survive the time gap. Record the meetings that matter. Rotate call times so the same person is not always the one dialing in at night. Habits like these, set in week one, signal that the person is a full teammate, not a remote afterthought.
A 30/60/90 skeleton
Onboarding does not end when the laptop arrives. A light 30/60/90 plan gives the first three months a shape and gives the manager checkpoints, without turning into a bureaucratic exercise.
- By day 30 — settled. Access works, the person has met the team, understands how work flows, and has shipped something small. Any setup gaps from onboarding are closed.
- By day 60 — contributing. They own a piece of real work, know who to go to for what, and are giving as well as receiving in the team's rhythm.
- By day 90 — independent. They work without hand-holding, have clear goals for the next quarter, and have had an honest two-way check-in on how the fit is going.
Keep it to a page. The value is in the checkpoints and the conversation, not the document.
Common failure modes
The same handful of mistakes account for most botched international onboardings. Knowing them is half of avoiding them.
- Leaving compliance to the end. Treating the contract, payroll registration, and right-to-work as day-one paperwork instead of pre-offer work. These have lead times, and skipping them is how a start date slips or a first paycheck is late.
- Reusing the home-country contract. A template that is legal at headquarters often does not hold up in the hire's country. The employing entity — you or the EOR — must issue a locally compliant one.
- Underestimating equipment. Ordering a laptop the week before, then watching it stick in customs. Cross-border hardware is a lead-time item, not a day-one errand.
- Misclassifying to move faster. Engaging an employee as a contractor to skip payroll setup. It saves days now and creates misclassification exposure later.
- No human plan. Getting the legal and logistics right, then leaving the person alone on day one with no buddy, no goals, and no structure. A compliant hire who feels lost still churns.
Frequently asked questions
How long should remote employee onboarding take?
Plan the compliance groundwork to start well before day one — often two to four weeks ahead, because payroll registration, a locally compliant contract, and equipment shipping across borders all have lead times you cannot compress. The human side of onboarding, by contrast, runs across the first 30 to 90 days. So there are two clocks: the setup that must be finished before the start date, and the settling-in that continues for the first three months.
What is different about onboarding an international employee?
A domestic hire slots into a legal and payroll setup that already exists; an international hire does not. They are subject to the employment law, tax rules, and data rules of the country they work from, so before you reach buddies and welcome calls you have to settle their right to work, their legal employer, a locally compliant contract, and payroll registration. Compliance and logistics come first, and both take longer across a border.
Who issues the employment contract when you use an employer of record?
The employer of record issues it. Because the EOR is the legal employer in that country, it provides the locally compliant employment contract and signs it with the employee, while you approve the commercial terms such as pay, title, and start date. If instead you employ through your own legal entity in that country, you issue the contract yourself. Either way, it must satisfy local law, not just your home-country template.
How do you handle equipment for a remote hire in another country?
Treat it as a lead-time item, not a day-one errand. Shipping hardware across a border brings in customs, import duties, and slower delivery, so order early and decide who covers any charges. Keep the specifics at the category level and check the route for each country, because what works for one destination fails for another. Where shipping is slow or costly, a local purchase or an equipment stipend is a practical fallback.
What has to be done before a remote employee starts?
Before day one, confirm the right to work and identity, decide the engagement vehicle — employee through your entity or an employer of record, or contractor — and put a locally compliant contract in place. Register the person for local payroll ahead of the pay cutoff, provision system access and security, set data-handling rules, and enroll them in statutory and company benefits. These are precondition items with lead times, not paperwork to tidy up later.
How is onboarding a contractor different from onboarding an employee?
A contractor is engaged under a services agreement, not an employment contract, so there is no payroll registration, no statutory benefits enrollment, and no employing entity or employer of record involved. Onboarding focuses on the scope of work, invoicing, and access rather than local employment setup. The key is getting the classification right first: engaging someone as a contractor when the role is really employment is the misclassification risk to avoid. Our contractor management guide covers it.
Onboard your global team on one system
Remote& runs onboarding, employment records, and compliant hiring on one platform. An AI-native HRIS holds every hire's contract, goals, and policies from day one. So a remote employee across a border is a full teammate, not a scattered set of files. See how it fits your team.