The CFO's Blind Spot: Why Multi-Country Organizations Can't Answer Their Simplest Profitability Question
Last year I sat in on a board review at a consumer goods company headquartered in Florida with operations in six Central American countries and the Dominican Republic. The meeting was going well — consolidated revenue up 11%, EBITDA margins holding at 14.2%, the new Dominican distribution center on schedule. Then the CEO asked what should have been a straightforward question:
“Are we actually making money in Honduras? Because the team there keeps asking for headcount and I don’t have a good reason to say yes or no.”
The room went quiet. The CFO pulled up a slide showing revenue by country. The regional VP showed volume growth by SKU category. The controller had a cost allocation model in Excel that split corporate overhead by revenue share — the laziest allocation method in existence, but nobody had challenged it because the consolidated number looked fine.
After twenty minutes of back-and-forth, the honest answer was: nobody knew. They had revenue by country. They had cost of goods by plant. But the cost of serving Honduras — the logistics, trade spend, regulatory compliance, local sales team, and credit risk — was buried across seven line items in four systems. The profitability they were reporting was an arithmetic artifact, not a business truth.
I’ve seen this scene play out in banking, insurance, pharma, and logistics across Latin America and the Caribbean. The specifics change. The underlying failure doesn’t.
Three questions should guide this conversation:
Why can’t multi-country organizations isolate profitability by geography, channel, and customer — even with modern ERP systems?
What does the regulatory environment — BEPS 2.0, transfer pricing, IFRS 18 — do to profitability visibility, and why is it getting worse before it gets better?
How do you build a profitability architecture that works across borders without a two-year transformation program?
I. The structural problem: ERPs were built for accounting, not for decisions
Here’s something that sounds obvious but has enormous consequences: your ERP system was designed to record transactions and produce financial statements. It was not designed to tell you whether your Honduran operation is creating or destroying value.
Most multi-country organizations consolidate financial data by legal entity. That’s what the auditors need. That’s what the regulators require. So the chart of accounts is built around legal structure — Entity 101 is Guatemala, Entity 102 is Honduras, Entity 103 is El Salvador. Revenue and direct costs flow naturally into these buckets.
But shared costs don’t. And in a multi-country operation, shared costs are where the truth hides.
The distribution center in Guatemala serves Honduras, El Salvador, and Guatemala itself. How do you allocate its costs? By revenue? By volume? By number of deliveries? Each method produces a wildly different picture of profitability. I ran the numbers for one client: under revenue-based allocation, Honduras showed a 6.3% operating margin. Under activity-based allocation — factoring in delivery frequency, order complexity, return rates, and credit terms — Honduras was underwater by 2.1%. Same business, same period, eight-point swing depending on the allocation method.
Revenue-based allocation is the financial equivalent of splitting a restaurant bill evenly among ten people when three of them ordered lobster. It’s convenient. It’s wrong. And it systematically subsidizes your worst-performing geographies with margin from your best ones.
The CFO who reports “we’re profitable in every country” based on revenue allocation isn’t lying. But they’re not telling the truth either. They’re telling a story the data can’t support.
This isn’t a technology gap. Oracle, SAP, and every major ERP can produce entity-level financials. The gap is analytical — the cost model that sits between your general ledger and your profitability statement. Without Activity-Based Costing (ABC/M) providing the causal logic for how costs flow to products, customers, channels, and geographies, your profitability numbers are a function of your allocation assumptions rather than your business reality.
II. The regulatory layer: BEPS 2.0 and IFRS 18 are making the blind spot dangerous
For years, imprecise profitability by geography was an internal management problem. You could live with it because nobody outside the organization was asking for the breakdown. That’s changing — fast.
BEPS 2.0 and the Pillar Two GloBE rules are reshaping transfer pricing and minimum taxation for multinational groups with consolidated revenue above €750 million. The core requirement: demonstrate where value is created in your value chain, and ensure each jurisdiction pays a minimum effective tax rate of 15%. The operative word is demonstrate. Not estimate. Not approximate. Demonstrate — with data, with methodology, with documentation that can survive a tax authority audit.
If you can’t disaggregate profitability by jurisdiction with analytical rigor, you can’t comply. And if your transfer pricing documentation relies on the same revenue-based allocation as your management reporting, you have a problem. Tax authorities in Mexico, Colombia, and Brazil are already challenging intercompany pricing models that lack granular cost attribution. The OECD’s guidelines explicitly call for transactional analysis that reflects the actual functions performed, assets used, and risks assumed in each jurisdiction. That’s ABC/M language — whether the regulators call it that or not.
IFRS 18, effective January 2027, goes further. It replaces IAS 1 and fundamentally restructures how the income statement is presented. Three mandatory categories — operating, investing, and financing — replace the current flexible format. More critically, companies must disclose “management-defined performance measures” (like adjusted EBITDA) with transparent reconciliation to IFRS figures.
Why does this matter for multi-country profitability? Because IFRS 18 will expose the analytical infrastructure — or lack thereof — behind every performance measure a CFO reports. If your operating profit by segment relies on arbitrary allocations, the new disclosure requirements will make that visible to investors, analysts, and board members. The accounting standard is, in effect, demanding a cost architecture that most organizations don’t have.
I sat on a panel last year discussing IFRS 18’s implications for analytical accounting. The consensus among the practitioners in the room was stark: organizations with ABC/M and integrated EPM architectures will comply with minimal incremental effort. Organizations without them face a 12- to 18-month infrastructure buildout — and most haven’t started.
The regulatory timeline is not ambiguous. BEPS 2.0 is being implemented now. IFRS 18 applies to annual periods beginning on or after January 1, 2027. The window for building the profitability architecture that both require is closing.
III. The solution: profitability architecture that works across borders
I use the word “architecture” deliberately. This isn’t a project — it’s a system. And like any architecture, it has layers.
Layer 1: ABC/M as the cost truth engine. Activity-Based Costing provides the causal model for how resources flow to activities, and activities flow to cost objects — products, customers, channels, and geographies. It replaces arbitrary allocation with operational logic. The distribution center’s costs are assigned to Honduras, not based on Honduras’s revenue share but on the number of deliveries, the average order size, the handling complexity, and the return rate. The result is a profitability number that reflects what actually happens in the business, not what a formula assumes.
For multi-country operations, ABC/M must work at two levels simultaneously: within each country (customer and channel profitability) and across countries (shared service allocation, intercompany pricing, regional overhead distribution). The model needs to be precise enough for transfer pricing documentation but flexible enough for monthly management reporting. That’s a design challenge, not a technology challenge.
Layer 2: Oracle EPM as the planning and consolidation backbone. ABC/M produces the cost truth. EPM makes it actionable at the speed of business. Oracle EPM Cloud — specifically the Profitability and Cost Management (PCM) module integrated with Planning — allows you to run multi-dimensional profitability analysis across entities, simulate allocation scenarios, and produce management and regulatory reporting from the same data model.
The critical design choice: don’t build two parallel systems. I’ve seen organizations run ABC/M in a standalone tool and EPM separately for planning, with a manual bridge between them. It works for about six months, then the bridge breaks and nobody trusts either system. The architecture must be integrated — one data model feeding both profitability analysis and planning processes.
Layer 3: Decision-to-Value (D2V) as the governance framework. The profitability architecture produces numbers. D2V ensures those numbers connect to decisions. Every strategic initiative — entering a new market, launching a product, restructuring a channel — has a traceable financial impact mapped to specific profitability drivers: margin, volume, cost-to-serve, churn. The business case is updated quarterly against actuals, not defended once at approval and forgotten.
Without this governance layer, you end up with an expensive reporting system. With it, you have a decision engine. The difference shows up in six months: organizations with D2V governance reduce their strategic portfolio to initiatives with measurable financial impact. The ones without it keep running 30+ initiatives and wondering why the P&L doesn’t move.
A practical note on timeline: Building this architecture doesn’t require a two-year transformation. For a mid-size multi-country operation (4–8 entities, $100M–$500M in revenue), we typically scope the initial deployment in three phases: ABC/M design and pilot in one geography (8–10 weeks), EPM integration and rollout to remaining entities (10–14 weeks), and D2V governance activation (4–6 weeks). That’s roughly six months from kickoff to a functioning profitability architecture. Not perfect — no architecture is perfect on day one — but operational and producing decision-quality data.
Consolidated profitability is the most dangerous number in finance. It tells you the patient is alive. It doesn’t tell you which organ is failing. And by the time the failure shows up in the aggregate, you’ve lost the window to intervene.
Five actions for Monday morning
1. Run the allocation test. Take your most recent country-level P&L and recalculate operating profit using three different allocation methods for shared costs: revenue-based, volume-based, and headcount-based. If the profitability ranking of your countries varies by method, you don’t have a profitability answer — you have an allocation assumption.
2. Map your BEPS 2.0 exposure. If your group’s consolidated revenue exceeds €750 million — or is approaching it — assess whether your current transfer pricing documentation can demonstrate value creation by jurisdiction with analytical rigor. If it relies on revenue splits or formulary apportionment, it won’t survive a challenge.
3. Assess your IFRS 18 readiness. Review how your management-defined performance measures (adjusted EBITDA, operating profit by segment) are constructed. Can you reconcile them transparently to IFRS figures? Can you disclose the methodology without embarrassment? If not, you have 18 months to build the infrastructure.
4. Identify your “Honduras.” Every multi-country organization has at least one geography that looks profitable under consolidation but is value-destructive under proper cost attribution. Find it before the regulators or the board does. The conversation is easier when you bring the data than when someone asks for it.
5. Start with one country, not all of them. Don’t try to build a profitability architecture across eight entities simultaneously. Pick the country with the most operational complexity, build the ABC/M model there, prove the methodology, then replicate. The pilot teaches you more about your data quality and organizational readiness than any assessment ever will.
In 12 to 24 months, the regulatory pressure on multi-country profitability transparency will be materially higher than it is today. The organizations that build the architecture now will be ready. The ones that wait will be explaining to tax authorities, regulators, and board members why they can’t answer the simplest question in finance: where are we actually making money?
About the Author
Pedro San Martín is Principal at Asher & Company, Strategic Finance Center of Excellence in partnership with PwC Interamericas. He chairs the IMA Profitability & Cost Management SIG and teaches at ITAM and Universidad Anáhuac. Contact: psanmartin@asheranalytics.com
Ready to map your multi-country profitability architecture? Schedule a Discovery Call at asher.company/contact
References
OECD. (2023). “Tax Challenges Arising from the Digitalisation of the Economy — GloBE Rules (Pillar Two).” oecd.org/tax/beps
IASB. (2024). “IFRS 18: Presentation and Disclosure in Financial Statements.” ifrs.org
Kaplan, R., & Anderson, S. (2007). Time-Driven Activity-Based Costing. Harvard Business School Press.
Oracle. (2024). “Profitability and Cost Management Cloud.” oracle.com/epm
PwC. (2024). “IFRS 18 — What It Means for Preparers.” pwc.com/ifrs18
EY. (2024). “Pillar Two GloBE Rules: Implementation Considerations for Multinationals.” ey.com
Cokins, G. (2015). “Activity-Based Cost Management in the Public Sector.” Journal of Cost Management, 29(3).
