---
title: "The entity question is not the due diligence. It's the start of it."
description: "When you're evaluating an employer of record provider, 'do you own the entity?' has become the default opening question. It's a reasonable one. An…"
canonical: https://www.teamed.global/insights/eor-due-diligence-checklist
datePublished: 2026-06-22
---

When you're evaluating an employer of record provider, 'do you own the entity?' has become the default opening question. It's a reasonable one. An owned entity matters. But most buyers stop there, and most providers are happy for them to.

The harder questions come next. This checklist gives you those questions. They're structural, not legal. They're about how compliance is actually delivered, not just whether an entity exists.

## The entity layer

Start here, but don't finish here.

- Does the provider own the legal entity, or are they contracting through a third-party aggregator?
- In which countries do they own entities outright?
- Where they don't own an entity, how is that disclosed, and what alternative structure is in place?

The entity is the foundation. If a provider can't answer the first question cleanly and immediately, that tells you something. But a 'yes' to entity ownership is not, by itself, a compliance architecture. It's one layer of one.

## The counsel layer

An entity gets you a registered presence. It doesn't give you cross-border legal consistency.

- Who provides the provider's global legal oversight?
- Is that relationship with a named firm, and is it a formal partnership or an ad hoc arrangement?
- How does global counsel interact with the entity layer when an employment issue crosses borders?
- If you expand from one country into another with a very different regulatory environment, is the same legal framework applied to both, or does quality vary by region?

This is where most providers go quiet. A local entity in each country, without a global legal partner stitching them together, means your compliance in each market is only as good as that market's individual setup. You have no way of knowing whether the standard is consistent.

## The local specialist layer

Global counsel sets the framework. But some jurisdictions require depth that only comes from practitioners who work in that market every day.

- Does the provider use local employment-law specialists in high-complexity markets, or does the entity alone handle everything on the ground?
- How are those specialists selected and overseen?
- Are they integrated into the compliance process, or are they a fallback called only when something goes wrong?

The honest version of this looks like three distinct layers working together: owned entity, global counsel, local specialist. The incomplete version is one layer presented as if it's the whole answer.

## The transparency layer

Compliance architecture is only useful if you can see it.

- Can the provider show you, in writing, how compliance is delivered in each country where you're hiring?
- Do they disclose when a jurisdiction sits outside their owned-entity footprint?
- If something changes — a new ruling, a shift in local practice — how does that information reach you, and how quickly?

You should be able to draw a diagram of how your provider delivers compliance in any given country. If you can't, that's not a knowledge gap on your side. It's a disclosure gap on theirs.

## The people layer

Structure without people is a document. It's not a practice.

- Who actually handles your account, and what's their background?
- Is there a legal expert involved in your onboarding, or does that only appear when you raise a problem?
- When you have a question about an employee in a particular country, who answers it, and how?

The four things that should hold an EOR provider together are honesty about how they work, genuine care for the people being employed, real legal expertise at every layer, and technology that makes the whole thing visible and manageable. If any of those are thin, the structure underneath them is thinner than it looks.

## What to do with the answers

Don't accept vague answers to structural questions. 'We have local experts' is not an answer. 'We work with a global legal partner' is not an answer if they can't name the firm and describe the relationship. 'We own entities in over fifty countries' is a starting point, not a conclusion.

Push for specifics on the countries where you're actually hiring. Ask what happens when the entity layer isn't enough. Ask who you'd call in the middle of the night in a given market if something went wrong.

The providers who have built a real compliance architecture will answer these questions without hesitation. The ones who haven't will change the subject back to the entity count.

Entity ownership is table stakes. Now ask the rest.