Cross-border collections: Mexico–US corridor without two conflicting playbooks
Groups that originate in one country and collect in another fail on data residency, consumer-law mix and cash rails — not on “culture.” Here is an operating split that works.
Direct answer: Run one economic scorecard and two legal playbooks. The Mexico–US corridor breaks when a US FDCPA-style instinct is pasted onto CONDUSEF work, or when Mexican CFDI cash is reconciled like ACH.
Split conduct, share physics
Physics: invoices, ageing, promises, payments. Those can be one data model.
Conduct: call windows, mini-Miranda-style disclosures where required, Mexican identity and data rules. Those cannot be one script.
Cash is two rails
SPEI vs ACH/wire vs cards. Collectors must see the rail the customer actually used. Treasury must know which entity is the beneficiary.
Accounting is two closes
Mexican SAT/CFDI close and US GAAP/local close can share a group pack, but exception queues stay local. See international operations and accounting.
If you are building the corridor now, register with a two-entity extract (no names required).
Questions operators actually ask
Can one script serve Mexico and the US?
No. Hours, disclosure language, and third-party contact rules differ. Share scoring and cash application; split conduct rules.
Where should data live?
Default to storing Mexican debtor data in a Mexico-aware processing purpose and US data under US policy. Mixing lakes “because the CRM can” is how you fail both regimes.
What belongs on the group scorecard?
Cash, cost-to-collect, complaints, and close timeliness — by country. Blended group numbers hide a broken corridor.
Send an anonymised extract.
We return a recovery projection within five business days. No cost, no obligation to sign.
Register my company