Unclaimed Property in Accounts Payable: AP Escheatment Guide

Unclaimed property in accounts payable arises when money your company still owes, usually from a vendor payment or credit, sits unresolved beyond the applicable dormancy period. In practice, AP teams identify dormant items from payment records, perform due diligence to contact the owner, and then report and remit the property to the appropriate state if it remains unclaimed.

For AP, your company is the holder of property owed to a vendor or other payee. The most common examples are stale-dated checks, outstanding checks, and unapplied vendor credits that were never refunded, reissued, or otherwise cleared with support. Unclaimed property in accounts payable is not just a legal concept. It is a records, controls, and documentation issue that starts inside your invoice, payment, and reconciliation data.

A practical way to think about unclaimed property accounts payable exposure is a three-step workflow:

1. Find dormant items. Review invoice, credit, and payment records for liabilities that remain unresolved after normal follow-up, especially checks that were issued but never cashed and credits that remain on vendor accounts.
2. Document due diligence. Preserve the owner details, transaction history, and outreach record needed to show you attempted to contact the vendor or payee before the item became reportable.
3. Report and remit if still unclaimed. If the property remains unresolved after the dormancy period and due diligence window, it may need to be reported and remitted to the appropriate state.

This matters because dormancy periods, due diligence requirements, and reporting deadlines vary by state, so ad hoc cleanup is not a reliable control. If AP only looks at old items once a year, you can miss owner outreach windows, lose supporting detail, and create avoidable audit exposure. Many teams refer to this work broadly as escheatment in accounts payable, but the operational risk appears much earlier, when payment data is incomplete, aging logic is inconsistent, or ownership records are hard to reconstruct.

The compliance stakes are large enough that this should not be treated as a niche back-office issue. According to the National Association of Unclaimed Property Administrators, NAUPA's FY 2024 unclaimed property report says 51 member offices reported returning $4,493,390,785 in unclaimed property during July 1, 2023 to June 30, 2024. For controllers, treasurers, AP managers, and compliance leads, that scale is a reminder that dormant AP items can become a material reporting obligation if they are not identified and worked through with defensible controls.

Which AP Items Become Reportable, and When

Not every old AP item belongs in an escheatment review. A routine open payable can be aged, disputed, or still moving through normal follow-up without creating unclaimed property exposure. The better question is whether money owed to a vendor has sat unresolved without owner activity for long enough to enter a dormancy period. Invoice age by itself is not enough. A 120-day invoice that is still in active dispute, tied to a missing receipt, or awaiting vendor correction is different from a payment or credit balance that has gone quiet and now looks abandoned.

In practice, the review population usually comes from ordinary AP reporting, not from a legal memo. Start with AP aging, your outstanding-check report, and any vendor credit balance report. If your team already uses an aging review for liability cleanup, this is where how to use an AP aging report to spot stale liabilities becomes operationally useful. From there, pull the items that look less like normal payables management and more like dormant vendor-owned funds:

• Checks issued to vendors that remain uncleared well past expected presentment windows
• Reissued or replacement checks where the audit trail is incomplete
• Voided payments where the underlying liability was never properly resolved
• Unapplied vendor credits and credit memos that have been sitting without offset or refund activity
• Other dormant balances that still represent money potentially owed to a vendor

Phrases like stale-dated checks unclaimed property and vendor credit balances unclaimed property stop being abstract compliance terms once they show up in your ERP as unresolved vendor-owned funds. The common thread is not simply age. It is the combination of an unresolved vendor entitlement, no meaningful owner response, and enough elapsed time to trigger state review.

The dates in your records tell you where each item sits in that timeline. The payment date is often the first anchor for outstanding checks because it helps establish when the dormancy clock may have started. The last contact date helps show whether the vendor took an action that may interrupt or restart the analysis, such as cashing a replacement check, confirming an address, requesting reissue, or otherwise acknowledging the funds. Void and reissue history helps separate clerical cleanup from unresolved liability: if a check was voided and reissued promptly, that may point to normal AP handling; if it was voided with no documented vendor resolution, the underlying amount may still need review.

