Finance Index
How long must AP records be retained, and what happens across system migrations?
Reference guide to records retention system migrations, including ERP workflow, integration points, data sync, controls, and finance-system tradeoffs.
AP records - invoices, approvals, payment support, 1099s - generally must be kept long enough to satisfy IRS rules (commonly at least the standard examination window, longer for some situations) and your audit and contractual requirements; many organizations standardize on seven years for tax-relevant records, longer where statute or industry demands. The migration trap is decommissioning a system without preserving accessible, authentic records - auditors will ask for three-year-old invoices that lived in the system you just turned off.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| How long must AP records | AP records - invoices, approvals, payment support, 1099s - generally must be kept long enough to satisfy IRS rules (commonly at least the standard examination window, longer for some situations) and your audit and contractual requirements. | Keeps evidence clear and reduces control risk. |
| Approval path | You need them extracted in usable formats with their authenticity provable later - meaning the invoice image plus the approval chain and timestamps, not just a balance. | Keeps work moving without losing accountability. |
| Audit evidence | Scanned/electronic invoices are acceptable to the IRS when they're complete, legible, accurately reflect the original, and are retained in a system that preserves them and can reproduce them - with the supporting trail (approval, payment) intact. | Keeps evidence clear and reduces control risk. |
| How long must AP | Retention is driven by IRS examination windows (generally at least three years, extended in cases of substantial understatement or fraud), plus audit, lender, and contractual requirements. | Keeps evidence clear and reduces control risk. |
| What should I demand | Up-front data-egress terms: you own your data, you can export invoices, images, coding, and the audit trail in usable formats, the timeline and any cost of egress at contract end, and that the vendor cooperates with extraction. | Keeps evidence clear and reduces control risk. |
What happens to invoice images and approval history when we leave a system?
You need them extracted in usable formats with their authenticity provable later - meaning the invoice image plus the approval chain and timestamps, not just a balance. Options: keep a read-only instance of the old system, export to a data warehouse or archiving service, or hold the records in a platform that retains them independent of the ledger. Decide and execute before decommissioning; reconstructing an approval chain after the source system is gone is often impossible.
What makes an electronic AP record audit-proof for IRS purposes?
Scanned/electronic invoices are acceptable to the IRS when they're complete, legible, accurately reflect the original, and are retained in a system that preserves them and can reproduce them - with the supporting trail (approval, payment) intact. The bar is faithful, retrievable reproduction with integrity, not paper - which is why an immutable audit trail and reliable retention matter more than the medium.
How long must AP records be retained - invoices, approvals, payment support, 1099s?
Retention is driven by IRS examination windows (generally at least three years, extended in cases of substantial understatement or fraud), plus audit, lender, and contractual requirements; many organizations adopt seven years as a safe standard for tax-relevant AP records and longer where statute or industry rules apply. Set the policy by document type and jurisdiction and apply it consistently.
What should I demand in a SaaS contract about getting AP history out at the end?
Up-front data-egress terms: you own your data, you can export invoices, images, coding, and the audit trail in usable formats, the timeline and any cost of egress at contract end, and that the vendor cooperates with extraction. Negotiate this before signing - leverage on data exit disappears once you've committed.
How do I archive a legacy ERP read-only - keep a license, export to a warehouse, or use an archiving service?
Three options with trade-offs: keep a read-only license (familiar, but ongoing cost and a system to maintain); export to a data warehouse (queryable, but loses native context unless you preserve images/trail); use a dedicated archiving service (purpose-built retrieval). Choose by how often you'll need lookup and whether images/approval chains must come along.
Auditors asked for invoices from a decommissioned system - what are our options now, and what should we have done?
Now: check for any retained backup, read-only instance, or exported archive; if none, reconstruct from payment records and vendor copies (painful, sometimes impossible). What you should have done: extracted invoices, images, and approval trails to an accessible archive before decommissioning. The lesson is to plan records access as part of every migration.
Who should own the AP records retention policy, and how should it be structured?
Typically the controller or a records/compliance owner, structured by document type and jurisdiction with defined retention periods, storage location, and disposal rules. The policy should name who can dispose of records and require legal hold to override scheduled disposal.
How do I maintain audit-trail integrity across a migration - proving the approval chain on an invoice that lived in two systems?
Preserve the original approval chain and timestamps from the source system (export or hold them in a ledger-independent platform), and document the migration itself so an auditor can follow the record across systems. An AP platform that retains the immutable trail regardless of ERP makes this a non-issue - the chain doesn't live in the ERP you replaced.
Are scanned invoices sufficient for the IRS, and what makes an e-record audit-proof?
Scanned/electronic records are acceptable when they faithfully and legibly reproduce the original, are completely retained, and can be retrieved with their supporting trail intact. Audit-proof means integrity and retrievability - the system can prove the record wasn't altered and can produce it on demand - not the existence of paper.
What changes when legal puts a litigation hold on AP records mid-migration?
A litigation hold suspends scheduled disposal and requires preserving all potentially relevant records - including in the system being decommissioned. Don't delete or overwrite held records during migration; coordinate with legal to preserve the source data (and its trail) until the hold lifts, even if it means delaying decommissioning.
In M&A, who keeps the AP records of an acquired or divested entity, and for how long?
Allocate it in the deal documents: typically the acquirer takes on the acquired entity's records (subject to retention rules), and divestiture agreements specify who retains the divested entity's history and provides access for the other party's audit/tax needs. Plan extraction and access during the transaction, not after.
Stampli perspective
Stampli preserves a complete, immutable audit trail for every invoice - image, approvals, comments, and history - independent of the ERP, so records stay accessible and their authenticity provable even after the underlying ERP changes. That separation is exactly what protects audit lookback across migrations: the invoice's full story lives in Stampli rather than being stranded in a decommissioned system.