TCPA vs. Mexico and Argentina DNC Rules for US Callers

DNC LATAM · Compliance guides

TCPA compliance in the US does not clear you to call Mexico or Argentina. The three countries run separate Do Not Call registries, with different regulators, different refresh cycles and no shared database — a calling list scrubbed clean under US rules can still be full of registered numbers the moment it crosses the border. The commercial comparison is DNC scrubbing vs US TCPA.

This is the single most common gap outbound teams expanding into Latin America discover, usually after the fact. Here is where the three regimes actually diverge, and the mistakes that follow from assuming they don’t.

TCPA only governs the US registry

The TCPA and the FTC/FCC’s National DNC Registry cover calls to US numbers. Damages run $500–$1,500 per call under the TCPA, which is why US compliance teams take scrubbing seriously domestically. But that framework has no jurisdiction over a Mexican or Argentine phone number, and neither country’s regulator recognizes US registry status as a substitute for checking their own list. A number can be clear under the National DNC Registry and still be registered with Mexico’s or Argentina’s official system.

Mexico and Argentina are two more, separate systems

Mexico’s official Do Not Call registry is maintained by the national consumer-protection authority and published in zone-by-zone extracts, refreshed every 15 days. Argentina’s registry was created by Law 26.951 and requires companies to register as authorized users with local tax credentials before they can even download the list. Neither integrates with the US National DNC Registry, and neither publishes an English-language self-service portal. See our full breakdowns of Mexico Do Not Call compliance and Argentina Do Not Call compliance for what each one specifically requires.

Mistake 1: treating LATAM as an extension of US compliance

The most common failure mode is assuming a single “international DNC” checkbox covers all destinations. In practice, calling into Mexico and Argentina means maintaining two more sets of registered-user credentials, two more download cadences and two more suppression files — on top of, not instead of, the domestic TCPA program. Teams that budget compliance work as “US plus a bit more” consistently underestimate the ongoing operational load. Our call center compliance guide walks through what a complete multi-country program actually needs.

Mistake 2: applying one refresh cadence to every country

US teams are used to the TSR requirement that a registry version be no older than 31 days. That cadence does not transfer. Mexico republishes its official data every 15 days, and a scrub older than one cycle is checking against a stale list. Argentina expects a current download before each campaign, not a periodic one. Applying a single “monthly refresh” policy across all three markets means the Mexico list, and often the Argentina list, is out of date for part of every cycle.

Under the TCPA, documented prior express consent generally lets a company call a number even if it is registered. US teams sometimes assume the same logic applies abroad and treat any existing customer relationship as sufficient cover in Mexico or Argentina. Consent and suppression rules are decided by each country’s own regulator, not by whatever standard a company already meets domestically — assume nothing transfers across the border. Mexico specifically runs an opt-out model rather than a consent-first one; see do you need consent to cold-call Mexico? for what that changes about where compliance effort should go.

Mistake 4: missing the registration barrier entirely

Both Mexico and Argentina require callers to register locally before they can access official data — Mexico through a provider registration tied to specific geographic zones, Argentina through a company-user account tied to a CUIT tax ID and a local representative. A US company with no local entity typically cannot complete either registration on its own. Teams that plan a LATAM expansion around “we’ll just scrub the list like we do at home” usually hit this wall in week one, not month one.

Mistake 5: assuming debt collection is a separate lane

US collections teams sometimes assume this whole comparison doesn’t apply to them — that ARM calls sit outside TCPA-style marketing rules at home, so the same separation must hold once a number crosses into Mexico or Argentina. It doesn’t. REPEP and No Llame are scoped by what a call actually offers, not by which department places it, and payment-plan or settlement scripts read as commercial contact under either country’s rules. See do DNC rules apply to debt collection calls? for where that line sits.

Mistake 6: assuming a B2B audience is out of scope

US teams sometimes bring over another TCPA-shaped habit: the National DNC Registry is built around residential consumer numbers, so a lot of US B2B cold-calling programs are structured around that distinction, and the assumption travels that a B2B pitch is automatically clear abroad. Neither REPEP nor No Llame is scoped that way. REPEP flags whichever number a consumer registered, business landline or personal mobile alike, and Law 26.951 applies to any company that offers or sells goods or services by phone, without a business-audience carve-out. See B2B cold calling in Mexico and Argentina: DNC rules for what actually determines scope.

What a compliant multi-country workflow actually looks like

  • Keep the US National DNC Registry scrub and TCPA consent records exactly as they already are — nothing here changes that program.
  • Maintain separate, current suppression files for Mexico (refreshed on its 15-day cycle) and Argentina (refreshed before each campaign), sourced from each country’s own official registry.
  • Document consent and opt-outs per country, since none of the three regulators accept another country’s records as proof.
  • Keep a dated screening record for every campaign, in every market — see how DNC scrubbing works for the mechanics.

Most compliance stacks built for US telemarketing simply were not designed to also cover Mexico and Argentina, which is why teams calling all three markets typically end up managing the LATAM half separately. DNC LATAM maintains the registered access for each supported country and delivers current scrubs and dated screening records through the same API or CSV workflow, so the only thing that changes when you add a market is which list you check — not how your team works.