The key control point is that dormancy periods and reportability thresholds vary by state. One universal aging rule, such as "review everything over 180 days," is not enough for AP escheatment. Your list needs jurisdiction-aware dates tied to the likely reporting state and property type, so the team can distinguish items that are merely stale from items that are approaching reportable status. That is why a strong AP review file tracks not just amount and invoice number, but also check issue date, last owner activity, void/reissue dates, vendor address, and any evidence that the liability was actually resolved.

A compact example shows how that review file works in practice:

Field	Example stale-check review item
Vendor	Midwest Industrial Supply LLC
Payment date	2025-01-15
Amount	$4,850
Last owner activity	Vendor emailed AP on 2025-02-03 asking for remittance detail, then no further response
Void or reissue history	Original check voided on 2025-09-30 after going stale; no replacement payment issued
Last known address	Texas remit-to address from the vendor master
Current status	Liability still open in AP; due diligence not yet completed
Review outcome	Keep the item in the escheatment review population until the team documents a valid resolution or completes the applicable due diligence and reporting steps

Why Voiding an Old Check Does Not Eliminate the Liability

Voiding an old check changes the payment instrument, not the underlying obligation. If your company still owes the vendor, employee, customer, or other owner, the liability usually remains on the books even after the original check is canceled. That is why stale checks often stay relevant for unclaimed property review: the paper or electronic payment may be gone, but the obligation may not be.

AP and treasury teams should separate four different actions that often get blurred together:

• Voiding cancels the original check or payment record.
• Reissuing creates a new payment instrument for the same obligation.
• Offsetting applies the amount against another valid balance, such as a documented credit or open payable.
• Resolving the liability means you can prove the owner was paid, the amount was validly netted, the obligation was extinguished under a supported business event, or the balance was otherwise cleared with defensible documentation.

Only the last step actually answers the compliance question. A void followed by nothing else can leave the same dormant amount sitting in AP, payroll clearing, vendor credits, or another suspense account. In other words, voided checks can still leave an unclaimed property liability if the owner was never paid and the balance was never legitimately cleared.

Check reissuance records matter. If a check was voided and then reissued, your file should show the full chain: original payment date and number, void date and reason, replacement check or payment reference, delivery or clearing evidence, and any vendor correspondence explaining what happened. Without that trail, an item can look resolved in one report and still appear outstanding somewhere else in the ledger. Teams doing accounts payable cleanup for old open bills and unsupported balances see this problem often because the bookkeeping entry may move, while the ownership question stays unanswered.

The operational failure is usually a handoff problem, not a policy problem. Treasury voids the check to clean up stale outstanding items. AP assumes the vendor issue is closed. No one confirms whether the vendor actually received replacement funds, whether the balance was offset to a real obligation, or whether the liability should remain open pending due diligence and reporting review. That gap is what turns routine cleanup into audit exposure.

Before you decide an item is out of scope for escheatment review, your records should support the conclusion. At minimum, keep:

• The original invoice, credit, refund, or other source creating the obligation
• The original payment record and void transaction details
• Any check reissuance history or replacement payment reference
• Proof of negotiation, receipt, offset, or other legitimate resolution
• Internal research notes explaining who reviewed the item, what was found, and why the balance was cleared or left open

If those records do not show that the obligation was truly resolved, treat the item as potentially still in scope rather than assuming the void fixed it.

What Data AP Needs for Due Diligence Letters and Audit Support

A due diligence letter is the formal outreach step that comes before reporting and remittance. In the AP escheatment workflow, its purpose is to show that your team identified a potentially abandoned payable, attempted to contact the apparent owner at the last known address, and gave that party a chance to respond before the item moved into the reporting queue. That makes an unclaimed property due diligence letter both a compliance action and an audit artifact.

For most teams, the real challenge is not generating the letter. It is proving that the letter was based on reliable records. You need enough underlying data to answer basic questions without hesitation: who was owed the money, why the amount is still open, when the payment became dormant, what address was used, and what happened after outreach.

At minimum, preserve these fields for every candidate item:

