EOR, Contractor, or Local Entity? A First-Hire Decision Framework for Japan

The first hire in Japan is not a headcount decision. It is a decision about who employs the person, who controls the work, who touches the customer, who owns the data and the IP, and what happens when the arrangement ends. A provider sold as an employer of record, a true independent contractor, and a local entity are three buying paths whose legal structures must be verified. The useful framework compares the role against the decision axes that matter, then verifies the actual arrangement.

Independent guide. This article is research-based, evidence level C, not a hands-on test. Japan Legible has no commercial relationship with any employer-of-record provider mentioned. It is not legal, tax, employment, immigration, or worker-classification advice. Official Japanese sources were checked on August 11, 2026. Reddit threads are low-confidence user reports, not proof. For a vendor-by-vendor comparison of Deel and Remote, including pricing and onboarding, see our Deel vs Remote guide. This article is limited to the employment-model decision.

Short answer

There is no one-person or N-person threshold. The right model follows the role and the company's operating plan: how long the work lasts, how much direction the company keeps, whether the person needs customer-facing authority, whether the activity is regulated, what data and IP the person touches, and how the company would end the relationship.

"Employer of record" is a buyer-facing label, not a legal category defined by the Japanese primary sources reviewed here. The provider's contract must identify the employer and whether the actual structure is direct employment, licensed worker dispatch, or something else. A true independent contractor is a B2B relationship, and Japan assesses worker status by substance, not by the contract label. A local entity creates the most direct employment path, but it is an ongoing operating commitment: payroll, social insurance, tax filings, and governance continue after the first hire.

The decision behind the framework

The practical question is not which model is cheapest; it is which model the company can operate defensibly for this role, timeline, and market-entry plan.

Nine decision axes make that concrete:

1. Role duration: is the work a project, a year-long need, or an open-ended function?
2. Direction and control: does the company decide hours, methods, priorities, and review?
3. Exclusivity: must the person work only for this company?
4. Customer-facing authority: does the person sign, commit, or represent the company to customers?
5. Regulated activity: does the work touch an activity Japan regulates, such as financial services, medical care, or legal services?
6. IP and data access: does the person create IP or access customer, employee, or personal data?
7. Termination risk: how would the relationship end, and what would a departure expose?
8. Hiring runway: how fast is the hire needed, and what infrastructure exists today?
9. Entity and market-entry plans: will the company open a Japan entity anyway for banking, contracting, or customers?

Each axis changes the answer. A six-month project with no customer authority may work as a contractor; an open-ended customer-facing role with daily direction points toward employment. The framework refuses to reduce that to a headcount.

Shared ground: Japan decides by substance

MHLW's official page on the Labor Standards Act states that a "worker" is a person employed at a business or office and paid wages. It explains that status is judged by two criteria: whether the labor is performed under another's direction and supervision, and whether the remuneration is compensation for that directed labor. Contract form or name does not decide the answer; the actual contract contents, work form, remuneration, and other factors are considered case by case. Supplementary factors include business independence, exclusivity, and other reinforcing elements.

That has a direct consequence: calling someone an independent contractor does not make them one. A full-time "contractor" who cannot refuse work, follows the company's hours, and is paid as compensation for directed labor may be a worker under the Labor Standards Act, with the protections that follow.

The freelancer law does not change that boundary. MHLW's official page for the Act on Proper Treatment of Specified Freelance Workers states the act took effect on November 1, 2024, and requires business operators that outsource to freelancers to disclose transaction terms, generally pay within 60 days after receipt of deliverables, and take harassment and working-environment measures. The same page states that if a person is substantively a worker under the Labor Standards Act, labor law applies and the freelancer act does not.

Two more laws shape the framework. The official English translation of the Worker Dispatching Business Act describes worker dispatching as an activity carried out by a person licensed under Article 5(1), with protections for dispatched workers. And the Act on the Protection of Personal Information is a general personal-information statute, which matters because a first hire with access to customer or employee data creates data-handling obligations regardless of the employment model.

Model one: local entity

A Japanese entity employs the person directly. The entity becomes the legal employer and owns the employment contract, payroll process, and related filings.

The boundary is operational, not just legal. JETRO's current setup guidance places company registration, tax notices, hiring, and social-insurance notices in the path to operating a Japanese base. Those workstreams do not end when the first employment agreement is signed. This guide does not assert specific tax rates or setup days; those depend on the company's facts and filings.

Local entity fits when the company plans long-term hiring, needs to contract and bill in Japan, or needs a regulated employer structure. It is the highest-setup path and the most direct employment path.

Model two: true independent contractor

A true independent contractor is a business-to-business relationship. The contractor controls how the work is performed, can refuse or substitute work, uses their own tools and processes, and prices the outcome. The company should not direct hours, review every step, or treat the person as a full-time member with no independence.

The freelancer act adds real duties to this model: written disclosure of terms, payment timing, and harassment and environment measures. Those duties do not make a contractor safe from worker-status review. If the substance is employment, the Labor Standards Act applies regardless of the contract name.

Contractor fits for short, bounded, high-autonomy work where the company does not need day-to-day control and the person can refuse or delegate. It is not a way to get an employee's output without an employment structure.

Model three: the structure sold as employer of record

This guide uses "EOR" only as the market label a buyer may encounter. The official Japanese sources reviewed do not define that label. They do define worker dispatch as one person employing a worker who works for another person under the latter's instructions, and they require a license for a worker-dispatching business. A buyer should therefore ask which entity signs the employment agreement, who gives instructions, whether the proposed structure is licensed dispatch or direct employment, and what the actual documents say.

