Intercompany Automation for Multi-Entity Organizations

Every multi-entity organization deals with intercompany transactions. A shared services entity bills the operating companies for IT and HR. The parent funds a subsidiary's payroll. One location buys inventory from another. A management company charges fees across the portfolio.

The accounting for these transactions is conceptually simple: when Entity A owes Entity B, Entity A records a Due To and Entity B records a Due From. When you consolidate, these balances eliminate — they're internal, not real economic obligations to outside parties.

In practice, intercompany accounting is one of the most time-consuming and error-prone parts of the month-end close for any organization with more than two entities.

Why intercompany breaks down manually

The core problem is bilateral. Every intercompany transaction touches two sets of books. If Entity A records a $50,000 management fee payable to HQ, then HQ needs to record a $50,000 management fee receivable from Entity A. Both sides need to agree on the amount, the period, and the account coding. If they don't match, the elimination won't be clean, and the consolidated financials will be off.

In a manual process — spreadsheets, emails, shared drives — mismatches are the norm, not the exception:

Entity A posts the charge in March; Entity B doesn't record the receivable until April.
Entity A codes it to management fees; Entity B codes it to consulting expense.
Entity A records $50,000; Entity B records $48,500 because they applied a different allocation methodology.

Each mismatch requires investigation: pull the trial balances, compare the IC accounts line by line, identify the differences, determine which side is correct, draft correcting entries, get both controllers to sign off. Multiply this by every entity pair in the network, every month, and you have a process that can consume days of close time. It's the same kind of version-control failure that breaks Excel at any scale — just with more parties.

The matrix problem

For organizations with more than three or four entities, the number of possible intercompany relationships grows geometrically:

Four entities = 12 possible directional relationships
Eight entities = 56
A PE platform with fifteen portfolio companies plus a management company = 240 possible IC pairings

Nobody is going to reconcile 240 relationships manually every month. So what happens in practice is that teams only reconcile the "big" relationships — the ones they know have activity. Small balances accumulate unreconciled. Over time, the immaterial differences become material. The year-end consolidation takes a week longer than it should because someone has to untangle twelve months of accumulated IC drift.

A matrix view — showing every entity on both axes with the outstanding balances at each intersection — makes the full picture visible at a glance. You can see not just the total IC exposure but exactly which pairs are out of balance and by how much.

Elimination entries are mechanical but tedious

Once the IC balances are reconciled, generating the elimination entries for consolidation is straightforward accounting. You debit the Due From, credit the Due To, and the balances net to zero in the consolidated trial balance. If there are IC revenue and expense transactions, those eliminate too.

The problem isn't the accounting — it's the volume and the repetition. Every IC pair with a balance needs an elimination entry. Every period. And if you're consolidating monthly (as most PE-backed companies do for investor reporting), that's twelve times a year, times however many active IC pairs you have.

In a spreadsheet, this means maintaining an elimination template that references the IC schedules, updating it every month, verifying it ties to the trial balances, and posting the entries manually. It works, but it's exactly the kind of repetitive, high-accuracy-required task that shouldn't be done by hand.

What PE sponsors and banks actually need

Private equity firms and lenders don't just want consolidated financials. They want clean consolidated financials with a transparent IC layer.

When a PE firm acquires a platform and starts bolting on add-ons, every acquisition increases the IC complexity. The management company charges fees. Shared services get allocated. Entities lend to each other. The sponsor needs to see the consolidated view (for investor reporting), the entity-level view (for operational performance), and the IC layer in between (to understand the true economics at each entity).

Banks running covenant calculations on a consolidated basis need to verify that IC transactions aren't inflating revenue or obscuring leverage. A clean IC reconciliation — with matching balances on both sides and full elimination entries — gives them confidence in the consolidated numbers.

If your IC process is a mess of spreadsheets with unreconciled differences and manual eliminations, the quarterly reporting cycle becomes an exercise in cleaning up the IC layer rather than analyzing the business.

System-generated IC entries change the workflow

The alternative to manual IC reconciliation is a system where IC entries are generated from pre-configured relationships rather than recorded independently by each entity.

Define the relationship once: Entity A pays a 3% management fee to HQ based on revenue. The system reads Entity A's revenue, calculates the fee, and generates matching entries on both sides — the payable at Entity A and the receivable at HQ. Same amount, same period, same coding. No bilateral coordination needed.

For cost allocations — IT, insurance, shared office space — define the allocation methodology (headcount, square footage, revenue, equal split) and the system distributes the cost across entities with matching entries on each side.

The elimination entries become automatic: wherever the system generated a Due To, it generates the offsetting elimination. The consolidated view always nets to zero because the entries were created in pairs from the start.

This doesn't mean the controller is out of the loop. Every generated entry flows through an approval queue. The controller reviews the IC entries alongside lease amortization, depreciation, and every other scheduled entry — one queue, one review, one approval cycle. The difference is that the entries arriving in the queue are already matched and balanced, not raw journal entries that need to be reconciled against a counterparty.

The consolidation payoff

When IC is clean and systematic, the consolidation itself becomes trivial. Pull the entity trial balances, apply the elimination entries, and the consolidated financials are ready. No week-long reconciliation process. No unexplained differences in the eliminations column. No last-minute correcting entries that push back the reporting deadline.

For organizations reporting to PE sponsors on a monthly basis, this is the difference between getting the reporting package out by the 15th and getting it out by the 10th. Five days that the sponsor notices, and five days that the CFO can spend on analysis rather than data cleanup.

Stop fighting your eliminations. Start owning the close.

AccelClose includes a full intercompany module with Due To / Due From matrix tracking, system-generated IC entries from pre-configured relationships, and automatic elimination entries for consolidated reporting — and posts to QuickBooks Online, NetSuite, Sage Intacct, Xero, or Dynamics 365.

Try the interactive demo free → No signup. No credit card.

Sean Mintz is the founder of AccelClose. He spent years closing books for PE-backed multi-entity platforms before building the platform he wishes he'd had then. More about Sean →