• Vendor legal name
• Last known address from the vendor master or the source transaction record
• Invoice number or credit memo reference
• Payment date, check date, or original issue date
• Outstanding amount
• Unresolved credit details, including why the credit remains unapplied or unrefunded
• Void, stop-payment, and reissue history
• Contact attempts, including dates, method, recipient, and outcome
• Jurisdiction cues from the underlying records, such as remit-to address, vendor address, entity responsible for payment, and any state indicators tied to the transaction

If you cannot trust your vendor master data, the rest of the process gets shaky fast. Due diligence letters usually need to go to the last known address, so stale vendor profiles, duplicate suppliers, outdated remit-to records, and missing legal names can create avoidable exposure. AP should be able to show which address source was used, whether it matched the transaction history, and whether the vendor record had been updated after the original payment was issued. The same discipline that supports year-end vendor payment tracking for 1099 compliance also helps here: clean payee identity data makes downstream compliance more defensible.

The hardest cases usually involve fragmented evidence. A single dormant item may require your team to piece together the invoice image, remittance detail, ERP status changes, check register entries, bank or treasury activity, and notes from prior outreach. That is why research becomes slow and error-prone. One system shows the invoice number, another shows the void date, and a third contains the only record of a reissue request or returned mail.

Treat due diligence as two linked tasks:

1. Mailing the notice: what was sent, to whom, to which address, and on what date.
2. Documenting the outcome: whether the letter was delivered, returned, ignored, or answered, and whether the item was paid, reissued, cleared, or kept in the escheatment population.

If your file does not capture both sides, you may be able to prove that a letter was generated but not that the process was actually completed. For audit support, the defensible record is not just the template. It is the full chain of evidence behind the outreach.

How State Rules Change the AP Escheatment Workflow

The hardest part of AP escheatment is that the data problem often looks the same while the compliance workflow does not. A stale vendor check, unresolved credit balance, or unapplied payment may sit in your ledger the same way regardless of location, but unclaimed property dormancy periods by state, due diligence notice rules, negative reporting rules, and filing deadlines can differ enough that there is no single universal calendar. If your company pays vendors across many jurisdictions, year-end cleanups and one-off spreadsheets usually fail because reportability depends on which state's rules attach to each item.

Useful frameworks exist, but they are not substitutes for the governing rule set. The Revised Uniform Unclaimed Property Act can help you understand common concepts, and NAUPA resources can help teams orient themselves around reporting terminology and standard holder workflows. But your actual obligations come from each state's statute, reporting portal, and filing instructions, often administered through state treasurers or other designated unclaimed property offices. Some states require negative reports or impose different due diligence timing and thresholds, while others do not, which is why how to report unclaimed property from AP is not just an accounting question. It is a state-by-state operating model.

At a high level, jurisdiction usually turns on the owner's last known address in your records. If you have a valid address for the payee or credit owner, that state often has the first claim. If you do not, the holder's state of incorporation may control as a fallback. You do not need a legal treatise to operationalize this, but you do need the right fields preserved in AP and vendor master data: payee name, address history where available, payment date, void or reissue history, credit origin, and the document trail showing why the liability is still open. Without that, ownership analysis becomes guesswork under deadline pressure.

This is also where functional ownership gets messy. AP may identify dormant items and support owner outreach. Treasury may control cash movement, check voids, and remittance support. Controllership usually owns the balance-sheet view, reconciliations, and sign-off on what remains outstanding. Tax or legal may need to review edge cases, entity structure questions, and unusual property classifications. If nobody owns the handoffs, due diligence letters go out late, state deadlines are missed, or reporting decisions are made without supportable records. Teams that already manage state-by-state AP tax compliance workflows from invoice data usually recognize the pattern: once obligations vary by jurisdiction, process discipline matters more than heroic cleanup work.

AP escheatment works best as a repeatable review calendar, not a one-time filing project. The more states you touch, the more you need consistent status fields, documented review cutoffs, and a jurisdiction-aware tracking file that shows where each item stands, from dormancy monitoring through outreach and remittance support. At minimum, that file should show the payee name, last known address, payment date, void or reissue status, dormancy review date, assigned owner, and current disposition. State variation is what turns unclaimed property from a ledger aging issue into a controls issue.

