What is multi-entity accounting? How growing companies manage expenses across multiple entities
Subject matter expert input by Daniel Vidal, Chief Strategy Officer at Expensify. Follow Daniel on LinkedIn.
When a company opens a second office in a new country, acquires a business, or separates a product line into its own legal entity, suddenly, the accounting setup that worked perfectly falls apart. And it’s not because anything is broken. It’s because it was designed for one company, and now there are two.
Key takeaways
- Multi-entity accounting means managing separate books for each legal entity while producing consolidated reports that show the full picture.
- 58% of middle market CFOs report forecasting delays caused by fragmented systems, and that number gets worse with every entity added.
- Tools built for single entities force workarounds the moment a second entity appears. Expensify's workspace model is designed so each entity operates independently from day one.
- Employees and approving managers don't need to know which entity they're working in. Expensify handles the separation invisibly.
What multi-entity accounting actually means
To understand what managing multiple entities actually means, start with the legal definition. A legal entity is a separately incorporated business with its own tax ID, bank accounts, legal obligations, and financial records. It exists independently in the eyes of the law and in the eyes of tax authorities, regulators, and auditors.
When an organization operates more than one of them, each entity needs its own bookkeeping, its own compliance structure, and its own reporting.
But the organization also needs a consolidated view of what the whole group is doing financially, not just any one part of it. That's the dual requirement at the heart of multi-entity accounting. Clean separation at the entity level, coherent rollup at the group level. Both matter, and most tools are only really built for one.
Why companies create multiple entities
The trigger is almost always growth, even if the specific reason varies. The most common ones:
Opening a country office: A new market often requires a locally incorporated entity for tax, employment, and regulatory compliance.
Acquiring another business: Acquisitions typically retain the acquired company's legal structure, at least initially.
Separating business lines: Companies isolate product lines or revenue streams for liability protection or tax efficiency.
Partnership and joint venture structures: These often require distinct entities for each component of the arrangement.
As Daniel Vidal, Expensify's Chief Strategy Officer, puts it: "When a company sets up a second entity, it's normally because a new country office is happening or various other growth reasons. Expensify is designed to make sure companies never outgrow us."
Whatever the reason, the accounting infrastructure rarely catches up as fast as the business does.
What makes it complicated
Managing multiple entities isn't just more of the same work. Each entity may operate in a different currency, under different tax rules, with a different chart of accounts and different approval structures.
The challenge is keeping each entity's records clean and separate, correctly coded, and properly attributed, while still producing a group-level view that's coherent and audit-ready.
That's a structurally different problem from running one company's books. It's also where single-entity tools stop working, sometimes without anyone noticing until everything’s a mess.
Why single-entity tools struggle when you add a second entity
Most accounting and expense software is built around one account for one company. That works… until it doesn't. The moment a second entity appears, there's no natural way to extend the existing setup. You're effectively starting over in a parallel instance, with separate logins, separate data, and no native way to see across both.
Consolidation becomes a manual job. Exporting from each system, reconciling in a spreadsheet, hoping nothing got miscoded. Every entity added makes it longer and more error-prone. That's where the forecasting problem shows up.
According to Cherry Bekaert's 2025 Middle Market CFO Survey, 58% of middle market CFOs report delays in forecasting caused by fragmented systems. That's not a technology problem in isolation. It's what happens when a company's structure outgrows the infrastructure it was built on.
The QBO and Xero limitation
QuickBooks Online and Xero are excellent tools for single-entity businesses, and they're Expensify's integration partners for companies at that scale. But both are built around a single company file. Adding a second entity means:
A second account with a separate login and subscription
No native consolidated view across both entities
Manual reconciliation whenever you need a group-level picture
That's not a flaw in the software, but a product design decision that reflects their core use case. The constraint only becomes visible when the business structure outgrows it.
Why companies typically looked to NetSuite and Sage Intacct
NetSuite and Sage Intacct were both built with accounting for multiple entities in mind. Multiple subsidiaries, intercompany transactions, consolidated reporting. These are native capabilities, not workarounds. For companies that needed full accounting consolidation across many entities, migrating to one of them made sense.
But both are enterprise software with enterprise pricing and enterprise implementation timelines. A company opening its second country office doesn't necessarily need to migrate its entire financial infrastructure to solve an expense management problem.
NetSuite and Sage Intacct also an Expensify integration partner, which matters for companies that have already made the move and need expense management to work cleanly on top of it.
The expense management layer: Where the real friction starts
The accounting consolidation problem gets a lot of attention in multi-entity discussions. What gets less attention is what has to happen before any of that consolidation is possible.
Before finance teams can consolidate anything:
Employees have to submit expenses to the right entity
Managers have to approve them through the right workflow
Expenses have to be coded to the right chart of accounts
Records have to sync to the right accounting system
If any of that goes wrong at the submission layer, the problems ripple all the way to the consolidated report. An expense coded to the wrong GL account, a receipt submitted to the wrong entity, an approval landing with the wrong manager. By the time finance catches it, the month-end close is already delayed.
This is the expense management layer, and it's where most multi-entity companies feel the pain first. It's also where the fix has to start.
As Daniel explains: "We live and breathe small and medium-sized businesses. A big part of being successful in this customer segment means never letting a company outgrow you, which means having incredible multi-entity support. This is why we've invested so much in streamlining the multi-entity setup for companies, including making sure it works well with their accounting and ERP systems."
How Expensify handles multi-entity expense management
Every Expensify member starts with one workspace. Adding a second entity means creating a second workspace, each with its own accounting integration, card connections, approval workflows, and expense policies. From the finance side, they're completely separate. From the employee and manager side, it's seamless.
As Daniel puts it, "Your combined reporting rolls up nicely and to the employees and managers approving, they never know the difference. It's all the same for them, even if they are technically using two entities at times."
Full separation where finance needs it, and no added complexity for the people who just need to submit a receipt.
One workspace per entity
Each workspace connects to its own accounting package (QuickBooks Online, NetSuite, Xero, or others), its own corporate card program, its own approval chain, and its own expense policies. No shared logins, tangled chart of accounts, or workarounds.
Here's what that looks like in practice:
| Entity A | Entity B | |
|---|---|---|
| Currency | USD | GBP |
| Accounting integration | QuickBooks Online | NetSuite |
| Approval workflow | Two-step | Custom policy |
| Card program | Separate | Separate |
| Expensify account | Same | Same |
Both live inside the same Expensify account without any crossover between them.
Combined reporting that rolls up
From the finance manager's perspective, custom financial reporting across workspaces means expenses, receipts, and approvals from every entity appear in one place, with no manual exports, reconciliation, or spreadsheet required. The entity-level data stays clean and correctly attributed. The group-level view is just there.
This is what multi-entity reporting actually looks like when the expense layer is working correctly. One consolidated picture, built from clean entity-level records, available without any manual assembly.
Invisible to employees and managers
Employees submit expenses the same way, regardless of which entity they're working in. Approving managers see the same interface. The entity-level separation (correct coding, correct accounting sync, correct workspace) happens in the background.
An employee who splits time between two entities doesn't need to know they're using two workspaces. They submit, and the right things happen in the right places. Most expense management and spend management tools don't solve for that. The complexity instead gets pushed onto the people who shouldn't have to deal with it.
When does multi-entity accounting become necessary?
The inflection point is usually obvious in hindsight. Here are some signs it's already arrived:
A second legal entity has been incorporated, or incorporation is imminent
The current expense tool requires separate logins per entity and produces no consolidated view
Month-end close involves manually combining exports from multiple systems
Employees regularly submit expenses to the wrong entity or GL code
Finance is spending time on entity attribution that the software should handle
If any of those are true, the expense management layer has already become the bottleneck. The accounting consolidation problem will only get harder to solve without fixing it first.
Multi-entity expense management doesn't have to mean starting over
Opening a second entity is a sign of growth. As such, it shouldn't also mean rebuilding the expense infrastructure from scratch, triggering an ERP migration, or asking employees to manage two separate systems.
Expensify's workspace model is designed so growing companies can add entities without adding friction. Each entity stays separate where it needs to be, and seamless everywhere else. The accounting integrations connect at the workspace level, so each entity works with whatever accounting package it needs, without touching the others.
FAQs about multi-entity accounting
-
Multi-entity accounting is the practice of managing separate financial records for two or more legal entities under the same organization, while also producing consolidated reporting that shows the group's overall financial picture. Each entity has its own chart of accounts, compliance requirements, and reporting structure.
The challenge is keeping those records clean and separate at the entity level while still being able to see across all of them at once.
-
Single-entity accounting manages the financial records of one incorporated business. Multi-entity accounting manages separate records for two or more legal entities, each with its own chart of accounts, tax obligations, and compliance requirements, while also producing consolidated reporting that shows the group's overall financial position.
-
Yes. Each entity gets its own Expensify workspace, with its own accounting integration, card program, approval workflows, and expense policies. Combined reporting rolls up across workspaces, and the entity-level separation is invisible to employees and managers. They submit expenses the same way, regardless of which entity they're working in.
-
Not necessarily. NetSuite handles multi-entity accounting at the full ERP level, which makes sense for companies with complex inter-company transactions and consolidation needs across many subsidiaries.
But the expense management layer (getting expenses submitted, approved, coded correctly, and synced to the right accounting system) can be handled by Expensify, regardless of whether the underlying accounting package is NetSuite, QBO, Xero, or something else. The two layers solve different problems.
-
Each workspace syncs independently to its own accounting integration, so entity-level data stays clean and correctly attributed. Finance managers can view expenses, receipts, and approval status across all workspaces in one place, without the manual export-and-reconcile process that fragmented setups require.
-
Multi-entity accounting is the ongoing practice of managing separate books for each legal entity. Consolidated financial statements are the output, a group-level view that combines the financials of all entities, eliminates intercompany transactions, and presents the organization as a single economic unit.
You need clean entity-level records to produce accurate consolidated statements. If the expense layer isn't getting coded correctly from the start, the consolidated view will reflect that.
