Dominic Jainy stands at the forefront of the modern ERP landscape, blending deep technical proficiency in artificial intelligence and blockchain with a pragmatic approach to financial systems. As an IT professional who has navigated the complexities of Microsoft Dynamics 365 Business Central for years, he specializes in helping organizations transition from fragmented, manual processes to streamlined, multi-entity environments. His expertise is particularly relevant today as businesses face the pressure to scale rapidly through acquisitions and restructuring without losing financial integrity. In this conversation, we explore the strategic nuances of selecting intercompany solutions that not only solve today’s reconciliation headaches but also provide a robust foundation for future growth.
The following discussion examines the critical architectural decisions involved in multi-entity management, focusing on the alignment between software structure and business reality. We delve into the necessity of automating specific financial workflows, the pitfalls of relying on external spreadsheets for consolidation, and the importance of ensuring that operational modules—like warehousing and manufacturing—communicate seamlessly across entity boundaries.
When a company manages multiple entities, how do you determine if they should reside in a single Business Central company or be separated into their own distinct environments?
The decision rests entirely on your existing and projected organizational architecture, and it is vital that the software adapts to the business rather than the other way around. In my experience, entities generally fall into one of three arrangements: several entities housed within a single Business Central company, each entity operating as its own independent company, or a hybrid mix of both. For those keeping entities under one roof, dimension-based products are often the most efficient choice, whereas separate companies usually require robust intercompany add-ons because native Business Central features only cover these scenarios in part. Making the wrong choice during the discovery phase is an incredibly expensive mistake, often requiring a total re-implementation after the system has gone live. I always tell my clients to insist that vendors demonstrate their specific, complex structure during the sales cycle rather than settling for a simplified, “ideal world” demo.
Beyond just moving data from one place to another, what specific workflows should a finance team look to automate when evaluating intercompany tools?
Intercompany automation is a sophisticated dance that involves much more than just pushing a transaction through a digital pipe. You have to look at the recurring tasks that eat up your team’s time, specifically across payables, receivables, purchasing, and complex intercompany sales or drop shipments. I recommend that teams sit down and physically list every manual entry and reconciliation step they perform today to see where the friction actually lies. Some tools on the market are built to handle only a single workflow, like a basic sale between two entities, while others are comprehensive platforms designed for the full range of intercompany operations. If your team is currently buried under several different types of transactions, choosing a narrow, single-purpose tool will leave a significant portion of your labor manual and prone to error.
How can leadership distinguish between a solution that merely records transactions and one that provides true consolidated reporting and financial clarity?
Automating the transaction is really only half the battle; the real victory is achieved when the finance team has immediate access to reliable, consolidated numbers across all entities. A truly effective solution must produce both individual entity reports and full consolidated financials, while simultaneously handling eliminations to remove intercompany balances for an accurate bottom line. I’ve seen many organizations fall into the trap of treating transaction automation and reporting as two separate projects, which inevitably leads to a second, costly investment in custom reporting later on. If your month-end process still relies on export-to-Excel marathons and manual spreadsheet reconciliations, you haven’t actually solved the problem—you’ve just moved the bottleneck. You want a system where the eliminations are handled automatically so that the consolidated figures are audit-ready at a moment’s notice.
In what ways does the structure of a finance team—whether centralized or decentralized—dictate the level of control needed within an ERP system?
The “shape” of your team is a primary driver of your functional requirements, especially when it comes to security and visibility. A small, centralized team usually prioritizes shared visibility and streamlined, high-speed transactions to keep overhead low. However, a decentralized team often requires much stricter entity-level access restrictions, master data security, and the ability for entity owners to manage their own period closes and allocations. If you have a situation where certain users should not be able to see the books of a specific sister company, that’s a hard requirement, not a luxury feature. Furthermore, if you are dealing with high transaction volumes, you’ll need to look for batch processing capabilities that allow for efficiency across the entire corporate group without compromising these essential controls.
Why is it critical to look beyond the general ledger and assess how other Business Central modules integrate with an intercompany solution?
Financial requirements are often the loudest in the room, but operational requirements are what keep the business moving on a daily basis. You must verify if specialized modules like Fixed Assets, Projects, Assembly, or Advanced Warehousing need to function across your various entities. I’ve witnessed projects stall because a team assumed their manufacturing or service management data would flow seamlessly, only to find that transactions were posting to the wrong entity or remaining unassigned in a digital limbo. This creates a massive cleanup effort for the accounting team and can lead to significant operational delays. It is essential to assess financial and operational needs together as a unified strategy to ensure that a transaction in the warehouse doesn’t become a nightmare for the controller.
What strategy should a growing business employ to ensure their chosen solution remains viable as they scale and evolve?
The best strategy is to select a solution that solves your 2026 problems today without putting a ceiling on where you can go in the next few years. You have to anticipate changes like future acquisitions, a massive spike in transaction volumes, or a shift from a centralized finance model to one of entity-level ownership. I advocate for an expansion path that allows you to scale in steps, adding advanced functionality and tighter controls only as your organizational structure demands them. Buying too much complexity too early can overwhelm a team, but a solution that can’t grow will eventually force another painful and expensive software migration. Look for a partner and a platform that demonstrate a clear trajectory for handling more entities and more complex security requirements as your footprint expands.
What is your forecast for the future of multi-entity management within the Dynamics ecosystem?
I expect that by the end of 2028, the line between “intercompany” and “standard” operations will almost entirely disappear as AI-driven automation becomes the baseline. We are moving toward a reality where the system will proactively suggest eliminations and identify cross-entity discrepancies in real-time, rather than waiting for a human to find them during the month-end close. We will see blockchain-inspired immutable ledgers becoming more common for intercompany settlements to provide an absolute “source of truth” that satisfies even the most rigorous global audits. For organizations that invest in the right foundational structure now, the next two years will be defined by a shift away from manual data entry and toward a role where finance professionals act as strategic data architects.