Your New ERP System May Have Created a Problem Nobody Noticed π¨
By Josiah S. Osibodu, CPA, CFE, Certified AI Consultant | 5-minute read
Companies spend millions upgrading their business systems.
The goal is always the same. Better controls. Cleaner data. Stronger reporting.
And usually β it works exactly as planned.
But there is a side effect almost nobody catches during implementation.
A quiet, compounding unclaimed property exposure that builds in the background for years.
Until a state regulator asks for records that no longer exist. β οΈ
π How Does This Happen?
A system upgrade is an enormously complex project.
The teams involved are focused on the things that matter most β data migration, financial reporting, payroll integration, procurement workflows, and keeping the business running through the transition.
That focus is appropriate. But it leaves one question almost completely unasked:
“What happened to our unclaimed property controls when the system changed?”
That question almost always comes later.
Much later.
π Five Places Where the Risk Quietly Appears
1. Dormancy tracking disappears
Older systems often contain custom logic β aging flags, inactivity alerts, balance review triggers. That logic was built over years to catch reportable items before they became a problem.
During migration, those settings frequently do not make it into the new system.
Nobody notices. And reportable balances keep aging. Undetected and unreported.
2. Customer credits get reclassified
During account restructuring and data cleanup, customer credits are sometimes moved into miscellaneous liabilities, suspense accounts, or simply written off.
Operationally, it makes sense.
From an unclaimed property perspective β those balances may still be reportable. The reclassification does not make the obligation disappear.
3. Historical records go missing
System conversions are often guided by a practical question: what data do we actually need going forward?
The problem is that unclaimed property frequently depends on historical support. Owner data, original transaction details, prior filing documentation. If those records did not survive the migration, your ability to defend your compliance position weakens significantly.
4. Vendor and payroll data become fragmented
After a migration, data often lives across multiple systems β a legacy database here, an integration gap there, a workaround that never got fully resolved.
Without a single reliable source of truth, identifying dormant items consistently becomes nearly impossible. π
5. Write-off documentation gets lost
Many finance teams assume that a write-off ends the story.
States see it differently. If a balance was written off and the company cannot explain why β with documentation that holds up under review β that old item can reappear as an estimated liability in an audit.
π Why Delaware Makes This Even More Urgent
Here is the dimension most teams overlook entirely.
When owner address information is missing or incomplete, Delaware (or the holderβs state of incorporation) can step in as the default claimant state β even if the company never operated there.
That means data quality problems created by a system migration can translate directly into Delaware exposure.
And right now, Delaware is actively reaching out to companies with voluntary disclosure invitation letters. The message is direct: companies are expected to know their exposure and be ready to defend their position.
If your migration created gaps in owner data β you may already have a Delaware problem. β οΈ
π‘ The Real Issue Is Not the Technology
The system itself is not the problem.
The problem is the assumptions that get made during implementation.
Teams assume the data migrated cleanly. They assume the dormancy logic is still working. They assume the historical records are intact. They assume the compliance trail survived.
Those assumptions are often wrong.
And when they are wrong, audits get expensive.
π― Seven Questions Every CFO Should Ask After a System Migration
Before the next audit cycle, these seven questions deserve honest answers:
1. Did dormancy tracking logic survive the migration β or was it quietly left behind?
2. Were any customer credits reclassified during the data cleanup?
3. Is owner address data complete and accessible across all property types?
4. Are historical write-offs still documented with enough support to explain them to a state?
5. Did payroll integrations preserve records of inactive balances and uncashed items?
6. Do aging reports still flag reportable items the way they did before the migration?
7. Would your records hold up under a Delaware review today?
If any of those answers are unclear β the exposure may already be building.
π The Bottom Line
A system upgrade can improve almost every dimension of your business operations.
But it can also quietly undermine your unclaimed property defensibility β one workflow change, one data field, one reasonable assumption at a time.
The real measure of a successful migration is not whether the system went live on schedule. It is whether your compliance trail survived the transition.
The smartest finance teams are not just asking “Did implementation go well?”
They are asking: “Did implementation quietly create risk?”
That question is worth asking before a state asks it for you.
π Your Next Step
Find out whether your ERP migration created unclaimed property exposure β before a regulator does.
β Free 5-minute qualitative risk assessment: EscheatAnalyzer.ai β instant results, no cost, no generic advice, no manual review delays.
β Free 60-minute consultation: moyerosibodu.com
β FREQUENTLY ASKED QUESTIONS
When a company moves to a new business system, several things can go wrong for unclaimed property compliance without anyone realizing it. Dormancy tracking logic built into the old system may not transfer. Customer credit balances may be reclassified in ways that hide their reportability. Historical owner data and transaction records may be lost or fragmented. Write-off documentation may disappear entirely. Each of these gaps weakens the company’s ability to identify, report, and defend its unclaimed property position – sometimes for years before the problem becomes visible.
Five categories of data are most commonly affected. First, dormancy tracking logic – the aging flags and inactivity rules that identify reportable balances. Second, customer credit balances that may be reclassified during account cleanup. Third, historical owner address data needed to determine which state has jurisdiction. Fourth, write-off documentation that explains why specific balances were removed from the books. Fifth, vendor and payroll records that track dormant items across the organization. If any of these are lost or altered during migration, unclaimed property compliance becomes harder to maintain and defend.
Delaware can become the default claimant state for unclaimed property whenever a company holds funds but owner address information is missing or unavailable. This is called the secondary escheat rule. When an ERP migration destroys or fragments owner address data, it can inadvertently create Delaware exposure even for companies that had clean records before the migration. Delaware is currently actively reaching out to companies through voluntary disclosure invitation letters, making this risk particularly immediate for organizations with recent system changes.
It is neither entirely and both partially. The technical execution belongs to IT, but the compliance consequences belong to finance, legal, and risk leadership. The problem typically falls through the gap between departments – IT considers the migration complete when the system goes live, while finance focuses on reporting accuracy and compliance focuses on annual filings. Nobody owns the intersection where unclaimed property controls live. That ownership gap is exactly where hidden exposure grows.
Seven questions help identify whether an ERP migration created unclaimed property risk. First, did dormancy tracking logic survive the migration? Second, were customer credits reclassified during data cleanup? Third, is owner address data complete across all property types? Fourth, are historical write-offs documented with enough support to explain them to a state auditor? Fifth, did payroll integrations preserve records of inactive balances? Sixth, do aging reports still flag reportable items correctly? Seventh, would the company’s current records hold up under a Delaware review? Unclear answers to any of these questions suggest hidden exposure.
The Escheat Risk Analyzer at EscheatAnalyzer.ai provides a free, 5-minute qualitative risk assessment that evaluates your organization across four risk dimensions – Jurisdictional, Compliance History, Transaction/Revenue, and Operational Complexity. It is specifically designed to help finance leaders identify where unclaimed property controls may have been weakened by system changes, data migrations, or operational restructuring. Instant results, no cost, Β no manual review delays.
