Unclaimed Property Administration Software: How Do You Survive a Multi State Audit and Still Get the Money Back to Owners?

The file is not the problem. Deciding what belongs in it is.

Ask a corporate compliance lead what unclaimed property costs them and they will describe the wrong thing. They will describe the reporting: assembling files per state, generating letters, hitting the autumn deadline. That work is real and it is largely solved by tooling that already exists.

The expensive part happens earlier and nobody watches it. Somewhere in accounts payable there are uncashed cheques going back years. Payroll has terminated employees with final payments never presented. Accounts receivable carries customer credit balances that have been written off to income, which is the single most common finding in an audit. There are unredeemed rebates, customer deposits, and in the stock records unclaimed dividends and shares belonging to people the transfer agent stopped being able to reach in 2011. Those items sit in six systems with different owner keys and no shared concept of a last contact date.

Then a third party auditor arrives, usually on contingent fee, usually looking at several states at once, and asks for records going back decades. For the years where the records do not exist, they estimate, and the estimate is not built to flatter you. The defence against that is not a better reporting file. It is a documented, reproducible method for identifying property, applying dormancy and evidencing outreach, held for as long as the audit reach.

Problem one: dormancy is a rule set, and the rules disagree with each other

Dormancy periods differ by state and by property type, commonly three or five years for many categories, with plenty of exceptions and with several states having adopted revised uniform provisions while others have not. The clock does not start from a single date either: the trigger varies by property type, and owner generated activity resets it, which means what counts as contact has to be defined and captured.

Then sourcing. The priority rules established by the Supreme Court send property first to the state of the owner's last known address, and where there is no usable address, to the holder's state of incorporation. That second rule is why a company incorporated in Delaware carries exposure on every record with a bad address, regardless of where the customer lived, and why address quality is a compliance issue and not just a mailing one.

What a custom build does: hold dormancy as a versioned rules table keyed on state, property type and effective date, so a determination made in 2024 can still be reproduced in 2031 under the rules that applied at the time. Every property carries the rule version, the trigger date, the contact events considered and the resulting sourcing decision. When an auditor asks why an item was not reported in a given year, the answer is a record rather than a recollection.

Problem two: contact is an event, and nobody is recording it

Owner generated activity, a cashed cheque, a logged in session, a call to the service centre, a returned envelope, is what determines whether property is dormant. Most organisations can tell you the last transaction on an account. Very few can tell you the last time the owner did something, which is a different question and the one that matters.

What a custom build does: define contact events explicitly per property type, capture them from the systems that observe them, and store returned mail as its own event type with a date. Address status then becomes a tracked attribute rather than a guess. This is unglamorous plumbing and it is the difference between a property population you can defend and one you have reconstructed under pressure.

Problem three: due diligence has to be provable, not just performed

Most states require an attempt to reach the owner before the property is reported, with their own thresholds, windows and content requirements. Firms do the mailing. What they frequently cannot produce two years later is proof that a specific letter went to a specific address on a specific date, or the record of the response that removed the item from the report.

What a custom build does: run due diligence as campaigns with per state rule sets, generate the letters, and keep the delivery evidence, the returned mail and the owner responses linked to the property record. Responses reduce the report automatically and the reason is stored. Where a state permits electronic outreach, the same evidence discipline applies. The payoff arrives during an audit, when you can produce the outreach history for a sampled property in seconds.

Problem four: securities are a different animal

Cash property is arithmetic. Securities are not. Shares escheat, states commonly liquidate them, and years later a claimant appears and argues about what the position would be worth now. That exposure is real and it is why equity property deserves separate treatment rather than a column on a cash report.

What a custom build does: track the position, the escheatment date, what was delivered, and what the state did with it, alongside the dividend and corporate action history that preceded it. On the state administrator side, the same record supports a defensible claim decision. On the holder side, it supports the reimbursement claim you file when an owner surfaces and you make them whole.

Problem five: on the state side, paying the wrong person is the whole risk

