Cash flow forecast: USD revenue, local currency costs
When revenue arrives in dollars and costs are fixed in local currency, a cash flow forecast needs a rate assumption for every line, not a single rate applied to the whole period.
A Latin American company that bills a US client in dollars and pays payroll and suppliers in a local currency runs into a question its spreadsheet template rarely answers well: which exchange rate applies to which line. Forecasting the whole period at today's rate looks simple, but the number goes stale fast: most Latin American currencies move often and in both directions.
In Soulbit Academy we cover the mechanics of building a cash flow forecast when revenue arrives in one currency and costs leave in another. This is not a guide to hedging instruments or currency derivatives, that ground is covered in FX hedging for companies with USD revenue and local currency costs; this guide is about the forecasting mechanics themselves, line by line and scenario by scenario.
What a cash flow forecast means when revenue is in dollars and costs are local
A cash flow forecast in foreign currency is the periodic estimate of a company's expected cash inflows and outflows when those two streams are not denominated in the same currency. The basic structure does not change: expected collections and payments are listed for each week or month of the horizon. What changes is that every revenue line arrives in dollars and needs converting to local currency before it can be compared against cost lines that are already local.
A company that exports software or services and bills 30,000 dollars a month has a fixed dollar revenue, but the local currency amount that revenue represents changes every time the exchange rate moves. Payroll, rent and local suppliers, by contrast, are fixed in local currency and do not move with the exchange rate. A cash flow forecast exists to anticipate whether that local currency will be enough, depending on a variable the company does not control.
What gets forecast in each currency: the first step against the mismatch
The first step of a forecast with a currency mismatch is to separate every line by its currency of origin, without converting anything yet. Revenue that arrives in dollars gets forecast in dollars: the invoiced amount, the estimated collection date and the client, without touching the exchange rate yet. Costs in local currency get forecast in local currency: payroll, benefits, rent, local suppliers and taxes, also without touching the rate.
Separating each line by currency before converting avoids a common mistake: forecasting revenue already converted to local currency at the rate on the day the spreadsheet is built. If the rate moves before the actual collection date, the forecast figure is wrong from the start and the error carries through the horizon. Keeping revenue in dollars until the last step lets a company apply different rate assumptions without rebuilding the forecast.
What about costs that are already in dollars, like software or international suppliers?
Those costs get forecast the same way as revenue: in their original currency, with their own payment date, converted at the end using the same criteria. A company that pays software in dollars and bills its own clients in dollars has, on that portion, a natural hedge: the rate moves the same way for both sides. The real mismatch sits only in the portion of local currency costs with no dollar counterpart.
The most common mistake: forecasting the whole period at today's rate
The most common mistake in a foreign currency cash flow forecast is applying today's exchange rate to collections that will happen in 30, 60 or 90 days. That practice treats a daily-fluctuating variable as if it were constant across the whole planning horizon, producing a single figure that looks precise without being precise at all.
The problem is not just theoretical. A company forecasting a 50,000 dollar collection 90 days out using today's rate can end up with a meaningful gap in local currency terms between the forecast and the actual collection, without anything having gone wrong in the underlying sale. The gap comes entirely from the exchange rate: foreseeable in its existence, even if not in its exact size.
The alternative is not guessing the correct rate, because no one knows it with certainty: it is treating the rate as a range with three reference points, not a fixed number.
How to build three rate scenarios: base, pessimistic and optimistic
A cash flow forecast built with three exchange rate scenarios starts from a central rate assumption and applies a reasonable variation up and down, instead of a single figure. The base scenario uses the rate the company considers most likely for the date of each collection, anchored to the currency's recent behavior. The optimistic scenario applies a depreciation of the local currency against the dollar, which increases the local currency value of the collection. The pessimistic scenario applies an appreciation, which reduces it.
Why is a stronger local currency the pessimistic scenario for a company with dollar revenue?
Because a company that bills in dollars and pays its fixed costs in local currency receives less local currency for every dollar collected when the local currency strengthens. Dollar revenue does not change, but its local currency equivalent does, and that equivalent is what covers payroll.
| Scenario | Assumed rate (MXN/USD) | Variation versus base | USD 50,000 collection in MXN |
|---|---|---|---|
| Optimistic (local currency depreciates) | 21.60 | 8% above base | 1,080,000 |
| Base (starting assumption) | 20.00 | 0%, starting rate of the exercise | 1,000,000 |
| Pessimistic (local currency appreciates) | 18.00 | 10% below base | 900,000 |
The gap between the pessimistic and the optimistic scenario, 180,000 pesos in this example on the same 50,000 dollar collection, is the figure treasury needs before committing that revenue against fixed local currency costs. That gap should not come from intuition: it is worth anchoring it to the recent trading range of the local currency, which a central bank publishes officially, such as the Banco de Mexico FIX rate, and adjusting it to the horizon of each collection. A 30 day horizon supports a narrower range than a 120 day one. A company operating out of Colombia can build the same range around the TRM, documented in dollar treasury for Colombian companies facing devaluation.
The lag between the invoice date and the collection date
The lag between the date an invoice is issued and the date cash actually lands is the second source of error in a cash flow forecast, independent of the rate's level. A company that invoices on day one and collects in 60 days has two competing dates that could define which rate applies, and confusing them creates two distinct problems: one in cash planning and one in accounting.
For cash planning, the rule is simple: revenue belongs on the estimated collection date, not the invoice date, because that is when available cash actually changes. An issued invoice is not cash, it is an expectation of cash with a due date, and placing it too early makes treasury believe it has liquidity it does not yet have.
For accounting purposes, the governing date is different. Companies operating in Colombia, for example, follow article 288 of the Estatuto Tributario, which requires measuring foreign currency revenue at the official rate on the date of initial recognition, and recognizing the gap against the rate on the actual collection date as a separate foreign exchange difference only at settlement, a mechanic covered in detail in Colombia's TRM and the DIAN exchange rate rule. The official U.S. dollar reference rates published in the Federal Reserve's H.10 release illustrate how a central bank formalizes that same kind of daily reference for reporting purposes.
The practical consequence is carrying two rate columns for every collection: the assumed rate used for the cash forecast, drawn from the scenario range, and the rate that will ultimately be recorded for accounting, only known on the day of collection. A company evaluating whether to invoice in dollars in the first place can review what that involves in dollar invoices from Colombia: what they mean.
What Soulbit V1 delivers for cash forecasting and what it does not
Soulbit V1 offers a business account with balances in USDC and USDT, fiat in USD, EUR and GBP, and in Colombia a local rail with disbursement in COP and in USD. That layer is useful as an input to a forecast: it lets a company hold part of its revenue in digital dollars and decide when to convert, instead of converting automatically the moment a collection lands, an alternative worth comparing against the options in USD accounts for companies in Colombia.
What Soulbit V1 does not do matters just as much: it does not forecast a company's cash flow, does not calculate rate scenarios, and does not offer forwards, options or any currency hedging instrument, products that come from commercial banks and sit outside the V1 scope. Nor does it decide the accounting or tax rate for each entry, that sits with each company's own accountant.
| Cash forecast need | Does Soulbit V1 cover it? | How it is resolved |
|---|---|---|
| Holding part of revenue in digital dollars | Yes | USDC and USDT balances with institutional custody |
| Seeing the quote before converting to local currency | Yes | Visible quote before confirming the conversion |
| Receiving local disbursement in Colombia | Yes | Local rail with disbursement in COP and USD |
| Calculating base, pessimistic and optimistic rate scenarios | No | A treasury exercise the company runs itself |
| Contracting forwards, NDFs or hedging options | No | A commercial banking product, outside the V1 |
| Deciding the accounting or tax rate for each entry | No | Sits with the company's own accountant |
How to review and update the forecast every month
Reviewing the forecast every month means closing each period by comparing the rate that actually applied to each collection against the three forecast scenarios. The next step is noting where the real result landed inside that range, because the initial forecast is an assumption, not a fact.
That comparison serves two purposes. The tactical one: if the real result lands near the pessimistic scenario, the company has an early signal to review its cost structure or accelerate converting dollar balances. The methodological one: if the gap between scenarios turns out too narrow or too wide month after month, it is worth adjusting the variation percentage used to build it, rather than keeping an assumption the evidence has already contradicted.
The review horizon matters too. A 90 day forecast is worth updating weekly in its first month, when the margin of error is smallest. The farther months can be reviewed less often, because uncertainty there is structurally larger and a weekly update does not add real precision.
Frequently asked questions
What is a cash flow forecast in foreign currency?
It is the periodic estimate of a company's future cash inflows and outflows when those streams are denominated in different currencies, for example revenue in dollars and payroll or supplier costs in local currency. Unlike a single-currency forecast, every line needs its own exchange rate assumption and its own conversion date, not one rate applied across the whole period.
What exchange rate should a CFO use to forecast a dollar collection?
For forecasting, the safer practice is to build a range around a base, a pessimistic and an optimistic rate assumption, not a single figure. For recording a collection that already happened, most jurisdictions require the official rate on the date of initial recognition. Confusing the forecasting rate with the accounting rate is the most common error.
How wide should the gap be between the base and the pessimistic scenario?
There is no universal percentage: it depends on the historical volatility of the local currency and on the length of the forecast horizon. A company can look at the recent annual trading range of its local currency and apply a fraction of that range to a 90 or 120 day horizon. The exercise is about sensitivity, not prediction.
What should a company do when the invoice date and the collection date fall in different months?
Two questions need to be kept separate. For cash planning, the forecast should place the revenue on the estimated collection date, not the invoice date, because that is when cash becomes available. For accounting and tax purposes, most jurisdictions recognize revenue at the rate on the initial recognition date and treat the gap as a separate foreign exchange difference recorded at settlement.
Does a USDC balance replace a local currency cash flow forecast?
No. Holding part of a company's working capital in USDC reduces the friction of converting currency repeatedly and gives the company a digital dollar layer, but it does not remove the need to forecast how much local currency is required each month for payroll, local suppliers and taxes. The local currency cash flow forecast remains the reference document for those obligations.
Want your company to add stablecoins to its operations?
Join the Soulbit waitlist and start paying payroll, collecting and managing treasury without SWIFT.
Join the waitlist