Payment Complement Mexico: Payment Reporting Compliance Guide
Mexico’s Payment Complement is used to report payments received after the original invoice has been issued. Integrated into the CFDI framework, it helps businesses document deferred payments, instalments, and collections that do not take place at the time of invoicing. For companies operating in Mexico, this requirement is important for keeping payment information aligned with tax records and the fiscal treatment of the transaction.
How payment reporting works in Mexico
key implementation dates
01/07/2017
Payment Complement Mexico Overview
Implementation
Payment Complement 2.0 is the current version in Mexico. Since 1 April 2023, it has been mandatory as part of the CFDI 4.0 framework for payments received after invoicing
Tax Authority
SAT (Servicio de Administración Tributaria)
Format
Structured XML data incorporated into a CFDI 4.0 under the official Payment Complement standard and filling guidance
Digital Signature
Not a separate signature process. The complement is issued as part of the CFDI, following the standard validation and stamping model
Archiving
Supporting payment and tax records should generally be retained for five years in Mexico under the general tax record-keeping rules
Other Mexican regulations
CFDI 4.0, DIOT Mexico, Contabilidad Electrónica, Carta de Porte, Foreign Trade Complement
Looking to improve payment reporting control across your SAP landscape?
Frequently asked questions
What is the Payment Complement in Mexico?
When is the Payment Complement required in Mexico?
Is Payment Complement 2.0 mandatory with CFDI 4.0?
Do businesses need one Payment Complement for each payment received?
Is the Payment Complement separate from the original invoice in Mexico?
Can the Payment Complement in Mexico be managed through SAP or another ERP?
Our approach to SAP integration and Payment Complement compliance in Mexico
Mexico’s Payment Complement requires businesses to report payments received after invoicing within the CFDI framework. This means compliance depends on the accuracy and consistency of payment data, invoice references, and collection records across the wider process. As a result, the requirement affects not only payment reporting, but also how SAP systems support data reconciliation, document consistency, and alignment with SAT rules.
At Code10, we start by assessing the most suitable path for each SAP landscape. Where SAP standard is the right fit, we implement it through SAP Document and Reporting Compliance (SAP DRC), supported by our experience in SAP-based compliance projects. For companies looking for an alternative approach, our eCompliance Hub offers a flexible model to manage local requirements without the need for an SAP DRC licence. By combining regulatory knowledge, integration design, and delivery support, we help businesses adapt their SAP landscape to the Mexican framework in a clear and maintainable way.