Multi-country startup treasury: a four-country case

A startup with a team and clients in four countries rarely has a cash problem. It has four separate cash positions nobody sees together. One bank in Bogotá, another in Mexico City, another in São Paulo, another in Santiago, each with its own portal, its own cutoff time, and its own informal rule about who can approve a payment. The CFO rebuilds the full picture by hand, almost always too late for the decision that needed it.

At Soulbit Academy we present this case as an illustrative, composite example, not a real client. It differs from another case published on this blog, about a startup with a remote team in five countries that pays its entire payroll in USDC: that one solves salary disbursement, this one solves cash visibility and who approves what before a payment leaves any account.

The case: a software startup with cash sitting in four countries (illustrative profile)

Arion is an illustrative software startup, legally headquartered in Colombia with a Delaware holding structure for its investors, selling a billing and project management platform to professional services agencies. Its Series A closed 16 months ago, and annual recurring revenue runs close to 3.1 million dollars.

The team has 47 people: most based in Colombia, with small commercial teams in Mexico, Brazil, and Chile serving clients in each market. Arion does not sell a financial product. It sells software, and its treasury problem is one of internal governance, not product design.

Why does a software startup end up with a treasury problem as complex as a financial company's?

Because the number of currencies and banks it handles depends on how many countries it operates in, not on its sector. Arion bills clients in Colombian pesos, Mexican pesos, Brazilian reais, and Chilean pesos, and pays local payroll and expenses in those same four currencies, exactly as any company with the same geographic footprint would.

The problem: without consolidated visibility, every subsidiary made its own cash calls

Arion's problem was not a lack of cash. It was the lack of a single picture of the cash it already had. Every Monday, the finance lead logged into four separate bank portals, copied balances into a spreadsheet, and sent a summary to the board almost a full day after the week's decisions had already been made.

Payment approval had no written rule either. A country manager could authorize a wire over Slack, and the central team found out when it reviewed the bank statement, not before. In one quarter, that gap produced a duplicate payment to a Mexican vendor and a contractor payment that went unpaid for two weeks because nobody knew who was supposed to approve it.

Moving money between the four cities also carried a cost, even if it was not the sharpest pain point. As a public reference, the World Bank calculates in Remittance Prices Worldwide that sending money across borders costs 6.36% of the amount on average, and close to 15% through the banking channel, on a reference amount of 200 dollars. That is remittance data, not company-to-company payment data, but it describes the same banking pipeline Arion used between its four offices.

Why does missing an approval rule matter more once a company operates in several countries?

Because each subsidiary develops its own informal rule about who can pay what, and those rules do not match across countries. Without a written payment approval policy, every Arion subsidiary ended up operating under different rules, a risk that grows with each new country added to the operation.

Colombia, Mexico, Brazil, and Chile: what Soulbit's V1 covers today and what still depends on the local bank

Of the four countries where Arion operates, only Colombia has a local banking rail inside Soulbit's V1. That distinction orders everything else: the company's dollar balance gets centralized in one place, while local currency payments in the other three countries still leave from each subsidiary's traditional bank.

Country (illustrative case)	Role in Arion's operation	Local banking rail in V1?	How it is resolved today
Colombia	Headquarters and operating subsidiary	Yes	Collections and payments in pesos disburse through the local banking rail
Mexico	Commercial subsidiary and clients	No	Local payroll and expenses through the subsidiary's Mexican bank
Brazil	Commercial subsidiary and clients	No	Local payroll and expenses through the subsidiary's Brazilian bank
Chile	Commercial subsidiary and clients	No	Local payroll and expenses through the subsidiary's Chilean bank

That asymmetry is not an arbitrary product choice. It reflects that each country's exchange regime sets its own requirements for a company moving a balance in foreign currency. In Colombia, for instance, the Banco de la República regulates the registration and reporting of compensation accounts that channel foreign currency into the country, a framework with no identical equivalent in the other three countries of this case.

Arion's larger contracts, mostly the ones that renew annually, are already billed in dollars by agreement with the client, an increasingly common practice among B2B software in the region. Those collections arrive as dollar or stablecoin balance and can be requested through a payment link, without depending on a different correspondent bank per client. Smaller contracts, billed in local currency, still collect through each subsidiary's traditional banking channel.

