Practice Area · Governance & Controls

Corporate Escheatment Policies, Controls & Record Retention

Q: How should AP teams document voided checks older than 90 days?

Every void past 90 days should store a mandatory ERP reason code plus linked supporting artifact (reissue check/ACH reference, vendor credit memo, or duplicate-invoice cancellation) so future auditors cannot reclassify the void as escheatable.

The #1 driver of multi-hundred-thousand-dollar audit assessments is not unpaid obligations—it is missing bank reconciliations and undocumented check voids from 7 to 15 years ago.

15-Year RetentionERP Void ControlsSOX / Audit CommitteeAR Write-Off Rules

Target Retention

10–15 Years

Exceeds standard 7-yr tax retention policies

Void Safe Harbor

<= 90 Days

Structured ERP documentation for late voids

Policy Scope

AP · PR · AR · GC

Unified cross-departmental SOPs

Closing the 7-Year Tax Retention vs. 15-Year Escheatment Gap

Standard corporate document-destruction policies purge bank statements, canceled check images, and AP subledgers after 7 years to mirror IRS statute-of-limitations windows. Unfortunately, state unclaimed property lookbacks span 10 report years plus 3–5 years of dormancy—reaching back 13 to 15 transaction years.

Hamilton Ross authors comprehensive, audit-tested Corporate Unclaimed Property Policies & Procedures separating accounting-error check voids from true unresolved liabilities, banning unauthorized income write-offs of AR credits, and preserving digital reconciliation binders across ERP transitions.

Statutory Questions & Answers

How should AP teams document voided checks older than 90 days?

Every void past 90 days should store a mandatory ERP reason code plus linked supporting artifact (reissue check/ACH reference, vendor credit memo, or duplicate-invoice cancellation) so future auditors cannot reclassify the void as escheatable.