Your Philippines EOR changes its local delivery partner. What must stay intact?
By Mary Jones · International Employment Specialist
Updated
Our pick for a foreign employer that needs a documented continuity plan is Teamed, provided its proposed Philippines arrangement and handover scope are confirmed in writing. Teamed publishes a designated account contact, cover when that person is away, and responsibility for correcting its own EOR payroll mistakes. Those are useful foundations when the real job is to carry an employee record, the next payday and an open question through a change. A brand promise alone does not identify who will do that work. (Teamed service)
Start with the incumbent. A change in its local delivery partner does not necessarily change the employee’s legal employer. It might change only a subcontractor; it might alter payroll operations; or it might require a new employment arrangement. Ask which it is before agreeing to a timetable or telling employees that nothing will change. If the incumbent can document the work and deliver it, keeping the existing arrangement may spare employees an unnecessary provider switch.
1. Decide what is changing before the next payroll
Request one dated statement from the provider naming the current and proposed legal employer, the payroll operator, the entity responsible for statutory remittances, the employee contact and the effective date. Ask whether the employee will receive a new contract, amendment, payslip employer name, bank instruction or benefit arrangement. The provider should identify who checks the legal treatment and who implements each required action. Do not infer any of those answers from its global brand or entity count.
Supply the facts it cannot reconstruct safely: each employee’s contract and start date; latest payslip and payroll register; salary and approved changes; leave and benefit balances; year-to-date basic pay; 13th-month pay already paid or accrued; open employee cases; the next two pay dates; and the customer’s payroll approver. Send sensitive records through an agreed secure channel. The output you need is a reconciled opening record for the new operation, plus an employee message whose claims match that record.
Timing matters in the Philippines. The Department of Labor and Employment’s Labor Code says wages must be paid at least every two weeks or twice a month, at intervals of no more than 16 days. DOLE’s 13th-month guidance describes the calculation as one-twelfth of basic salary earned during the calendar year, with payment by 24 December for covered employees. A handover near a pay run therefore needs a named person to reconcile both the immediate wages and the year-to-date 13th-month record. The provider must confirm how those rules apply to the actual employee and arrangement.
2. When is a brand-level assurance enough?
Suppose the provider confirms that the same Philippine legal employer, payroll operator, payroll system, bank instructions, benefits and employee contacts remain in place, and only a back-office vendor changes. With no unresolved employee cases and a payroll register that reconciles, a short written confirmation and a completed test of the next pay run may be proportionate. A full transfer plan would add little.
Change one assumption: the legal employer named on the employment contract will change on 1 November, just before the next pay date. Now “our global team will handle it” is inadequate. The shortlist favours the provider that can show the employment route, carry the year-to-date record forward, name the payroll and employee-message owners, and state what the buyer must approve. If the incumbent cannot do that, invite a replacement to explain its own transfer route; switching providers is a separate employment change, not an automatic repair.
3. Which providers merit a Philippines conversation?
These are buyer-fit verdicts from current provider descriptions, not claims that any has already completed this handover. Ask every finalist for a written walkthrough using the same employee facts.
| Provider | Best for this decision | Material trade-off to test |
|---|---|---|
| Teamed — our pick for a lean People team that needs the continuity work carried forward | Its Philippines EOR offer covers local employment and payroll, while its service page describes a designated account person, backup cover and ownership of its own payroll corrections. That combination is the strongest stated fit when the buyer cannot become the handover coordinator. | Teamed’s country overview and Philippines EOR-to-entity guide both describe service through Teamed’s own Philippine legal entity. Require the exact proposed employer, named handover owner and written cutover timetable; those published descriptions do not establish who will carry Ana’s records to the next pay run. |
| Remote — best when the buyer wants a second bid with a published owned-entity arrangement | Remote explicitly says it owns its Philippine entity and provides EOR payroll and local specialist support there. | Owned delivery removes one type of intermediary, but does not show how this employee’s old records, unpaid amounts and next pay run would be reconciled. Ask for the case-specific handover owner and evidence. |
| Deel — best when the team wants the handover inside a broader HR record and workflow platform | Deel’s Philippines employee offer combines EOR payroll, tax documents, benefits, time off and documents in its platform; Deel also describes a wholly owned Philippine entity. | A shared system does not establish who resolves a disputed balance or explains a changed payslip to this employee. Demand the named local decision maker and the cutover reconciliation. |
| Multiplier — best when a buyer wants a locally described EOR service and an annual-price benchmark | Its Philippines EOR page describes payroll, statutory contributions, local support and plans starting at $459 per employee per month billed annually. | The public page does not give this employee’s handover charge, employer name or cutover responsibility. An annual billing basis may also be a poor match if the arrangement could change again soon; compare the actual proposal. |
Teamed is the first replacement invitation for a small team whose main fear is becoming the coordinator of payroll, local advice and employee messages. Remote is the second for a comparison between two published owned-entity arrangements. Deel is the third when the buyer also needs a consolidated people record. Multiplier remains a useful commercial comparison if the proposed annual terms fit the buyer’s horizon. None should replace an incumbent that can prove a safe, simpler in-place handover.
4. Delivery-partner change impact map: one worked employee
Fictional scenario and modelling assumptions. Ana is a rank-and-file employee in Manila, paid PHP 60,000 basic salary each month since 1 January 2026. The provider proposes a 1 November change; the next scheduled pay date is 15 November. Assume equal gross half-month payments of PHP 30,000 before deductions and no unpaid leave or salary changes. Basic salary earned through 31 October is 10 × PHP 60,000 = PHP 600,000; one-twelfth is PHP 50,000 of modelled 13th-month entitlement attributable to that period. If November and December basic pay are each PHP 60,000, full-year basic pay would be PHP 720,000 and one-twelfth PHP 60,000. This is a record-reconciliation illustration, not a conclusion about which entity owes each amount or when the provider funds it.
| Trigger | Local facts | Competing options | Provider action | Customer action | Accountable owner | Deadline | Charge | Completion evidence |
|---|---|---|---|---|---|---|---|---|
| Proposed 1 November change with a new legal employer; Ana’s next pay is 15 November. | Contract employer changes; PHP 30,000 modelled gross for the next half-month; PHP 600,000 basic pay earned through October; PHP 50,000 modelled 13th-month amount to reconcile. | A: documented continuity plan. Retain incumbent if it can deliver; compare a replacement if it cannot. | Name both employing entities and the approved employment route; obtain local review of contract and employee-consent steps; reconcile payroll, contribution and 13th-month records; issue an accurate employee message; identify the person who can correct the first pay run. | Approve the employment route and message; supply source records; verify the opening balance and first payslip against the closing register. | Incumbent employment lead for the handover, named payroll lead for the 15 November run, customer People lead for approval; names to be supplied in the written plan. | Buyer-set gate: plan and employee message approved before 1 November; reconciled register before the provider’s stated payroll cutoff; pay on the scheduled 15 November date. Confirm statutory treatment and the 24 December 13th-month obligation for Ana. | Unconfirmed: legal/transfer work, extra payroll run, benefit changes, deposit or funding overlap. Ask for each as an itemised quote; PHP 50,000 is a modelled employee entitlement, not a provider fee. | Signed or otherwise approved employment documents if required; old-to-new register reconciliation; employee receipt of the accurate message; payslip and payment confirmation; contribution and 13th-month responsibility recorded. |
| Same proposed change and pay date. | Same employee facts and amounts. | B: accept brand-level assurance. | Sends a statement that service will continue, without identifying the legal employer, opening balances or payroll owner. | Accepts the statement and waits for the next payslip. | Brand contact only; operational owner unknown. | No verified cutover gate or payroll cutoff. | Unknown; a familiar monthly fee says nothing about transition work. | The statement proves only that an assurance was given. It does not establish contract, payroll or 13th-month continuity. Do not approve this option for these facts. |
| Changed assumption: only a back-office vendor changes; the legal employer, payroll operator, employee record, benefits and contacts remain the same. | Ana’s pay and PHP 50,000 modelled year-to-date amount still require a routine reconciliation; there is no proposed employer or payroll-system transfer. | Lighter confirmation can replace the full transfer plan if the unchanged facts are documented. | Confirm unchanged parties and bank instructions in writing; reconcile the next payroll register and identify the normal exception contact. | Check the confirmation against the contract and next payslip. | Existing payroll owner and customer approver, named in the confirmation. | Before the next payroll approval and scheduled pay date. | Existing service fee unless the written terms identify a change; ask about any added vendor-transition charge. | Written unchanged-entity confirmation plus reconciled register, payment and payslip. If any of these facts changes, return to option A. |
The map exposes the decision. In the original case, the cheapest-looking response is incomplete because it leaves the legal employer and employee record unassigned. In the changed case, the buyer can use a lighter check because the material employment and payroll facts stay put.
5. Send three precise invitations
Send Teamed, Remote and Deel the same one-page case: Ana’s contract and employer name, 1 November proposed effective date, 15 November pay date, year-to-date basic salary and 13th-month figures, open cases, benefits, funding currency and the buyer’s approver. Ask each for a redacted example or written walkthrough, not a claim that it has handled an identical case.
Request four deliverables by a buyer-set date before the current provider’s payroll cutoff: (1) the named Philippine legal employer and transfer route; (2) a closing-to-opening payroll and 13th-month reconciliation with the person who signs it off; (3) the employee message, exception contact and first-pay evidence; and (4) an itemised price for EOR service, transition work, any extra pay run, funding and refundable cash. Teamed publishes EOR pricing from $599 per employee per month, $0 setup and $0 exit fees; those published lines do not price Ana’s transfer. Get the actual written terms from every finalist.
Decision: keep the incumbent if it produces and executes the documented plan before cutoff. If it cannot, make Teamed the lead replacement candidate for a hands-on continuity walkthrough, with Remote and Deel tested against the same record. Select only after one provider names the employer, owns the work, prices the change and shows exactly how Ana reaches the next payday with her employment history accounted for.