Latin America does not have a unified cross-border payments framework. Each country operates its own combination of foreign exchange controls, remittance reporting obligations, settlement system rules, and beneficiary identification requirements. A treasury team routing USD to Brazil faces a materially different compliance and operational task than one routing USD to Mexico or Colombia, even though all three corridors appear similar from the payment instruction side. The difference lives in what documentation the local regulator requires, what the local central bank mandates for FX conversion, and how settlement actually completes on the beneficiary side.
Brazil: BACEN Reporting and the SISBACEN System
Brazil's Banco Central do Brasil (BACEN) requires that all foreign exchange transactions be registered in SISBACEN, the central bank's electronic monitoring system. The FX operation is conducted through an authorized Brazilian bank acting as the exchange dealer, and the registration must include: transaction type (the nature of the underlying commercial contract), the parties involved, and the value of the FX operation.
For a US corporate treasury paying a Brazilian supplier, this means the payment does not simply arrive as USD and convert to BRL. The beneficiary's bank must process an FX contract on the beneficiary's behalf, register the transaction with BACEN, and then credit the BRL amount after conversion. The time from USD receipt to BRL availability depends on how quickly the beneficiary's bank processes the exchange contract registration. In practice, this adds one to two business days beyond the USD settlement itself.
The specific documentation required depends on the transaction category. Trade payments follow different requirements than intercompany transfers or royalty remittances. Brazilian eCF (Extrato de Câmbio, the FX contract extract) must be maintained by the exchange dealer and is subject to BACEN inspection. Corporate treasuries funding Brazilian operations need to ensure the underlying payment purpose is clearly documented in the payment instructions, because the beneficiary bank's compliance team will ask for it to complete the FX registration.
Mexico: SPEI Settlement and FIRA/SAT Considerations
Mexico's domestic real-time settlement runs through SPEI (Sistema de Pagos Electronicos Interbancarios), operated by Banco de Mexico. Inbound international payments convert at the market FX rate and settle into SPEI as MXN once the receiving bank processes the incoming USD wire. SPEI itself settles in near real-time during business hours, but the conversion step at the receiving bank introduces a variable lag, typically same-day for morning arrivals.
Mexico does not have the same formal FX transaction registration requirement as Brazil for routine commercial payments, but the Servicio de Administracion Tributaria (SAT) requires that international payments above certain thresholds be supported by valid invoicing (a CFDI, Comprobante Fiscal Digital por Internet, is the standard). The beneficiary must have a valid RFC (Registro Federal de Contribuyentes) and the payment description must align with the CFDI issued. Payments that cannot be matched to a valid CFDI create a tax documentation gap for the beneficiary, which then creates a query back to the originating treasury.
Colombia: DCIN-83 and Cambiaria Compliance
Colombia's foreign exchange regime requires that all inbound foreign currency be channeled through authorized exchange intermediaries, primarily banks supervised by the Superintendencia Financiera de Colombia. The beneficiary's bank must file a DCIN-83 form with the Banco de la Republica, which is the declaration of exchange for commercial transactions. This filing must specify the underlying contract type, value, and counterpart information.
For a US company making a one-off payment to a Colombian supplier, the DCIN-83 obligation sits with the Colombian beneficiary, not the originator. But in practice, if the payment instruction does not include sufficient information for the beneficiary's bank to classify the transaction, the bank will delay credit while it requests documentation. The most common delay source is a missing or ambiguous payment purpose code in the original wire instruction.
Chile and Argentina: Contrasting Approaches
Chile maintains a relatively open capital account with few restrictions on inbound USD. The Informe de Operaciones de Cambio Internacionales (IOCI) reporting obligation applies to transactions above USD 10,000, but the compliance burden is on financial institutions rather than on the beneficiary corporation directly. For most corporate treasury purposes, USD-CLP corridors are operationally simpler than Brazil or Colombia.
Argentina presents the opposite case. Foreign exchange controls have fluctuated significantly. As of early 2026, the Argentine Peso regime has undergone multiple adjustments, and the MULC (Mercado Unico y Libre de Cambios) rules that govern access to official FX rates apply specific conditions to different payment types. Intercompany payments from a US parent to an Argentine subsidiary, trade payments for goods versus services, and profit remittances each follow different MULC access rules. Treasuries managing Argentina exposures typically require country-specific legal and compliance sign-off on each significant payment type, not just a standard wire process.
What This Means for Payment Routing and Reconciliation
The practical implication for a treasury team running Latin American corridors is that compliance documentation is not separable from the payment process. The payment instruction must carry enough structured data for the beneficiary bank to complete its local compliance obligations without having to query the originator. Payment purpose codes, beneficiary RFC or RUC or CPF numbers, underlying contract references, and invoice identifiers all affect whether the credit lands cleanly or stalls in the beneficiary bank's compliance queue.
We are not saying that Latin American corridors are uniquely difficult or that the regulatory requirements are unreasonable. The requirements generally exist to support tax compliance and FX monitoring, which are legitimate policy objectives. The argument is that a treasury team needs these requirements mapped at the corridor level before routing a payment, not discovered after the beneficiary reports non-receipt or delayed credit. Birch Hill's routing logic includes per-corridor documentation requirements so that the payment instruction is built correctly the first time, with the structured fields each local regime expects.