Employer of Record Mexico: Costs and Compliance Guide for Foreign Companies

An employer of record in Mexico can employ local staff for a foreign company that does not have a Mexican entity. In the employment agreement, the EOR is the named employer and carries the local payroll and benefits obligations. Candidate selection during the hiring process and day-to-day direction normally remain with the foreign company.

Separating legal employment from day-to-day direction defines the EOR's operational role. Mexico's labor laws and its REPSE, tax, intellectual-property, privacy, and permanent-establishment rules follow the actual arrangement, not the EOR label. Buyers need a documented chain from the Mexican employer to payroll and exit before the first employee starts.

The legal sources and public price examples in this guide were checked on August 13, 2026. Obtain advice on Mexican law, tax, and payroll requirements for the actual arrangement.

What is an employer of record (EOR) in Mexico?

The Mexican EOR entity is named as the employee's local employer and takes on payroll and employment administration. A typical service covers:

• localized employment contracts that comply with Mexican law;

• employee onboarding, registration, and payroll management;

• income-tax withholding, payroll tax filings, and payroll receipts;

• Mexican Social Security Institute (IMSS) and INFONAVIT processes;

• mandatory benefits and other employee entitlements, plus approved voluntary benefits such as private medical insurance;

• leave, expenses, and employment changes;

• local HR support; and

• resignation or termination administration.

The client remains responsible for the business role, technical work, day-to-day priorities, system access, performance input, and integration into its team. Managing remote development teams remains an operating responsibility, while the services agreement needs to show where the client's authority stops and the EOR's legal-employer authority begins.

EOR vs professional employer organization (PEO), payroll provider, and software vendor

Legal-employer status and control of the work distinguish the models below.

Forming your own legal entity is the closest structural comparison for an EOR. A managed software outsourcing arrangement is a different purchase because the provider controls its team and delivery method. Buyers evaluating staff augmentation also need to distinguish employment administration from delivery management.

Why foreign companies use an employer of record in Mexico

Companies hiring employees in Mexico may use an EOR to:

• hire a small initial team before an entity is justified;

• employ a candidate who must be on local payroll;

• enter Mexico while entity formation, payroll operations, and local HR infrastructure are still being evaluated;

• test a market or operating model with a defined decision date;

• transfer an existing worker from a contractor arrangement to employment; or

• support a temporary transition between providers or entities.

The model becomes weaker when the buyer expects a large, permanent operation, needs local contracting or regulated activity, wants complete control over employment policy, or pays growing per-employee fees that would finance its own infrastructure.

A provider is a poor fit when it cannot clearly identify the Mexican employer, explain its REPSE position, reconcile payroll, trace IP, or support the work location. Unusable transfer or termination terms are another warning.

The Mexico-based development hub provides the broader country and provider context; the directory of global software providers offers a wider market view.

Who is the actual Mexican employer?

The brand on the sales proposal may not be the entity on the employment agreement. A global platform can use its own local entity, an affiliate, or a local partner.

For example, the sales contract may name a global platform, the employment agreement a Mexican affiliate, and the payroll file a local operating partner. The buyer must pin down which entity owes wages, files payroll, controls the employment relationship, and holds employee data.

Request this evidence before approving a candidate:

• full legal name of the Mexican employing entity;

• RFC and corporate-registry details;

• registered address and contracting entity;

• IMSS and INFONAVIT employer registrations;

• whether another party runs payroll or provides local HR services;

• the employment-agreement template;

• the service agreement and order form identifying all parties; and

• the entities that invoice, receive funds, process data, and hold deposits.

The buyer needs one entity map from the commercial contract to the employee. If the commercial counterparty and local employer differ, the agreement should allocate liability, instructions, audit rights, service continuity, and replacement if that relationship ends.

Mexico labor law and REPSE requirements

There is no reliable one-word answer for every EOR arrangement.

Article 12 of the Federal Labor Law prohibits personnel subcontracting. Articles 13–15 permit specialized services or works outside the beneficiary's corporate purpose and predominant economic activity when the statutory conditions are met. The STPS describes REPSE registration in terms of specialized services and the provider placing its workers at a third party's disposal.

