TL;DR
Escheatment is the legal process of turning unclaimed property, such as uncashed vendor checks and aged credit balances, over to the state after a dormancy period. Most of the pain is treated as a year-end filing problem, but the real liability is created upstream in accounts payable, when checks go uncashed and credits sit unresolved. Fixing those AP exceptions before they age into unclaimed property is where the problem is actually solved.
Key Takeaways: Escheatment requires companies to remit unclaimed property to the state after a dormancy period, or face penalties and audits. For most businesses, the unclaimed property is AP-related: uncashed vendor checks and aged, unresolved credit balances. Specialist software handles the multi-state filing and dormancy rules. What that software cannot fix is the upstream AP mess that creates the liability. Resolving those exceptions early is the highest-leverage move, and it must be auditable.
What is escheatment?
Escheatment is the legally mandated process by which a business turns over unclaimed property to the relevant state government after the property has sat dormant for a defined period, typically one to five years depending on the state and the property type. Unclaimed property is any financial asset a company owes to another party that goes uncollected: an uncashed check to a vendor, an unrefunded credit balance, an outstanding payment no one claimed. When the dormancy period passes without the rightful owner claiming it, the company is legally required to report and remit it to the state.
Unclaimed property compliance is not optional, and it is aggressively enforced. States rely on escheated property as a revenue source, and the penalties for non-compliance are real: most states charge penalties for failing to report or remit on time, many add interest, and non-compliance is a common trigger for a state audit. Because the rules differ by state and by property type, and because reporting deadlines are staggered across jurisdictions, compliance is genuinely complex for any company operating in multiple states.
Where the liability actually comes from
Here is the part that gets lost when escheatment is treated purely as a compliance-filing exercise. For most businesses outside of banking and insurance, the unclaimed property that has to be escheated is overwhelmingly accounts-payable related. It is the uncashed check a vendor never deposited. It is the credit balance that was issued but never applied or refunded. It is the duplicate payment that created an outstanding amount no one reconciled.
In other words, the escheatment liability is not created at year-end. It is created continuously, in AP, every time a payment or credit is left unresolved. The check that went uncashed six months ago and the aged credit balance sitting on a vendor account are already the beginnings of an unclaimed property obligation. They just have not aged past the dormancy threshold yet.
This reframes the problem. By the time unclaimed property reaches the filing stage, the liability already exists and the company is simply reporting it. The opportunity to actually reduce it, by finding out why that check was never cashed, resolving the aged credit, or reconciling the outstanding balance, sits much earlier, in the AP process that created it.
Two different problems: filing versus prevention
It helps to separate two distinct things that both get called “unclaimed property compliance.”
The filing problem is tracking dormancy periods across states, generating and sending the required due diligence letters to owners, preparing state-specific reports, and remitting the property on each state's deadline. This is a specialized, rules-heavy, multi-jurisdiction task, and there are purpose-built escheatment platforms and managed services (the Sovos, Trintech, and specialist providers of the world) that do exactly this. If your problem is the filing itself, that is what those tools are for.
The prevention problem is the upstream one: reducing how much unclaimed property you generate in the first place by resolving uncashed checks and aged credits before they age into a liability. This is not a filing problem, it is an AP exception problem. And it is the part the filing tools are not designed to solve, because it lives in the messy, document-heavy work of figuring out why a specific check went uncashed or what a specific aged credit actually represents.
Most companies focus on the filing problem because it has a hard deadline. But the prevention problem is where the money and the risk actually are, an uncashed check resolved is a liability that never has to be escheated, a vendor relationship kept whole, and one less item in the audit population.
Where automation fits
The prevention side is fundamentally an exception-handling problem, which is exactly the kind of work modern AI addresses. Uncashed checks and aged credits are not clean, uniform records; each one requires investigation, why was this check never cashed, is this credit still owed, was this a duplicate, has the vendor moved, and that investigation means reading documents, comparing records, and reasoning about the cause.
Automation that can read unstructured information and reason about ambiguous cases can work the aged-item backlog continuously rather than in an annual panic: identifying uncashed checks and aged credits as they approach dormancy, investigating the likely cause, reconciling them against payment and vendor records, initiating outreach to the owner where appropriate, and clearing the items that can be resolved, so only genuine unclaimed property remains to be escheated. That shrinks both the liability and the audit population before the filing step ever begins.
And because this is compliance-adjacent work with an audit on the other end, it has to be defensible. If an item was resolved, you need to show how. If a check was determined to be a genuine unclaimed liability, you need the record of the due diligence performed. Every investigation and resolution has to be transparent and produce a trail you can stand behind, which a probabilistic system that cannot explain its reasoning does not provide.
This is the frame Kognitos works on, and the scope matters. Kognitos is not an escheatment filing platform or a multi-state dormancy-rules engine, those specialist tools and services handle the state reporting and remittance. Kognitos is the reasoning-and-exception layer that works alongside your ERP, AP system, and escheatment provider: it works the upstream problem, identifying and investigating uncashed checks and aged credits, reconciling them, and resolving what can be resolved, using deterministic, English-as-code logic so every action produces a complete audit trail. The filing platform reports and remits what genuinely remains; Kognitos reduces how much genuinely remains and makes the whole population defensible. Because uncashed checks and aged credits are AP exceptions at their core, the same capability that clears AP and reconciles supplier statements is what keeps unclaimed property from quietly accumulating.
Getting started
Treat unclaimed property as an AP hygiene issue, not just a filing deadline. Before the next reporting cycle, look at the population of uncashed checks and aged credit balances that are approaching dormancy, and work them down: investigate, reconcile, and resolve what you can while the trail is still fresh and the owner is still reachable. What remains after that is genuine unclaimed property to escheat, and it will be a smaller, cleaner, more defensible population than if you had waited for the deadline to look.
For the related AP and reconciliation processes, see our guides on accounts payable automation, supplier statement reconciliation, and account reconciliation automation. To see how deterministic AI resolves the aged AP items that become unclaimed property, book a demo or try the platform.
