Post-Merger Asset Reconciliation: Combining Two Registers
How to merge two radically different fixed asset registers without losing data or triggering audit failures.
Who It's For
Financial Controllers & IT Directors
Review Level
Financial
Knowledge Layer
Post-Merger Asset Reconciliation: Combining Two Registers
Clear operational guidance designed to move from understanding into implementation.
Category
Change Management & Strategy
Section
Mergers and Acquisitions
The M&A Data Nightmare
When Company A acquires Company B, they acquire two distinct sets of data. Company A might run SAP, use 8-digit metal barcodes, and separate assets by geographic region. Company B might run Sage, use unformatted printed QR codes, and categorize assets strictly by department. Smashing these two spreadsheets together creates an immediate audit crisis.
Establishing the Parent Standard
The immediate ruling must be that the acquiring company's metadata structure wins. Company B's data must be heavily scrubbed and mapped to fit into Company A's asset class structures, useful life expectations, and depreciation rules. This is incredibly manual, but it is unavoidable.
The Go-Live Physical Baseline
You cannot trust the acquired ledger. Before migrating the acquired assets into the parent ERP, a massive wall-to-wall physical verification must be commissioned across the newly acquired sites. The organization must retag Company B's assets with Company A's branded labels, confirm the actual existence of the hardware, and build a verified, ground-truth list to carry forward into the merged balance sheet.
FEEDBACK
Was this helpful?
Tell us how this article felt in one click.
Cite this resource
If you found this documentation helpful, link to it in your internal wikis, RFP requirements, or project plans. Copied links include the full structural schema.