An EOR service level agreement is what turns “we handle payroll” into a measurable commitment you can hold a provider to. This guide sets out the four service levels to demand in writing for Vietnam hiring, the evidence each one should produce, and the red flags that signal an SLA is not really an SLA. For Vietnam, the commitments to insist on are payroll on time every month, onboarding in 2 to 4 weeks, offboarding action within 24 hours, and clear incident response times.
TL;DR
- An EOR service level agreement should define when each service happens, who owns each input, what evidence the provider gives you, and what happens when a target is missed, so a vague “prompt support” promise is not enough.
- The four service levels to demand in writing are payroll on time every month, onboarding in 2 to 4 weeks, offboarding action within 24 hours, and incident and query response times by severity, each with named evidence.
- For Dutch and EU buyers, the SLA should also name a GDPR Article 28 data processing route, Vietnam SHUI and PIT proof, and a Vietnam PDPL process under Decree 356/2025 effective January 1, 2026, with a named escalation owner rather than a generic inbox.
What an EOR SLA should include
“An EOR service level agreement should turn payroll, onboarding, offboarding, and incident or query support into measurable commitments, each with clear ownership, named evidence, and an escalation path”.
A service promise tells you what a provider intends to do. An SLA tells you when it happens, who is responsible, and what you receive as proof.
If a commitment in the agreement cannot name a target, an owner, and an evidence output, it is not yet measurable, and that is the gap to close before you sign.
Why your EOR SLA matters before you sign
In an EOR arrangement, the provider operates the employment layer as the legal employer, while you keep operational control over the employee’s actual work. That split is useful, but it also means the parts you cannot see directly, payroll runs, statutory filings, offboarding actions, are exactly the parts that need written service levels.
A provider with no written SLA is asking you to trust operations you cannot observe. An employer of record SLA is not paperwork for its own sake, and an EOR performance guarantee is only as good as the targets behind it. It is the mechanism that makes cross-border employment measurable, which is the whole reason a finance or operations lead signs off on the spend.
An SLA review usually comes after you have already shortlisted vendors. If you are still at the comparison stage, it helps to compare EOR providers in Vietnam first, then return to the service levels once you have a shortlist.
The 4 EOR SLAs to demand in writing
These four service levels cover the operational core of Vietnam hiring. Each should state a metric, the scope, your dependencies, the evidence you receive, and the escalation path when a target slips.
1. Payroll on time every month
This is the SLA that finance cares about most. A payroll SLA, sometimes presented as an EOR payroll guarantee, means payroll on time every month depends on a defined calendar, not goodwill.
Demand a fixed payroll cut-off, an approval window, a payment date, a payslip delivery deadline, and a correction SLA for any error. Ask for the evidence too: a payroll calendar, a payslip sample, a reconciliation report, and a payment confirmation. The key dependency to agree is what happens when you submit late changes, since that is the most common cause of a missed run.
2. Onboarding in 2 to 4 weeks
A start date is a commitment to the new hire, so the EOR onboarding SLA needs a workflow, not a slogan.
Demand that the employee is ready to start within 2 to 4 weeks after complete documents and a signed agreement, subject to work permit and legal dependencies. Ask for an onboarding checklist, a document tracker, the employment contract issuance date, SHUI setup status, and a start-readiness confirmation. Agree up front what the provider needs from you, and when, so the clock does not stall on missing inputs.
The onboarding workflow itself is worth understanding in detail; an EOR onboarding Vietnam guide walks through each step.
3. Offboarding action within 24 hours
Offboarding is where operational speed and legal timelines must be separated clearly. The EOR offboarding SLA and the legal termination process are not the same thing.
Demand that operational offboarding actions start within 24 hours of an authorized request: access handoff, equipment recovery, and record steps. Legal termination, notice, final pay, and severance follow Vietnam law and the contract, on a different timeline. Ask for an offboarding request log, an access and equipment handoff list, a final payroll plan, and SHUI deregistration status.
Because the legal side is distinct, treat termination separately from the 24-hour operational action; an EOR termination Vietnam guide covers the statutory timeline.
4. Incident and query response times
Not every issue is urgent, so the SLA should sort them by severity. A single response time for everything is a sign the SLA was not designed for real operations.
Demand response targets by severity, covering a payroll issue, an employee query, a compliance question, and a data or security incident, each with a named resolution owner and an escalation path. Ask for a ticket log, a severity matrix, escalation contacts, and an incident summary when needed. Data or security incidents should align with your DPA and applicable GDPR and Vietnam data protection duties.
Before you sign an EOR agreement in Vietnam, make sure the service commitments are measurable. Sunbytes helps foreign companies set up EOR operations with payroll on time, onboarding in 2 to 4 weeks, and offboarding actions within 24 hours.
See how our EOR service works →
What each SLA should define
A useful way to pressure-test any provider’s draft is to put every service area into the same structure. If a row cannot be filled, the SLA has a gap.
| SLA area | Measurable target | Evidence to request | Red flag |
| Payroll on time | Paid on the agreed monthly date; payslips by deadline; correction window defined. | Payroll calendar, cut-off, payslip sample, reconciliation report, payment confirmation. | “Payroll handled promptly” with no date or correction process. |
| Onboarding | Ready to start within 2 to 4 weeks after complete documents and signed agreement. | Onboarding checklist, document tracker, contract issuance date, SHUI setup, start confirmation. | “Start immediately” with no document dependencies named. |
| Offboarding | Operational actions started within 24h of an authorized request. | Offboarding log, access and equipment handoff, final payroll plan, SHUI deregistration. | One vague “termination support” clause with no first-24h action. |
| Incident and query | Response targets by severity; named escalation owner and resolution path. | Ticket log, severity matrix, escalation contacts, incident summary. | No severity model, no owner, no written reporting. |
| Compliance update | Provider notifies of payroll, labor, SHUI, or data changes with an action path. | Compliance update log, effective date, action owner, payroll update note. | “Monitors compliance” with no cadence or responsibility. |
Vietnam-specific evidence to request
Service levels mean little without proof, and in Vietnam the proof is specific. The SLA should name which document, report, or tracker the provider produces for each obligation.
For Vietnam operations, request evidence across these areas:
- Labor contract setup: a Vietnamese or bilingual labor contract issued under the Vietnam Labor Code 2019 (Law No. 45/2019/QH14), with an issuance date you can see.
- Payroll, SHUI, and PIT proof: recurring remittance evidence and payroll summaries, not a statement that contributions are handled.
- Data processing terms: a GDPR Article 28 data processing agreement where the EOR processes EU personal data on your behalf.
- Cross-border transfer controls: a documented process under Vietnam’s PDPL, introduced by Decree 356/2025, effective January 1, 2026, which replaced Decree 13/2023.
- Compliance update process: a named owner and cadence for notifying you of payroll, labor, or data protection changes.
The contract-level detail behind these items, including clause wording, sits in the companion guide on EOR contract clauses. Treat all statutory and contract wording as items for legal or HR compliance review before you sign.
Red flags in an EOR SLA
If the language in an SLA cannot name the evidence, it is not measurable. Each red flag below has a better requirement you can ask for in writing, framed as a request rather than a confrontation.
| Red flag wording or issue | Better requirement to ask for |
| “As soon as possible,” “promptly,” “reasonable time” | Exact targets: by the agreed payroll date, within 1 business day, within 24h, 2 to 4 weeks after complete documents. |
| Provider commits to a service but names no proof output | A monthly payroll summary, SHUI and PIT status proof, ticket log, onboarding tracker, or offboarding confirmation. |
| No ownership split between provider and client | Defined client dependencies: signed approvals, employee documents, payroll inputs, start-date decision, termination instruction. |
| All requests go to a generic inbox or “support team” | Named escalation levels: account manager, payroll lead, compliance contact, and an emergency contact. |
| Repeated missed SLAs have no consequence or review | A service review cadence, a corrective action plan, and agreed remedies for repeated misses. |
| DPA missing or limited to generic confidentiality | GDPR Article 28 terms for EU data, plus Vietnam PDPL obligations, sub-processors, and transfer safeguards. |
| Offboarding, termination, and final pay mixed in one clause | Separate first-24h operational actions from legal termination and final payroll steps. |
Mini SLA template for your provider review
Use this as a working template you can send to a provider or turn into an internal review sheet. Fill the target and owner columns together, since a target with no owner is not enforceable.
| Service area | Target | Owner | Evidence | Escalation or remedy |
| Payroll | Paid by agreed date; corrections within set window | Provider payroll lead | Calendar, payslip, reconciliation, payment confirmation | Account manager, then service review |
| Onboarding | Ready in 2 to 4 weeks after complete docs | Provider onboarding owner | Checklist, contract date, SHUI setup status | Named contact, exception log |
| Offboarding | Operational action within 24h of request | Provider ops owner | Request log, access handoff, final payroll plan | Emergency contact |
| Incident or query | Response by severity tier | Resolution owner per tier | Ticket log, severity matrix, incident summary | Escalation ladder |
| Compliance update | Notice with effective date and action path | Compliance contact | Update log, action note | Service review cadence |
If you want a fuller scoring sheet across vendors, an EOR provider checklist extends this template into a side-by-side comparison.
How Sunbytes supports measurable EOR operations in Vietnam
A good service level agreement should leave fewer grey areas, not more. The point of every target above is the same: written commitments you can verify, rather than promises you have to trust.
When the agreement names a payroll date, an onboarding window, and a 24-hour offboarding action, Sunbytes delivers against those exact commitments through our Employer of Record (EOR) service in Vietnam. Payroll lands on time every month, onboarding completes in 2 to 4 weeks, and offboarding actions start within 24 hours, backed by the documentation an SLA should require.
This sits inside the broader employment infrastructure we operate for international companies entering or scaling in Vietnam. Through our EOR, staffing, and Contractor of Record (COR) services, we keep cross-border employment consistent and observable at every stage.
Why Sunbytes?
Founded in the Netherlands in 2011, Sunbytes has delivered more than 300 client projects across 20+ countries, with a delivery hub in Ho Chi Minh City and a 4 to 5 hour NL to VN working overlap. That combination of Dutch-led accountability and local grounding is what makes the service levels above realistic rather than aspirational.
Our three service pillars turn EOR operations into measurable commitments:
- Operations you can measure: Through Accelerate Workforce Solutions, we run EOR hiring against written targets, payroll on time, onboarding in 2 to 4 weeks, offboarding within 24 hours, with evidence on request.
- Payroll cadence and statutory proof: Through Payroll Services, we manage the Vietnam payroll calendar, SHUI, and PIT, producing the reconciliation and remittance proof your SLA should name.
Compliance-aware data handling: Through CyberSecurity Solutions, we apply access controls and incident handling that support your GDPR Article 28 DPA, with ISO 27001 certification
FAQs
It is the part of an EOR arrangement that defines measurable service commitments: when payroll runs, how fast onboarding and offboarding happen, and how incidents are handled. It names targets, owners, evidence, and escalation. A general statement that a provider “handles payroll” is a promise, not a service level agreement.
A proper SLA defines what happens when a target is missed, including a correction window for payroll errors and a corrective action plan for repeated misses. Without this, a missed deadline has no consequence and no review. Ask for a service review cadence and named remedies before you sign, so a missed run triggers a defined process rather than an argument.
No. The EOR contract sets the legal relationship, liability, and termination terms, while the SLA defines the operational service levels and evidence. They work together, and the SLA often sits as a schedule to the main agreement. Reviewing both matters, because a strong contract with a vague SLA still leaves the day-to-day operations unmeasured.
Operational offboarding actions, such as access handoff and equipment recovery, should start within 24 hours of an authorized request. Legal termination, notice periods, and final pay follow Vietnam law and the contract on a separate timeline. Keeping the two distinct in the SLA prevents the 24-hour operational commitment from being confused with statutory termination steps.
Yes, where the provider processes EU personal data on your behalf, the SLA should reference a GDPR Article 28 data processing agreement and align incident response with it. It should also reflect Vietnam’s PDPL obligations under Decree 356/2025, effective January 1, 2026. For cross-border transfers from the EU to Vietnam, ask qualified counsel to confirm the transfer mechanism.
At a minimum, expect a payroll summary, payslips, a reconciliation report, and payment confirmation, plus SHUI and PIT status proof. For onboarding and offboarding, expect trackers and confirmation logs. If a provider commits to a service but cannot name the proof output, that is the gap to close before signing.
Let’s start with Sunbytes
Let us know your requirements for the team and we will contact you right away.