The label does not eliminate the company's operating questions. The client may still direct work, hold customer relationships, define IP use, access data, and ask to end the commercial arrangement. Each point needs case-specific review: who is the legal employer, who may direct the worker, who owns IP, who accesses data, how termination is handled, and how responsibilities are allocated between provider and client.

The provider route can fit when the company wants a faster path than opening an entity and the provider can document a lawful structure for the specific role. It is not a legal category, a disclaimer, or risk elimination.

Why headcount is the wrong axis

"One person means EOR; five people means entity" is a comfortable rule and a bad one. A one-person hire who will run customer support with daily direction and customer data access has the operating shape of an employee, whether EOR or entity. A five-person plan may still be better served by contractors for bounded work while the entity decision is made.

The headcount threshold also ignores runway. If the company plans to open an entity in nine months, an EOR for the first hire may be a bridge, not a destination. If there is no entity plan, the first hire may be the moment to build the entity the company will need anyway.

Pre-mortem

Assume the first hire goes wrong and work backward. Which model fails first?

• Contractor pre-mortem: the person works full-time under company direction for a year, then disputes the contractor label; the contract alone no longer answers which labor protections and obligations apply.
• EOR pre-mortem: the company directs the person daily, owns the customer account, and stores the work in company systems, then discovers termination cannot unwind control and data questions.
• Entity pre-mortem: the company opens an entity for one hire, no one owns payroll and tax filings, and a missed filing becomes the first operating problem.
• Visa pre-mortem: the candidate's immigration status limits what they can do, and the chosen model assumes the hire can start without a right-to-work check.
• Data pre-mortem: the person accesses customer data, and no one has defined who controls, stores, or transfers that data under APPI.

The pre-mortem does not predict which model wins. It reveals which risks the company is willing to own.

The 90-day decision checklist

Use the first 90 days to make the decision, not to defer it.

Days 1–30: define the role.

1. Write the role's duration, hours, deliverables, and reporting line.
2. Score the nine axes with the person who will manage the hire.
3. Check right-to-work and visa requirements before any offer.

Days 31–60: test the model.

4. If contractor, review the role against MHLW's worker criteria with qualified counsel.
5. If EOR, ask which entity would be the employer, whether the arrangement is dispatch or direct employment, and how termination, IP, and data access work.
6. If entity, map payroll, social insurance, tax, banking, and governance owners.

Days 61–90: verify before commitment.

7. Confirm the agreement matches the actual control and role, not a template.
8. Confirm data and IP ownership in writing, with data-handling obligations under APPI identified.
9. Run a termination rehearsal: who ends the relationship, on what notice, and what happens to access, equipment, and records.
10. Revisit the model when the role or market-entry plan changes.

What readers report

Three r/japanlife threads are attached as low-confidence user reports. They cover the lived questions behind this framework: how an EOR arrangement feels in practice, when a contractor relationship starts to look like employment, and why first-hire structure confuses both sides. The threads could not be fetched by automated checking on August 11, 2026 (HTTP 403), so they are cited as pain signals to read directly, not as verified facts about any company's arrangement.

Strongest counterargument

The strongest objection is that a global EOR is the standard first-hire answer, so this framework overcomplicates one person. That can be true when the role is straightforward, the provider's Japan structure is established, and the contract clearly allocates everyday management, data, IP, and termination responsibilities.

It fails when the company's actual operating shape looks like employment: daily direction, customer authority, exclusive work, and data and IP flowing to the company. In those facts, the EOR carries payroll but the company still owns the control and the outcome. The framework exists precisely because "standard practice" and "defensible arrangement" are different questions.

Unknowns

• Whether a specific role is a worker or contractor under the Labor Standards Act depends on facts and qualified review.
• Whether a specific EOR arrangement is worker dispatch or direct employment, and how the vendor's Japan entity is licensed.
• Local-entity setup costs, tax rates, social insurance contributions, and incorporation timelines were not verified from official sources in this guide and depend on the company's facts.
• The immigration and visa path for a specific candidate.
• What a specific EOR contract says about IP, data access, termination, and indemnities.
• The current contents of the three Reddit threads, because automated access was blocked.

Verification checklist

Before choosing, verify what this framework cannot:

1. Read MHLW's worker criteria and the freelancer law page in their original Japanese or with qualified translation.
2. Ask the EOR for the Japan entity, license status, employment agreement template, payroll register, and termination process.
3. Ask how the company's direction, customer authority, IP, and data access are documented under the EOR or contractor agreement.
4. Confirm the person's right to work before signing anything.
5. Run the 90-day checklist with the actual hiring manager, not a template.

Final recommendation

Choose by operating shape, not by headcount. Use a true independent contractor only for bounded, high-autonomy work where the substance supports it. Use a provider marketed as an EOR only after the legal employer, instruction model, license status where relevant, IP, data, and termination terms are documented. Use a local entity when the company plans long-term hiring and is ready to own payroll, social insurance, tax, and governance.

The first hire is the cheapest time to make the boundary explicit: name the employer, define the control, write the IP and data rules, and rehearse the exit. For EOR vendor comparison, see our Deel vs Remote guide. This article is not legal, tax, employment, immigration, or worker-classification advice; confirm the specific arrangement with qualified professionals.

Primary sources

• MHLW: What is a worker under the Labor Standards Act
• MHLW: Freelance and business-to-business transaction fairness law
• Worker Dispatching Business Act, official English translation
• Act on the Protection of Personal Information, official English translation
• JETRO: Setting Up Business in Japan

Low-confidence user reports: r/japanlife thread on EOR reality, r/japanlife thread on contractor experience, r/japanlife thread on hiring structure.