The Organisation

Multi-entity and multi-currency forecasting

Forecasting for a single entity in a single currency is one challenge. Consolidating forecasts across ten, twenty, or fifty entities in multiple currencies is a different game entirely. The complexity does not scale linearly — it multiplies. Three challenges in particular: eliminating intercompany flows, handling multiple currencies, and reconciling timing mismatches between entities.

Intercompany eliminations. Entity A in the Netherlands pays €500,000 to Entity B in Germany for management services. That is an outflow for A and an inflow for B — but at group level, it nets to zero. The cleanest way to handle this is to tag intercompany flows up front: every transaction between group entities goes into a dedicated Intercompany category. At a single-entity view they appear as normal flows; at group level the Intercompany category should net to zero. If it does not, that is your signal to drill down.

Multi-currency challenges. Each entity forecasts in its local currency. Group treasury needs the consolidated view in EUR or USD. Which exchange rate? Spot rates change daily — your three-month forecast moves even when nothing in the business has changed. Budget rates set at the start of the fiscal year give stability but diverge from reality. Forward rates represent the market’s expected exchange rate for a future date and are the most economically accurate for forecasting, though they require a forward-curve data source. For actuals, you can translate every transaction at the spot rate of the day it settled, or apply a single closing rate to the period — both valid, but they answer different questions about FX performance.

Timing mismatches. Entity A books a payment on Monday. Entity B receives it on Wednesday. In between, there is a two-day window where the cash has left one account but not arrived at the other. In the consolidated forecast, this creates a phantom cash gap that does not exist in reality. For intraday or daily forecasting, your system needs to understand that a payment and its corresponding receipt are the same transaction at different stages of settlement.

Centralised vs. decentralised forecasting

Bottom-up usually wins. Local teams have better visibility on local conditions. The most effective model is a hybrid: central treasury sets the framework (categories, time horizons, submission deadlines, quality standards) and local teams provide inputs within that framework. The AI validates everything.

AI as the quality layer

Decentralised forecasting introduces a quality problem. If twenty subsidiaries each submit forecasts, how do you ensure consistency? The Treasury Agent automatically reviews every submitted forecast against historical patterns and flags anomalies. A subsidiary in Brazil submits their quarterly forecast; the agent notices supplier payments are 40% below the same period last year with no corresponding change in customer receipts. It flags. The treasury team reaches out. The local team had forgotten to include a large vendor contract renewal due next month. These guardrails do more than catch errors — they educate users across the organisation about what a good forecast looks like.

Common pitfalls and how to avoid them

• Garbage in, garbage out. Spend the time on the foundation. Get 24 months of clean, categorised history before you turn on forecasting. It is not glamorous, but it is the highest-leverage thing you can do.
• Over-trusting the model. A forecast of €5M next week will usually be more accurate than €5M in one year. Always understand how confident the system is in its prediction, and treat different categories differently. Some forecast beautifully; others are inherently noisy.
• Ignoring business context. AI does not know about the acquisition you are planning next quarter, or the customer you are about to lose. The best forecasting systems make it easy for users to overlay their knowledge on top of the AI’s predictions. AI provides the baseline; human provides the context.
• Trying to forecast everything at once. Customer Receipts and Supplier Payments alone typically represent 60–70% of total cash flows. Start there. Add Salaries and Taxes next. Then the long tail. Prove the value, build trust, grow the scope deliberately.
• No feedback loop. If you never compare your forecast to what actually happened, you never improve — and worse, you never know how wrong you are. Close the loop. Every period, compare actuals to forecast. Measure accuracy by category. Identify systematic biases.