Mexico Employment Law and Payroll: Benefits, Labor Cost, and Employer Obligations

Mexico employment law does not turn a software engineer's salary into one universal payroll-cost percentage. The employer must account for statutory benefits, social security, housing contributions, state payroll tax, profit sharing, telework duties, paid-time capacity, payroll administration, and scenario-specific termination exposure.

This guide builds those layers from a dated Mexico City example. It helps foreign employers compare a Mexican entity, an employer of record, and other routes for hiring developers in Mexico. The final payroll calculation still has to be performed employee by employee.

The legal and payroll sources were checked on August 14, 2026. Actual payroll should be calculated in the current IMSS SUA system and reviewed by qualified Mexican payroll, tax, and labor advisers.

Mexico employment law: the employer comes first

An employment relationship exists when a person performs subordinate personal work for another in exchange for pay, and the working facts carry more weight than an invoice, contractor label, platform description, or foreign-law clause.

Before building a cost model, identify:

• the Mexican legal employer and its employer registrations;

• the employee's work location and applicable state payroll tax;

• the contractual salary, pay frequency, variable compensation, and benefits;

• the employee's service-based vacation entitlement;

• the work schedule, weekly rest, overtime, and on-call arrangements;

• whether the statutory telework threshold is met;

• the employer's IMSS risk classification and current premium; and

• the termination, transfer, or conversion scenario being planned.

A buyer using its own Mexican entity carries these duties directly. An employer of record in Mexico performs local employer and payroll functions under contract, but the underlying employment costs and buyer-side operating risks do not disappear.

The software development in Mexico hub provides broader provider and country context.

Put the employment terms in writing

The written employment agreement should identify the employer and employee, the employment term, the services and work location, and the schedule. It also needs to record salary and payment arrangements, training, benefits, and other working conditions. For a software role, add confidentiality, applicable telework terms, repository and system access, and the intended intellectual-property chain to the control file.

An indefinite relationship is the default when the parties do not establish another valid term. A fixed term or defined project is valid only when its basis is permitted by the Federal Labor Law; an agreement's end date cannot supply that basis. Test the statutory basis before treating contract expiry as the termination or cost assumption.

Statutory employee benefits in Mexico

The Federal Labor Law establishes minimum rights. Employment agreements and collective terms can improve them, and service length changes some entitlements.

Mexico's aguinaldo minimum equals 15 salary days. For a monthly-paid employee, that is less than a full thirteenth salary, so the familiar “13th-month payment” shorthand overstates the statutory floor.

Paid vacation remains inside contractual salary, while the vacation premium is the separate cash addition and the days still reduce delivery capacity unless another person covers the employee's work.

The minimum vacation entitlement and the model's fixed-benefit integration factor increase with service:

The factor assumes statutory-minimum benefits and a fixed salary. Better contractual benefits, longer service, or variable compensation require a new employee-level calculation.

Minimum wage is a legal floor, not a software salary benchmark

For 2026, the official daily minimum is MXN 315.04 generally and MXN 440.87 in the northern-border free zone. These figures help test legal floors and some statutory calculations. They do not describe software engineer salaries in Mexico.

The maximum workweek is now on a transition path

Mexico's May 1, 2026 workweek reform keeps the maximum ordinary workweek at 48 hours in 2026 and reduces it by two hours per year until it reaches 40 hours in 2030.

The reform does not permit employers to reduce salary or benefits because the maximum week falls. A business that needs to preserve the same coverage may face a capacity cost even if annual salary is unchanged.

Do not translate the statutory maximum into a default schedule for nearshore software teams in Mexico. The employment agreement, daily limits, rest, overtime, night work, on-call coverage, and actual delivery pattern all need review.

What Mexican payroll includes

A comparable payroll model has at least five layers:

1. contractual salary and variable pay;

2. statutory minimum cash benefits;

3. IMSS and INFONAVIT employer contributions;

4. state payroll tax; and

5. contingent or arrangement-specific costs.

The fifth layer includes PTU, voluntary benefits, telework, overtime, paid-time coverage, administration, termination, immigration, equipment, and any EOR or intermediary fee.

IMSS requires a component calculation

Employer social-security cost combines:

• a fixed sickness-and-maternity item tied to the UMA;

• an amount on the salary base above three UMA;

• several percentages of the salary base for cash benefits, pensioner medical benefits, disability and life, childcare, social benefits, and retirement;

• a salary-band-dependent cesantía en edad avanzada y vejez (CEAV) rate;

• an employer-specific work-risk premium; and

• a 25-UMA ceiling for applicable contribution calculations.

Salary, pay mix, benefits, UMA, risk experience, contribution days, and year all affect the result. The 2026 CEAV rate used in the worked example is transitional; projections need the rate for the year being modeled.

For a salary base above 4.01 UMA, the employer CEAV rate follows this official transition:

These percentages cover only the CEAV component of IMSS. Other salary bands use their applicable rates.

Work risk also prevents one-rate budgeting. The Social Security Law sets a 0.5% to 15% range, while the employer's registered activity and claims experience determine the applicable premium. The 0.54355% used below is only the Class I mean or initial scenario input.

INFONAVIT and state payroll tax remain separate

INFONAVIT adds an employer contribution equal to 5% of the applicable integrated salary base.

State payroll tax depends on the employing state, its current rate, taxable base, exclusions, and incentives. The worked example uses Mexico City's 4% rate. It must not be copied into a Jalisco, Nuevo León, Querétaro, Baja California, or other state model.

Worked Mexico City employment-cost example

The following narrow scenario uses:

• MXN 600,000 annual contractual salary, paid as MXN 50,000 per month;

• statutory-minimum 15-day aguinaldo;

• 12 days of vacation and a 25% vacation premium;

