ERP Issues Faced by Multi-Entity Organizations

Last week, I spoke to the finance lead at a PE-backed roll-up juggling three ERPs, a dozen entities, and 5 lines of business. They were “forecasting” revenue by… guessing. Here’s what went wrong (and why “Single Source of Truth” is the big lie in fp&a): Convo Recap: Finance Lead: “Our CRM is HubSpot. Our core ERP is NetSuite. Some entities sit in Sage and QuickBooks. A couple are flat-file only.” Me: “How are you forecasting revenue across that mess?” Finance Lead: “We aren’t. It’s a high-level estimate once a year. We’d love a stage-weighted pipeline, but we don’t have the plumbing. Intercompany and FX make it worse. Dashboards don’t reflect reality.” Me: “What does “better” look like?” Finance Lead: “Live data into one model. Stage-weighted conversion by segment and rep. Headcount tied to payroll. FX drivers we control. Flexible consolidation. And no vendor telling us to file a ticket when something breaks.” My take (as a CFO who builds other people’s models for a living): We don’t have a planning problem. We have a data-flow problem. FP&A teams get sold dashboards and templates while their model, the actual, living logic of the business, is stranded in spreadsheet purgatory. Consolidation becomes a monthly scavenger hunt. And the “SST” promise collapses the moment you add one new entity, one acquisition, one CSV. It’s layers of consolidation - literally “consolidation on top of consolidation”, not a plan. FP&A should NOT be about: - Curating prettier reports of stale actuals. - Brute forcing CSV acrobatics every month. - Models built to handle one ERP, one currency, one go-to-market motion. - Waiting days for tiered support to un-break your model. FP&A SHOULD be about: - Operational + CRM + ERP data flowing live into the same forecasting logic. - Pipeline-based revenue models (stage-weighted, velocity-aware, segment-specific) you actually own. - Eliminations, FX and rollups as first-class citizens, not add-ons. - Scenario switches you can flip in the meeting, not three weeks after. We could get away with “vibe-budgeting” back when the world was simple. But in 2025, finance is asked to run: - Multi-entity consolidation with intercompany eliminations and cash impact. - Headcount plans that sync to the org chart and payroll. - Rolling re-forecasts that react to pipeline swings daily. - Board packs that tie back to GL and to the Go-To-Market math That’s not reporting. That’s an operating system. And here’s the uncomfortable truth: if your “planning platform” can’t ingest CRM, payroll, ops metrics and multiple ERPs into one model your team controls, you didn’t buy fp&a software- you bought a nicer spreadsheet. Spicy take? Maybe. Necessary? Absolutely. This is exactly why we built Pluvo: finance-owned models, live across ERP/CRM/HRIS/spreadsheets, with consolidation, FX, headcount and scenario planning in one place - so the plan isn’t a monthly project; it’s the daily source of decisions.

The Trillion-Dollar Problem No One Talks About Large enterprises often have multiple legal entities doing business with each other (e.g., US HQ billing APAC subsidiary). But when intercompany receivables and payables aren't reconciled properly, they sit like ticking time bombs — misreporting margins, bloating balance sheets, delaying audits. Real-world scenarios inside large companies: Scenario 1: “Forgotten Intercompany Invoices” Entity A sells software licenses internally to Entity B. Invoice raised ✅ Payment assumed ✅ But Entity B books the service cost without processing payment. ❌ Result: Entity A shows revenue, Entity B shows an unpaid liability. Net impact: Internal receivable aging quietly bloats over time. Problem during audits and monthly closes. Scenario 2: “Currency FX Mismatches” Entity A (USD) invoices Entity B (EURO) — but books it in local currency. By the time payment happens, FX has shifted. No one records the FX revaluation properly. ❌ Result: Internal balances don’t match—reconciliation gaps. Finance teams spend weeks explaining "noise" to auditors. Scenario 3: “Manual Settlements Go Wrong” During quarterly close, accounting manually adjusts old intercompany balances “to clean it up.” But they adjust Entity A's books without corresponding entries in Entity B. ❌ Result: Mismatch across statutory reports. One side writes off. The other side reports outstanding. Scenario 4: “M&A Entity Confusion” After an acquisition, legacy systems aren't integrated. Entity A’s receivables from Entity B (an acquired company) sit in two different ERP systems. No automated reconciliation. ❌ Result: $3M in unreconciled balances written off after external audit. The Blindspot: Nobody owns intercompany recons end-to-end because they’re “someone else's problem.” If you’re a CFO of a $1B+ company with global operations, “Are you confident every dollar owed between your entities is clean, matched, and settled?” Or are you just hoping your teams are manually offsetting it month-end? #UncoveringBlindspots #FinancialDiscrepancies #IntercompanyReconciliation #CFOPlaybook

