---
id: KB-LE-006
url: https://app.codecontract.io/help/legal/payroll-and-hr-for-multiple-clients
idioma: en
categoria: sector-legal
subcategoria: laboral
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CS-022, KB-CF-007]
citadoPor: [KB-LE-007]
---

# Running payroll and HR for several clients

_Many different calendars, many deadlines, and data about people who are not yours._

**Responde a:** payroll bureau client documentation · hires and leavers for several clients · client payroll document management · employment deadlines across companies

Running payroll and HR for thirty companies is not doing the same thing thirty times: it is doing the same thing with thirty different calendars, thirty contacts and thirty ways of sending you things late. And with data about people who belong neither to you nor to your client: it is theirs.

## What repeats every month

| What | Who it depends on | What happens if it is late |
| --- | --- | --- |
| Payroll variables | The client | The whole chain slips |
| Hires and leavers | The client, with legal deadlines | The only thing that tolerates no delay |
| New employee documentation | The worker, via the client | You can start without it, but better not |
| Contract and amendment signatures | The worker | It blocks the hire if it does not arrive |

> [!IMPORTANT]
> Hires tolerate no margin and arrive latest, because the client tells you when the person is already working. A recurring request with reminders does not fix it entirely, but it turns "I found out on the 20th" into "I asked on the 1st and it is on record".

## The data you handle is not your client's

Payslips, identity documents, sometimes health data. They belong to your client's workers, people who never engaged you. One team per client is not internal tidiness: it is what stops one company's adviser seeing another's payroll.

**En corto**

- One team per client, with scoped permissions.
- Ask for the minimum: many tasks need no ID copy.
- And delete when the period ends, rather than accumulating.

> [!WARNING]
> When a client leaves, return their file and apply retention to the rest. Keeping the payslips of a former client's workers, with no obligation justifying it, is pure risk.

> [!NOTE]
> A scheduled monthly request with reminders at days 3, 7 and 12 turns the first week of each month from a phone campaign into four calls.

**Can I give the client access to their own?**

Yes, scoped to their company.

**What about the workers' signatures?**

They sign from their phones; they need no account and need not know you.

**How long do I keep it after a client leaves?**

Whatever your professional and employment rules require; check.

## Ejemplos

**A payroll bureau with 34 clients spends the first week of each month chasing variables.**

- Schedules the monthly request with reminders
- One team per client

→ The first week goes from thirty calls to four, and no adviser sees another client's payroll.

**Each company sends its returns through a different channel.**

- Agrees a single delivery channel

→ Deliveries stop getting lost.

**An onboarding arrives on the day the person starts.**

- Requests documentation in advance

→ Onboarding is prepared before day one.

**A client asks what they are missing every month.**

- Shows them their own outstanding list

→ They answer for themselves.

**A worker's documentation expires.**

- Records expiries per person

→ The warning arrives before it bites.

**Every close chases the same things.**

- Reuses the process from one month to the next

→ Follow-up stops being rebuilt.