An intercompany mismatch is a discrepancy between the two sides of an internal flow: entity A and entity B do not record the same intercompany transaction in the same way. It is the single most persistent pain point of a group close, and it blocks consolidation because an intercompany elimination cannot be posted on two figures that disagree.
Six causes account for almost all of them. Timing: one entity books in period n, the other in period n+1. Amount: different fee allocations or rounding applied on each side. Foreign exchange: different rates used on the same flow. Missing mirror entry: an invoice issued but never processed by the receiving entity. Entity coding: the flow booked against the wrong counterparty in a group of ten. VAT treatment: one side gross, the other net.
The consolidation impact is direct. Unresolved items artificially inflate both revenue and costs at group level, distort intragroup margin, and get flagged systematically by auditors. The cost is rarely the accounting entry itself. It is the days spent comparing ledgers, emailing counterpart accountants and rebuilding history under close deadline.
The structural difficulty is that entities rarely share a reference. The same flow appears as an invoice number in one ERP and a free-text label in another, which is why matching by reference number fails and matching by hand does not scale beyond a handful of entities.
Phacet's intercompany flow reconciliation agent applies semantic matching rather than exact-reference logic: it recognises corresponding entries across differently structured ledgers, classifies each gap by cause, and presents mismatches as a prioritised exception list before period end. The team reviews alerts instead of hunting for them, which is what cross-entity finance control looks like in practice.