Before I let a CFO in Dubai sign an ERP contract, I ask 7 questions about multi-currency and FX rules. (Most vendors can’t answer even 3.) And that’s exactly why 90% of ERP finance teams end up with workarounds, Excel patches, or fire drills every month-end. Here’s what I ask every single time: (1) How does the system handle revaluation gains/losses across ledgers in real-time? (Or are you manually booking journals at month-end?) (2) Can FX rates be pulled live from central banks or is it still a static upload via CSV? (3) What happens to historical FX rates when you reopen a prior-period transaction? (4) Can you tag currency exposure by project, vendor, or contract in reporting? (5) Does multi-entity consolidation auto-adjust for intercompany FX differences? (Or do you have to “explain” the ₹6.2M gap to auditors every year?) (6) How does the ERP treat rounding off in multi-currency AP/AR aging reports? (7) Does the ERP allow dual base currencies? (say, for reporting in USD and AED natively?) If your vendor can’t answer these, walk away. Because the moment your business hits scale or enters new geographies… Your ERP won’t just fail. It’ll cost you millions in lost visibility and manual firefighting. Want the full 23-question FX audit checklist I use before every ERP project? Just comment “FX Checklist” below and I’ll send it across. ♻️ 𝐑𝐄𝐏𝐎𝐒𝐓 so others can learn.

In 2016, we dropped out of Dartmouth. In 2024, we built the ERP to take down NetSuite Before, there was no money, no network. Just a study room that we made our office. Our first business: • Bootstrapped it from scratch. • Survived on oatmeal and cold brew. • Grinded for five years straight. We built every system ourselves. And eventually, scaled it to $25 million in revenue. Then came the real challenge: We decided to go bigger. We raised capital ($300 million total) a mix of equity and debt. Not because we were chasing some vision of being “funded,” but because we wanted to acquire companies and build something more durable. But raising debt is very different from raising equity. Debt investors care about one thing: Collateral. They want visibility into the business. They want reporting every week. They care about covenants. And if you miss one of those reporting obligations, it can be a breach. There’s no “we’ll fix it later.” It has to be tight. Every number, every week. And that’s exactly when our ERP became a liability. We were dealing with Brexit, regulatory changes, and localization… All while expanding into Europe. Every new acquisition brought its own entity, its own accounting, its own lender terms. What used to be a 5-entity operation was now a multinational conglomerate. And all of it had to be reported. But our ERP couldn’t keep up. We were stuck in a NetSuite implementation that was already behind schedule. We couldn’t close the books. We couldn’t get clean reports. And here’s the kicker: We chose NetSuite because we thought, “It’ll be expensive, but at least it’ll solve our problem.” That wasn’t the problem. The real cost wasn’t the invoice… The real cost was standing in front of your investors with incomplete numbers. Trying to explain why KPIs and dashboards were all you had. Trying to look like a competent operator when your own systems were broken. And when you’re acquiring companies, they want to know that you're the safe bet. That you can run their business better than they can. But when your own books aren’t closed, what does that signal? That’s when we realized our ERP was a foundational risk. A threat to our ability to raise money, acquire companies, and stay in covenant. Legacy ERPs trap you inside a system that makes every dollar of scale more dangerous. So we started building the thing we wished we had back then. DualEntry. A modern ERP that actually works for finance teams who have to move fast. That gives you real-time visibility across every account and entity. That doesn’t rely on third-party consultants just to turn the lights on. We’re doing it for the CFO with debt reporting deadlines… The controller trying to get numbers locked before the board meeting…. And the founder who just needs their company to run properly. If that’s you, follow along. We’re not here to play the SaaS game. We’re here to replace it.

