Invoice Requirements in Mexico: Legal Rules for 2026

Mexican IVA compliance runs through Comprobantes Fiscales Digitales por Internet (CFDI), issued via PAC providers and validated by the SAT. A pretty PDF without UUID, Timbre fiscal digital, and matching XML is usually useless for buyer deductions and internal audit. Complementos extend CFDI for carta porte, leases, payroll, and other regimes—your template must stay aligned with the Régimen Fiscal and Uso CFDI you actually operate under. This guide reflects 2026 expectations for ordinary B2B; it is not legal advice. Confirm 8% border rules, withholdings, and maquila structures with your contador. Multinationals often run parallel CFDI series per legal entity—never share folios across RFCs.

Required fields

CFDI 4.0-era invoices carry RFC for issuer and recipient, UUID, serie/folio, Fecha y hora de emisión, ClaveProdServ and ClaveUnidad per line, ObjetoImp, Traslados and Retenciones with correct rates, subtotals and totals, and digital certificates from the SAT. Notas de crédito must reference original UUIDs and adjust tax consistently. Carta porte and other complements attach when statute demands—omission can block logistics payments even when IVA math is otherwise fine.

Tax rules (VAT/GST/sales tax rates)

The general IVA rate is 16% across much of Mexico; certain border regions may apply 8% on qualifying transactions—verify SAT tables before freezing template footers. Zero-rated exports and specific transactions need correct tipo de comprobante and evidence. ISR withholdings on professional services often appear as retenciones on the CFDI; separate them clearly from IVA lines for AP teams. Maquila and IMMEX programmes demand complementos that generic templates omit—loop trade compliance into invoice design reviews.

Language requirements

Spanish is mandatory for SAT catalogue fields and official descriptions. English contract clauses do not replace códigos and regímenes printed on the fiscal XML.

Digital invoicing rules

PAC validation responses are part of your audit trail—archive XML, human-readable PDFs, and acknowledgements. Cancellation flows often need customer acceptance; avoid silent edits to issued files. Enterprise customers may reconcile UUID against portal uploads daily. Localisation of catalogue codes matters—ClaveProdServ mistakes are a top reason PAC rejections spike after SKU launches.

Penalties

The SAT may assess tax, fines, and recargos for invalid CFDI, late issuance, missing complements, or ledger mismatches. AP teams may withhold cash until UUID checks pass. SAT audits increasingly trace UUID histories across years—retain cancelled comprobantes with reason codes, not deleted rows. Related-party charges should mirror transfer-pricing documentation IDs on invoice memos when policy requires traceability.

Before each CFDI batch job, validate RFC, Uso CFDI, and Régimen Fiscal against SAT catalogues—PAC rejections spike after HR or legal updates change entity metadata without finance noticing. Keep a changelog of complementos attached to recurring services so seasonal adjustments do not orphan historical UUID chains.

Monthly, reconcile PAC acceptance logs to accounts-receivable subledgers; UUIDs without matching cash expectations often reveal mapping bugs before SAT correspondence arrives. When legal entities merge, freeze invoicing until new RFC metadata propagates to every CFDI template variant. Escalate any PAC rejection pattern above five per cent of daily volume to tax and IT leadership the same day—silent retries create cascading UUID gaps.

Template link

Use our Mexico invoice template as a summary layout alongside your PAC-authorised XML. Read the invoice tax compliance guide and tax rate lookup tool. Official references include SAT and the SAT portal home. Join InvoiceQuickly early access to keep Mexico aligned with your North American operations.