Blog · Forecast and pipeline · Finance and FP&A teams
Build cash forecasts in each transaction currency before translating them into USD. Use a worked schedule to separate operating movements, currency headroom and exchange-rate effects.
Multi currency cash flow forecasting starts with separate receipts, payments and balances for each transaction currency, then translates them into USD. Check each currency against its own required balance before reading the consolidated total. Otherwise, cash held in one currency can hide a payment shortage in another.
Export bank balances by account, open customer invoices, open supplier invoices and the planned payroll, tax and investment payments. Keep the entity, account, transaction currency, outstanding amount, expected cash date and source reference on every row. A ledger's USD book value is useful for reconciliation, but it cannot replace the amount actually payable in euros or Canadian dollars.
Use a common forecast cutoff. Mark restricted balances and cash that cannot be moved between entities promptly. Treasury should confirm those restrictions; a spreadsheet consolidation does not establish that an account can fund another entity's obligations.
The broader cash flow forecast explains the company cash roll-forward. Here the additional work is preserving currency units and explaining the USD bridge. For short-term dates, the 13-week cash flow layout supplies a useful weekly structure.
Keep exchange-rate assumptions in a separate table with currency, period, rate, quote direction and approval date. Normalize the calculation to USD per one currency unit. The Federal Reserve's H.10 release illustrates why the label matters: its rates generally use currency units per USD, while starred currencies use USD per currency unit. Do not multiply both types by the foreign balance without normalizing them.
Closing native cash = Opening native cash + Native receipts − Native payments
Native headroom = Closing native cash − Required native balance
A US distributor prepares its November 2026 forecast. These are supplied planning assumptions, not current market exchange rates. Receipts and payments exclude any currency conversions between its own accounts.
| Currency | Opening (currency units) | Receipts (currency units) | Payments (currency units) | Closing (currency units) | Required balance (currency units) | Headroom (currency units) |
|---|---|---|---|---|---|---|
| USD | 200,000 | 140,000 | 180,000 | 160,000 | 100,000 | 60,000 |
| EUR | 100,000 | 60,000 | 120,000 | 40,000 | 50,000 | -10,000 |
| CAD | 80,000 | 50,000 | 70,000 | 60,000 | 30,000 | 30,000 |
With these columns in A:G, enter the following in E2 and G2, respectively, then fill down:
=B2+C2-D2
=E2-F2
There is no meaningful grand total for the native-currency columns. Adding euros to Canadian dollars produces a number without a usable unit. The EUR row is already actionable: its expected balance is below the supplied requirement even though it remains positive.
For transaction detail, place currency in column B, expected cash date in C, receipt amount in D and payment amount in E on a Transactions sheet. On a Summary sheet put the currency in A2, the period start in J1 and the next period start in K1. November receipts in C2 are:
=SUMIFS(Transactions!$D$2:$D$5000,Transactions!$B$2:$B$5000,$A2,Transactions!$C$2:$C$5000,">="&$J$1,Transactions!$C$2:$C$5000,"<"&$K$1)
Use the same formula with the E range for payments in D2. Microsoft documents SUMIFS for summing values that meet multiple criteria. Here the criteria are currency and the two date boundaries. Store dates as actual dates, and extend every range together when adding records. Covirage is not affiliated with Microsoft.
Use one reference rate for opening balances and forecast flows in this simplified example. First translate closing native cash at that same rate. Then revalue the closing balance at a separate closing-rate assumption.
| Currency | Reference rate (USD/unit) | Closing rate (USD/unit) | Closing at reference rate (USD) | Closing at closing rate (USD) | Translation effect (USD) |
|---|---|---|---|---|---|
| USD | 1.00 | 1.00 | 160,000 | 160,000 | 0 |
| EUR | 1.10 | 1.15 | 44,000 | 46,000 | 2,000 |
| CAD | 0.75 | 0.72 | 45,000 | 43,200 | -1,800 |
| Total | 249,000 | 249,200 | 200 |
On a Rates sheet with this table starting in A1, D2 is =Summary!E2*B2, E2 is =Summary!E2*C2, and F2 is =E2-D2. The total translation effect is $200. It does not represent a customer receipt.
The consolidation check uses the same reference rates throughout:
| Bridge step | Calculation | Amount (USD) |
|---|---|---|
| Opening cash | 200,000 + 100,000 × 1.10 + 80,000 × 0.75 | 370,000 |
| Receipts | 140,000 + 60,000 × 1.10 + 50,000 × 0.75 | 243,500 |
| Payments | 180,000 + 120,000 × 1.10 + 70,000 × 0.75 | -364,500 |
| Closing before translation effect | 370,000 + 243,500 − 364,500 | 249,000 |
| Translation effect | 2,000 − 1,800 | 200 |
| Translated closing cash | 249,000 + 200 | 249,200 |
All money results are rounded to whole units after calculation. If different flow-date rates are supplied, build the bridge from those rates instead; do not reuse this simplified reference-rate calculation unchanged. The historical reporting treatment belongs with the foreign-currency cash flow statement, which serves a different purpose from a planning scenario.
The consolidated closing balance is $249,200, but EUR headroom is still negative. Treasury must review the timing of EUR receipts, supplier commitments, available conversion arrangements and account restrictions. A stronger euro increases the reported USD value without curing the shortage of euro units.
Record any proposed conversion as two linked native-currency entries with a common reference. Include approved fees and expected settlement dates. Consolidated cash should change only for the economic costs and any genuine timing differences, rather than treating the transfer receipt as new external funding. Keep the proposed action separate until its owner confirms the assumption.
For annual investment and financing choices, link these currency schedules to long-term cash flow forecasting rather than extending one month's exchange-rate assumption indefinitely.
Bring a sample of your own bank, receivables and payables exports with currency identifiers, expected dates and supplied rate assumptions. Covirage maps the columns; its tools compute and check balances and comparisons, and the external AI model explains the results with every figure traced to its rows. Create a free Covirage account, then set up your business and bring your file.
See Covirage for finance teams for the supporting finance workflow.
Start with transaction currency because that is what customers pay and suppliers receive. Translate the completed currency schedules into your reporting currency afterward. Keep both views so a favorable consolidated total does not hide a shortage in one currency.
Use documented planning assumptions for the expected payment dates and closing balances. Record the quote direction and effective period. Keep an approved base set and separate rate scenarios; a forecast assumption is not a guaranteed future conversion rate.
A higher USD equivalent can arise while the foreign-currency bank balance stays unchanged. It changes the reporting value, but does not itself add currency units to the account. Funding decisions still require the native balance, payment dates and any restrictions.