Cleanup Fundamentals
Multi-Entity and Intercompany: Keeping Each Company’s Books Clear
When you manage more than one company, it helps to separate each company’s activity and document the transactions between them.
Most people believe multi-entity problems come from complexity. Too many entities. Too many transactions. Too much going on at once.
A common source of confusion is recording activity across companies without clearly identifying which company paid, which one benefited, and what is owed between them.
Here is how I distinguish the overall company structure from the transactions between companies, and what I look for during a review.
Multi-Entity Is About Boundaries, Not Activity
Multi-entity does not mean multiple bank accounts, locations, or revenue streams. It means more than one financial reality exists. Each entity has its own risk boundary, obligations, and balance sheet that must stand on its own.
Common signals boundaries are being ignored:
- Separate entities sharing cash without documentation
- One balance sheet making sense only when combined with another
- Activity crossing entities without a recorded obligation
How Intercompany Activity Masks Structural Failure
When intercompany behavior is not intentionally designed, the system compensates. Cash fills gaps. Clearing accounts linger. Reports appear reasonable enough to move on.
- Due To and Due From balances that never reconcile
- Expenses absorbed by one entity for simplicity
- Revenue and payroll living in different places without logic
- Loans that exist in name but behave like equity
The books look calm because the system is absorbing confusion, not because the structure is sound.
The Symmetry Test Most Files Fail
For a recorded intercompany receivable and payable, compare both companies’ records. Differences may reflect timing, missing entries, currency, or other accounting treatment; they need an explanation.
If the balances do not agree, trace the underlying activity before making an adjustment.
Why Cleanup Never Sticks
Most attempts to fix multi-entity issues focus on transactions. Reclassifications. Adjustments. Management fees added after the fact.
Transaction corrections can help, but recurring issues also need clear rules for how shared costs, transfers, and repayments are recorded.
Accuracy Should Not Depend on Memory
This is not a knowledge problem. No one should need to remember where money really belongs for the books to be correct.
A documented process, consistent account mapping, and regular review make this work easier to maintain. Supporting notes help the next person follow a transaction without relying on memory.
Final Thoughts
Multi-entity structures fail quietly when boundaries are ignored. Intercompany activity is not the problem. Uncontrolled intercompany behavior is.
Eventually, every system is forced to answer who owns what, who owes whom, and who paid for this. If the books cannot answer without explanation, the structure is already drifting.
If your books look clean but keep breaking under scrutiny, are they recording reality or compensating for missing structure?
The Complete Check reviews entity separation and intercompany activity, then recommends the next steps for the bookkeeping file.
Start the Complete Check