> For the complete documentation index, see [llms.txt](https://help.marcopayroll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.marcopayroll.com/marco-user-guide-x4/joe-black/eor.md).

# EOR

## **The Vendor Admin Chronicles – Episode 1: The EOR Conundrum**

Joe Black, the ever-diligent Vendor Admin at Marco, took a long sip of his coffee as he logged into the Marco Platform. His inbox was already lighting up.

> **Subject: Urgent - EOR Hires Needed**
>
> **Hey Joe,**
>
> We need to onboard two employees under our EOR vendor—one local, one foreign. Also, there's an expat case we need your help with. Here are the details:
>
> **Local Hire**
>
> * **Name:** Emily Tan
> * **Job Title:** Marketing Coordinator
> * **Country:** Singapore
> * **Start Date:** March 1, 2025
>
> **Foreign Hire**
>
> * **Name:** Alejandro Gómez
> * **Job Title:** Software Engineer
> * **Country:** Hong Kong (working remotely from Spain)
> * **Start Date:** March 5, 2025
>
> **Expat Assignment**
>
> * **Name:** Daniel Lee
> * **Job Title:** Finance Manager
> * **Home Country:** Malaysia
> * **Host Country:** Japan
> * **Start Date:** March 10, 2025
>
> Since these hires fall under an EOR arrangement, you'll need to set them up through **GlobalEdge Solutions** (our EOR vendor). Let us know once it’s done!
>
> **- HR Team, Orion Tech Solutions**

Joe leaned back in his chair. **Why do we need a vendor for EOR again?**

***

### **Why an EOR Vendor?**

An Employer of Record (EOR) acts as the **legal employer** for workers in countries where a company doesn’t have a local entity. Since **Orion Tech Solutions** didn’t have legal entities in **Singapore, Hong Kong, or Japan**, they partnered with **GlobalEdge Solutions** to handle employment compliance.

This meant GlobalEdge would:\
✔ Hire employees on Orion Tech’s behalf\
✔ Manage payroll, taxes, and benefits\
✔ Ensure compliance with local labor laws

Joe cracked his knuckles. "Alright, let’s get to work."

***

### **Step 1: Hiring a Local EOR Employee**

Joe navigated to **People > Add New Worker**.

1. Selected **Singapore** as Emily’s home country.
2. Chose **Local** for employment status.
3. Entered her **job title, start date, and assigned GlobalEdge Solutions** as the EOR vendor.
4. Clicked **Add**.

A success message popped up. One down.

***

### **Step 2: Hiring a Foreign EOR Employee**

Next, Alejandro’s profile:

1. Selected **Hong Kong** as the home country (since GlobalEdge was handling compliance there).
2. Set employment status to **Foreigner**, since Alejandro was based in Spain.
3. Entered his **job title, start date, and assigned GlobalEdge Solutions** as the EOR vendor.
4. Clicked **Add**.

Two down.

***

### **Step 3: Setting Up an Expat**

For Daniel’s case, **GlobalEdge Solutions was already added as the EOR vendor** in the earlier steps. Joe just needed to **verify that the correct entity was assigned**.

1. Selected **Daniel’s profile** under **People**.
2. Went to **Contract > Manage Record > Add New Record**.
3. Entered **Malaysia** as his home country and **Japan** as his host country.
4. Checked that **GlobalEdge’s Japan entity** was assigned.
5. Saved the changes.

***

### **Mission Accomplished**

Joe double-checked everything, then fired off a reply to HR:

> **Subject: EOR & Expat Setup Complete**
>
> **Hey HR Team,**
>
> All set! Here’s a summary:
>
> **Emily Tan (Local EOR - Singapore)**
>
> * Onboarded under **GlobalEdge Solutions**
> * Start Date: March 1, 2025
>
> **Alejandro Gómez (Foreign EOR - Hong Kong, working from Spain)**
>
> * Onboarded under **GlobalEdge Solutions**
> * Start Date: March 5, 2025
>
> **Daniel Lee (Expat - Malaysia → Japan)**
>
> * Host Country: **Japan**
> * Employer: **GlobalEdge Solutions (Japan entity)**
> * Start Date: March 10, 2025
>
> Let me know if you need any adjustments!
>
> **- Joe**

Within seconds, a reply came in:

> *"You're the best, Joe. We owe you coffee!"*

Joe smirked. Just another day in the life of a Vendor Admin.

***

#### **To Be Continued…**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.marcopayroll.com/marco-user-guide-x4/joe-black/eor.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.