LC
LedgerCraft
Scalability Strategy

The Multi-Entity Trap: When Separate Files Break Consolidated Reporting

Adding a second entity is easy. Reporting on it is hard. Why the "separate file" architecture of SMB software creates a permanent "Excel Gap" for growing groups.

When a business expands from a single operating company to a group structure—perhaps by opening a UK subsidiary, spinning off a holding company, or acquiring a competitor—the default reaction in the SMB accounting world is simple: "Just open another file."

In platforms like Xero or QuickBooks Online, this means creating a new subscription instance. It is quick, cheap, and initially functional. You have Entity A and Entity B, each with its own login, its own bank feeds, and its own chart of accounts.

The problem arises the moment you need to answer a simple question: "How much cash does the group have?"

The "Excel Gap" in Consolidation

Because these files are architecturally isolated databases, they do not talk to each other. To produce a consolidated Balance Sheet, your finance team must:

  1. Export the Trial Balance from Entity A to Excel.
  2. Export the Trial Balance from Entity B to Excel.
  3. Manually map the Chart of Accounts (COA) if they aren't identical.
  4. Perform currency conversion if Entity B is in GBP and Entity A is in USD.
  5. Manually calculate and post elimination entries (e.g., removing intercompany loans).

We call this the "Excel Gap." It is the manual bridge between your source of truth (the accounting software) and your decision data (the board pack). And it is where 90% of reporting errors occur.

The Intercompany Nightmare

The most dangerous risk is Intercompany Mismatch. Entity A records a "Management Fee Expense" of $10,000 paid to Entity B. Entity B records it as "Revenue." In a consolidated view, this revenue is fake—it's just moving money from left pocket to right pocket. It must be eliminated. If your consolidation is done in Excel, and someone forgets to update a formula, you might be double-counting revenue and inflating your valuation.

True Multi-Entity Architecture

As detailed in our Enterprise Selection Guide, true ERP systems (like NetSuite or Sage Intacct) handle this differently. They use a Unified Database architecture.

In a unified system, Entity A and Entity B exist as "segments" within the same database. This allows for:

  • Automated Eliminations: The system recognizes that a transaction between Entity A and Entity B is internal and automatically creates the elimination journal at the consolidation level.
  • Shared Chart of Accounts: You can enforce a global COA while allowing local variations, ensuring that "Marketing Expense" always rolls up to the same line item.
  • Real-Time FX: Currency translation happens instantly using daily rates, rather than waiting for a month-end manual spot rate calculation.
Diagram comparing Separate File Architecture vs Unified Database Architecture
Figure 1: The Consolidation Gap. Separate files (left) require a fragile manual bridge (Excel) for reporting. Unified architecture (right) handles consolidation natively.

When to Upgrade?

You don't need an ERP for two entities. But you should start planning for a migration when:

  • You have 3 or more operating entities.
  • You have entities in different currencies.
  • Your intercompany transaction volume exceeds 50 per month.
  • Your board requires a consolidated close within 5 days of month-end.

Staying on "separate files" too long creates technical debt. The cost of unwinding years of messy intercompany loans and mismatched ledgers often exceeds the first year's license fee of a proper system.