Home › Guides

Mexico CFDI: connect PUE, PPD and payment complements to receivables

A sales CFDI and a payment complement describe different events. If an ERP treats both as revenue documents, it can double sales while still producing valid-looking XML. If it treats a receipt as an ordinary bank posting with no fiscal workflow, it can close receivables while leaving the payment documentation incomplete.

This guide follows an ordinary domestic seller using CFDI 4.0 and the Pagos 2.0 complement. It separates invoice payment method, actual bank receipt, allocation and fiscal-document status. It excludes foreign exchange, factoring, withholding, advances, refunds and sector-specific concessions. Those cases need their own approved design before being added to this process.

Establish the current rule baseline

RMF 2026 rule 2.7.1.32 requires the operation's full-value CFDI and subsequent payment documentation in the applicable unpaid or instalment cases. The payment CFDI has zero in its header Total and carries the payment complement. Its deadline is the fifth calendar day of the following month. RMF 2026, rule 2.7.1.32

SAT's technical presentation distinguishes CFDI 4.0 with the payment complement version 2.0 and explains the payment document's zero invoice value. Use that distinction when designing the import, rather than treating a payment document as a sales credit or another commercial invoice. SAT payment-complement presentation

The first published 2026 RMF amendment's list of changes does not amend rules 2.7.1.32 or 2.7.1.39. First amendment, published 9 July 2026

The second published amendment changes other specified provisions, not those two rules. Second amendment, published 1 October 2026

The third published resolution concerns Annex 7 and states an entry into force of 31 December 2026; publication does not make that future effective date immediate. Third amendment, published 2 October 2026

These checks anchor the selected rules in 2026 material rather than an old FAQ's historical rule citation. They do not replace monitoring later amendments or reviewing the full technical specifications for the deployed connector. The tax owner should record the checked baseline and calendar controls in the implementation evidence.

Separate payment method from payment form

PUE and PPD belong to the invoice's payment-method decision. The actual means of settlement, such as a bank transfer, is a different fact. A customer promising to pay, a bank receipt arriving and a payment complement obtaining its fiscal identity are three different statuses.

Create a receivables record that connects the original invoice's UUID, commercial invoice number, customer, currency, gross balance and approved payment method. Connect each bank receipt to its allocation and each allocation to the relevant payment-complement document. Preserve the original receipt date, even if the integration submits the complement later.

Avoid using a free-text "paid" flag as the integration trigger. It cannot distinguish an unallocated bank transfer from a receipt applied to several invoices, a credit-note application or an incorrect receipt that was reversed. The fiscal workflow should start from an approved allocation with a stable identity and enough evidence to reconstruct the outstanding balance.

The tax owner should decide the supported policy for individual or permitted monthly payment documentation. Accounts receivable then works to that policy's cut-off and deadline. A daily exception queue is preferable to discovering undocumented receipts when preparing a month-end report.

Worked example: one sale and two receipts

The synthetic seller issues an approved PPD sale in MXN for goods with a net value of MXN10,000 and assumed standard-rated VAT of MXN1,600. The gross receivable is MXN11,600. The 16% rate is an explicit assumption for this transaction, not a statement about every Mexican supply. There are no fees, credits, exchange differences or tax remittances in the example.

For accounting, assume the goods have been delivered and revenue recognition has been approved. Record revenue MXN10,000, an output-tax control amount of MXN1,600 and receivable MXN11,600. This control amount does not assert that all MXN1,600 is payable or reportable before collection. The local tax owner must approve pending-versus-collected VAT realization and period reporting separately. The invoice's fiscal UUID must map to this receivable without requiring another revenue posting when payment information arrives.

The first bank receipt is MXN4,640, exactly 40% of the invoice's gross amount. Its proportional net component is MXN4,000 and tax component MXN640. Apply MXN4,640 to the invoice, leaving MXN6,960 outstanding. The payment documentation must identify the invoice and preserve the receipt, allocation, preceding balance, paid amount and remaining balance required by the approved technical implementation.

