How long should you keep converted bank statement records?

You converted five years of statements into clean spreadsheets months ago. Now an auditor wants three years of records, your accountant wants seven, and someone on an unrelated matter is asking about a transfer from a decade back. Bank statement retention rules are not a single number: how long you keep a record depends on who is asking and why, and the answer changes the moment a dispute or a filing obligation enters the picture.

Why retention length depends on who is asking

A bookkeeper closing monthly books, an accountant defending a tax position, and a solicitor responding to a discovery request are working from different clocks. Bookkeeping retention is about having enough history to reconcile and correct. Tax retention is set by how long a taxing authority can reopen a return. Legal retention is set by how long a claim connected to those transactions can still be brought, plus any active duty to preserve.

Treat these as separate, overlapping requirements rather than one universal rule. The safest retention period for a given record is the longest of the periods that actually apply to it, not an average of them.

Baseline timeframes used in tax and accounting practice

In the United States, commonly cited guidance from the IRS on record retention (Publication 583 and related guidance under Topic 305) sets out a tiered structure that many accountants use as a working default even beyond strict tax compliance:

• Three years is the standard floor for records supporting a filed return, matching the ordinary window in which the IRS can open an audit for most situations.
• Six years applies if you underreported gross income by more than 25 percent, since the assessment window extends for substantial underreporting.
• Seven years applies to records supporting a claim for a loss from worthless securities or a bad debt deduction.
• Indefinitely applies if no return was filed for that period, or if a return is found to be fraudulent.

These figures are US-specific, and other jurisdictions set comparable but not identical assessment windows for tax authorities, so confirm the equivalent period where you file before relying on the US figures directly. What carries across jurisdictions is the structure: a short default floor, a longer period for material discrepancies, and no ceiling where fraud or non-filing is involved. That structure is a reasonable model for setting a bookkeeping retention policy even in a different country, once you substitute the locally correct numbers.

Litigation holds and disclosure obligations

A duty to preserve records is not the same thing as a retention schedule, and it does not simply reset every clock you already have running. The duty typically arises once litigation is reasonably anticipated, which can be earlier than the date a claim is actually filed, and its scope is set by relevance to the anticipated dispute and by proportionality rules that vary by jurisdiction and court.

Once a hold applies, it sits alongside your ordinary retention schedule rather than replacing it. Records that would otherwise have been eligible for routine deletion must be preserved for as long as the hold's scope covers them, even if that is longer than your normal policy, but records outside that scope are unaffected. A common practical pattern in corporate hold policies is to set a default preservation period, often illustrated at around seven years for financial records tied to a dispute, and then have counsel narrow or extend that default once the actual claims and their relevant date range are known. Treat any such figure as a starting point for a hold notice, not as a rule that applies automatically to every matter.

If you handle statements for clients who may end up in a formal dispute, it is worth understanding how conversion and disclosure interact before a hold ever lands; the workflow for converting bank statements for litigation discovery covers what a review team typically needs from the source files.

How evidence rules treat a converted file

A spreadsheet produced from a statement document is not automatically a duplicate of the original in evidentiary terms. Federal Rule of Evidence 1001 defines a duplicate as a counterpart produced by a process that accurately reproduces the original, and data transcribed or extracted into a new format does not meet that definition on its own. Its admissibility instead turns on separate rules, including authentication of the extraction process, hearsay and business-record questions, and, for larger volumes, the summary provisions of Federal Rule of Evidence 1006.

In practice, this is why keeping the source statement document is not optional once you have converted it. If a figure in the spreadsheet is ever challenged, the fastest way to resolve the question is to point to the original document and, ideally, to a record of how the conversion was checked. Building that trail into your ordinary workflow is cheaper than reconstructing it after the fact; see keeping converted financial records defensible for the specific checks worth logging at conversion time, and what a bank statement can prove for the limits of what the document itself establishes even when it is authentic.

Statute of limitations and how long to actually keep records

Retention length and the statute of limitations are related but distinct. A limitations period sets the outer date by which a claim connected to a transaction can be brought; if you have already deleted the record supporting or disputing that transaction before the period runs, you have no way to respond if a claim does arrive near the deadline.

Two things complicate this in common law jurisdictions. First, limitations periods differ by claim type: a simple contract claim, a fraud claim and a tax assessment period rarely share the same length, so a single transaction can sit under several different clocks depending on what dispute might eventually attach to it. Second, discovery rules in many jurisdictions delay the start of the limitations clock until the claimant knew, or reasonably should have known, about the relevant facts, which means the effective deadline can fall well after the nominal period would suggest. A reasonable retention policy accounts for both: it sets the retention window to the longest of the applicable limitations periods for the kinds of claims plausible for that record, and it builds in a margin for delayed discovery rather than measuring strictly from the transaction date. This is also the reasoning behind longer retention for records tied to loans, disputed deductions or divorce settlements, where the underlying claim can surface years after the transaction; divorce financial disclosure is a concrete example where several years of statements routinely have to be produced well after the accounts were closed.

A practical retention workflow

1. 1

   Set the baseline period

   Apply the longest of your tax assessment window, your relevant limitations periods and any client or firm policy to each category of record.
2. 2

   Store originals with conversions

   Keep the source statement document next to the converted spreadsheet, not as a separate, harder-to-find archive.
3. 3

   Log the verification

   Record how the running balance was checked at conversion time, so authenticity questions can be answered without redoing the work.
4. 4

   Check for open holds before deleting

   Confirm nothing in the batch falls within an active litigation hold before any scheduled purge runs.
5. 5

   Review the schedule annually

   Adjust retention periods when a client's exposure changes, such as a new loan, a filed claim or an ongoing dispute.

When to review and purge

Retention policies fail more often from inertia than from bad rules: records get kept forever because nobody set a review date, or deleted early because a hold from an old matter was never lifted from the policy. Set an explicit review date for each retention category, not just an end date, and confirm at that review whether the original reason for the period still applies.

Secure disposal matters as much as the retention length itself. When a record's retention period genuinely expires and no hold applies, delete it rather than letting it accumulate past its purpose; a growing archive of records nobody is actively required to keep is exposure without benefit.