Build a Repeatable Escheatment Process From Invoice and Payment Records

A repeatable accounts payable escheatment process should run like a recurring control, not a once-a-year scramble. The goal is to move each stale item through the same sequence every cycle: identify it, confirm whether the liability is still open, gather the owner and jurisdiction facts, complete outreach, assemble reporting support, and retain enough evidence that an auditor can reconstruct what you did and why.

A practical AP escheatment workflow usually looks like this:

1. Identify candidate items from AP and payment data. Start with open credits, voided or outstanding checks, unapplied vendor balances, refund situations, and other payables that have had no valid owner activity for a meaningful period. Pull the invoice number, vendor name, payment date, check or payment reference, amount, current balance, last activity date, document type, and any ERP notes so the team is not reviewing stale balances with no context.
2. Validate that the liability is still unresolved. Before you treat an item as dormant, confirm whether it was already reissued, applied to another invoice, netted against a credit, returned to the business, or cleared through a later payment event. This is where teams often lose time because the invoice record says one thing, the ERP payment table says another, and treasury has the bank detail that explains the mismatch.
3. Enrich owner and jurisdiction data. Once an item is still open, add the fields needed for the next decision: legal payee name, last known address, tax or vendor master identifiers, supporting document source, and the state logic the team uses for review. If you cannot trace the payee or address back to source records, you are already weakening your filing support and your audit position.
4. Run due diligence and document the result. Record when outreach was triggered, what address or contact path was used, what documents supported the outreach, whether mail was returned, whether the vendor responded, and whether the item was resolved before reporting. The control is not just sending letters. It is preserving proof that outreach was evaluated and performed according to your policy.
5. Prepare the report and remittance support package. By the time the reporting team gets the file, each line should already include the amount, owner detail, dormancy support, document references, and approval history needed for final review. That reduces the common failure where controllership receives a late spreadsheet of stale checks but has to rebuild the support before the filing deadline.
6. Preserve the audit trail and feed exceptions back into the next cycle. Keep the candidate population, review notes, due diligence evidence, approvals, and final disposition in one retained package. Then log why items got stuck, missing address fields, poor void and reissue visibility, inconsistent credit-note handling, so the next review starts with better source data.

To make that workflow work, centralize four record groups:

• Source liability records: invoice images, credit notes, vendor statements, and remittance records that explain the original obligation
• Payment lifecycle records: check or ACH references, payment date, void date, stop-payment history, reissue history, and bank-clearing status
• Payee and jurisdiction records: vendor master data, address history, contact history, and entity information used for owner and state analysis
• Review evidence: ERP notes, approvals, due diligence logs, returned-mail evidence, response logs, and final disposition notes

When those records sit across PDFs, email threads, ERP comments, bank reports, and remittance attachments, every cycle turns into manual reconstruction. Invoice data extraction software for AP compliance workflows can help upstream by extracting structured data from invoices, remittance records, and related financial documents into Excel, CSV, or JSON, giving AP and controllership a usable review file with vendor, payment, and document-reference fields preserved. Used that way, it supports research and documentation. It does not determine legal escheatment obligations, dormancy rules, or state filing decisions.

Clear ownership matters just as much as data quality:

• AP owns the first-pass research on stale items, invoice support, vendor history, credit application review, and evidence that a balance is still unresolved
• Treasury owns payment-status evidence, bank-clearing detail, void and reissue history, stop-payment activity, and confirmation of whether funds actually left or returned
• Controllership or compliance owns the reporting calendar, policy interpretation, approval thresholds, final inclusion decisions, and the report support package used for filing or advisor review

That separation closes the usual handoff gaps. AP should not be guessing whether a check cleared. Treasury should not be reconstructing invoice history from scratch. Controllership should not be receiving a late, unsupported list of balances with no due diligence record behind it.

Treat escheatment as a recurring records-and-controls discipline: if you can identify dormant liabilities quickly, trace them back to source documents, prove your outreach steps, and show who approved each disposition, the annual filing cycle becomes far more defensible and far less disruptive.