Every group structure eventually runs into the same accounting headache. One entity sells to another. One entity charges another for shared services. One entity lends cash to another to cover a short-term gap. Each of these is a normal part of running a group business. Each one also creates two separate accounting entries, in two separate entities, that need to match perfectly before consolidated numbers mean anything.
They often do not match. A timing difference, a currency conversion applied inconsistently, a transaction recorded in one entity but missed in the other. None of these mistakes are dramatic on their own. Together, they turn month-end consolidation into a reconciliation project, one where finance spends real time tracking down mismatches instead of reviewing numbers that were already correct.
This post covers why intercompany reconciliation breaks down when it runs manually, what group entity accounting actually needs to get this right, and how intercompany elimination works when the underlying transactions stay connected from the start.
Why intercompany transactions create a reconciliation problem by design
An intercompany transaction, by definition, touches two sets of books. Entity A sells goods to Entity B, so Entity A records revenue and a receivable, while Entity B records a purchase and a payable. From a consolidated group perspective, this transaction should net to zero, since it represents money moving within the same overall business rather than a genuine external sale.
That netting only works if both sides of the transaction match exactly. The amount needs to agree. The currency conversion, if the entities operate in different currencies, needs to apply consistently on both sides. The timing needs to align, so the transaction lands in the same reporting period for both entities rather than one entity recording it a few days before the other.
When two entities record their side of a transaction independently, in separate systems or even separate instances of the same system, any small divergence between the two creates a mismatch that consolidation software cannot automatically resolve. Someone has to find it, understand which side is wrong, and correct it before the elimination entry can go through cleanly.
Where manual intercompany reconciliation actually breaks down
A handful of specific failure points show up consistently in group entity accounting run without automation.
Timing mismatches are the most common. Entity A might record a sale on the 28th of the month, while Entity B does not process the corresponding purchase until the 2nd of the following month. Individually, both entries are correct. Together, they land in different reporting periods, which means the consolidated elimination for that period will not balance until someone identifies and adjusts for the timing gap.
Currency conversion inconsistency creates a second failure point for groups operating across multiple currencies. If Entity A converts a transaction using the rate on the transaction date and Entity B converts using a rate from a different date, the two entries will not match in the group’s base currency, even though both entities recorded the transaction accurately in their own local currency.
Missed entries happen more often than most finance teams expect. A service charge, a management fee, a short-term loan between entities, gets recorded correctly on one side and simply forgotten on the other, especially when the two entities’ accounting work is handled by different people or different local teams without a shared process for confirming both sides got recorded.
Manual elimination entries introduce their own error risk. Even once a mismatch gets identified and corrected, someone still has to manually prepare the consolidation elimination entry itself, a process that depends on correctly identifying every intercompany transaction for the period and eliminating it accurately, without missing one or double-counting another.
What intercompany elimination actually requires to work cleanly
Consolidation software needs three things from intercompany transaction data to eliminate cleanly, without a manual reconciliation step standing in the way.
Matching needs to happen automatically, not through someone manually comparing two entities’ transaction lists line by line. The system needs to recognize when a transaction in one entity corresponds to a transaction in another and confirm the two sides genuinely match, in amount, currency, and timing.
Currency conversion needs to apply consistently across both sides of every intercompany transaction, using the same rate and the same conversion logic regardless of which entity recorded which side of it.
Elimination entries need to generate automatically once matched transactions confirm cleanly, rather than requiring someone to manually prepare the consolidation adjustment for every intercompany relationship each reporting period.
Why this needs to run on connected data, not connected reports
A common approach to solving intercompany reconciliation is building better reporting on top of separate entity systems, exporting transaction data from each entity and running a comparison process to catch mismatches after the fact. This helps identify problems faster than pure manual review, but it does not remove the underlying issue, that the two sides of each transaction were recorded independently in the first place, with every opportunity for a mismatch to occur before anyone catches it.
Genuine intercompany transaction software removes that gap at the source. When an intercompany transaction gets recorded, both sides post consistently because the system generates them together, from the same underlying transaction, rather than relying on two separate entities to independently record matching entries and hoping they agree. Reconciliation stops being a detective exercise after the fact and becomes unnecessary, because the two sides were never able to diverge to begin with.
Why this matters more as group structures grow
A group with two entities and occasional intercompany transactions can manage reconciliation manually without too much pain. The problem scales sharply as a group adds entities, since the number of possible intercompany relationships grows much faster than the number of entities itself. A group with three entities has three possible intercompany relationships to reconcile. A group with six entities has fifteen.
Each additional entity does not just add its own transactions to reconcile. It multiplies the number of entity pairs whose transactions need to match, which means the manual reconciliation burden grows disproportionately as a group structure expands, right at the point where finance has the least spare capacity to absorb extra manual work.
What to look for in intercompany transaction software
Not every consolidation tool that mentions intercompany functionality actually removes the manual reconciliation work. A few things are worth checking before assuming a platform solves this properly.
Both sides of an intercompany transaction should generate together from a single source, not recorded independently by each entity and reconciled afterward. Currency conversion should apply consistently across both sides automatically. Elimination entries should generate automatically once transactions confirm as matched, without requiring manual preparation each period. And the system should flag genuine exceptions, real timing gaps or missing entries, clearly and early, rather than surfacing every intercompany transaction as a potential mismatch that finance has to manually review regardless of whether it actually needs attention.
How Monesize Core approaches this
Monesize Core generates both sides of an intercompany transaction from the same underlying record, so Entity A and Entity B never independently record a version of the same transaction that could drift apart. Currency conversion applies consistently across the transaction automatically, and elimination entries generate directly from matched intercompany data rather than requiring a manual consolidation step each period.
For a group running multiple entities, that structure removes the reconciliation burden that grows disproportionately as entity count increases. Finance reviews a consolidation that was already accurate when it generated, rather than spending the days before consolidation tracking down which intercompany transaction did not match and why.
Consolidating without the reconciliation project
Intercompany reconciliation only feels like an unavoidable part of group accounting because most systems record each entity’s side of a transaction independently and leave matching them up to someone after the fact. That approach guarantees mismatches will happen, then treats catching and fixing them as the normal cost of running a group structure.
If your group is still manually reconciling intercompany transactions before every consolidation, that recurring work is worth measuring against what it would take to remove the mismatch risk at the source instead.
Automate intercompany transactions and eliminations with Monesize Core. Request a demo to see how it handles your group structure.