In a typical EOR setup, the client directs the employee's daily work. That allocation matters under Mexico's subcontracting rules. Remote work, a global platform, or an EOR clause does not settle whether workers are placed at the client's disposal or whether the service qualifies as specialized.

Before signature, obtain a written Mexican legal position that addresses:

• the buyer's corporate purpose and predominant economic activity;

• the EOR's registered activity and service scope;

• who assigns work, hours, leave, performance goals, and discipline;

• where and how the employee works;

• whether the employee is integrated into the buyer's normal operation;

• the relevant REPSE registration, activity, and validity if the arrangement is in scope;

• the written-contract and approximate-worker-count requirements; and

• the supporting tax, IMSS, and INFONAVIT evidence.

“The provider has REPSE” is not a complete answer. Check the legal name, RFC, registered service, status, renewal date, and fit with the contracted work. Being registered does not, by itself, make an otherwise prohibited arrangement permissible.

What an EOR in Mexico costs

Budgeting starts with more than the EOR platform fee. Separate these cost lanes:

1. contractual employee salary;

2. statutory employer contributions, including social security contributions and payroll tax;

3. voluntary benefits and employee expenses;

4. EOR service fee;

5. FX and payment charges;

6. deposit, reserve, or prefunding requirements;

7. equipment, immigration, checks, and add-ons; and

8. termination, transfer, and exit exposure.

Current public EOR list-price examples

On August 13, 2026, these global list prices were displayed. They are reference points rather than Mexico quotes and can change.

At list price, a fee of USD 599 per month is USD 7,188 per employee per year; USD 699 is USD 8,388. Those annual figures cover only the service fee; project rates and delivery assumptions belong in a separate software outsourcing cost model. Do not add them to a peso payroll model without a dated exchange rate and the provider's actual invoicing terms.

Request a binding Mexico quote that states:

• billing currency and the currency used to pay employees;

• exchange-rate source, timing, spread, and conversion fee;

• deposit or reserve and refund conditions;

• invoice timing and prefunding deadline;

• included HR and legal support;

• benefits and insurance administration;

• equipment, background-check, immigration, and equity charges;

• off-cycle payroll and correction fees;

• termination assistance and continuing fee treatment; and

• discounts, minimum terms, and price-increase rights.

Underlying employment cost still matters

The narrow 2026 Mexico City scenario starts with MXN 50,000 monthly base salary, 15 days of aguinaldo, and 12 vacation days with a 25% premium. It uses the 2026 UMA reference value and the cesantía en edad avanzada y vejez contribution band for that salary. After adding a 0.54355% Class I mean or initial work-risk input, INFONAVIT, and the 4% Mexico City payroll tax, annualized cash cost reaches about MXN 794,380—32.4% above twelve monthly salaries.

The example excludes PTU, voluntary benefits, telework cost, administration, EOR fees, FX, deposits, termination, and other arrangement-specific items. It cannot be applied to a self-reported dollar compensation figure or another state without recalculation.

Read the invoice structure rather than the percentage alone. Ask the EOR for the employee-level employment-cost build rather than one total that buries salary, statutory charges, benefits, fee, and adjustments.

Payroll tax and monthly payroll evidence

Monthly records should reconcile what the buyer funded with what the employee and authorities received.

Privacy and access controls still apply. The buyer doesn't need every sensitive payroll document. Scoped evidence should still show accurate, timely payment and support a provider-performance review.

Mandatory benefits and employment contract terms in Mexico

The EOR employment agreement and client service order need to align on:

• role, job description, manager, work location, and start date;

• salary, applicable minimum wage, pay frequency, currency, and variable compensation;

• benefits, aguinaldo, vacation, leave, and expenses;

• working hours, rest, overtime, on-call coverage, and holidays;

• remote-work or telework terms, equipment, and connectivity;

• confidentiality, security, monitoring, and acceptable use;

• inventions, software, documentation, and assignment cooperation;

• performance input, warnings, and legal-employer authority;

• termination, resignation, notice, settlement, and dispute handling; and

• conversion or transfer to another employer.

Any probation period or contractual notice periods should appear consistently in the employment agreement and service order.

Don't let the client handbook silently promise terms the EOR has not adopted. Decide which policies apply, which are only operating guidance, and who can approve exceptions.

