Employer of Record vs ODC in the Philippines: A Singapore Sponsor’s Decision Guide

If you are a Singapore company building engineering capacity in the Philippines, an employer of record (EOR) gives you people fast, but it leaves you running the team and it does not hand you the code by default. An offshore development centre (ODC) or dedicated team gives you people plus delivery management, and the IP transfer is written into one contract with one vendor. Pick an EOR when you already have strong engineering leadership and want direct control of each hire. Pick an ODC when you need a working team, not just headcount.

Educational only; not legal, tax or employment advice. Confirm the specifics for your arrangement with Philippine and Singapore counsel.

Who this is for, and who should skip it

For: CTOs, heads of engineering and finance leads at Singapore companies that want three to thirty engineers in the Philippines within the next two quarters, and have heard “just use an EOR” from a peer or an investor.

Skip if: you are choosing between Manila, Ho Chi Minh City and a Singapore-only core (read ODC location for Singapore buyers first); you are comparing an ODC with short-term staff augmentation (see ODC vs staff aug); or you plan to set up your own Philippine entity in the next twelve months. This article does one job: help a Singapore sponsor decide between an EOR, a dedicated team and an ODC for Philippine engineers.

The three models in plain terms

• Employer of record. A Philippine company becomes the legal employer of people you choose. It runs payroll, statutory contributions and employment paperwork. You direct the work day to day. Nobody else manages delivery.
• Dedicated team. A software vendor employs engineers who work only on your product. You set priorities; the vendor handles hiring, replacement, equipment, line management and some delivery leadership.
• Offshore development centre. A larger, longer-term version of a dedicated team, usually with its own team lead, QA, DevOps and a governance rhythm (a QBR, a steering group, an agreed exit path). The vendor is accountable for delivery outcomes, not just attendance.

The headline difference: an EOR sells employment. A dedicated team or ODC sells delivery capacity. Everything below follows from that.

The comparison matrix

Use this in your next internal meeting. Each row is a question your board, auditors or future acquirer will eventually ask.

Question	Employer of record	Dedicated team	ODC
Who is the legal employer in the Philippines?	The EOR	The vendor	The vendor
Who directs the work each day?	You, entirely	You set priorities; vendor manages people	Shared: your product owner plus vendor team lead
Who owns the code by default under Philippine law?	The EOR, as employer, unless assigned on	The vendor’s employees create it; you need a written assignment	Same as dedicated team
How many contracts form the IP chain?	Two (employee to EOR, EOR to you)	One (vendor to you), backed by vendor employment terms	One, usually with escrow or repo-ownership terms
Who replaces a resignation?	You recruit; EOR onboards	Vendor recruits and backfills	Vendor, often with a bench
Who carries termination and redundancy cost?	Passed through to you	Vendor, subject to notice terms	Vendor, subject to ramp-down terms
Who supplies laptops, access and security controls?	You, usually	Vendor, to your standard	Vendor, audited by you
Who runs QA, DevOps and release discipline?	You must hire or provide it	Partly vendor, often optional	Vendor, as part of the model
How do you exit?	End each employment (with Philippine termination rules)	Contract notice plus handover	Contract exit plan, knowledge transfer, optional transfer of staff

Four Philippine rules that decide most of this

1. Probation ends at six months, then people are regular

Under the Labor Code, probationary employment cannot exceed six months from the start date, and an employee allowed to keep working after that is a regular employee. Regular employees can only be let go for a just or authorised cause. With an EOR, you decide who to hire, so you also own the six-month judgement on each person. Most Singapore sponsors underestimate how quickly that window closes when nobody in Manila is managing the team.

2. Redundancy has a notice period and a separation-pay floor

The same Code allows termination for redundancy, but only with written notice to the worker and the labour department at least one month before, and separation pay of at least one month’s pay or one month’s pay per year of service, whichever is higher. An EOR passes that cost to you. A dedicated-team or ODC vendor absorbs it inside its own workforce, and your contract only needs a ramp-down notice period.

3. Labour-only contracting puts liability back on the principal

Article 106 of the Labor Code describes “labor-only” contracting: where the party supplying workers lacks substantial capital or investment, and the workers perform activities directly related to the principal’s business, the supplier is treated as merely an agent and the principal answers to the workers as if it employed them directly. An arrangement where you hire, direct and control every engineer, and the intermediary only runs payroll, is exactly the pattern your counsel should test against this article and the labour department’s contracting rules. A vendor with its own premises, equipment, managers and multiple clients sits in a different place.

4. Copyright follows the employer, and commissioned work stays with the creator

