Acquisitions close on a register that fits on one slide. The data room had a tidy fixed-asset listing, the auditor signed off, the deal got done. Then comes integration, and the register multiplies.
By day 30 you find the second register — the one the operations team was actually using. By day 60, the third — a depreciation schedule maintained in Excel by the controller of a subsidiary nobody integrated cleanly last time. By day 90, the spreadsheet on the operations director’s laptop with the assets nobody’s logged in two years, the ones that show up on insurance policies and not in the GL.
This is normal. It doesn’t have to be expensive.
The four mismatches you find post-close
Across most acquisitions in asset-heavy industries, the reconciliation work concentrates in four places. Each has a predictable pattern and a predictable cost.
Missing assets. The register lists 400 pieces of equipment. The field has 437. The 37 untracked units are usually rental conversions, equipment moved between sites without paperwork, or assets the operations team treats as consumable but the GL still depreciates. Until you find them, your insurance is wrong, your maintenance is incomplete, and your write-off potential is hidden.
Phantom assets. The reverse case — the register lists assets that physically aren’t there. Stolen, scrapped, sold for parts, or disposed of by a site manager three years ago without telling finance. Each phantom asset is an open depreciation entry that hits P&L until it’s identified and written off.
Vocabulary fork. The acquired company calls it a forklift. You call it a counterbalance truck. Same physical thing, different category in the GL, different coverage in the maintenance contract, different line in the audit. Reconciliation across vocabularies is the most under-estimated cost of integration — it’s slow, semi-manual, and never finishes if you do it in spreadsheets.
Ownership ambiguity. The asset is registered to the acquired entity, on a lease originated by the parent, used at a site operated by a subsidiary. Three legal entities, three depreciation schedules, three sets of audit obligations. Untangling these post-close consumes a quarter of your finance team’s bandwidth, easily.
A 90-day playbook
The work is sequential. Each step assumes the previous one is done.
Days 1–30: Establish the source of truth. Pick one system that will hold the merged register. Not the inherited one — almost certainly not capable of absorbing a second tenancy without forking. Most acquirers default to their own ERP fixed-asset module and underestimate how much manual reconciliation that triggers.
Days 30–60: Walk the floor. Send finance to the field. Compare what’s on the floor to what’s on the register, on every site, in person, with photos. The walk catches the missing assets, the phantom assets, and the ownership ambiguities in one pass. It also gives the operations leaders confidence that finance is taking integration seriously, which earns you cooperation later.
Days 60–90: Reconcile the vocabulary. Sit the controllers, the operations leads, and the maintenance leads in one room. Map every category in the acquired register to a category in your register. Decide which version wins, asset by asset class. Write the mapping down. The mapping is the artefact that survives — every report, every audit, every future M&A leans on it.
By day 90 the merged register reflects reality, the GL has caught up, and the auditor reads from one source. The cost of getting here is consistent: 0.5–1.5% of asset book value, depending on portfolio size and how badly the acquired company tracked its estate. The cost of not getting here compounds quietly until the next audit, the next acquisition, or the next regulatory enquiry — at which point it stops being quiet.
What changes when the register can absorb the next acquisition
The 90-day playbook above is a one-time fix on a one-time event. It works. It also doesn’t scale to organizations that acquire on an annual cadence.
The structural fix is a register that doesn’t fork when the business changes shape — one where the acquired company’s vocabulary maps without rewriting history, where the merged depreciation schedule survives a restatement, and where the auditor reads the same data the operations team writes to. Velaurum was built for that pattern. The polymorphic asset model means a new asset class is a configuration change, not a release cycle. The append-only ledger means you can restate a prior period without rebuilding the dataset. The vocabulary layer means acquired companies fold in without forcing everyone onto your nomenclature.
If the reconciliation work above sounds familiar — and the prospect of doing it again next quarter sounds worse — the conversation is worth having.