Intercompany Reconciliation: Why the Numbers Never Quite Match

If you run more than one entity, you already know the quiet dread of intercompany accounts. Entity A lends money to Entity B. Entity B pays a vendor invoice on Entity A’s behalf. Someone allocates shared payroll. By the end of the quarter, the “due to” balance on one set of books is supposed to mirror the “due from” balance on the other — and it almost never does.

A missing $4,200 between two of your own companies isn’t fraud. It’s a timing difference, a one-sided entry, or a transaction someone booked in one place and forgot in the other. But you can’t close clean until you find it, and finding it usually means exporting two general ledgers and eyeballing them line by line.

Why intercompany balances drift

The problem is structural, not sloppy. Each entity keeps its own books, often in its own QuickBooks company file. There’s no shared ledger enforcing that a credit in one place creates a matching debit in the other. So the two sides can drift apart in ordinary ways:

• A reimbursement gets recorded by the paying entity but not by the receiving one.
• The same transaction lands in two different periods.
• Someone books the amount to a slightly different account.
• A transfer gets entered twice on one side.

Each of these is small. The trouble is they accumulate silently, and you only discover them when the consolidated numbers don’t foot — usually late, usually under deadline.

What automated intercompany reconciliation actually does

Flying Ledger runs intercompany reconciliation across your entities: it confirms that what one entity owes another matches on both sides of the books, and flags it when it doesn’t. Instead of you diffing two ledgers by hand, the platform checks both sides and tells you exactly where they diverge.

That matters because the work isn’t in fixing the discrepancy — that part is usually a two-minute journal entry. The work is in finding it. Automated reconciliation collapses the hunt so you’re left with the decision, not the search. It’s the same shift we’ve written about in From Data Entry to Decision-Making: let the software do the matching so your people do the judging.

This is only possible because the underlying data is already connected. Flying Ledger connects QuickBooks per entity and keeps that data synced automatically, so reconciliation runs against live books rather than a stale export you pulled last Tuesday.

It’s one piece of a cleaner close

Intercompany reconciliation rarely lives alone. The same messy books that hide a mismatched intercompany balance also hide duplicate vendor names, unreconciled POS revenue, and open bills scattered across entities. Flying Ledger tackles those alongside it — cleaning up vendor names so you can see every open bill by who it’s really owed to, and reconciling daily point-of-sale revenue against what the POS system itself reports.

When those checks run continuously instead of once a month, the close stops being an event you brace for. That’s the whole idea behind closing the books without the all-nighter: the reconciliations that used to pile up at month-end are handled as you go, and the exceptions surface early enough to fix calmly.

See it across the whole portfolio

Once your entities reconcile against each other, the consolidated view you build on top actually means something. The CFO Dashboard shows cash, debt, revenue, net income and accounts payable across every entity in your portfolio, with drill-down into any number. A consolidated figure is only trustworthy when the pieces underneath it tie out — and intercompany reconciliation is a big part of making sure they do.

If you’ve ever spent an afternoon chasing a few hundred dollars between two of your own companies, you know why this is worth automating. It’s not about the dollars. It’s about being able to trust the number without re-checking it every time.

Flying Ledger is in active use today with real customer data and isn’t yet open to external users. If matching intercompany balances is eating your close, this is the kind of problem it’s built to end.