Mexico Withholding Tax on Invoices: ISR, IVA, Retenciones

Mexico withholding tax on invoices usually means the payer does not hand over the full gross amount shown on the supplier's CFDI. Instead, the payer keeps back part of the tax, remits that amount to the tax authority, and pays the supplier the net balance after the retention. For many service payments from a Mexican legal entity to an individual, the common working pattern is 10% ISR plus IVA withholding equal to 10.6667% under the two-thirds rule, although the exact result still depends on the payment scenario and taxpayer status.

That is why this topic is not only about percentages. It is also about document classification. Routine retentions can appear inside a normal CFDI de Ingreso, while certain operations require a separate CFDI de Retenciones e Informacion de Pagos. If your team reviews only the rate table and ignores the document type, you can still approve the wrong payable amount or request the wrong supporting CFDI.

From an AP and accounting perspective, two questions matter first:

• Which retention applies to this payment?
• Where should that retention appear in the CFDI workflow?

Once you answer those two questions, the rest of the review becomes more mechanical: confirm the supplier type, validate the invoice math, check how ISR and IVA are represented, and make sure the payment record matches what SAT expects.

---

Which payments usually trigger ISR and IVA retention

The common withholding pattern appears most often when a persona fisica provides services to a Mexican legal entity. In that scenario, AP teams often see both ISR retention and IVA retention on the same invoice review. A frequent operational shorthand is:

Payment scenario	Common withholding pattern	What AP should verify
Professional services paid to an individual	10% ISR is commonly withheld	Confirm supplier type, contract nature, and taxable base
Services subject to 16% IVA where the two-thirds rule applies	IVA retention often equals 10.6667% of the taxable base	Confirm the invoice actually carries 16% IVA and the transaction falls into the common withholding scenario
Rent or commissions paid to an individual	ISR withholding is often part of the review	Check whether the payment falls into the same retention logic as the underlying tax treatment
Supplier is not in the standard individual-service pattern	The headline rates may not apply	Stop and verify taxpayer classification before calculating the payable amount

The important point is that 10% ISR and 10.6667% IVA are useful starting points, not universal defaults. Teams get into trouble when they see a Mexican service invoice and assume the same result applies every time. The invoice needs to be read together with the supplier's taxpayer profile and the type of payment being made.

In many professional-services cases, AP will review both retentions together on the same invoice: 10% ISR and IVA retention at 10.6667%. That combined pattern is common, but it still needs to be confirmed against the supplier profile and the transaction type before payment is approved.

For regional teams, it also helps to remember that Mexico's logic is not interchangeable with other Latin American regimes. If you manage cross-border workflows, compare it with Brazil's service-invoice withholding workflow for contrast rather than assuming the same service-payment mechanics apply country to country.

How taxpayer type and missing RFC details change the result

The first control point is whether the supplier is a persona fisica or a persona moral. The common invoice-retention pattern discussed above is associated with specific payer and supplier combinations, especially where an individual supplies services and the customer is the withholding party. If the supplier is a legal entity, the review often changes immediately because the standard individual-service assumptions may no longer fit.

The next control point is the supplier's RFC. If the RFC is missing, inconsistent across documents, or tied to the wrong taxpayer type, the team may not be able to support the withholding treatment shown on the invoice. Even if the invoice math looks plausible, weak taxpayer data can turn a routine approval into a tax-review exception.

This is where finance teams should slow down and check the basics before they calculate net payment:

• Is the supplier classified correctly for Mexican tax purposes?
• Does the RFC on the invoice match the supplier master data?
• Does the payment really belong to the standard domestic withholding workflow?
• Is there any sign this is a foreign or atypical arrangement that needs separate review?

In practice, withholding mistakes often come from classification errors rather than arithmetic. A team that confirms supplier type and RFC quality early will catch more issues than a team that jumps straight to the percentage.

---

How routine retentions appear inside a CFDI de Ingreso

For ordinary invoice scenarios, routine ISR and IVA retentions are usually handled inside the CFDI de Ingreso itself. The payer does not need a separate retention document just because the invoice includes withheld taxes. Instead, the retained amounts sit within the invoice's tax structure and reduce the amount the supplier actually receives.

From a workflow perspective, that means the invoice review has to connect tax fields to payment math. Under CFDI 4.0, teams should look at the invoice tax breakdown, including the Impuestos Retenciones node, and reconcile it against the commercial totals on the document. A clean review should identify:

• Gross taxable amount
• IVA charged by the supplier
• ISR retained by the payer
• IVA retained by the payer
• Final net amount to be paid
• Supplier identity and RFC

