Real-Time BRL Settlement for ERPs: What Embedded FX Changes for Corporate Treasury

An ERP with a financial module serving companies with cross-border flows usually hits the same limitation: currency conversion between reais and dollars runs through a banking rail that settles in days, during business hours only, with a spread the client only sees after the fact. Embedding real-time foreign exchange directly into that financial module changes what the software can promise a treasury user.

What changes when FX is embedded instead of routed through a bank

Crown FX, Crown’s institutional foreign exchange infrastructure, converts reais (BRL or BRLV) into dollar-pegged stablecoins, and back, with settlement in minutes rather than the T+1 or T+2 windows typical of bank-routed conversion. Operations through the API execute instantly, with liquidation in a few minutes (D+0); very high-volume operations can be liquidated within the same business day, and a client can also choose D+1 or D+2 settlement if that fits its process better. The quote shows the full spread before confirmation, with no hidden fees, and settles on both sides through rails already in use: Pix on the real side, dollar-pegged stablecoins on the other.

Why this route avoids the currency exchange tax

Crown FX operations are not subject to Brazil’s IOF-Câmbio tax. What is being traded are virtual assets, not foreign currency in the traditional sense: buying a virtual asset with reais does not involve an actual currency conversion, so there is no taxable event under the IOF-Câmbio rule.

What an ERP integration actually looks like

In Crown’s FX-as-a-Service model, a company embeds Crown’s APIs directly into its own product, so an ERP’s financial module can offer instant conversion inside the same screen a treasury user already works in, without sending the client to a separate banking portal. Crown’s API is authenticated by API keys and JWT tokens and covers creating and managing accounts and sub-accounts (a model built for software that serves its own clients), generating Pix QR codes for deposits, requesting quotes and executing conversion orders, requesting withdrawals via Pix, TED or token, querying balances and full transaction history, and receiving webhooks for each event: deposit processed, order completed, transfer completed, withdrawal completed. The company embedding this monetizes the FX spread and keeps the client relationship, while Crown handles settlement and all mandatory reporting to the Central Bank of Brazil, including reporting on transactions made by the end clients of the embedding company’s own product.

What a treasury team gets from this, concretely

For a treasury team working inside an ERP, the practical change is in three places: same-day settlement instead of a multi-day window for currency conversion tied to a cross-border payment or receipt; a visible, fixed spread at the moment of quoting, instead of a rate confirmed only after the transfer clears; and programmatic access, meaning the conversion can be triggered automatically from the ERP’s own workflow instead of requiring a manual step in a separate banking system.

Frequently asked questions

Does an ERP need to support BRLV specifically to use embedded FX? No. A company can convert reais and dollar-pegged stablecoins directly without holding BRLV; BRLV is a separate, optional real-pegged token issued by Crown.

How fast does an embedded FX conversion actually settle? Operations through the API settle in minutes (D+0) in most cases. Very high-volume orders can settle within the same business day, and a client can also choose D+1 or D+2 if preferred.

Who is responsible for regulatory reporting when FX is embedded inside another company’s software? Crown is. In the FX-as-a-Service model, Crown consolidates and reports every transaction, including those made by the end users of the embedding company’s own product, in the format the Central Bank of Brazil requires.