A Day in the Life of a Multi-Entity Controller Running Three Sets of Books
A composite, not a specific company — the multi-entity close pattern we hear about constantly, just multiplied by three.
Like the other field notes pieces, this is a composite pattern, not a specific company — but it's an especially common one for anyone running finance across a parent company and a couple of subsidiaries or related entities.
The morning starts with three logins
Each entity has its own accounting file, sometimes its own system entirely. Checking on outstanding invoices means logging into three separate places, because there's no single combined view — just three parallel versions of the same kind of question, answered separately every time.
An intercompany invoice that has to agree with itself
One entity bills another for shared services. That invoice has to be recorded correctly on both sides — as a payable on one, a receivable on the other — and the two records have to actually match for consolidation to work. When they don't, which happens more often than anyone would like, finding the mismatch means comparing two separate sets of books line by line.
Approval chasing, times three
The same approver often signs off across all three entities, which means the same person is the bottleneck for every entity's AP at once. A single day of being unavailable doesn't stall one company's payments — it stalls three.
Close weekend, but multiplied
Month-end close isn't one close — it's three closes that have to happen in roughly the same window, plus a consolidation step that only works once all three are actually done and reconciled with each other. A discrepancy discovered in the consolidation step means going back into whichever entity's books it came from, re-tracing the same reconciliation work already done once that month.
Why this consistently takes longer than it should
None of this is a sign of a poorly run finance function — it's what happens when tools built for a single entity get stretched across several, without anything actually designed for the intercompany layer connecting them. The work that should take three times as long because there's three times as much of it ends up taking more than that, because of the reconciliation between entities on top.
How Vyomiyra helps
Vyomiyra keeps invoice and approval workflow entity-aware, so intercompany items are flagged as such from intake rather than discovered as a mismatch during consolidation — and approval routing accounts for which entity's rules actually apply, automatically.