The Intellectual Property Code is the rule most sponsors have never read. Section 178.3 gives copyright to the employer when a work results from the employee’s regularly assigned duties, unless agreed otherwise. Section 178.4 says that for a commissioned work, the person who commissioned and paid for it owns the work, but the copyright stays with the creator unless there is a written stipulation to the contrary. In practice: with an EOR, the EOR owns the code first, and you need an assignment from the EOR to you, plus employment terms that make software your engineers write part of their regular duties. With a vendor, you need one clear written assignment from the vendor. For the wider contract picture, see background IP and licence-backs.

The Singapore side: personal data leaves the country either way

If Philippine engineers can see production data about Singapore customers or staff, that is a transfer of personal data outside Singapore. The PDPC’s summary of the Transfer Limitation Obligation requires the receiving side to protect it to a standard comparable to the PDPA. With a vendor, those safeguards sit in the services and data-processing agreement. With an EOR, the engineers’ access runs through your own systems, so your own policies, contracts and access controls carry the obligation. The zero-trust access checklist for ODC engineers applies under any of the three models.

Worked example: six engineers for a Singapore payments product

Constructed example for illustration, not a client case. Peso figures are made up to show the arithmetic.

A Singapore fintech with an in-house CTO and two senior engineers wants six Philippine engineers for its merchant dashboard. The CFO likes the EOR quote because it looks like salary plus a monthly fee.

Run the four rules against it:

1. Probation. The CTO interviews and hires all six in month one. By month six each one is regular. The CTO spent those months shipping product, so two weak hires slip past probation without a structured review.
2. Redundancy. In year three the roadmap shifts and two roles are no longer needed. Each engineer has three years of service on an illustrative ₱120,000 monthly pay. The separation-pay floor is the higher of one month’s pay or one month per year of service: ₱360,000 each, ₱720,000 in total, plus at least one month of written notice. The EOR invoices all of it.
3. IP. Due diligence for a Series B asks for the IP chain. The EOR contract assigns “deliverables”, but the employment contracts never described software as the engineers’ regular duties. Counsel spends weeks tidying assignments.
4. Delivery. Nobody owns QA or release discipline, so the CTO becomes the team lead, the release manager and the recruiter.

The same six engineers in a dedicated team cost more per head on the invoice, but the vendor carries probation reviews, backfills, redundancy within its own workforce, and a single IP assignment. The real decision is not “EOR fee versus vendor rate”. It is whether the CTO’s time and the exit cost are worth the saving.

Common mistakes

• Comparing only monthly cost. An EOR quote leaves out management time, recruitment, equipment, QA and exit cost. Put every line on the same sheet before comparing.
• Treating an EOR as a vendor. An EOR does not promise delivery. If nothing ships, the contract was still performed.
• Assuming “work for hire” applies. Philippine copyright rules are specific. Get the assignment chain in writing, from the person who writes the code to the company that needs to own it.
• Ignoring the six-month clock. Diarise a probation review for every hire on day one.
• Skipping the exit plan. Decide on day one what happens if you scale down, switch vendors or open your own entity. The ODC knowledge transfer exit checklist covers the handover side.

Decision framework: five questions, in order

1. Do you have a full-time engineering leader with time to manage a remote team? No: rule out the EOR. Yes: keep it in.
2. Do you need named individuals you already know, or a capable team? Named individuals point to an EOR. A capable team points to a dedicated team or ODC.
3. Will you need QA, DevOps and delivery management you don’t have in-house? Yes points to an ODC.
4. How likely is a scale-down, pivot or acquisition in the next three years? High likelihood favours a vendor model, where redundancy cost and the IP chain are simpler.
5. Do you plan your own Philippine entity within eighteen months? Yes: an EOR or a dedicated team with an agreed staff-transfer option bridges well. Agree the transfer terms before the first hire.

If questions 1 and 2 say EOR and questions 3 to 5 say vendor, choose the vendor model and negotiate the right to interview every engineer. That gives you most of the control without the employment exposure.

FAQ

Is an employer of record legal in the Philippines?

EOR services operate openly in the Philippines. The question to test with counsel is not whether EORs exist, but whether your specific setup, with you hiring and directing every worker, could be characterised as labour-only contracting under Article 106 and the related labour department rules.

Can we move EOR engineers to our own entity later?

Yes, with planning. The transfer is a new employment relationship, so agree with the EOR in advance how service, benefits and any conversion fee are handled.

Does a dedicated team mean we lose control?

No. You still set priorities, join stand-ups and approve who joins. You give up payroll and line management, not product direction. See how a dedicated development team in the Philippines is usually structured.

Which model is fastest to start?

An EOR is fast to employ someone you have already found. A vendor with an existing bench is usually faster to start a whole team, because recruitment, equipment and onboarding already exist.

What to do next

Take the matrix to your CTO and CFO, answer the five questions honestly, and write down the exit you expect before you sign anything. If the answers point to a vendor model, compare it properly against our ODC and dedicated teams approach or the offshore development centre for Singapore companies, and get in touch for a walkthrough of the contract and IP structure.