• the UMA of MXN 117.31 effective February 1, 2026;

• a fixed salary for contribution purposes;

• a 7.513% 2026 cesantía and old-age rate because the modeled salary base exceeds 4.01 UMA;

• a 0.54355% Class I mean/initial work-risk input solely for illustration;

• Mexico City's 4% payroll tax; and

• no exemptions, credits, subsidies, incentives, or special treatment.

The example presents an annualized current run rate. A 2026 calendar calculation would instead apply the values and employee facts for each payroll period rather than carry one set of assumptions across the year.

Step 1: calculate the daily and integrated salary base

Article 29 of the Social Security Law uses a divisor of 30 for monthly pay.

Monthly salary = MXN 600,000 / 12
               = MXN 50,000

Daily salary   = MXN 50,000 / 30
               = MXN 1,666.666667

With statutory-minimum benefits, the integration factor is:

(365 + 15 aguinaldo days + 12 vacation days × 25%) / 365
= 1.049315068

The modeled daily salary base is MXN 1,748.858447. It sits below the 25-UMA ceiling of MXN 2,932.75 per day under the February 2026 UMA used here.

Recalculate the factor whenever contractual benefits or service-based vacation change.

Step 2: add minimum cash benefits

The first additions are the two statutory-minimum cash benefits used in this scenario.

The next step adds the employer-side charges used in this scenario.

Step 3: add modeled social security, housing, and payroll tax

The remaining narrow cost layers combine employer social security, housing, and the applicable Mexico City payroll tax.

Using these Mexico City assumptions, the annualized cash build reaches about MXN 794,380, or 32.4% above twelve monthly salaries.

The 32.4% result belongs only to this Mexico City scenario. PTU, telework, voluntary benefits, administration, termination, work-risk classification, state tax, salary level, and other facts can change it.

Why one payroll-burden percentage fails

The same model assumptions produce different salary uplifts because fixed UMA-based items matter more at lower salaries and the contribution ceiling matters at higher salaries.

All three rows are illustrative scenarios built from the same benefit, risk, tax, and annualization assumptions. An actual quote requires the employee's payroll facts.

The buyer should model each actual salary and employing state. Averages are especially weak when comparing senior engineers, whose salary base may approach or exceed a contribution ceiling.

The Mexico software outsourcing statistics reference keeps employer-cost measures separate from compensation, workforce, establishment, and services-trade data.

PTU belongs in a contingent cost lane

Employee profit sharing follows the employer's applicable profit rather than payroll. The current PTU percentage is 10% of the relevant profit base. Article 127 caps an individual's payment at three months of salary or the average PTU received during the preceding three years, whichever is more favorable to the employee.

New-business and other exemptions, the profit base, allocation, eligible workforce, and employee cap require entity-specific analysis. Budget PTU in one of three ways:

• zero only when an exemption or absence of distributable profit is supported;

• a scenario based on forecast taxable profit and the eligible workforce; or

• “not modeled—obtain entity-specific tax and labor advice.”

Do not bury a guessed PTU percentage inside loaded payroll cost.

Remote work can add employer duties and cost

Mexico's statutory telework rules apply when work from the employee's home or chosen location exceeds 40% of the time; occasional or sporadic home working falls outside that definition.

For a qualifying arrangement, the employer's control file needs to address written terms, equipment, maintenance, telecommunications, and proportional electricity. Information security, occupational safety and health, training, supervision, privacy, and the right to disconnect also belong in the file. NOM-037-STPS-2023 adds safety and health requirements for telework.

Budget telework from the actual policy and role. Equipment replacement, connectivity, coworking, travel, ergonomic controls, and home-office support do not reduce to a national allowance.

The broader remote vs hybrid work decision remains operational; the Mexican employment duties follow the actual arrangement.

Termination cost depends on the scenario

No single Mexican severance percentage works across resignation, mutual separation, justified dismissal, unjustified dismissal, or the valid end of a fixed term.

Article 50's 20-days-per-year measure applies under its own conditions; the three-month indemnity and Article 162's 12-days-per-year seniority premium have different triggers and calculation bases.

Obtain an employee-specific calculation before approving a reserve, settlement, or dismissal. Offboarding must separately address final payroll, access removal, devices, repositories, data, confidentiality, and transition.

Payroll controls and evidence to require

A compliant calculation is only one part of payroll. The employer needs a traceable monthly process.

Payroll files contain employee personal data, so access, retention, transfers, and provider handling need to follow Mexico data privacy law throughout the monthly process and the later retention period.

At the August 14, 2026 check, SAT's payroll complement version 1.2 uses revision E from January 1, 2026; the payroll control file should record the specification used and retain issuance, cancellation, correction, and employee-delivery evidence. A generated PDF alone is not the complete CFDI record.

If an EOR or payroll provider performs the process, require employee-level reconciliation. A single monthly invoice cannot show whether salary, benefits, employer charges, withholding, fee, FX, and adjustments were handled correctly.

Compare direct employment with other hiring routes

Direct employment gives the buyer the clearest control over roles, management, and continuity, while requiring a Mexican entity capable of handling employment, payroll, tax, accounting, privacy, and corporate compliance.

An EOR can provide the local employer while the buyer directs day-to-day work, whereas staff augmentation supplies vendor-employed capacity and can raise a separate REPSE in Mexico question. With a managed software provider, more of the delivery method and outcome sits with the vendor. Responsibility shifts. The commercial comparison therefore has to follow responsibility as well as price.

Use separate columns for:

1. employee compensation;

2. statutory employer cost;

3. voluntary benefits and operating costs;

4. entity or EOR administration;

5. staffing or provider fees; and

6. delivery-management and outcome risk.

This distinction also prevents a direct comparison between payroll and software outsourcing cost.

The same budgeting errors recur.