FP&A in emerging markets is one of those competencies that looks straightforward on paper and proves deeply challenging in practice. The standard planning frameworks — annual budgets, rolling forecasts, driver-based models, three-scenario analysis — were developed in stable, data-rich, institutionally mature environments. Applied to the GCC, South Asia, or Sub-Saharan Africa without significant adaptation, they produce plans and forecasts that look credible and prove unreliable.
The finance professionals who do this work well are those who understand exactly where the standard frameworks break down, why they break down, and what adapted approaches actually work in these operating environments. This is not theoretical knowledge. It is earned through the experience of building financial plans that held, and through the harder experience of building ones that did not.
Where Standard FP&A Frameworks Break Down
The failure modes are specific and predictable.
Annual planning cycles assume a predictable operating environment. In stable Western markets, the rate of change in the macro environment, regulatory framework, and competitive landscape within any given financial year is usually modest. Annual budgets are set with the expectation that the key assumptions — demand levels, cost inputs, regulatory requirements — will remain broadly within the range of the base case. In emerging markets, that assumption fails routinely. A Pakistani business building a three-year financial plan is operating in an environment where inflation, currency movements, regulatory changes, and political dynamics can shift assumptions by 30-50% in a single year. An annual budget built on a specific set of assumptions can be materially wrong within six months.
Driver-based models require reliable input data. The core value proposition of driver-based FP&A is that it grounds financial projections in observable operational and commercial drivers. But the quality of this approach is entirely dependent on the quality of the input data. In many mid-market businesses across the GCC and South Asia, the data infrastructure required to build genuinely reliable driver-based models does not exist. Customer data is incomplete. Operational metrics are inconsistently measured. Historical data is either absent or of questionable reliability. Building a driver-based model on poor data creates a false precision that is worse than acknowledging the uncertainty directly.
Discount rate and cost of capital assumptions are not transferable. DCF-based valuations and capital investment appraisals built on WACC assumptions derived from Western capital markets are not reliable when applied to businesses in markets with different risk profiles, different capital structures, and fundamentally different investor return expectations. The cost of equity capital for a business in Pakistan or Saudi Arabia is not the same as for a comparable business in the UK — and a financial model that does not reflect this will systematically mislead capital allocation decisions.
Forecasting in High-Inflation Environments
Building financial models in high-inflation environments requires a fundamental rethinking of how projections are structured.
The central error is building nominal projections that embed implicit inflation assumptions without making those assumptions explicit and manageable. A revenue growth forecast of 15% in an environment with 20% inflation is actually a real revenue decline of 5% — but if the forecast is presented in nominal terms without this context, it creates a misleading picture of business performance.
The most effective approach is to structure financial models in real (inflation-adjusted) terms for operational decision-making, while maintaining the nominal projections required for financial reporting. This means having an explicit, separately identified inflation assumption that flows through the model — affecting both revenues and costs — rather than embedding inflation assumptions inside growth rates in ways that make them invisible and unmanageable.
For businesses operating in environments like Pakistan, where CPI has exceeded 25% in recent periods, or Nigeria, where inflation has been consistently above 20%, maintaining the real vs nominal distinction is not academic. It is the difference between a management team that understands whether the business is genuinely growing and one that is being misled by nominal revenue increases that are not keeping pace with inflation.
The Currency Exposure Problem
Businesses operating across multiple emerging market currencies — whether through multi-country operations or supply chains that cross currency boundaries — face a financial modelling challenge that standard templates do not address well.
The starting point is understanding the business's actual currency exposure profile. Revenue currencies, cost currencies, and debt currencies need to be mapped clearly: a business that earns in Saudi Riyals, buys inputs in USD and Euros, and has employees in Pakistan earning Pakistani Rupees has a complex currency exposure that needs explicit modelling rather than implicit treatment.
In the GCC context, the USD peg of Saudi Arabia and UAE currencies significantly simplifies currency modelling for businesses with USD-denominated cost structures — but creates a specific challenge for businesses with significant non-USD cost bases, particularly those with large workforces in South Asian markets where currency depreciation can either benefit or complicate the financial model depending on how labour costs are contracted.
For businesses with genuine multi-currency complexity, the financial model needs sensitivity analysis on key exchange rate pairs — and the P&L and balance sheet presentation needs to clearly identify currency translation effects separately from underlying operational performance.
Data Quality: The Foundational Challenge
In Western markets, FP&A professionals spend most of their time on analysis. In emerging markets, a disproportionate amount of FP&A time is spent on data validation — checking that the numbers being analysed are actually correct before drawing conclusions from them.
This is not a criticism. It is a reflection of operating environments where ERP systems are less mature, where data entry disciplines are less rigorously enforced, and where the integration between financial and operational data that leading-edge finance functions take for granted is simply not present. The garbage-in-garbage-out problem is more acute and more consequential in these environments.
The practical response is to build data validation as a formal, documented step in every FP&A process — not an afterthought. This means establishing clear data sources for every metric, documenting the reconciliation between operational and financial data, and building automated checks that flag anomalies before they propagate into management reports and forecasts.
Scenario Planning as an Operational Discipline
In stable market environments, scenario planning is often treated as a strategic exercise — something that is done periodically, generates interesting analysis, and then sits on a shelf. In emerging markets, it needs to be an operational discipline that is embedded in every planning cycle.
The standard three-scenario framework — base, upside, downside — is often insufficient. Businesses operating in high-volatility environments need at least five scenarios that cover the specific risk vectors most material to that business: a currency stress scenario, a regulatory change scenario, a macro demand shock scenario, and a combined stress scenario in addition to the base. Each scenario needs to be operationally actionable — meaning management can identify specific decisions they would take if that scenario materialised, and the financial model makes those decisions traceable to their P&L and cash flow impact.
The difference between a scenario planning exercise that is genuinely useful and one that is academic lies in the operational specificity of the management responses. Scenarios without pre-defined management responses are analysis. Scenarios with them are contingency plans.
Building FP&A Without Enterprise ERP
A practical reality for most mid-market businesses in the GCC and South Asia is that their financial infrastructure is not ERP-supported at the level that would make standard FP&A processes straightforward. Most are operating on combinations of accounting software, Excel, and manual data collection processes that require significant effort to consolidate into anything resembling a coherent management information pack.
In this environment, the FP&A function's value is not in building sophisticated models on top of integrated data. It is in building the discipline and the systems — often relatively simple ones — that improve data quality and process consistency to the point where reliable analysis becomes possible. This means standardised chart of accounts, disciplined month-end close processes, and clear ownership of every metric in the management pack.
TVC's Experience Across the GCC and South Asia
Working with clients across Saudi Arabia, UAE, and Pakistan has given us direct experience of the specific adaptations that make FP&A work in these environments. The clients who get the most value from their FP&A function are not necessarily those with the most sophisticated tools — they are those whose finance function has built reliable data foundations, genuine scenario discipline, and the ability to translate financial analysis into clear operational decisions.
FP&A in emerging markets is harder than in stable markets. It also tends to be more consequential — because the operational decisions it supports are being made in environments where the cost of a bad capital allocation decision, or a forecast that proves wrong in the wrong direction, is higher. The rigour required matches the stakes.