���𝗻𝗵𝗲𝗿𝗶𝘁𝗲𝗱 𝗘𝗥𝗣 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 𝘄𝗲𝗿𝗲 𝗯𝘂𝗶𝗹𝘁 𝗳𝗼𝗿 𝗮 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝘆. 𝗦𝗼 𝗻𝗼𝘄 𝘄𝗵𝗮𝘁? When a new CEO steps in, one of the first surprises is how often the ERP reflects the 𝘰𝘭𝘥 𝘣𝘶𝘴𝘪𝘯𝘦𝘴𝘴 rather than 𝘵𝘩𝘦 𝘰𝘯𝘦 𝘵𝘩𝘦𝘺 𝘯𝘰𝘸 𝘯𝘦𝘦𝘥 𝘵𝘰 𝘳𝘶𝘯. It was built for a different product mix. A different scale. A different market reality. A different set of priorities. The system isn’t broken.
It’s simply aligned to a strategy the company moved on from years ago. You see it when a single-entity organization becomes multi-entity, but consolidation still happens manually. Or when a business expands internationally, yet the ERP was never configured for multi-currency or local compliance. Or when new revenue models are added, but billing and recognition rules remain stuck in the past. Or when digital processes take over, but the ERP continues to mirror outdated manual workflows. At that point, the system becomes a constraint on growth. So what do you do when the business evolves and the ERP stays where it was? Start by identifying the misalignment:  • What strategy was the system built for?  • How has the business changed since then?  • And what capabilities does the new strategy require that the current setup cannot deliver? From there, you have options.  • Reconfigure what exists.  • Turn on dormant features.  • Extend with new modules or integrations.  • Or, in rare cases, replace components that cannot scale. 𝘞𝘩𝘢𝘵 𝘺𝘰𝘶 𝘤𝘢𝘯𝘯𝘰𝘵 𝘥𝘰 𝘪𝘴 𝘦𝘹𝘦𝘤𝘶𝘵𝘦 𝘢 𝘯𝘦𝘸 𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺 𝘸𝘪𝘵𝘩 𝘢 𝘴𝘺𝘴𝘵𝘦𝘮 𝘣𝘶𝘪𝘭𝘵 𝘧𝘰𝘳 𝘵𝘩𝘦 𝘰𝘭𝘥 𝘰𝘯𝘦. Your ERP either supports your next stage of growth or slows it down. There is no middle ground. #First90Days #ERPStrategy

After 90+ data migrations, here are 3 areas to focus on when handling intercompany transactions in NetSuite. In multi-entity businesses, overlooking intercompany during migration creates a reconciliation nightmare: -Entities don’t tie out -Intercompany AP and AR are out of balance -Consolidated reports are useless -Finance spends weeks reclassifying and fixing errors And it usually surfaces during the first close when it’s too late to fix easily. If you’re migrating to NetSuite with multiple subsidiaries, intercompany isn’t optional. 1. Identify open intercompany balances before cutover. Run a clean report of all outstanding activity and make sure it reconciles before loading. 2. Map transactions cleanly, by entity. Assign the right subsidiaries and align with NetSuite’s segment structure to avoid downstream AP/AR problems. 3. Validate eliminations and consolidated reporting before Day 1. Test in a sandbox so you don’t discover issues during your first close. OptimalData Consulting has helped private equity portfolios, BioTech businesses, SaaS companies, and international firms avoid these mistakes, because once intercompany is loaded wrong, it’s much harder to fix. Have you seen intercompany trip up a migration? How did you fix it? And if your team is tackling a multi-entity migration, let’s talk.I can help you get it right the first time.