What changes when treasury gets centralized: a consolidated balance and a written approval policy

Centralizing treasury changed two things for Arion: where the balance is visible and who can approve a payment. The dollar and stablecoin balance that used to sit scattered across correspondent banking relationships moved to a single place, visible to the founder and the finance lead without copying figures from one portal to another.

The second part, and the one that took the longest to draft, was a written treasury policy with approval thresholds by amount: below a certain value, the finance lead approves alone; above it, the founder signs off too. The treasury policy template for SMBs Arion used as a starting point sets exactly that kind of rule, along with who can authorize a new banking counterparty.

That consolidated balance sits alongside the multi-currency balance in USD, EUR, and GBP Arion started using to hold part of its reserve without converting it to pesos immediately, something it used to do by default and that cost it spread every time it was not needed. Holding balance in several currencies also changed the monthly close, because the team now records foreign exchange differences at close for each currency, an adjustment that did not exist before because everything converted to pesos right away.

The monthly flow, step by step: from client collection to accounting close

Arion's monthly flow starts when a client pays an invoice and ends when the finance lead reconciles the full month against the budget. It used to run through four independent processes; now it shares one starting point.

A large client pays its annual renewal in dollars through a payment link; the balance is available the same day, without waiting for a correspondent bank confirmation. A smaller Colombian client pays in pesos by local transfer, which Arion still receives through its traditional bank account in Bogotá. Payroll for the three subsidiaries outside Colombia leaves from each local bank, while Colombian payroll and expenses disburse through the V1 local banking rail.

At month end, the finance lead reconciles the centralized balance's movements against the on-chain identifier of each collection, a procedure described in more detail in multi-currency bank reconciliation. The three local bank statements, one per subsidiary, still get reconciled separately, but they no longer determine how long it takes the team to know how much cash the company holds overall.

How long did monthly close take before and after the change?

Before, Arion took between six and eight business days to close the month, because each subsidiary reconciled its own bank separately and the consolidated result arrived last. After, closing the centralized balance takes less than a day, though the three local bank statements from Mexico, Brazil, and Chile still follow their own reconciliation calendar, which the change did not remove.

Dimension (illustrative case)	Before	After
Consolidated balance visibility	Spreadsheet rebuilt by hand every Monday	One balance visible instantly, no copying figures
Payment approval	Informal rule over Slack, different per subsidiary	Written policy with thresholds by amount
Monthly close of the centralized balance	6 to 8 business days	Less than 1 day
Collection of large contracts	International wire through a correspondent bank	Payment link in dollars or stablecoin
Idle cash reserve	Converted to pesos by default	Held in dollars, euros, or pounds as needed
Local currency payments in Mexico, Brazil, and Chile	Each subsidiary's local bank	Still each subsidiary's local bank

What still depends on the local bank in each country, and the case's honest limits

Soulbit's V1 does not open a bank account in Mexico, Brazil, or Chile, and it would be dishonest to suggest Arion's case solves treasury equally across all four countries. The local banking rail only exists in Colombia, so payroll and expenses in Mexican pesos, Brazilian reais, and Chilean pesos still depend on each subsidiary's traditional bank, with its own timelines and fees.

There is also no automatic conversion between the balance's currencies: each one is held separately until the company requests an OTC quote on demand to convert it. And the consolidated balance does not replace reconciling the three local banks, which remains the job of each subsidiary's finance team, not the product's.

Another startup with a similar geographic footprint can take one concrete idea from this case: consolidated visibility and a written approval policy solve the internal governance problem, but they do not remove dependence on the local banking system in the countries Soulbit's rail does not reach yet. Recognizing that boundary from the start avoids promising the team something the product does not deliver today.

What another regional startup can take from this case

Three conclusions carry well to another company with a team and clients across several LATAM countries.

The first is that centralizing treasury is not the same as centralizing banks: Arion still uses three separate local banks, and what changed was having a single picture of available cash, not eliminating those banking relationships. The second is that a written approval policy takes longer to draft than to run, and it prevents exactly the kind of error, the duplicate payment or the payment with no clear owner, that cost Arion the most before the change. The third is that billing large contracts in dollars and collecting them through a single channel reduces dependence on local currency conversion, but only for the share of revenue the client agrees to pay that way.