Mexico's live workweek transition also affects scheduling. The maximum ordinary week remains 48 hours in 2026 and falls by two hours per year until it reaches 40 in 2030, without a corresponding reduction in salary or benefits.

Intellectual property needs a complete chain

Software rights don't flow to the foreign client just because an engineer is paid through an EOR.

Mexico's Federal Copyright Law treats commissioned works, employment works, and computer programs through related but distinct provisions. The written employment agreement matters. The buyer needs a traceable chain:

developer → Mexican EOR employer → client

The employment agreement and software outsourcing contract should cover:

• source code, object code, documentation, designs, data models, and inventions;

• foreground and background IP;

• assignment, license, further transfer, and post-termination cooperation;

• open-source and third-party components;

• repository, cloud, domain, and credential ownership;

• moral-rights limitations under applicable law; and

• subcontractor or prior-employer conflicts.

Trade-secret protection also requires practical controls: classified information, restricted access, confidentiality duties, logging, device handling, and an evidenced exit.

Permanent-establishment risk under an EOR

The US–Mexico income-tax treaty addresses permanent establishment through tests that include a fixed place of business and certain non-independent persons who habitually exercise authority to conclude contracts in the enterprise's name. Independent-agent and preparatory or auxiliary exceptions depend on the facts.

Tax diligence should cover:

• the employee's work location and any space at the foreign company's disposal;

• authority to negotiate or conclude contracts;

• customer-facing and revenue-generating activity;

• management functions and local decision authority;

• how long the arrangement is expected to last;

• the relationship between client, EOR, and employee; and

• the applicable treaty and domestic-law analysis.

A “no entity” structure still requires tax analysis. The EOR addresses employment administration; work location, authority, and local activity help determine the PE position under the applicable treaty and domestic rules.

Data privacy and security follow the actual access

The EOR processes employee and payroll data. The employee may also access the client's customer records, repositories, logs, credentials, analytics, or production systems. A software vendor security review should separate those processing purposes because they may place the parties in different roles.

Start with a data map that identifies:

• each dataset and purpose;

• the client, EOR, platform, benefits providers, and other subprocessors involved;

• hosting and support locations;

• international access and transfer terms;

• permissions, monitoring, incident escalation, retention, and deletion; and

• the records returned or retained after employment ends.

Contracts, employment documents, privacy notices, and technical controls should describe the same roles and data flows. A platform security certificate is useful only within its actual boundary.

Termination, severance, and labor-dispute procedures

The client can't treat a platform button as a Mexican termination process. As the employer, the EOR should control the legally required notice, evidence, severance pay calculation, and settlement. The client controls the business decision and system access under the agreed workflow.

The termination scenario—resignation, mutual separation, justified dismissal, unjustified dismissal, or valid fixed-term completion—changes the calculation. The 20-days-per-year measure in Article 50 isn't a blanket add-on. Employee tenure, accrued rights, claim strategy, settlement, and evidence matter.

The order form and termination protocol should assign:

• who can request and approve termination;

• what evidence and performance process the EOR requires;

• expected advice and response times;

• deposit or reserve mechanics;

• who bears settlement and litigation costs;

• how service fees continue during notice or dispute;

• final payroll and employee-document delivery;

• device, repository, credential, and data recovery;

• transition assistance; and

• conversion to the buyer's entity or another provider.

A sound exit leaves the buyer with code, documentation, access, and continuity while the EOR retains only records it has a lawful reason to keep. When the EOR sits inside a broader provider relationship, the vendor transition plan should also cover delivery ownership and knowledge transfer.

EOR due-diligence scorecard

Use the same evidence categories for every finalist so that platform presentation does not obscure differences in legal structure, compliance risk, or operating control. This EOR scorecard adds employment-specific evidence to a broader software vendor selection process.

Run the same request across finalists. A polished platform demo is not local-entity evidence.

Employer of record versus your own entity in Mexico

Choosing between an EOR and a Mexican entity changes setup speed, recurring cost, policy control, and the buyer's ability to conduct broader local activity.

An EOR often works as a bridge within a broader software team hiring strategy. If exclusive vendor-employed capacity is the goal, compare a dedicated team model separately. Define the bridge's end: headcount, duration, commercial activity, cost, or policy complexity that triggers an entity review.

Legal and tax outcomes depend on the named entities, contracts, and actual working practices.