What goes wrong in the first close after a core conversion

The first close after a core conversion is where hidden mapping problems tend to show up. Balances tied out on conversion weekend, but month-end reports now run on new product codes, new GL mappings and new hierarchies for the first time. Variances appear in places nobody tested, and the close stretches while teams trace them back.

Conversion weekend gets the war room. The first close gets whoever is left. That gap is why the month after go-live can feel harder than the conversion itself.

What usually breaks

  1. Product code mapping. Old products were folded into new codes. Reports that grouped by product now group differently, so deposit and loan mix shifts on paper even though nothing changed in the business.
  2. GL feeds and accruals. Interest accruals, fee income and suspense accounts post through new feeds. Small timing differences add up across thousands of accounts.
  3. Branch and cost center rollups. Accounts moved to new branch or cost center codes. Profitability reports and allocations shift without a clear reason.
  4. Spreadsheets nobody inventoried. Analysts maintained lookup tabs that translated old codes for board and regulatory reports. Those tabs may still point at codes that no longer exist.

A checklist for the first close

  1. Run last month's key reports on the new structure before close starts, and explain every variance above your threshold.
  2. Confirm every product, branch and cost center mapping has a named owner who can answer questions during close.
  3. Reconcile core to GL by product and cost center, not just in total.
  4. Find every spreadsheet that feeds a board, regulatory or management report, and check its lookups.
  5. Keep a running log of each variance, its cause and its fix, so the second close is faster.
  6. Agree in advance which definition wins when legacy and new reports disagree.

Why it keeps happening

Conversion plans track accounts and balances. They rarely track meaning: which definition of "core deposits" the CFO's report uses, or which accounts make up "commercial real estate" for the concentration report. When meaning isn't written down, the first close becomes the place where teams rediscover it.

How Preql helps

Preql helps finance teams write down and approve the mappings between old and new definitions across their existing systems and spreadsheets. Each mapping has an owner and a version history, so the translation is recorded once instead of rebuilt every month.

FAQ

Is the first close always harder than conversion weekend?

Not always, but it is often longer. Conversion is planned and staffed. The first close inherits every mapping decision made under time pressure.

Should we freeze report changes during the first close?

Freezing new reports helps. Freezing fixes doesn't. Log every change so you can trace any number back to the definition it used.