Mexico’s Digital Services Tax: RFC Registration and IVA Compliance for US SaaS

For most US SaaS founders, “VAT” lives in the EU, not on the other side of the Rio Grande. Mexico changed that in 2020 when it introduced a full digital services regime that forces non‑resident platforms to charge 16% IVA to Mexican users, file monthly returns with SAT, and even grant real‑time access to transactional data.

If you sell subscriptions, streaming, gaming, or downloads into Mexico from the US without collecting IVA, you are not just creating a tax exposure. You are risking SAT invoking its kill switch and asking Mexican ISPs to block your domain and apps until you register and start filing.

This guide walks your finance and legal teams through the core mechanics: when a foreign SaaS business must register for an RFC, how to distinguish Mexican B2C versus B2B for IVA, what the 2026 reforms changed for platform withholding, and how to model grossed‑up Mexican pricing so your net revenue stays where it should.

Mexico’s 2020 digital services reform in plain English

Mexico inserted an entire chapter on foreign digital service providers into its VAT Law with effect from 1 June 2020. The regime targets non‑resident companies that provide automated digital services to Mexican users through apps, websites, or platforms, regardless of whether they have a permanent establishment in Mexico.

The law lists digital services to include streaming video and music, gaming, downloads, cloud storage, digital advertising, dating and community platforms, and any other automated digital content where payment is collected electronically. If the user is in Mexico based on payment, billing, phone, or IP data, IVA is in scope.

There is no minimum turnover threshold. A US SaaS business with 200 Mexican subscribers at $25 per month is expected to register, collect 16% IVA, and remit monthly, just like a global streaming giant.

How SAT decides a user is “in Mexico”

For foreign SaaS businesses, one of the first questions is how SAT decides whether a subscription is Mexican. The guidance mirrors EU VAT logic and allows platforms to rely on practical evidence.

• Payment through a Mexican bank or payment provider
• Customer billing address in Mexico
• Mexican country code on the customer’s phone number
• IP address or device location in Mexico

If these indicators point to Mexico, IVA is due at the standard 16% rate unless a specific exemption applies. The safest assumption: if your billing and payment systems say “Mexico,” treat it as in‑scope for IVA, even if your corporate group is entirely US‑based.

The SAT kill switch: ISP blocking as an enforcement tool

Mexico did not stop at registration and filing obligations. The 2020 reforms gave SAT a blocking mechanism for foreign digital providers that simply refuse to engage with the VAT regime. SAT can request that Mexican telecoms and ISPs temporarily block access to a non‑compliant platform’s domain and IP addresses.

According to KPMG and Global Trade Alert commentary, SAT may invoke blocking where a foreign provider fails to register for VAT, does not appoint a legal representative or provide a Mexican address, or skips three consecutive VAT returns or two quarterly information returns.

Mexico is not alone here; other Latin American jurisdictions have explored similar kill switches. But Mexico is the one where foreign SaaS companies already appear on public SAT lists of registered digital providers, and where non‑registration can quickly escalate into reputation and revenue damage, not just a tax audit.

RFC registration and ongoing SAT compliance for foreign SaaS

Once you cross the line into Mexican digital VAT territory, the practical work starts. SAT expects non‑resident providers to enter the Federal Taxpayers Registry (RFC), appoint a local tax agent, and comply with several ongoing obligations.

1. Join the RFC as a foreign digital services provider

Foreign providers that fall under the regime must register with the RFC and are then published on SAT’s public list of foreign digital providers. That list is now in the high hundreds of names and is updated every six months.

Recent updates show more than 270 foreign platforms registered, and 2026 commentary notes that SAT is enforcing a stricter proof‑of‑domicile rule: new registrants must provide Mexican address documentation in the entity’s name, which has made it harder for fully remote providers to register without a local footprint.

2. Grant SAT online access to platform data

An additional 2026 obligation now requires digital platforms in the VAT regime to give SAT real‑time online access to internal data about Mexican users and transactions. Providers must file a written notice by April 30, 2026, explaining how SAT can access this data, and new entrants must do so within the month after they start operations. If they do not, SAT may treat the failure as grounds for temporary blocking.

3. Issue Mexican‑compliant invoices and file monthly returns

The regulations require prices to be quoted with IVA shown separately. SAT expects platforms to file a monthly VAT return by the 17th of the following month and to submit a separate information report by the 10th with details by customer type and transaction.

Technically, foreign digital providers are not fully inside the Mexican CFDI e‑invoicing system in the same way as domestic taxpayers, but practical compliance often means aligning your invoice layout, metadata, and transaction logs with CFDI standards so that Mexican customers can reconcile your charges in their records.

