How to Hire an EoR Employee

If you want to hire offshore without setting up a local entity, an Employer of Record, or EoR, is usually the fastest compliant path. On paper it looks simple, find a candidate, sign an agreement, start work. In reality, the time sink is nearly always in the details, role classification, contract terms, benefits expectations, onboarding documentation, and making sure payroll and tax are done correctly from day one.

This guide gives you a practical overview of how to hire an EoR employee in the Philippines, what decisions you need to make up front, what the usual steps look like, and where people typically waste weeks.

What an EoR actually covers, and what it does not

An Employer of Record is the legal employer in the Philippines on your behalf. You direct the employee’s day to day work, while the EoR handles local employment compliance.

In practice, an EoR arrangement usually includes:

• Employing the worker under a compliant local employment contract
• Payroll processing, including statutory contributions and withholding as required
• Administration of mandated leave, holiday pay, and basic employee entitlements
• Issuing payslips, managing employee records, and handling routine HR administration
• Guidance on compliant offboarding if the employment ends

It does not automatically include everything you might assume, for example:

• Recruitment, screening, and skills assessment, unless explicitly bundled
• Managing performance, day to day supervision, and workload planning
• IT equipment, security controls, tooling, access management, and asset recovery
• Detailed role design, KPIs, and internal training
• Operational leadership, project management, or delivery management

If you are unclear on this split, you will end up with gaps, either the employee is unmanaged, or you are expecting the EoR to do operational work they do not do.

Step 1: Define the role properly before you recruit or make an offer

Most EoR hiring delays come from a role that is not properly defined. “We need someone good at admin”, or “we need a developer” is not enough.

Before you recruit or issue an offer, get clarity on:

• Role scope: what outcomes the role owns, and what it will not touch
• Working arrangement: remote, hybrid, or office based, and how oversight will work
• Hours: local hours, ANZ aligned hours, shift work, or overlap windows
• Seniority: junior, mid, senior, lead, and what “good” looks like at that level
• Comp structure: base pay, allowances, incentives, and any performance linked components
• Equipment: who provides it, who owns it, and how support will work

If you change these late, you can end up reissuing an offer, redoing contracts, and missing your planned start date.

Step 2: Choose the right EoR provider, and line up responsibilities

Not all EoR providers operate the same way. Some are pure compliance payroll engines. Some will also help with HR, onboarding, and local context. Some are good at one off hires but struggle with teams.

When choosing an EoR provider, pressure test:

• Compliance depth: do they actually handle contracts, statutory obligations, and employee lifecycle properly
• Process: what they need from you, what they provide, and where handoffs occur
• Speed: how quickly they can issue contracts and start payroll
• Support: who you talk to when something goes wrong, and how quickly they respond
• Transparency: whether fees and inclusions are clear, or buried in fine print
• Scale: whether they can handle 1 hire today and 20 hires later without changing everything

The goal is simple, no ambiguity over who does what, especially around onboarding, leave, payroll timing, and offboarding.

Step 3: Set employment terms, compensation, and benefits that will hold up

This is where companies accidentally create friction, either they offer something that does not fit the market, or they offer something that later turns into a compliance or cost issue.

Key decisions usually include:

• Employment type: ongoing employment vs fixed term arrangements, where appropriate
• Probation: what probation means operationally, and how you will assess performance early
• Salary: base pay, payment frequency, and whether it is local market aligned
• Allowances: internet, equipment, transport, or night shift allowances if relevant
• Leave: expectations around leave, holiday calendars, and notice for planned time off
• Confidentiality and IP: ensuring you actually own work output and protect sensitive data

If you do not set expectations properly here, you will pay for it later through churn, disputes, or a messy termination process.

Step 4: Contracts, compliance documents, and onboarding

Once the offer is accepted, the EoR will usually handle the local employment contract and required employee documentation. Your job is to make sure onboarding is not just “paperwork done”.

A clean onboarding process usually covers:

• Employment contract issuance, signing, and document collection
• Start date confirmation, schedule, and internal points of contact
• IT setup, accounts, security, MFA, device policies, and access boundaries
• Role training, documentation access, and a clear first two weeks plan
• Performance expectations, first milestones, and how feedback will work

A bad onboarding looks like this, the contract is signed, then the employee sits idle because accounts, tools, and direction are not ready.

Step 5: Payroll, tax, leave, and ongoing employee operations

Once the employee is active, most issues come from basic operational hygiene. Payroll timing, approvals, leave tracking, and clarity on overtime or schedule changes.

Common operational areas to lock in:

• Payroll cadence: cut off dates, approval workflows, and what changes require lead time
• Leave process: how leave is requested, approved, recorded, and communicated
• Role changes: how promotions, salary changes, or scope changes get documented
• Incident handling: what happens if there is misconduct, poor performance, or security issues
• Offboarding: notice, access removal, asset return, and handover expectations

Treat this as a system, not a one off hire, especially if you plan to build a team.

Typical timeline and what affects it

A realistic timeline depends on:

• How quickly you define the role and finalise compensation and benefits
• How responsive the candidate is with documents and signing
• How fast the EoR can issue the contract and register the employee for payroll
• Whether you need equipment provision, shipping, or device setup
• Whether the role requires background checks or additional compliance steps

If you are working to a commercial deadline, start by working backwards from the target start date, then build a checklist that includes contract, payroll cut off, and tool access readiness.

Common mistakes that cost time and money

• Making an offer before the role scope, hours, and reporting lines are locked in
• Assuming the EoR handles operational management, and leaving the employee without direction
• Underestimating how much onboarding depends on your internal tooling and documentation
• Using generic contracts or informal arrangements that do not protect IP and confidentiality
• Changing pay, hours, or role scope after signing, then scrambling to fix paperwork
• Not planning the offboarding path, then getting stuck when a hire does not work out

When it makes sense to use an EoR, and when you should not

You will usually want an EoR if:

• You want to hire offshore without setting up a local entity
• You need speed and compliance, and you do not want to learn local employment administration the hard way
• You are hiring your first team member in country and want a low risk start
• You are testing a market, building a pilot team, or validating operations before incorporating
• You want a clean pathway to expand, either by scaling under EoR, or transitioning to your own entity later

An EoR may not be the right fit if:

• You already have a local entity, payroll capability, and HR compliance handled properly
• You require deep custom policies that sit outside standard employment administration
• Your hiring volume is large enough that running your own entity is clearly the better long term economic choice