The accounts you inherit.

Most of what we write here assumes an institution reviewing its own book: the accounts it opened, under its own onboarding, over years it can remember. An acquisition breaks that assumption. Overnight, a portfolio you have never seen becomes a portfolio you own, and every one of its accounts was approved by a different team applying different controls with different diligence. You did not run the signup checks. You inherited the results of someone else's.

This is not a hypothetical corner case

Consolidation is putting more institutions in exactly this position. Among credit unions in particular, buying whole banks has gone from a curiosity to a steady channel. According to S&P Global Market Intelligence, credit unions announced deals to acquire 16 banks in 2025, down from a record 22 in 2024 but still high by historical standards. Each of those transactions moves a book of accounts from one institution's controls to another's. Branch purchases and credit-union-to- credit-union mergers do the same thing on their own cadence. The common thread is that the acquirer ends up responsible for accounts it never onboarded and never monitored during the years that matter most.

Why an inherited book is a distinct risk

A cultivated synthetic is a patient investment. As earlier notes describe, it is opened thin, raised over months into a creditworthy-looking customer, and only busted out once its borrowing power is maximized. That lifecycle can span years, which means an acquired book can carry synthetics at every stage of maturity: some freshly opened, some mid-cultivation, some primed and near the end. And the acquirer arrives with the worst possible vantage point for catching them.

• You did not see the origin. Provenance is read from the funding history you watched accumulate. On an inherited account, that history happened on someone else's system, under someone else's eyes.
• The controls were not yours. Whatever the selling institution did or did not do at onboarding is now baked into a book you are accountable for. Its blind spots became your blind spots the day the deal closed.
• Integration is loud. Migrations, re-numbering, and system cutovers generate exactly the kind of noise that a bust-out can hide inside. A regime break is harder to see when the whole book is changing systems at once.
• The clock does not reset. A synthetic that was two years into cultivation at the selling institution is two years in at yours. Its inflection is coming on its own schedule, not yours.

The case for a retrospective look

You cannot re-onboard a book you have already bought, and re-running identity checks would not help anyway, because a cultivated synthetic was built to pass them. What you can do is read the history you inherited the same way you would read your own: backward. The behavioral signals do not care which institution's system recorded the transactions. Provenance, coherence, ramp, inflection, and the clustering that ties accounts together are all computed from the account's own timeline, and that timeline came with the acquisition. A retrospective review is the one diligence step that can be run after the deal closes, on accounts you did not open, without needing anything the acquired data does not already contain.

Integration playbooks are usually thorough about credit quality, systems, and compliance. They are much quieter about whether the acquired book is carrying manufactured customers that will only ever surface as ordinary charge-offs, now on your ledger instead of the seller's. That gap is worth closing deliberately. An inherited book is precisely the kind of portfolio a retrospective review exists for: large, unfamiliar, opened under controls you did not set, and old enough that its history is the only place its risks are written down.