Collect revenue with cross-border payments in LATAM

Most conversations about cross-border payments in Latin America focus on money going out: paying suppliers, contractors, or payroll across the region. But if your company sells in Mexico, Brazil, or Colombia, the flow that determines your cash position runs in the opposite direction. Revenue has to come in, land somewhere, and eventually reach your treasury in the currency your treasury uses to operate.

That inbound journey has its own rules. Customers in each market pay through local systems, in local currency, with local references. This article explains how to collect revenue through local rails, consolidate income across countries, and repatriate funds without leaving capital trapped along the way.

Why is collecting revenue different from paying it out?

When you pay out, your company controls the transaction: the amount, the timing, the reference, the destination account. When you collect, the customer initiates the payment. You control almost nothing about how the money arrives, which changes three things for finance teams:

• Volume and unpredictability. A payout batch might contain 500 known payments. Collections can mean thousands of inbound transfers arriving at any hour, in amounts you did not schedule.
• Matching. Every inbound payment must be matched to an invoice, order, or customer account. If the reference is wrong or missing, someone has to investigate manually.
• Where the money lands. Revenue collected in local currency stays in local currency until you decide otherwise. Without a plan for consolidation and FX, income accumulates as idle local balances across countries.

The good news is that the same local rails that made payouts faster across the region also work in reverse. The question is how your customers actually use them.

How do customers pay in Mexico, Brazil, and Colombia?

What does a multi-country collection flow look like?

A working collection setup connects four stages. Companies do not need a legal entity in every country to run this flow: a licensed provider can stand in front of the local rails and receive funds on your behalf, with the compliance coverage each market requires.

• 1. Local collection. Your customer pays in their currency, through the rail they already use. You expose a CLABE in Mexico, a Pix QR or key in Brazil, a Bre-B key in Colombia. The customer experience is identical to paying any local business.
• 2. Identification. Each collection point carries a unique reference tied to an invoice or customer account, generated before the money moves. This is what allows automatic matching later, instead of guessing by amount and date.
• 3. Confirmation. Inbound payments trigger webhooks or automated confirmations the moment funds land, so your systems can release the product, activate the service, or update the account receivable in real time.
• 4. Consolidation. Balances collected across countries appear in one consolidated ledger, with every movement linked to its original reference. Finance sees regional revenue as a single position instead of three disconnected bank statements.

An API for cross-border payments in LATAM should cover this entire inbound sequence as well as the outbound one. If a provider can send funds to a CLABE but cannot receive funds through one, you only have half the flow.

How do you consolidate revenue and repatriate funds?

Collection solves how money comes in. Repatriation solves where it goes next, and this is where most of the trapped capital hides. Revenue that sits in local currency for days or weeks is capital your business cannot invest, and it carries FX exposure the whole time.

There are three practical patterns worth evaluating:

• Scheduled conversion. Convert local balances to your treasury currency on a fixed calendar (daily or weekly), with the FX quote captured and stored at each conversion. Predictable, easy to audit, and simple to explain to auditors.
• Threshold-based sweeps. Keep a small operating balance in each market and automatically convert anything above it. Useful when you also pay local expenses from collected revenue.
• Netting against payouts. If you also run mass payouts in Latin America (refunds, sellers, creators, suppliers), collected revenue can fund them directly. Money that comes in as pesos and goes out as pesos never needs to cross a border at all, which removes two FX conversions from the cycle.

Stablecoins for business payments play a specific role in this stage. Converting collected pesos into digital dollars gives treasury a settlement asset that moves across borders in minutes and is available on weekends, when banking rails for repatriation are closed. The same USDC to MXN liquidity that companies use to fund payouts into Mexico works in the opposite direction: MXN revenue converts to USDC, moves to where treasury needs it, and lands as dollars without waiting for a correspondent banking chain.

What should a CFO measure in a collection operation? 

Four numbers tell you whether the inbound side of your operation is healthy:

• Time-to-cash: hours from customer payment to confirmed, usable balance. On instant rails this should be measured in minutes, not days.
• Auto-match rate: the share of inbound payments matched to an invoice without human intervention. With unique references per payment, above 95% is a realistic target.
• Idle balance days: how long collected revenue sits in local currency before it is converted, deployed, or repatriated. Every idle day is unpriced FX exposure.
• Cost per collection: all-in, including rail fees, FX spread on conversion, and the manual work of resolving unmatched payments. Exceptions usually cost more than fees.
• If any of these four is invisible today, that blind spot is the first thing to fix, before changing providers or rails.
  
  

What to demand from a collections provider

FAQs
 

Do customers pay a fee when they pay a business through SPEI, Pix, or Bre-B?

For individuals these systems are generally free or very low cost: Pix is free for personal transactions, Bre-B is free for most low-value personal operations, and SPEI costs depend on each bank, but many offer it at no cost. Businesses receiving funds may pay fees depending on their institution or provider, so cost per collection should be modeled market by market.

Is settlement time the same as fund availability?

No, and the difference matters for treasury planning. Settlement is when the rail confirms the transfer, usually in seconds. Availability is when those funds can actually be converted, deployed, or repatriated, and that depends on the provider's operating model and cut-off rules. Ask providers about both before integrating.

What is the difference between a pay-in and a payout?

A pay-in is money coming into the business, initiated by a customer or partner. A payout is money leaving the business, initiated by the company. They travel over the same rails but require different controls: pay-ins depend on matching and confirmation, payouts depend on validation and approval.

Where do stablecoins fit in a collection flow?

Mainly in the consolidation and repatriation stage. Revenue collected in local currency can convert into digital dollars for cross-border movement, weekend availability, and reduced idle balances, while customers keep paying through the local method they already use.

How can a company test a collection flow before going live?

Start with a sandbox pilot in one market: generate references, receive test payments, confirm webhooks fire correctly, and measure the auto-match rate on a controlled batch. Once matching and confirmation behave as expected, expand to production in that market and then replicate the setup in the next country.

*NVIO México enables direct access to SPEI and delivers payment services fully compliant with Mexican regulation. NVIO Pagos México, S.A.P.I. de C.V., IFPE (“NVIO México”) is authorised and regulated by the Mexican National Banking and Securities Commission (CNBV). Learn more at nvio.mx/terms.