Payroll Template Payslip Mexico

Standard Operating Procedure: Mexico Payroll Template Configuration (CFDI 4.0 Compliance)

1. Executive Summary & Purpose

This SOP mandates the architectural requirements and procedural steps for generating compliant Mexican payslips (Recibos de Nómina) under the SAT (Servicio de Administración Tributaria) CFDI 4.0 schema. The purpose is to ensure full legal compliance with Mexican Labor Law (LFT) and Fiscal Legislation, mitigating risks of tax non-compliance.

2. Scope & Prerequisites

• Scope: Applies to all payroll administrative staff and HRIS architects processing payments for employees subject to Mexican tax jurisdiction.
• Software Requirements:
  • Validated SAT-authorized PAC (Proveedor Autorizado de Certificación).
  • Digital Tax Stamp (Timbrado) service integration.
  • ISO-compliant payroll calculation engine (e.g., SAP, Oracle NetSuite, or local equivalent).
• Prerequisites: Validated Certificado de Sello Digital (CSD) and tax identification data (RFC) for both employer and employee.

3. Roles & Responsibilities (RACI Matrix)

4. Step-by-Step Procedure

Phase I: Data Validation & Mapping

• Verify employee RFC (must match SAT Constancia de Situación Fiscal).
• Confirm "Código Postal" of the employee's registered fiscal address.
• Validate "Régimen Fiscal" codes (e.g., 605 for Wages/Salaries).

Phase II: Calculation & Template Injection

• Apply statutory deductions (IMSS, ISR, Infonavit).
• Populate template fields: Percepciones (001-Salary, 023-Bonus), Deducciones (002-ISR, 001-IMSS).
• Execute XML generation ensuring CFDI 4.0 schema compliance.

Phase III: Certification (Timbrado)

• Submit XML batch to PAC for electronic stamping.
• Capture the UUID (Universal Unique Identifier) provided by the SAT.
• Update the payroll register with the timestamped metadata.

Phase IV: Distribution & Archive

• Generate PDF representation (Representación Impresa) including the QR code.
• Deliver via encrypted portal or secure email to the employee.
• Store XML/PDF package in a 5-year immutable audit repository.

5. Quality Assurance & Pro-Tips

• Precision Metric: 100% of generated payslips must be validated against the SAT schema validator before final transmission.
• Common Pitfall: Mismatch between employee name on the payslip and the SAT tax ID database. This is the #1 cause of timbrado rejection.
• Pro-Tip: Use a "Sandbox Environment" for payroll template changes to ensure calculated values (ISR tables) reflect the most current SAT updates before production deployment.
• Audit Threshold: Any error rate >0.5% in tax calculation requires an immediate reconciliation audit of the payroll engine's logic.

6. Frequently Asked Questions

Q: Why was the CFDI rejected by the PAC? A: Most rejections are due to metadata mismatches. Verify that the "Nombre" (as recorded in the SAT registry), "RFC," and "Código Postal" are character-perfect matches.

Q: How do we handle end-of-year bonus (Aguinaldo) tax calculations? A: The template must support "Complemento de Nómina" logic, specifically the calculation of the ISR sobre aguinaldo using the annual table, rather than the standard monthly payroll table.

Q: Is digital signature mandatory for Mexican payslips? A: Yes. The electronic stamp provided by the SAT (via the PAC) is the only legally binding evidence of payment for tax deductibility under Article 29-A of the CFF.

Authorization: Julian Vance Chief Architect, Template Registry