An administrator's job is the mirror image. The property arrives from thousands of holders in inconsistent quality. A claimant appears. Now the state must decide whether this person is the owner, or the heir of a deceased owner, or the successor entity of a dissolved business, and it must decide with enough evidence that the decision survives review, while under continuous fraud pressure and political pressure to return money faster.

What a custom build does: define evidence requirements per claim type as configuration rather than as staff knowledge. An individual claim on a bank account needs one set of documents. An heir claim needs the death evidence and the relationship chain. A business claim on a dissolved entity needs successor documentation. The workflow enforces the set, records the reviewer, and stores the decision with its rationale. Proactive matching against reliable identity sources allows outbound payment programmes for the straightforward cases, which is where the political win sits, and the evidence trail is what makes those programmes safe to run.

Where the existing tools fit

Eagle Technology Management's UPExchange is widely used by holders for preparing state files and due diligence letters, and for a small or mid size holder it does the job well. Sovos offers holder compliance reporting as part of a broader regulatory portfolio. Kelmar works extensively on the state side, including systems and audit services.

The gap in all cases is the same: none of them reaches into your accounts payable, payroll, receivables and stock records to identify property with lineage back to the originating transaction, and none of them holds your dormancy determinations as versioned, reproducible decisions across a decade of audit reach. Holders buy the reporting tool and keep the identification work in spreadsheets, which is precisely where audits find their money.

What it costs and how long it takes

Across the 2,000 plus projects Digital Heroes has delivered, this category prices predictably. A holder side first release covering property identification from source ledgers with transaction lineage, the versioned dormancy rules engine, contact event capture, due diligence campaigns with evidence and state file generation runs $70,000 to $150,000 and ships in 12 to 18 weeks. A full platform adding securities property, remittance and reconciliation, holder reimbursement claims, negative reporting where required, and on the administrator side claim adjudication with evidence rules and an owner portal, runs $200,000 to $450,000 across 7 to 12 months.

What moves the number: the number of legal entities and states, since exposure is a matrix rather than a list. The number of source systems, because each ledger has its own definition of an outstanding item. Securities property, which is a distinct workstream. Whether you are under audit already, which changes priorities from prevention to evidence production. And historical loading, because the value of the system depends on how far back it can reproduce a determination.

When you should not build

A single entity holder reporting a few hundred properties a year in a handful of states should use an existing reporting tool with a written checklist and a named owner. The compliance risk is real but the cost of a custom system exceeds it. We would say so on the first call.

If your problem is purely that reporting season is chaotic, fix the process and the calendar before you fix the software. Sometimes a documented month by month schedule with owners removes most of the pain.

Build when two or more of these are true. You file across many states from several legal entities. You hold securities property. You have received an audit notice, particularly a contingent fee audit reaching back decades, because at that point evidence production becomes the priority and spreadsheets will not carry you. Your accounts receivable credit balances have historically been written off to income, which is the most common finding and the most expensive one. Or you are a state administrator whose claim backlog and fraud exposure are both growing and whose current system cannot express evidence requirements per claim type.

How to choose a developer for unclaimed property software

Ask them to draw the model: source transaction, property, owner, address with status, contact event, dormancy rule version, due diligence attempt with evidence, report submission, remittance, claim, decision, payment. If they cannot explain why the rule version has to be stored on the property, they will build something that cannot answer an audit question about a determination made six years ago.

Ask them about the priority rules and what happens to a property with no usable owner address. Anyone who has worked in this domain will bring up state of incorporation without prompting.

Ask how they handle a property that has already been reported and remitted when the owner appears at your door. Holder reimbursement is a real workflow with real money in it and it is routinely forgotten in scoping.

Ask who owns the code and put it in the contract before kickoff. You should hold the repository, the infrastructure accounts and the right to hire another firm. At Digital Heroes the client owns it from the first commit. Audit reach in this field is measured in decades, and the system that holds your determinations needs to outlive whoever built it.