This distinction matters because a Mexican invoice can show both taxes charged and taxes withheld at the same time. If your team reads only the subtotal and total, you can miss why the payable amount is lower than the supplier's tax-inclusive figure.

If your reviewers need a refresher on the wider XML structure, Mexico's CFDI 4.0 document types and XML structure gives the broader context. For this article's purpose, the key point is narrower: routine withholding on a normal invoice is an invoice-data extraction and reconciliation problem, not evidence that a separate Retenciones CFDI is automatically required.

When you need a separate CFDI de Retenciones

The CFDI de Retenciones e Informacion de Pagos is a separate document type used for specific withholding and information-reporting operations. It is not a duplicate invoice, and it is not required every time a service invoice contains retained ISR or IVA. That distinction is where many review errors start.

In everyday AP work, the safer question is not "Does this transaction involve withholding?" but "Does this transaction stay inside the invoice, or does the regime require separate retention reporting?" If the transaction is a standard service invoice and the retained taxes are already part of the CFDI de Ingreso, the review usually stays with the invoice. If the operation belongs to a regime that uses the Complemento de Retenciones e Informacion de Pagos 2.0, the document workflow changes and the team should expect a separate retention CFDI.

This is why the Mexico CFDI retenciones complement should be treated as a document-classification topic, not just a tax-rate topic. The legal or tax trigger may be outside the scope of the invoice itself, but the accounting consequence is clear: your records need to show which document carries the retention evidence.

A practical decision rule is:

1. Start by checking whether the withholding is part of a normal invoice payment flow.
2. If yes, review the retained taxes inside the invoice-level CFDI data.
3. If no, determine whether the transaction belongs to a specific reporting regime that requires a separate Retenciones CFDI.

That sequence prevents teams from asking suppliers for the wrong document set.

---

What changed for digital-platform withholding in 2026

Digital-platform withholding sits in its own lane. It affects Mexican withholding calculations and CFDI generation logic, but it should not be confused with the standard service-invoice pattern covered earlier in this guide.

The most important 2026 update is that KPMG's 2026 update on Mexico's digital-platform withholding complement reports Revision E became effective on January 1, 2026 and recalculates ISR for legal entities using a fixed 2.5% rate instead of catalog rates. For teams handling platform flows, that is not a small wording change. It affects how the withholding should be calculated and how the related CFDI logic should be interpreted for those transactions.

The operational takeaway is straightforward: if the payment belongs to the digital platforms complement regime, do not reuse the assumptions from an ordinary professional-services invoice. Confirm the regime first, then confirm the rate logic, then confirm which CFDI structure supports the withholding evidence for that specific flow.

That is also why platform scenarios deserve their own review path inside AP or tax operations. They are part of the broader Mexico withholding landscape, but they are not the baseline rule set for every Mexican supplier invoice.

---

AP review checks before you approve payment

The cleanest way to review a Mexican invoice with retenciones is to follow the same sequence every time:

1. Identify whether the supplier is a persona fisica or persona moral.
2. Validate the RFC and make sure it matches supplier master data.
3. Decide whether the transaction is a routine CFDI de Ingreso withholding scenario or one that belongs to a separate CFDI de Retenciones e Informacion de Pagos workflow.
4. Recalculate the expected retained ISR and retained IVA from the taxable base.
5. Compare the retained taxes, gross amount, and net payable against the invoice data and XML.
6. Keep the supporting documents needed for reconciliation and tax reporting.

That checklist matters because the most expensive mistake is often misclassification, not a small arithmetic slip. If the team treats a separate-retention scenario as an ordinary invoice, or treats an ordinary invoice as if it needed a separate CFDI, the payment file and compliance record can diverge quickly.

This is also where structured extraction helps. In a workflow tool such as Invoice Data Extraction, reviewers would want dedicated output columns for supplier type, RFC, retained ISR, retained IVA, document type, and the source file and page reference for each row. That makes it easier to trace the net payment decision back to the original document instead of relying on manual notes.

For multinational teams, it is useful to compare local mechanics before standardizing controls. This article focuses on Mexico, but how Argentina's layered retenciones model compares is a good reminder that "withholding" can involve a very different document and reconciliation burden depending on the country.

For another regional variation where AP must verify that part of the invoice value is diverted into a tax-control deposit, Peru's factura con detraccion requirements are a useful contrast.

If your team builds the review around classification first and percentages second, Mexican withholding becomes much easier to control. You are no longer just checking tax rates. You are validating which document carries the evidence, how the payable amount was reduced, and whether the invoice data can support reconciliation later.