An EOR service agreement should identify the employing entity, define each party’s responsibilities and state what happens to your money, employees and data when something goes wrong. Review all 12 clause groups together: a favourable indemnity may offer little protection if it sits under a low liability cap, while an easy commercial exit may still leave employee transfers unresolved.
The costly terms are rarely confined to the pricing page. They can appear in a country schedule, order form, data-processing addendum or online policy incorporated by reference. Before signing, give Legal, Finance, Security and People Operations the same document set. This guide explains what each team should test and how to turn broad promises into obligations you can operate.
What Is an EOR Service Agreement?

An EOR service agreement is the commercial contract between your company and the employer of record provider. It defines the services, responsibilities, charges, risk allocation and exit process.
It is different from the local employment agreement between the employing entity and the employee. A country schedule, order form, service-level agreement and data-processing addendum may also form part of the contract. State which document prevails when terms conflict. If you need to confirm the wider model first, review the Employer of Record services.
Twelve Clause Groups Decide What You Have Bought
Treat this table as a review tool, not model legal wording. Your counsel should assess the final agreement against the countries, roles and employing structures involved.
| Clause to review | What the agreement should answer | Escalate if |
| 1. Employing entity and scope | Which registered entity employs workers in each country? Is a partner involved? Which document records changes? | The provider can substitute an employer without notice or the named contracting company accepts no responsibility for its local partner. |
| 2. Responsibility matrix | Who approves offers, prepares contracts, supervises work, runs payroll, files contributions, handles leave and manages employee relations? | “The EOR handles compliance” replaces task-level ownership. |
| 3. Pricing and foreign exchange | Which fees apply to setup, monthly service, benefits, amendments, off-cycle payroll, termination and data export? Which FX source, date and margin are used? | Charges can be added through an online policy, or the invoice does not separate salary, statutory costs and provider fees. |
| 4. Payroll funding and deposits | When must funds clear? How is a deposit calculated, held, replenished, used and returned? What happens to undisputed payroll if one invoice line is challenged? | Late-funding remedies permit immediate payroll suspension without escalation, or deposit deductions are not itemised. |
| 5. Indemnities | Does each party cover losses caused by matters it controls? Who manages the defence, approves counsel and settles a third-party claim? | The client indemnifies every employment-related claim, including losses caused by provider error. |
| 6. Liability caps | Is the cap per claim or aggregate? Which fees and period form its base? Do separate caps or exclusions apply to confidentiality, data, fraud or indemnities? | A promising indemnity is neutralised by a low general cap or broad exclusion of recoverable losses. |
| 7. Employment claims | Who investigates grievances, payroll disputes, discrimination allegations and dismissal claims? Who preserves evidence and communicates with the employee? | Every claim arising from a client instruction is shifted to the client, even where the provider implements it incorrectly. |
| 8. Data and subprocessors | What are each party’s data roles? Where is data stored and accessed? Which subprocessors are used? How are incidents, requests, transfers, retention and deletion handled? | The data-processing addendum is unavailable before signature or material subprocessor changes require no notice. |
| 9. IP and confidentiality | How does work product move from employee to employing entity and then to the client? What information is protected, for how long and under which exceptions? | The agreement assumes the client automatically owns all employee-created work in every country. |
| 10. Service levels | Which payroll, onboarding, support and incident targets are measured? What are the escalation route, reporting method and remedy for repeated failure? | Targets are described as aspirations, exclude partner performance or provide only discretionary service credits. |
| 11. Termination and renewal | What are the initial term, automatic renewal, non-renewal deadline, price-review mechanism, cure period and termination-for-cause rights? | A missed notice date creates another long fixed term or permits an uncapped renewal increase. |
| 12. Employee transfer, survival and disputes | How are employees, records, deposits and data transferred at exit? Which terms survive? What law, forum, language and dispute process apply? | Commercial termination automatically triggers employee termination, or transition help has no deliverables or deadline. |
Use the EOR due-diligence checklist to verify the provider and local structure. Use this article to negotiate what the resulting agreement must do.
A Responsibility Matrix Makes Scope Testable
Put the matrix in the agreement or an incorporated schedule. “Joint” should still name one accountable owner, a required input and an escalation deadline.
| Activity | EOR provider | Client company | Joint control |
| Validate local employment structure | Accountable | Supplies role, location and working model | Approve deviations before an offer |
| Select candidate and set compensation | Checks local feasibility | Accountable for selection and business case | Record approved offer |
| Issue local employment contract | Accountable | Confirms commercial inputs | Approve material changes |
| Direct daily work and performance | Advises on local process | Accountable | Escalate conduct or capability concerns |
| Run payroll and statutory calculations | Accountable | Supplies and approves inputs | Reconcile corrections |
| Fund payroll | Provides amount and deadline | Accountable for timely cleared funds | Escalate shortfalls before pay date |
| Handle grievances or claims | Leads employer process | Supplies evidence and management context | Agree communications and legal strategy |
| End employment or transfer employee | Implements lawful process | Provides business decision and evidence | Confirm cost, timing and continuity |
The safest position is responsibility aligned with control. The provider should stand behind employer-side work it performs; the client should stand behind accurate inputs and lawful workplace instructions. Where both contribute, the contract should allocate loss by cause rather than sending every claim to one party.
A CPF Calculation Tests Funding Language
Suppose the provider employs a Singapore Citizen aged above 55 to 60 who earns S$10,000 entirely in Ordinary Wages.
According to the CPF Board, the rates effective 1 January 2026 for this age group and monthly wages above S$$750 are **16% employer** and **18% employee**. The Ordinary Wage ceiling is **$$8,000** as of November 2026.
- CPF-assessable Ordinary Wages:
min(S$10,000, S$8,000) = S$8,000 - Employer contribution:
16% × S$8,000 = S$1,280 - Employee contribution:
18% × S$8,000 = S$1,440 - Total CPF funding:
S$1,280 + S$1,440 = S$2,720
Your agreement should distinguish the S$$1,280 employer cost** from the **$$1,440 deducted from wages, while explaining how both amounts enter the funding request. It should also allocate responsibility when the client submits the wrong age or citizenship status, and when the provider applies the wrong rate despite receiving correct data.
For broader budgeting categories, use the EOR cost guide.
Data Duties Cannot Be Outsourced in One Sentence
Employee payroll records can include identity details, salary and bank information. Singapore’s Personal Data Protection Commission uses payroll administration as an example of processing by a data intermediary.
In its guidelines revised 29 April 2026, the PDPC states that an organisation has the same PDPA obligations for personal data processed on its behalf as if it processed the data itself. The regulator recommends making the intermediary’s scope and responsibilities clear in the contract.
That makes “each party will comply with applicable law” an incomplete operating rule. The agreement should identify processing purposes, data roles, approved locations, security duties, subprocessor controls, incident cooperation, retention and return or deletion. It should also say who answers employee requests and who supplies evidence during an investigation.
What Employers Get Wrong About EOR Agreements
Reviewing clauses separately. An indemnity, exclusion and liability cap can change one another. Read them as one recovery mechanism.
Confusing service termination with employee termination. Ending the MSA does not itself settle local employment, final pay or employee consent. Build a separate transfer or lawful exit workflow.
Accepting changeable web terms. Record which online policies apply, their version date and the process for material changes.
Negotiating a credit instead of continuity. A small service credit does not pay employees. For missed payroll or security incidents, prioritise escalation, corrective action and exit rights.
If planned headcount is uncertain, prefer shorter commercial commitments and a documented transfer route. If your workforce will be stable and long term, compare the agreement with the control and operating cost of your own entity before accepting restrictive renewal terms.
FAQ About EOR Service Agreements
Who Should Review an EOR Agreement?
Legal should review risk allocation and dispute terms. Finance should test fees, FX, deposits and funding. People Operations should test employment workflows. Security or Privacy should review data terms. One contract owner should reconcile their comments because the most important risks sit between clauses.
Is the EOR Liable for Employment Claims?
Not automatically for every claim. Applicable law and the final contract matter. The agreement should distinguish claims caused by provider payroll or employer-process errors from claims caused by inaccurate client data, workplace conduct or an unlawful client instruction. Review the indemnity, cap, exclusions and claim-control procedure together.
What Should an EOR Service Level Cover?
Useful service levels cover measurable events such as payroll delivery, funding notices, employee queries, onboarding steps, incident escalation and corrections. Each target needs a starting point, clock, owner, exception rule and remedy. Availability percentages alone say little about whether an employee is paid correctly.
Can Employees Move to Another EOR?
They may be able to, but the method depends on local requirements and the providers involved. The agreement should require transition cooperation, specify records and timelines, and explain fees and deposit reconciliation. The operational steps belong in a transfer plan, supported by the guide to switching EOR providers.
Should the EOR Agreement Include a Data-Processing Addendum?
Include or incorporate appropriate data terms before personal data is transferred. The document should reflect the parties’ actual roles rather than assign one label to every activity. It should cover instructions, security, subprocessors, transfers, incidents, assistance, retention and exit.
Review the Agreement Before the First Hire
You can build a local employing entity and manage these responsibilities internally, or use an EOR under a contract that fits your countries and risk tolerance. Glints TalentHub’s Employer of Record service can provide a country-specific structure and scope for review before onboarding.
Key Takeaway
Choose the agreement whose obligations remain clear when payroll is late, an employee makes a claim or you decide to leave. If a clause does not identify the entity, owner, deadline, cost and remedy, ask for an operational schedule before signing.



