A clean post-merger reconciliation runs in five stages. Teams inventory every system and report on both sides, map accounts, cost centers and product codes, run both sets of definitions in parallel, and tie out balances at conversion. Then they assign one owner to each definition so the two banks' numbers stay aligned.
Many deal plans treat data as a conversion-weekend problem. The harder part often starts after the balances move, when the same question gets two answers because each bank had its own idea of which branch, product or cost center a balance belongs to. About 181 US bank deals were announced in 2025, roughly 45% more than in 2024, according to Forvis Mazars. That means many finance teams will face this problem soon.
The first close after conversion is often where gaps surface, because it is the first time every report runs on the new structure. Serial acquirers feel it most, since each deal adds another layer of definitions on top of the last. Banks crossing an asset threshold during a deal also face new reporting at the same time.
Preql helps finance teams map both banks' definitions across their existing systems. Business owners approve each mapping, and every decision is versioned with an audit trail, so the reasons behind each call stay on record after the deal team moves on.
How long does post-merger reconciliation take?
It depends on the number of systems and how much was written down before the deal. Most of the effort sits in the map and govern stages, which continue well past conversion weekend.
Who owns it, finance or IT?
IT owns the conversion. Finance owns what the numbers mean. Reconciliation goes wrong when nobody owns the second part.
Doesn't the core vendor handle this?
The vendor converts accounts and balances. Definitions, hierarchies and report logic stay with the bank.

