Managing a business with multiple legal entities can feel like trying to conduct an orchestra where every musician is in a different room. The standard tools in powerful ERP systems like Microsoft Dynamics 365 Business Central often treat each entity as a separate, siloed operation, creating significant friction for teams that need to work collaboratively. We’re joined today by an expert who specializes in dissolving these digital walls. With over 15 years of experience developing market-leading add-on apps for Microsoft Dynamics, his work focuses on re-architecting ERP environments to create a unified, seamless experience for complex organizations.
In our conversation, we’ll explore the practical frustrations of navigating segregated company databases and contrast that with a more integrated approach. We’ll delve into how a simple but powerful shift in thinking—using dimensions to define entities—can solve fundamental accounting challenges and unlock new efficiencies. The discussion will cover the automation of complex intercompany transactions, the power of real-time consolidated reporting without cumbersome processes, and a look ahead at the evolving landscape of multi-entity management within the Business Central ecosystem.
The article mentions that users constantly switching between companies can be “painful.” Could you walk us through a specific, time-consuming task like checking cross-company inventory in the standard setup? Then, contrast that with how your MEM app makes that process quicker and more efficient.
Absolutely, that “pain” is a very real, day-to-day headache for many users. Imagine you’re a sales representative entering a large order. The customer wants 100 units, but you only have 60 in your entity’s warehouse. In a standard Business Central setup, your process grinds to a halt. You have to save or close your order, navigate to the company switcher, select the next entity, wait for it to load, search for the item again, check its inventory, and repeat this for every single related company. It’s a clumsy, disruptive process of switching back and forth, and it completely breaks your workflow.
Now, contrast that with the multi-entity approach within a single company database. You’re on that same sales order page. Instead of switching companies, you simply glance at the “Availability by Dimension FactBox” right on your screen. It instantly displays the inventory levels for that exact item across all entities, side-by-side. You can see immediately that your production company has 200 units available. There’s no switching, no waiting, no disruption. The information is right where you need it, when you need it, turning a frustrating five-minute scavenger hunt into a five-second glance. It’s a fundamentally more efficient way to work.
You explain that DimensionPath uses Global Dimension 1 as the “Entity.” For a business considering this approach, what are the key setup steps? Please describe how your app ensures the general ledger for each entity remains balanced, even within a single company database.
The setup is conceptually elegant and powerful. The first step is to define Global Dimension 1 as your “Entity” dimension. Then, you create dimension values for each of your legal entities—let’s say “Sales Co,” “Production Co,” and “Holding Co.” This becomes the foundational tag for every transaction. From that point on, every document, every journal line, requires an Entity dimension value. This is the core of the structure.
The real magic is how the app maintains financial integrity. We’ve built logic deep into the posting routines that enforces balancing not just for the overall general ledger, but for each individual entity dimension value. Think of it like a set of virtual sub-ledgers. When you post a journal, the system checks to ensure that for “Sales Co,” the debits equal the credits. It does the same check independently for “Production Co.” If a transaction crosses entity lines, the app automatically generates the due-to and due-from entries to keep each entity’s books perfectly balanced. So, even though everyone is working in one shared database, the financial integrity of each legal entity is protected just as rigorously as if they were in completely separate companies.
The post calls centralized A/R and A/P “not really feasible” out-of-the-box. Could you share a real-world anecdote of a client’s struggle with this? Then, explain step-by-step how your app’s automatic due-to/due-from entries resolve this challenge during a cash receipt posting.
I remember one client whose accounts receivable team was spending the first three days of every month just untangling payments. They had a structure where one entity, the corporate headquarters, would receive a single large check from a customer that was meant to pay invoices across three different operating entities. In the standard system, this was a nightmare. They would have to post the cash in the headquarters company, then create complex intercompany journal entries to move the funds and manually clear the open invoices in the other two companies. It was a slow, error-prone process that created reconciliation headaches every single month.
Our Multi-Entity Management app completely transforms this. Let’s walk through that same scenario. The A/R clerk opens a single cash receipt journal in Business Central. They enter the total payment received by the headquarters entity. Then, they simply apply that payment against all the outstanding invoices, regardless of which entity they belong to. When they click “Post,” the app takes over. It automatically recognizes that invoices from the operating entities are being paid by the headquarters entity. Behind the scenes, it generates and posts the necessary due-to/due-from entries instantly. The cash is recorded correctly in the headquarters’ bank account, the invoices are closed across all entities, and the intercompany balances are perfectly updated. A multi-step, three-day reconciliation nightmare becomes a single, clean posting that takes about two minutes.
You state that with MEM, consolidated results are “readily accessible.” How does this immediate access to cross-entity reporting differ from the traditional consolidation process in Business Central? Can you give an example of a specific report that a manager can now run instantly?
The difference is night and day; it’s the difference between a static photograph and a live video feed. The traditional consolidation process in Business Central is a separate, deliberate step. You have to configure the consolidation company, import the data from each subsidiary, run the consolidation routine, and then, finally, you can run your reports. It’s a batch process that gives you a snapshot in time—what the financials looked like as of last night, or last week. It’s not a tool for real-time decision-making.
With our multi-entity approach, all the data for all entities resides in the same database, just tagged with an “Entity” dimension. This means consolidation isn’t a process you run; it’s just a filter you apply. A CFO, for example, can open a standard Business Central report like the “Trial Balance” or an “Income Statement” at any moment during the day. They can run it for a single entity, or they can simply remove the entity filter to see a live, up-to-the-minute consolidated view across the entire organization. There’s no waiting for a batch job. They can see the immediate impact of a large sale or a significant expense on the consolidated bottom line, enabling far more agile and informed management.
The article notes your app handles complex scenarios like drop-shipping from a production company to a sales company’s customer. Please elaborate on this. What specific documents does the functionality automate, and how does it handle aspects like intercompany transfer pricing in that scenario?
This is a perfect example of where the unified structure shines. Let’s trace the flow. A customer places an order with your sales company. The sales team creates a sales order and realizes the inventory should ship directly from the production company’s warehouse to save time and cost. Using our functionality, they can flag this on the sales order. This single action triggers a fully automated chain of events.
First, the system automatically creates a corresponding purchase order in the sales company, directed at the production company. Simultaneously, it generates a sales order in the production company, with the “Ship-to Address” populated with the end customer’s details. The system then uses predefined transfer pricing rules—which can be set up as a cost-plus-markup or a specific price list—to value this intercompany transaction, ensuring the profit is allocated correctly between the entities. When the production company ships the goods, the system processes the shipment and invoices the sales company. This, in turn, allows the sales company to invoice the end customer. The entire end-to-end process, from order to fulfillment and intercompany billing, is orchestrated automatically, eliminating manual data entry and ensuring all related documents are linked and accurate.
What is your forecast for multi-entity management within Business Central? Do you see Microsoft incorporating more of this functionality natively, or will specialized apps like DimensionPath always be essential for complex organizations?
I believe we’ll see a hybrid evolution. Microsoft is constantly improving the base product, and I expect they will continue to enhance the native intercompany functionalities to make them a bit smoother for simpler use cases. However, for organizations with truly intertwined operations, shared services, and complex legal structures, I’m confident that specialized apps like DimensionPath will always be essential. The level of depth required—enforcing entity-level balancing on every transaction, managing dimension-based security, automating intricate cross-entity workflows, and providing flexible transfer pricing—is a significant architectural commitment.
Platform providers like Microsoft have to build for the 80% of the market. Our focus is on perfecting the solution for the other 20%—the companies whose complexity is their reality. We can innovate faster in this specific niche, responding directly to the nuanced needs of these organizations. So, while the native tools may become more capable, the demand for powerful, dedicated multi-entity management solutions that offer a deeper, more seamless, and more robust feature set will remain strong. We’ll always be pushing the boundaries of what’s possible.