B2C vs B2B: Who actually charges the 16% IVA?

From a pricing and CRM perspective, the single most important distinction in Mexico is whether your customer is a final consumer (B2C) or a registered Mexican business (B2B). The VAT and withholding flows change materially between these scenarios.

B2C: You charge and remit 16% IVA directly

When you sell subscriptions or digital content to individuals or unregistered micro‑businesses in Mexico, you are in pure B2C territory. In this scenario, the foreign SaaS provider must charge 16% IVA on the price, show it separately, collect it from the user, and remit it to SAT each month.

Some foreign platforms try to bury this by keeping the sticker price constant and absorbing IVA into margin, but that is not sustainable at scale. On a 16% VAT rate, the difference between “inclusive” and “exclusive” pricing is material to net revenue per Mexican user.

B2B: Your Mexican customer may shift into self‑assessment or withholding

For B2B SaaS sold to Mexican companies with their own RFC and CFDI processes, the picture is more nuanced. Historically, foreign digital services aimed at business customers often leaned on a reverse‑charge logic where the Mexican company accounted for VAT under self‑assessment.

Subsequent guidance and 2025‑2026 updates point in a different direction. Mexico now requires providers of B2B digital services to charge VAT as well as B2C, and it has tightened withholding rules so that Mexican intermediaries or platforms may withhold 50% or 100% of the VAT in specific structures.

The takeaway is simple. You cannot rely on a generic “reverse charge” assumption to avoid registration in Mexico. The legal trend has been to push foreign digital providers into the VAT net and to backstop with withholding when they are not registered.

2026 withholding changes for platforms and B2B digital services

Mexico has layered withholding requirements on top of the digital services regime. Intermediary platforms and Mexican legal entities must withhold part of the VAT or income tax due when payments are made to certain providers, and 2026 reforms tightened this further.

For digital platforms handling sales of goods or services, recent guidance indicates that Mexican entities must withhold 50% of the VAT when they sell on behalf of other taxpayers and 100% of VAT when those sales are made by non‑residents with payments going into foreign bank accounts.

The 2026 economic package extends similar thinking to B2B digital platform transactions. Mexican tax commentary notes that platforms now face clearer obligations to withhold 50% of VAT on certain B2B digital services when the foreign provider is already registered, and full VAT when it is not.

From a cash‑flow planning perspective, your gross receipts from Mexico may be 50% short of the IVA line you show on invoices. That gap is not lost money, but it needs to be handled correctly in your Mexican VAT returns and in your internal revenue recognition models.

CFDI e‑invoicing, location evidence, and audit‑ready records

Mexico’s CFDI e‑invoicing system is one of the most mature in the world. Even though foreign digital providers operate under a simplified regime, your B2B customers and any Mexican intermediaries must reconcile what you charge to CFDI records and their own ledgers.

For your tax and legal teams, three data pillars matter most:

• Evidence that the customer is in Mexico (payment method, billing address, phone, IP)
• Breakdown of net price and 16% IVA on every Mexican transaction
• Cross‑reference identifiers that platforms and Mexican corporates can use in their CFDI records

This is where your billing and engineering teams have to collaborate with legal. You need to design invoice PDFs and transaction records that are not full CFDIs but still expose enough metadata that Mexican corporates and intermediaries can tie your charges to their own CFDIs and withholding CFDIs.

Pricing models: How to gross‑up Mexican plans and protect margin

Once you are clear on the legal obligations, the commercial question is how to adapt your Mexican pricing so you do not quietly donate 16% of your ARR to SAT. The right answer depends on whether you frame your plans as IVA‑inclusive or IVA‑exclusive for Mexican customers.

IVA‑inclusive pricing: User‑friendly, margin‑unfriendly

With IVA‑inclusive pricing, Mexican users see one rounded price, and you back out the tax on your side. That makes marketing simple but reduces your revenue per user by 13.8% relative to a US customer on the same sticker price, because the 16% tax hits a smaller net base.

IVA‑exclusive pricing: Enterprise‑friendly, consumer‑sensitive

With IVA‑exclusive pricing, you treat the published plan price as net and add 16% IVA at checkout for Mexican customers. B2B buyers expect this because they recover VAT. B2C users do not, so they perceive your price as higher than a competitor that buries IVA in the headline number.

