This content is provided for informational purposes only. It does not constitute financial, legal, tax, or regulatory advice. Each company should evaluate its implementation with its own internal teams and professional advisors.
It's 9:00 a.m. in Mexico City. The CFO asks a simple question: how much cash do we have across the region, and how much of it can we use today? Treasury opens five bank portals, a payout report and two spreadsheets. By the time the answer is ready, part of it has already changed.
For companies running cross-border payments in Latin America through entities in Mexico, Brazil, Colombia, Chile and Argentina, that question is harder than it looks. It's also a common problem: in PwC's 2025 Global Treasury Survey, 52% of companies with revenue between $1 billion and $10 billion said they still collect and consolidate forecasting data manually, and 76% named poor data quality as a challenge.
Here we break it into three questions, show why each country answers them at a different speed and share a daily check your team can start using this week.
Treasury visibility is the ability to answer three questions for every entity, with numbers that share the same timestamp:
A dashboard that shows five bank balances answers only part of the first question.
A bank balance tells you what sits in the account. It doesn't tell you what's free. In a multi-country setup, part of that balance is often tied up by local rules or by decisions the business already made.
Argentina is the clearest example. Since April 2025, companies can pay dividends to non-resident shareholders only from earnings of fiscal years starting in 2025, and in May 2026 the central bank confirmed that other corporate FX restrictions remain, such as waiting periods for some intercompany service payments. The cash is visible, but not all of it can move.
Currency adds another layer. If the group keeps a buffer in USDC or USDT to fund Mexican operations, that balance belongs in the position, but its value in pesos depends on the rate you can execute right now. Strong liquidity from USDC or USDT into MXN turns that line into a live quote with a timestamp, instead of last week's reference rate.
Practical rule: tag every balance as free, committed or restricted, and show the CFO free cash first.
Pending payments are the most common blind spot. A payroll file approved on Tuesday for Friday is Friday's cash, spent on Tuesday. The same happens with supplier runs and mass payouts in Latin America, where one approved batch can include thousands of payments to contractors, sellers or drivers in several countries.
When approvals live in the ERP (enterprise resource planning system), a payout platform and an email thread, Treasury sees them only when they hit the bank. By then, the decision window has closed. Good visibility shows each approved batch in the position the moment it's approved, by entity and by value date.
This is money between two points: FX conversions waiting to settle, transfers between your own entities, and local payments sent but not yet confirmed by the receiving bank.
Stablecoins for business payments help here in a specific way. A USDC or USDT transfer between wallets controlled by two eligible group entities, using a compatible network, can be tracked on-chain at every step, so it doesn't disappear between two bank statements. The discipline that matters is simple: every item in flight gets an expected arrival time, and anything past that time becomes an exception someone owns that same day.
Visibility is only as good as the data behind it, and access to bank data isn't the same across the region. That creates a rule many teams learn the hard way: your consolidated view is only as current as your slowest entity.
|
Country |
Instant rail |
Bank data access for third parties (2026) |
What Treasury should watch |
|---|---|---|---|
|
Mexico |
SPEI, 24/7 |
The 2018 Fintech Law set the basis for open APIs, but transactional data rules are still pending |
Balances move overnight and on weekends, so a morning file already lags |
|
Brazil |
Pix, 24/7 |
Open Finance turned five in February 2026, with over 100 million connected clients |
Data is rich; the gap is usually internal approvals |
|
Colombia |
Bre-B and PSE |
Decree 368 of April 2026 made open Finance mandatory; standards come first, then up to 12 months to comply |
Plan for mixed formats while banks connect |
|
Chile |
Bank transfers (TEF) |
The Open Finance System under the Fintech Law now starts in July 2027 |
Bank-by-bank connections until then |
|
Argentina |
Transferencias 3.0 (CBU/CVU) |
Bank-by-bank connections |
Cash can be visible and still not movable because of FX access rules |
Cross-border messages got richer when Swift ended the coexistence of legacy MT formats and ISO 20022 on November 22, 2025. Local account data, however, still arrives in different formats and at different times in each market.
That's where an API for cross-border payments in LATAM matters beyond sending money. When balances, conversions and payment statuses come through one API and webhooks (automatic notifications sent the moment a status changes), the position updates itself instead of waiting for five statement files.
Run it every morning, entity by entity, before approving the day's payments:
To see whether visibility is improving, track three numbers over time: the age of your oldest data point, the share of cash that carries a tag, and the value of items that stay unmatched for more than 24 hours.
Bitso Business gives Finance teams one connection for local payments, conversions and stablecoin settlement. In Mexico, companies connect directly to SPEI* through Bitso Business, with tracking for every transaction. Through the same connection, teams can convert between stablecoins and local currency and run mass payouts, so balances, pending batches and payment statuses feed one Treasury view instead of a separate report per country.
If you're preparing a new market, our guide on whether your company is ready for cross-border payments in LATAM is a good next read.
Not necessarily. A Treasury management system (TMS) organizes the data it receives. If balances arrive once a day or payout approvals never reach it, the view stays incomplete. Visibility depends first on fresh data and on capturing commitments, and then on the tool.
It depends on how fast money moves. SPEI in Mexico and Pix in Brazil run 24/7, so balances in those entities can change overnight and on weekends. Many teams aim for intraday updates on instant rails and at least a daily close elsewhere, with the timestamp visible on every line.
They add a line to the position, and usually a transparent one, since blockchain balances and transfers can be checked at any time. The key is to value them at an executable rate in local currency and tag them like any other balance.
Start with commitments. Bringing approved payroll, supplier runs and payout batches into the position usually changes the free cash number more than a new dashboard does. Then add timestamps, and only then automate data feeds country by country.
*Nvio Pagos México, S.A.P.I. de C.V., IFPE ("Nvio México") is an entity authorized and regulated by the Comisión Nacional Bancaria y de Valores (CNBV). Nvio México enables direct access to SPEI and provides payment services in full compliance with Mexican regulation.