The second receipt is MXN6,960. Its proportional net component is MXN6,000 and tax component MXN960. Applied after the first receipt, it reduces the invoice's balance to zero. Total cash is MXN11,600, proportional net amounts total MXN10,000 and tax amounts total MXN1,600.

The original sales CFDI's gross amount remains MXN11,600. Each payment CFDI has a zero header Total while its complement carries the actual payment information. Zero in that header therefore does not mean that no cash was received. Conversely, adding the complement's MXN4,640 and MXN6,960 to sales revenue would double the commercial event.

The final simplified ledger has cash MXN11,600, receivable zero, revenue MXN10,000 and output tax MXN1,600. The accounting equation is MXN11,600 cash equals MXN10,000 contribution before excluded costs plus MXN1,600 unpaid tax. The payment documentation supports settlement; it does not create another MXN10,000 sale.

Manage an unpaid PUE concession

Rule 2.7.1.39 permits a conditional PUE treatment where full payment is expected and actually received by the invoice month's end. If that condition fails, it requires cancellation and replacement with PPD, the prescribed invoice relationship, and the relevant payment complements. Special financial-sector treatment is outside this guide. RMF 2026, rule 2.7.1.39

Maintain a separate month-end exception list for invoices using this concession. Compare the expected receipt with actual fully allocated payments, not the customer's promise or a bank file that has not yet been matched. Escalate partial and missing payments to the tax owner before the correction workflow proceeds.

Do not implement a blind "change PUE to PPD" update on the original XML. The controller and tax owner should approve the replacement sequence, verify any applicable cancellation conditions and preserve both old and new UUIDs. The integration owner must establish which document is authoritative and how already received cash remains allocated to the surviving commercial receivable.

Accounting should verify that replacement has not created a second open customer balance or an extra sale. The desired accounting outcome remains one underlying transaction, with a documented fiscal correction. Keep submitted requests and authoritative statuses, including any pending cancellation, so that customer support does not send inconsistent documents.

Recover from duplicate payment processing

Suppose the first MXN4,640 receipt is imported twice and both records are treated as separate payments. After the valid second receipt, the system appears to have received MXN16,240 against MXN11,600, creating a false overpayment of MXN4,640. A zero receivable achieved through a manual write-off would conceal the duplicate.

Treasury should match the bank's actual receipt identities. Accounts receivable should reverse the duplicate allocation through the approved accounting process. The fiscal owner should assess and correct any duplicate payment document using the appropriate supported procedure. The integration owner should make the receipt-and-allocation identity idempotent before replaying the affected batch.

At close, reconcile bank receipts to allocations, allocations to payment-document statuses, and remaining balances to the customer ledger. Include failed, pending and cancelled documents. "All receipts posted" and "all required payment documents completed" should be separate close assertions.

Completion checklist

• Approve the PUE/PPD policy, current legal baseline and payment-document calendar.
• Keep payment method, payment form, bank receipt and fiscal status distinct.
• Link original invoice UUIDs, receipts, allocations and payment documents.
• Reconcile preceding balance, paid amount and remaining balance per invoice.
• Test two partial receipts, a duplicate receipt and an unpaid PUE concession.
• Preserve replacement relationships without duplicating revenue or receivables.
• Retain authoritative responses and an owned queue of incomplete documents.

Use the Mexico receivables and payment-complement worksheet. Related guides cover cash allocation and tax recognition and revenue, billing and tax points.

Sources checked 17 October 2026. Public SAT schemas could not be retrieved during research; this is not a field-by-field XML validation recipe or a tested connector walkthrough.

Worksheet: Mexico receivables and payment-complement worksheet

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Related on this site

• Country pages: key facts with sources
• E-invoicing matrix: country × ERP support
• All guides

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: 2026-10-17 · Markdown version