Many SaaS companies end up with a hybrid: enterprise and B2B contracts are IVA‑exclusive, while self‑serve Mexican plans are IVA‑inclusive with country‑specific price points that are slightly higher than US sticker prices to keep net revenue aligned.

Using a calculator to model different gross‑up strategies

Your finance team needs to compare three scenarios side by side for every major Mexican plan: keep sticker price constant and absorb IVA, increase sticker price for Mexico only, or keep sticker price and introduce a Mexican‑specific “service fee” that tracks the IVA amount transparently.

Practical compliance playbook for Tech CFOs

You do not need to turn your SaaS finance team into Mexican VAT specialists overnight. You do need a structured plan to manage exposure and pricing.

1. Map your Mexican footprint

• Pull a 12‑ to 24‑month export of all customers with Mexican country codes, billing addresses, or payment methods.
• Classify them as B2C, SME, or large‑enterprise based on contract sizes and RFC availability.
• Quantify historical Mexican revenue, split by channel (direct, marketplace, reseller).

2. Decide whether to enter or regularize the digital VAT regime

If your Mexican revenue is already meaningful and likely to grow, proactive registration is almost always better than waiting for SAT to notice you. If your footprint is tiny and opportunistic, you may choose to turn off self‑serve signups from Mexico instead of taking on the compliance overhead. There is no one‑size answer, but there should be a conscious decision.

3. Coordinate RFC registration and data‑access obligations

Work with Mexican tax counsel to navigate the RFC process under the new domicile rules, appoint a representative, and file the April 2026 data‑access notice. Build an internal checklist of all logs, tables, and dashboards SAT will be able to see once you turn that access on.

4. Update billing logic and CRM

• Implement country‑aware pricing and tax logic in your billing platform.
• Identify Mexican users in CRM with tags for B2C vs B2B and whether RFC is on file.
• Align invoice templates with Mexican expectations for displaying IVA separately, even if not full CFDI.

5. Build a board‑ready IVA model

Your board will want to know the EBITDA impact of Mexican VAT compliance. Use a tool that lets you input your current ARR, your Mexican share, percentage B2C vs B2B, expected gross‑up, and the likelihood of platform withholding, then produces three cases: status quo, compliant with margin erosion, and compliant with re‑priced Mexican plans.

FAQ: Short answers for busy founders and counsel

Does registering for Mexico’s digital VAT regime create an income tax permanent establishment?

No, the digital VAT regime is drafted so that registration and compliance for VAT purposes alone do not create a permanent establishment. You still need a separate PE analysis for income tax based on functions, risks, and assets in Mexico.

Can we rely on reverse charge for all B2B SaaS and avoid RFC registration?

That was a defensible position before 2020 in some service models, but current guidance makes it clear that Mexico expects foreign providers of digital services to charge VAT for both B2C and B2B where users are in Mexico. Reverse charge may still apply in narrow circumstances, but it is no longer a blanket escape from registration.

What happens if we never register and keep selling into Mexico anyway?

In the short term, payment providers or marketplaces may begin withholding 100% of VAT on payments to you, reducing your net receipts. In the medium term, SAT can classify you as non‑compliant and request that Mexican ISPs block access to your platform until you register and start filing.

Is every app in Spanish automatically caught by this regime?

Language is not the legal trigger. SAT looks at where the user is resident and consuming the service, based on payment instruments, addresses, phone numbers, and IP data. A Spanish‑language app with only US users is out of scope; an English‑language SaaS with Mexican corporates is in scope.

How often do we need to file VAT returns once registered?

The regulations align foreign digital providers with general Mexican VAT timelines. VAT returns and payments are due by the 17th of the month following the period, and information returns are due by the 10th.

Can we “geo‑block” Mexico to avoid these complications?

Yes, you can choose to stop serving Mexican users altogether by blocking signups and enforcing hard country checks, but that is a strategic market decision. If Mexico is part of your nearshoring or Latin America growth story, building compliant IVA processes is usually better than walking away from the market.

Related tools on USFinanceCalculators.com

• Mexico IVA & Retenciones Calculator: Model 16% VAT, gross‑up, and platform withholding
• Mexico AFORE & IMSS Pension Calculator: Ley 73 vs 97 scenarios for expat executives
• Legal Finance Hub: 15 calculators for cross‑border tax and compliance modeling /li>

Disclaimer: This article is for educational purposes only and does not constitute tax, legal, or accounting advice. Mexico’s digital VAT regime for foreign providers is complex and still evolving, and specific outcomes depend on your group structure, contracts, and user base. Always consult qualified Mexican tax counsel before making registration, pricing, or reporting decisions.