You got a notice from the IRS. They’re auditing your 2022 return. They want your 2022 bank statements. You deleted them.
IRS Publication 552 is the IRS’s guide for individuals on how bank statements interact with tax filings. This page covers the 5 key provisions, the retention period, and the recon cutoff tool’s per-IRS-Pub-552-handling.
IRS Publication 552 specifies that individuals should keep bank statements for at least 3 years from the date of filing. For some cases (substantial omission, bad debt, worthless securities), the retention period is 6-7 years. The publication covers how to claim deductions (charitable donations, mortgage interest) and how to report interest income (1099-INT).
The recon cutoff tool’s per-Pub-552-handling enforces the 3-7 year retention period. The recon cutoff tool’s per-1099-int-flag identifies interest income that must be reported. The recon cutoff tool’s per-deduction-flag identifies deductions that can be claimed from bank statements.
For the broader bookkeeper workflow, see the bookkeeper workflow. For the 5-year audit archive, see the 5-year audit archive. For the crypto tax, see the crypto tax guide.
What Is IRS Publication 552?
IRS Publication 552 is the IRS’s guide for individuals on bank statement recordkeeping. The publication is approximately 30 pages. The recon cutoff tool’s per-pub-552-tracking handles the publication updates. The current version is 2025.
What most guides miss about this workflow is that the quality depends on the mechanism, not on the tool. Two tools that look different on the surface often run the same 4-step process underneath: read, find, parse, verify. The difference is in how well each step handles edge cases (merged cells, missing balances, non-standard date formats, scanned vs digital input).
Choosing between tools based on UI alone misses the actual quality lever.
The publication is the authoritative source for individual bank statement recordkeeping. The recon cutoff tool’s per-pub-552-citation-flag tracks the citations. The recon cutoff tool’s per-pub-552-effective-date tracks the effective date of each provision.
5 Key Provisions of Pub 552
5 provisions cover the bank statement recordkeeping requirements. The recon cutoff tool’s per-provision-handling covers all 5.
Provision 1: The 3-Year Retention Period
Individuals should keep bank statements for at least 3 years from the date of filing. The recon cutoff tool’s per-3-year-flag enforces this. The recon cutoff tool’s per-archive-handling stores the 3-year set.
Provision 2: The 6-7 Year Retention for Specific Cases
For substantial omission (25%+ of gross income), the retention period is 6 years. For bad debt or worthless securities, the retention period is 7 years. The recon cutoff tool’s per-extended-retention-flag identifies the cases requiring extended retention.
Provision 3: Interest Income Reporting (1099-INT)
Banks issue 1099-INT for interest income over $10. The 1099-INT must be reconciled to the bank statement. The recon cutoff tool’s per-1099-int-flag identifies the interest income. The recon cutoff tool’s per-reconciliation-flag matches the 1099-INT to the bank statement.
Provision 4: Charitable Donation Deductions
Charitable donations documented in the bank statement can be claimed as deductions. The recon cutoff tool’s per-charitable-flag identifies the donations. The recon cutoff tool’s per-deduction-summary emits the Schedule A entry.
Provision 5: Mortgage Interest Deductions
Mortgage interest paid (from the bank statement or 1098) can be claimed as a deduction. The recon cutoff tool’s per-mortgage-interest-flag identifies the interest. The recon cutoff tool’s per-schedule-a-entry generates the Schedule A entry.
From PDF to Excel in one click
Forget retyping line by line. Upload any bank statement, get a spreadsheet you can actually use. Your files are never stored, and you can test the converter with 3 free conversions.
Try it freeHow Pub 552 Affects Individuals
5 practical impacts. The recon cutoff tool’s per-individual-impact-flag tracks each impact.
Impact 1: Record retention. The 3-7 year retention period means individuals must keep bank statements. The recon cutoff tool’s per-retention-tracking handles the per-statement retention.
Impact 2: 1099-INT matching. The 1099-INT must match the bank statement. The recon cutoff tool’s per-1099-int-matching handles the match.
Impact 3: Deduction proof. The bank statement is the proof for charitable and mortgage interest deductions. The recon cutoff tool’s per-deduction-proof-handling extracts the proof.
Compliance Documentation Checklist
5 documentation items. The recon cutoff tool’s per-Pub-552-checklist generates the per-individual checklist.
Item 1: 3 years of bank statements per account. The recon cutoff tool’s per-3-year-archive stores the 3-year set.
Item 2: 1099-INT for each account with interest. The recon cutoff tool’s per-1099-int-archive stores the 1099-INT.
Item 3: Charitable donation records. The recon cutoff tool’s per-charitable-archive stores the donation records.
Item 4: Mortgage interest records (1098 or bank statement). The recon cutoff tool’s per-1098-archive stores the 1098.
Item 5: Audit response package. The recon cutoff tool’s per-audit-package-export emits the complete package.
Common Mistakes with Pub 552
3 common mistakes. The recon cutoff tool’s per-Pub-552-mistake-flag identifies each.
Mistake 1: Discarding statements after 1 year. The 3-year minimum applies. The recon cutoff tool’s per-1-year-discard-flag warns against this.
Mistake 2: Not matching 1099-INT to bank statement. A common failure mode is the 1099-INT not matching the bank statement (e.g., wrong account, wrong year). The recon cutoff tool’s per-1099-int-reconciliation handles the match.
Mistake 3: Missing charitable deductions from the bank statement. A common failure mode bookkeepers report is the taxpayer missing charitable donations documented in the bank statement. The recon cutoff tool’s per-charitable-flag identifies the donations.
How Pub 552 Connects to Our Cluster
4 cluster spokes cite Pub 552. The recon cutoff tool’s per-citation-flag tracks the citations.
5-year audit archive cites Pub 552 for the retention period. Bookkeeper workflow cites Pub 552 for the monthly reconciliation. Crypto tax guide cites Pub 552 for the 3-7 year retention. Month-end close cites Pub 552 for the documentation requirements.
Related Regulations and Resources
5 related resources.
Fannie Mae Selling Guide B2-1.5-02 . HUD 4000.1 II.A.4 . ECOA Reg B . Bank statements and federal regulations . IRS Pub 552 glossary entry . The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
The bank statement converter handles all the steps with the integrity check at the end. The bank statement converter handles all the steps with the integrity check at the end.
Related:
This topic is part of the US bank-statement federal-regulations cluster on this site. The consolidated hub covering Reg E, Reg CC, Reg DD, ECOA Reg B, BSA, FinCEN CTR/SAR, FHA bank-statement guidelines, and Fannie Mae and Freddie Mac requirements now lives in the complete federal regulations bank statement guide.
For related reading on the broader clusters, the covers credit-card-side mechanics, the covers bank-account-side mechanics, and the expanded bank statement anatomy is a useful primer.
More on the broader cluster
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes.
Decision framework for this topic
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
Related reading and broader clusters
For the broader context on US bank-statement reading, see the consolidated hubs on merchant category codes, payment rails, and the statement anatomy. These hubs work together to cover credit-card statements, bank-account statements, and the categorization signals that survive merchant-name truncation.
Each hub is built to be the canonical reading for one cluster of search intent, with cross-cluster links that take you to the right next node.
When reconciliation runs into edge cases, the practical answer usually lives in the federal-regulations cluster, the bookkeeper-resource cluster, or the credit-card-statements cluster. Each offers a domain-specific take on the same underlying signal. The merchant category code is the same whether the reader is the small-business owner, the bookkeeper, or the lender.
For lender workflows, the merchant category code on credit-card statements and the ACH SEC code on bank-account statements are the two signals underwriters most often scan first. Lenders use the four-column conversion output as a quick reference for what the borrower actually spent.
Cash advances flagged at MCC 6011 and quasi-cash at MCC 6051 draw particular scrutiny at mortgage underwrite, and crypto exchanges on the ACH rail draw additional questions for self-employed applicants.
For bookkeeper workflows, the categorical signal ties directly into the chart-of-accounts. A bookkeeper who maintains categorization rules keyed off the merchant category code can process dozens of clients per week without manual categorization of common merchant types. The conversion output is the durable input; the rule set is the durable work product.
Easy Statement Sheet reads bank-statement and credit-card statement PDFs into a clean four-column output (Date, Description, Amount, plus Merchant Category Code for credit-card statements, plus the running balance for bank-account statements). Files are never stored. The conversion runs entirely in memory and produces a deterministic output that downstream tools can parse.
The first three statement conversions are free, no card required. Plans start at $15 per month. The four-column output preserves the categorization signals without retyping, so the rule-based reconciliation layer survives merchant-processor changes. For bookkeepers handling dozens of clients per month, this is the highest-leverage workflow to standardize.
Turn any PDF statement into a clean sheet
Skip the typos and the hours of copying. Our converter handles any bank statement format and outputs Excel, CSV, or QBO for QuickBooks. No file retention, free to try.
Convert your statement
