Intercompany accounting records the internal transactions between legal entities under common ownership: one LLC pays a bill that belongs to another, the holding company funds a trust, a management entity charges the others service fees.
In a corporate group, the same discipline covers transactions between a parent company and its subsidiaries; in a family office, it covers everything moving between the family's entities.
Intercompany eliminations remove that internal activity during the consolidation process, so the consolidated financial statements show only transactions with the outside world and avoid double counting.
In a family office, this is where the accounting workload concentrates. Among our multi-entity clients, 83% posted intercompany journal entries in the last 12 months, and for most offices it runs as a monthly routine.
This guide covers the mechanics: the account setup, worked journal entries, how eliminations behave in consolidation, and the specific reasons they go wrong.
Intercompany Accounting at a Glance
Term | What it means |
Intercompany transaction | Any transaction between two entities in the same structure |
Due-from account | An asset account recording what another entity owes this one |
Due-to account | A liability account recording what this entity owes another |
Counterparty | The related entity on the other side of the transaction |
Elimination | The removal of intercompany balances and activity from consolidated reports |
Upstream transaction | Activity flowing from a subsidiary entity to its parent entity |
Downstream transaction | Activity flowing from the parent entity to an entity it owns |
Account pair | A linked due-to/due-from configuration between two entities |
Why Family Offices Generate So Much Intercompany Activity
The root cause is ordinary operations. Someone pays a bill out of one entity's bank account when the expense belongs to a different entity, because of cash planning, a shortage, or convenience. The books then have to record who owes whom.
Multiply that by a structure with 10, 30, or 100 entities sharing staff, properties, and investments, and intercompany activity becomes the largest single source of journal entries in the office.
Intercompany transactions in family offices fall into five types. Ranked by how common each is across our clients with intercompany activity:
Expenses paid on another entity's behalf (83% of active clients). Shared and allocated costs are the single most common intercompany use case: one entity pays the insurance, the payroll, or the property expense, and portions belong to others.
Capital contributions and distributions (71%). Capital moving up and down the ownership chain between parents, holding companies, and the entities they own.
Entity-to-entity cash funding (47%). Straightforward transfers to cover cash needs.
Loans, notes, and advances (39%). Formal lending between family entities, tracked as due-to and due-from balances.
Management and advisory fees (24%). A management entity charging the others for service charges and cost allocations, usually monthly.
How Due-To and Due-From Accounts Work
Every intercompany balance lives in a pair of accounts: a due-from (asset) in the entity that is owed, and a due-to (liability) in the entity that owes.
Use separate due-to and due-from accounts rather than one combined contra account. We built SumIt with the accounts separated deliberately, because a single account holding both directions makes the balances impossible to trace when they stop matching. Our clients configure these as linked pairs, a median of 4 pairs per office, and each entry booked to them carries a code identifying the counterparty entity.
Worked example: one entity pays another's bill
The family's management LLC pays a $10,000 insurance bill that belongs to the Smith Family Trust. Two entries book at the same time:
In the Management LLC (the payer):
Debit: Due from Smith Family Trust, $10,000
Credit: Cash, $10,000
In the Smith Family Trust (the owner of the expense):
Debit: Insurance expense, $10,000
Credit: Due to Management LLC, $10,000
The journal entry is visible in both the entity that paid and the entity that owns the expense, the cash leaves the payer, and the two due accounts record the $10,000 obligation between the entities involved. When the trust repays, the entries reverse: cash moves, and both due accounts return to zero.
Three Booking Rules That Keep It Clean
Book both sides at the same time. The example above fails when someone books the payment in the LLC and forgets the entry in the trust. Systems that create both entries from one screen remove the main source of mismatches, and SumIt goes one step further by refusing to post an inter-entity entry whose sides do not match.
Keep the chains short. One entity paying on behalf of another, routed through a third, multiplies the entries and the error surface. Settle obligations directly between the two entities involved.
Watch the entity picker. Family structures carry many similarly named entities, especially trusts, and booking to the wrong one is one of the most common errors we see. Naming conventions that differentiate at a glance prevent it.
Document the Terms
Two intercompany types need paperwork beyond the journal entries.
An intercompany loan between family entities needs written terms: principal, interest rate, and repayment schedule. Management fees need a defensible basis for the amount charged. Tax authorities examine related-party arrangements, and documentation written when the arrangement starts supports compliance and costs far less than documentation reconstructed during an examination. Coordinate the rates and terms with your tax advisors.
How Eliminations Work in Consolidation
Elimination entries remove intercompany activity from a consolidated report. Without them, the consolidated results overstate: a $10,000 due-from in one entity and a $10,000 due-to in another would both appear on a combined balance sheet, inflating assets and liabilities by activity that, from the family's perspective, cancels out.
Worked example: the consolidated view
Continue the example above. On a consolidated balance sheet covering both entities:
The $10,000 due-from in the Management LLC and the $10,000 due-to in the trust eliminate against each other. Neither appears.
The insurance expense remains, once, in the consolidated income statement, because it is a real cost paid to an outside insurer.
Cash reflects the real combined position: $10,000 lower, in the LLC, where it actually left.
The consolidated report now describes the family's position against the outside world, which is what a consolidated balance sheet and a net worth statement exist to show. The net effect of the internal activity is zero, and the elimination process makes the accounting records say so.
An intercompany loan eliminates the same way: the receivables in the lending entity and the payable in the borrowing entity cancel on consolidation, and interest income in one entity eliminates against interest expense in the other.
Elimination entries never alter the entity ledgers, and nothing in an entity's own books gets eliminated. Each legal entity keeps its full activity in its own financial statements, because each entity still reports and files on its own.
Eliminations exist only in the consolidated financial reporting. In SumIt they apply automatically at report time, using the counterparty codes the entries already carry, so nobody books manual eliminations and nobody has to reverse them.
Why Eliminations Go Wrong
Five common challenges break eliminations, and family structures hit all of them.
Volume. High transaction volumes make manual eliminations error prone: with thousands of intercompany entries a year, tracking every one by hand guarantees misses, and every missed elimination overstates the consolidated numbers.
Layered ownership. Entity A owes Entity B, and Entity B owes Entity C. Obligations that chain across layers need each link eliminated at the right level.
Level logic. Eliminating between two entities at the same level of the structure works differently from eliminating between a parent and an entity two tiers down. Elimination treatments vary depending on the relationship, and the consolidation has to apply the right one for each.
Timing differences. Both sides should record transactions in the same period, but one entity books on time and its counterparty books late, so the two sides sit in different accounting periods and the balances stop matching at close.
Ownership percentages change. Contributions, distributions, and sales change the real ownership over time, and an elimination that was correct last quarter can be wrong this quarter.
This is also the main reason multi-entity books stop balancing at all. When offices tell us their consolidated numbers never tie, the cause traces to intercompany activity more often than to any other source.
Reconcile Before Every Close
One check catches most problems: across the whole structure, due-to and due-from balances must net to zero. Every dollar owed by one entity is a dollar owed to another, so a nonzero net means someone booked one side of a transaction and skipped the other.
When the net is off, intercompany reconciliation works at the transaction level: match the entries pair by pair, isolate the transactions missing a counterpart, document what happened, and post the correction in the period it belongs to. Transaction matching by counterparty code turns this into a filter instead of an afternoon of spreadsheet work.
Run the check before every financial close. A mismatch found in the month it happened takes minutes to fix, and the same mismatch found during the year-end audit can take days, because nobody remembers the transaction anymore.
Days-to-reconcile is worth tracking as a standing metric, because the trend tells finance teams and finance leaders whether the process is improving.
Automate the Entries, Then the Eliminations
The offices with clean intercompany books share one trait: standardized processes where the system records the transactions instead of people. Manual processes cannot keep up at these volumes.
Across our multi-entity clients, roughly 97% of inter-entity journal entries are system-generated. About 71% come from bank-feed transfer categorization, where marking a transfer between two entities' accounts creates both entries with the counterparty codes attached. Another 26% come from bill payments, where paying a bill from a different entity's account books the due-to/due-from pair automatically. Under 3% get typed by hand.
Automation at the entry level is what makes financial consolidation reliable at the report level. Entries created by the system arrive balanced and coded, so the report-time eliminations have clean inputs to work from.
How SumIt Handles Intercompany Accounting
Any pair of inter-entity accounts, configured once per counterparty. Due-to/due-from pairs are the workhorse, with separate accounts in each direction so balances stay traceable, and SumIt goes beyond them: you can link any pair of inter-entity accounts across two entities, including the equity pairs that carry contributions and distributions.
Both sides book from one action, whether the source is a bank-feed transfer, a bill payment, or a manual entry, and the system refuses to post an unbalanced inter-entity entry.
Contributions and distributions run as paired entries too. Capital moving up or down the ownership chain books in both entities at once, with the ownership percentages on the entity map keeping the equity side aligned. That coverage matters, because capital activity is the second most common intercompany type across our clients with intercompany activity, posted by 71% of them in the last 12 months.
Counterparty codes on every journal entry, which is what lets eliminations run automatically at report time on the consolidated balance sheet and the net worth statement. The coded entries ensure the elimination math ties back to the entity records, which is what accurate financial consolidation means in practice.
The entity map holds the ownership structure, including multi-tier chains and changing percentages, so the consolidation applies the right elimination treatment per relationship.
A complete audit trail on every entry: every change, who made it, and which field it touched.
Best Practices, In Short
Book both sides simultaneously, keep due-to and due-from accounts separate, settle directly instead of chaining through intermediaries, document loan terms and fee bases in writing, reconcile balances against the net-to-zero check before every close, and let the system generate the entries wherever a bank feed or bill payment can drive them.
Accounting teams that hold these habits get accurate financial statements at the entity level and accurate financial reporting at the consolidated level, which is what makes the consolidated reports usable for decision making.
If your intercompany balances never tie, schedule a demo and bring two entities that owe each other money. We will book a real transaction both ways, run the consolidation, and show you the elimination happening.
Try SumIt Today
