Agentic Escheatment and Unclaimed-Property Compliance: Catching Dormant Liabilities Before the Filing Deadline
written by Cooter:Labs
published on September 28, 2026
Introduction
Every company's books quietly accumulate liabilities nobody is actively managing: a payroll check that never got cashed, a vendor refund that bounced back to a closed mailing address, a customer credit memo issued against an invoice that was later paid in full some other way. None of it is fraud and none of it is an accounting error in the usual sense — the money is real, it's just sitting on the balance sheet owed to someone who hasn't claimed it. Every U.S. state (and most Canadian provinces) has an escheatment law that says this can't sit forever: once a liability crosses a state-defined dormancy period with no owner activity, the holder is legally required to attempt to contact the owner, then report and remit the balance to the state as custodian. Most ERPs have no native concept of any of this. Uncashed checks live in the bank reconciliation module until someone voids them; unapplied credits live in AR aging; the actual escheatment obligation — which items are dormant, under which state's rules, and whether the required owner notice has gone out — usually lives in a spreadsheet someone updates once a year under deadline pressure, if it's tracked at all.
The failure mode here isn't just under-reporting. States audit holders specifically for unclaimed property, the look-back periods in an audit can run a decade or more, and the penalties and interest compound per state, per property, per year missed. But the opposite mistake — a blanket "write off anything two years old" macro — is just as dangerous, because dormancy periods, property-type definitions, and required due-diligence steps genuinely differ by state and by property type, and getting the state wrong means escheating money to the wrong custodian entirely. Reliable compliance means tracking each liability's real dormancy status under the rules that actually apply to it, not applying one rule everywhere.
The agent's starting point is every open item that represents money owed to an external party and not yet paid out or claimed: uncashed AP and payroll checks past their stale-date, unapplied customer credit memos, unclaimed refunds, and unredeemed deposits. For each one it pulls the actual last-activity date as the applicable state's rules define it — for some property types that's the check's issue date, for others it's the date of the last confirmed contact with the owner, a returned-mail event, or a payment that was reissued and then itself went stale. This means reading actual bank-clearing status and correspondence history out of the ERP rather than treating every item's age the same way regardless of what triggered dormancy for that specific property type.
Unclaimed property escheats first to the state of the owner's last known address on the holder's own books, and only falls back to the holder's state of incorporation when no address is on record at all — this is the priority rule set by the U.S. Supreme Court in Texas v. New Jersey, and every state's statute follows it. The agent applies this per property using the address actually associated with the vendor, employee, or customer record as of the last activity date, not the company's current default mailing state, because dormancy periods and dollar thresholds for the same property type can differ meaningfully state to state, and applying the wrong state's period can make a genuinely dormant item look current, or vice versa.
Above a state-set dollar threshold, holders are legally required to mail an owner-notification letter within a specific window ahead of the annual filing, in language many states specify, and to keep proof it was sent. The agent generates that letter using the applicable state's required content and timing per property, logs when it went out, and — this is the part a static spreadsheet process usually misses — treats any owner response as a dormancy reset: a returned check that gets reissued and cashed, a corrected address, a customer confirming they're aware of an old credit, all pull that item out of the current filing instead of it escheating to the state when the owner was, in fact, findable.
A meaningful share of states exempt certain business-to-business transactions, gift cards, or specific property types from reporting entirely, and those exemptions aren't uniform. The agent checks each dormant item against a jurisdiction-and-property-type exemption table before it's added to a state's report, and a property type or holder relationship the table doesn't yet cover is flagged for a person to classify and add, rather than silently defaulting to "reportable" or "exempt" either way — an unreviewed default in either direction is how a company either over-reports money it didn't have to remit or under-reports and builds real audit exposure.
Once outreach windows close, the agent aggregates the remaining unclaimed items by state and by the NAUPA standard property-type code most states use for electronic filing, and totals each state's remittance. Before that report goes anywhere, it reconciles the aggregated total against the actual GL balance in the liability accounts those items came from — a mismatch between what the report says is being remitted and what the books actually show for those accounts is exactly the kind of discrepancy an auditor looks for first, and catching it here means a person resolves the reconciling item before filing, not after a state's examiner does.
Looking Ahead: Challenges and Innovations
The rules genuinely conflict across states, and they change
Dormancy periods, property-type codes, reporting deadlines, and B2B exemptions aren't a single national standard — they're fifty-plus separate statutes that get amended on their own schedules, and a jurisdiction table that was correct last filing season can be wrong this one. The agent can apply whatever table it's given consistently, but someone still has to own keeping that table current; treating it as a one-time setup rather than a maintained compliance artifact is how a company quietly drifts out of compliance in a state that changed its rules eighteen months ago without anyone noticing.
A 'found' owner still needs a human to actually resolve the payment, not just an address match
When due-diligence outreach gets a response, reissuing money to the person who replied isn't something the agent should finish on its own — verifying that the respondent is actually the rightful owner, updating banking or mailing details safely, and clearing the reissued payment through normal controls is deliberately still a person's job, for the same reason vendor banking-detail changes get a human sign-off elsewhere in AP: a due-diligence letter is also exactly the kind of official-looking correspondence a bad actor could try to intercept or spoof a response to.
Turning this on for the first time surfaces years of exposure the agent can't retroactively fix
The first time a company builds real dormancy tracking, it usually finds liabilities that have been sitting unreported for years — the agent's job is to surface that historical exposure accurately, not to decide how to handle it. Filing every back year directly versus pursuing a state's voluntary disclosure program, which can limit the look-back period and waive penalties in exchange for coming forward, is a legal and treasury decision with real tradeoffs the agent isn't positioned to make; it hands over a clean, dated inventory of what's outstanding and leaves the filing strategy to the people who own that decision.
The metaverse
Unclaimed-property reporting is slowly moving off flat-file uploads and toward direct electronic exchange — a handful of states already run online holder portals with structured submission and status tracking, and NAUPA's own standard formats keep pushing toward more machine-readable exchange rather than a PDF a person re-keys. As more states get there, the next step for agentic compliance isn't just producing a correct file for a person to upload — it's submitting and reconciling directly against a state portal's own record of what it received. The more durable shift, though, is upstream: catching a bad mailing address or a check about to go stale at the moment it's issued, using the same signals a due-diligence letter uses months later, so fewer liabilities become dormant in the first place instead of just being reported faster once they do.
Conclusion
Escheatment compliance fails quietly in both directions — miss it and a decade-long state audit finds real exposure with real penalties attached; automate it carelessly and a blanket write-off rule escheats money to the wrong state or skips a legally required owner notice entirely. An agent that tracks each liability's real dormancy trigger, applies the actual state whose rules govern it, runs the required due-diligence outreach and honors a response when one comes back, and reconciles the final report against the GL before it files, turns a once-a-year scramble into a maintained, auditable process. It doesn't decide exemption edge cases on its own, doesn't resolve a found owner's payment without a person checking it, and doesn't decide how to handle exposure a company is only now discovering — those stay judgment calls for the people who own the risk, which is exactly where they should stay.
Share this post:
Curious what this means for your business?
Get a personalized ROI estimate, or book a free discovery workshop with our team.