•

Unclaimed Property Process for Stale Vendor Checks

Unclaimed Property Process for Stale Vendor Checks featured image
What’s in this article?

    A vendor check that remains outstanding is not automatically an unclaimed-property filing item. It is an unresolved payment that needs a controlled path: confirm its status, contact the payee, document the result, apply the rules for the relevant jurisdiction, and preserve the evidence for finance and legal review.

    Quick answer

    Use a stale vendor-check process that moves each item through Outstanding → Investigated → Payee contacted → Resolved, reissued, voided, or held for jurisdictional review → Reported/remitted where required → Reconciled → Closed. The key control is a dated case record linking the original obligation, bank status, outreach, approvals, accounting entry, and any state-specific unclaimed-property conclusion.

    What makes a vendor check stale?

    “Stale” is an operating label, not a universal legal deadline. A check may become stale under the company’s payment policy or bank terms before it reaches a state’s dormancy period for unclaimed property. Treat those as separate questions. The first asks whether the instrument can still be paid; the second asks whether a holder may have a statutory reporting and remittance duty. State rules differ, so the owner’s address, the holder’s state of incorporation, payment type, and applicable state guidance matter.

    The National Association of Unclaimed Property Administrators’ overview explains that unclaimed property is governed by state programs. Use state guidance and qualified legal or unclaimed-property advisers for the actual dormancy, due-diligence, reporting, and remittance requirements; do not substitute a generic finance checklist for those rules.

    Set the control boundary before the first follow-up

    Open a case when an issued vendor check remains unreconciled past the company’s review threshold. The process should cover the unresolved payment from the original obligation to a documented endpoint. It should not silently replace a payment cancellation decision: if payment needs to be stopped or voided, use a controlled vendor payment cancellation process with the appropriate bank, payee, and approval checks.

    Stale vendor-check control matrix

    StageOwnerRequired evidenceControl and next state
    Outstanding reviewAP analystCheck number, issue date, payee, amount, invoice or obligation, bank reconciliation statusMatch the issued item to the bank exception list. Create one case; do not re-pay merely because the original check is old.
    InvestigationAP analyst with requesterProof of service or receipt, vendor master record, dispute/credit status, duplicate-payment checkClassify as valid unpaid obligation, invalid/credited obligation, payment already settled another way, or incomplete evidence.
    Payee outreachAP or vendor ownerDated contact attempts and verified response routeAsk the payee to confirm whether payment was received, lost, returned, or needs updated delivery details. Escalate changed banking details to the vendor-change control.
    ResolutionAP approverApproval, bank action where applicable, void/reissue support, replacement-payment linkVoid, reissue, settle, or retain as an open exception. A replacement must reference the original item to prevent a duplicate.
    Jurisdictional reviewController or designated compliance ownerOwner address research, entity/incorporation record, property-type classification, state rule analysisDetermine whether and when the item enters the organization’s unclaimed-property workflow. Record the specific state rule source and conclusion.
    CloseController reviewerReconciliation, accounting entry, retention record, filing/remittance proof if applicableClose only after bank, AP subledger, general ledger, and case status agree.

    Run the investigation before changing the payable

    Start with the original obligation. Confirm who was owed, what was delivered, whether a credit or dispute exists, and whether any replacement or electronic payment already settled the same amount. That matters because a stale check can coexist with a valid liability, a duplicate payment, or an obligation that was legitimately reversed.

    Search the payment history for the invoice, supplier ID, amount, and related remittance. If a second payment was made, follow a documented duplicate-payment recovery process rather than treating the old check as a harmless artifact. Separating those paths protects both the vendor relationship and the audit trail.

    Use outreach as evidence, not just a courtesy

    Define who contacts the vendor, which approved contact data they use, how many attempts are expected, and where the results are stored. Keep copies or logs of the notice, delivery result, response, and any address correction. A new bank account or payment instruction should trigger the organization’s existing supplier-change verification; it is not proof that the original payment was never received.

    Do not promise a reissue before confirming that the original is unpaid and before the required approver has accepted the evidence. If a check is voided or a stop-payment request is appropriate, record the bank confirmation and link any replacement payment to the same case.

    Route legal requirements to the right owner

    Unclaimed-property requirements are jurisdiction-specific. The U.S. Treasury’s unclaimed assets information is useful for federal context, but businesses should consult the unclaimed-property administrator and rules for the relevant state or states. Your policy should identify the responsible legal/compliance owner, the source used for the conclusion, and the review cadence.

    Keep policy separate from law: a 90-day internal review threshold can be a sensible control, but it is not a claim about statutory dormancy. Likewise, a controller’s sign-off is a company control, not a substitute for state notice or filing obligations.

    Worked example: one outstanding $4,800 vendor check

    AP finds a $4,800 check issued to a maintenance vendor that is still outstanding in the monthly bank reconciliation. The analyst links the check to the invoice and service confirmation, finds no matching ACH payment, and opens a case. The vendor confirms its mailing address changed and says the check never arrived. After the approver confirms the bank status and authorizes the action, AP completes the required void/stop-payment steps, preserves the confirmation, and issues a replacement tied to the original check number. The old check moves to voided; the replacement remains issued until it settles; the case closes only after the bank and AP records reconcile.

    If the vendor could not be located, the same case would move to jurisdictional review—not directly to a generic “write-off.” The conclusion, timing, and notices would depend on the applicable rules and the organization’s documented analysis.

    Make the monthly review auditable

    At month end, reconcile the stale-check register to the bank reconciliation and AP subledger. Review open cases by age, amount, owner, next action date, and status. Investigate any case with no recent evidence, an unlinked replacement payment, or a mismatch between the bank and ledger. Record the reviewer, date, exceptions, and remediation.

    Useful indicators include outstanding-check count by aging band, percent of cases with documented outreach, reissue rate, duplicate-payment incidents, and cases awaiting jurisdictional review. These are operational signals—not statutory thresholds.

    Where Workhint fits

    Workhint can help finance teams build a controlled exception workflow around stale vendor checks: intake from reconciliation, role-based investigation tasks, approval routing, evidence collection, vendor outreach handoffs, exception queues, and a traceable close record. The operating model should keep legal and state-rule determinations with the appropriate accountable owner. If you are mapping an exception process across AP, treasury, and compliance, book a demo with Workhint to map the workflow and its required evidence.

    Stale vendor-check process checklist

    • Define a policy review threshold separate from statutory dormancy.
    • Match every item to the original obligation, payment record, and bank status.
    • Check for credit, dispute, duplicate, replacement, or alternate settlement before reissuing.
    • Log payee outreach and protect vendor-master changes with verification.
    • Require approval and link void, stop-payment, or reissue evidence to the original case.
    • Send unresolved cases to the designated jurisdictional-review owner with the facts and source record.
    • Close only after the bank, AP subledger, general ledger, and case record agree.

    This article is operational guidance, not legal, tax, or accounting advice. Consult qualified advisers and the applicable state authority for jurisdiction-specific unclaimed-property obligations.

    Comments

    Leave a Reply

    Your email address will not be published. Required fields are marked *


    The reCAPTCHA verification period has expired. Please reload the page.