We onboarded 6 Tokyo engineers through an EOR — the 7 steps I would run differently next time

Sebastian

Head of International Operations · August 6, 2026

The employer of record did what it promised: we were hiring in Tokyo six weeks after the decision, without a Japanese entity. What it did not do — and what nobody told us until we hit it — was sponsor the visa we needed for our fifth hire, or let us grant equity to any of the six.

Step 1 — Decide whether you actually need an entity

Start with the question the EOR sales process will not ask you: how long do you intend to have people in Japan?

An EOR is excellent for a defined situation — testing a market, hiring one or two people quickly, bridging a gap while an entity is incorporated. It is a poor fit for a permanent Japanese engineering team, because you pay a recurring fee forever for something you could own.

The honest test: if you are confident you will still have engineers in Japan in three years, you should be planning an entity now and using an EOR as a bridge. If you genuinely do not know, the EOR is the right call — optionality has value and incorporation is hard to unwind.

What you should not do is what we did: adopt an EOR as a default, never revisit it, and discover at hire number six that the arrangement has been quietly shaping who you can hire.

Step 2 — Confirm exactly what the EOR can sponsor, in writing

This is the step that cost us a candidate, and it is the one I would change first.

EOR marketing tends to present visa sponsorship as a standard feature. In Japan it is conditional, case-specific, and dependent on the EOR entity’s own characteristics. Whether sponsorship is available, and what documentation the applicant must supply, turns on the sponsoring entity and the nature of the role.

This matters more since 15 April 2026, when applicants for the Engineer/Specialist in Humanities/International Services status applying to Category 3 or 4 employers became subject to additional documentation requirements — including, for language-heavy interpersonal roles, evidence of language ability at around CEFR B2 (JLPT N2 or above for Japanese). Applicants hired by Category 1 and 2 employers, meaning large or publicly listed firms, are exempt. Most EOR entities are not Category 1 or 2.

The action: before any offer to a candidate needing sponsorship, get written confirmation from the EOR covering the specific status of residence, the specific role, and the documentation the candidate will need. A verbal "yes, we handle visas" is not an answer.

Step 3 — Verify social insurance enrolment mechanics

Japanese social insurance — health insurance, pension, employment insurance — is mandatory, and the EOR handles enrolment. The part worth checking is timing.

Enrolment gaps at hire are common when an EOR is onboarding someone mid-month or coordinating across a handover from a previous employer. They look trivial administratively. They are not: immigration guidance revised in February 2026 made late payment of tax, pension or health insurance capable of harming a permanent residency application even where the amounts are later paid in full.

So a two-month enrolment gap created by your EOR in 2026 can damage your engineer’s life plan in 2030. Ask the EOR to confirm enrolment dates per employee, and keep the confirmations. We now do this as a standard onboarding checkpoint.

Step 4 — Model the fully loaded cost, not the headline fee

EOR pricing is usually quoted as a percentage of salary or a fixed monthly amount per employee. That number is not your cost.

Add: statutory employer social insurance contributions, which the EOR passes through; any deposit or reserve the EOR requires; currency conversion spread if you fund in a different currency; and the internal coordination overhead, which is real once you pass three or four people.

Compare against: incorporation cost for a Japanese subsidiary, ongoing accounting and tax filing, and a labour and social insurance specialist — the last of which is not optional if you want the enrolment mechanics in step 3 handled properly.

In our modelling the crossover landed at about seven employees, but I want to be careful with that number: it moved by three in either direction depending on assumptions about how long we would stay. Duration dominates headcount. A team of four you intend to keep for five years justifies an entity sooner than a team of nine for eighteen months.

Step 5 — Solve the equity problem before you offer, not after

This one cost us a senior candidate outright, and the failure was entirely self-inflicted.

Stock options do not flow cleanly through an EOR, because the entity issuing the equity is not the entity employing the person. Workarounds exist — phantom equity, cash-settled appreciation rights, or a direct grant structured as an agreement with the individual outside the employment relationship — but each raises tax treatment questions in Japan that need local advice.

This matters more in Tokyo than people assume. Equity is a normal part of startup compensation there, with mid-level engineers commonly in the ¥5–8 million range plus equity at some companies. A senior candidate comparing your offer against a Japanese startup that can grant options directly will notice the gap.

The action: decide your equity answer before the first interview, and state it plainly. "We cannot grant options while we operate through an EOR; here is the cash-based alternative and here is when that changes" is a workable position. Discovering the constraint after a verbal promise is not.

Step 6 — Design onboarding across two employers

The structural oddity of an EOR is that your engineer has two employers: one legally, one in every way that matters day to day. Onboarding usually reflects this badly.

What we do now: the EOR handles contract, payroll setup and insurance enrolment on a documented timeline the engineer can see, and we handle everything else on day one — accounts, hardware, team introductions, first task. The failure mode we hit early was assuming the EOR would cover more of the human side than it does. It covers none of it, correctly, because it cannot.

One specific point for English-speaking hires: make sure someone on your side can help navigate the Japanese-language administrative documents the EOR sends. Mercari and similar firms operate with English as a working language and this is handled internally; a distributed team using an EOR often has nobody who can read the pension enrolment form.

Step 7 — Plan the transition to your own entity from day one

The last step is the one nobody does at the start, and it is why teams end up paying EOR fees for two quarters longer than necessary.

Write down, at the moment you sign the EOR contract, the trigger that will start the entity conversation: a headcount, a date, or a strategic commitment. Then check it quarterly. Without a pre-agreed trigger, the decision defaults to inertia.

Budget three to six months from decision to first payroll on the new entity, and expect the visa transfer to be the critical path, not the incorporation. Engineers whose status is tied to the EOR need it updated to reflect the new employer, and that runs on immigration timelines you do not control.

Two related reads. The permanent residency threshold for foreign engineers in Japan is changing on 1 April 2027, which interacts directly with visa status continuity during any entity transition — we cover it in our analysis of the five-year visa rule and engineer retention. And if you are weighing similar structures elsewhere in the region, colleagues at HireDeveloper.sg cover quota and pass mechanics in Singapore, while HireDeveloper.ae documents the equivalent entity-versus-EOR trade-off in the UAE.