The IRS just sent a notice. Your client is being audited for 2022. You need 60 months of bank statements organized by entity and account, and the audit starts in 30 days.
Audit prep is the #4 pain point for bookkeepers. Most don’t keep 5 years of statements. This page covers the IRS audit window, the 3-tier archive structure, the cloud storage options, and the recon cutoff tool’s archive feature.
The IRS can audit up to 3 years (standard), 6 years (substantial understatement), or unlimited (fraud). Most bookkeepers don’t keep 5 years of statements. The recon cutoff tool’s archive feature stores converted statements as searchable .qbo/.csv files. The 3-tier structure: original PDF, converted file, reconciliation worksheet.
Audit-ready statements need all 3 tiers. The original PDF is what the auditor asks for. The converted file is what you reconcile against. The reconciliation worksheet is what proves the books are correct. Missing any tier is the most common cause of audit failure.
For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For client onboarding (the starting point of the archive), see the client onboarding guide. For 1099 (year-end archive), see the 1099 contractor guide.
The IRS Audit Window
The IRS audit window is 3 years for standard audits, 6 years for substantial understatement (more than 25% of gross income), and unlimited for fraud or unfiled returns. The 3-year window starts from the date the return was filed, not the tax year.
For a 2022 return filed in April 2023, the standard audit window closes in April 2026. The 6-year window closes in April 2029. The unlimited window for fraud never closes. The bookkeeper should keep statements for 7 years to be safe.
The 7-Year Rule
Most CPAs recommend keeping statements for 7 years. The 7-year rule covers the standard 3-year window, the 6-year substantial understatement window, and a buffer for late-filed returns. The recon cutoff tool’s archive feature defaults to 7 years of retention.
The 3-Tier Archive Structure
The 3-tier archive structure is the IRS-ready format. Each tier is a separate file. The bookkeeper stores all 3 tiers for every statement, for every account, for every year.
Tier 1: Original PDF. The PDF the bank produced. This is what the auditor asks for. The PDF is the source of truth. The recon cutoff tool’s archive feature stores the original PDF in the cloud.
Tier 2: Converted file. The .qbo, .csv, or .xlsx file generated by the recon cutoff tool. This is what you reconcile against. The converted file is searchable and editable. The recon cutoff tool’s archive feature stores the converted file alongside the original PDF.
Tier 3: Reconciliation worksheet. The worksheet showing which transactions matched and which didn’t. This is what proves the books are correct. The recon cutoff tool’s archive feature generates the reconciliation worksheet from the conversion step.
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 freeThe Cloud Storage Options
Cloud storage is the standard archive location. The 3 main options.
Google Drive. The most common. The 15GB free tier is enough for most bookkeepers. The paid tier ($2/month for 100GB, $10/month for 2TB) is enough for multi-client bookkeepers. The folder structure is the standard Google Drive folder pattern.
Dropbox. The second most common. The 2GB free tier is too small for most bookkeepers. The paid tier ($10/month for 2TB) is the same as Google Drive. Dropbox has better file versioning than Google Drive.
Box. The enterprise option. The free tier is 10GB. The paid tier starts at $5/month per user. Box has the best security and compliance features. Box is the choice for bookkeepers serving regulated industries (healthcare, financial services).
The Folder Structure
The folder structure is consistent across cloud options. The 4-level pattern: client name → entity name → year → statement type.
Example: Acme LLC/LLC1/2022/Bank Statements. Inside the Bank Statements folder: Chase_2022-01.pdf, Chase_2022-02.pdf, etc. The recon cutoff tool’s archive feature creates the folder structure automatically.
The Archive Workflow
The archive workflow runs every month. The 5 steps take 10-15 minutes per client.
Step 1: Receive the Statement
The statement arrives as a PDF or a link to a cloud folder. The recon cutoff tool’s archive feature logs the receipt date.
Step 2: Convert the Statement
The recon cutoff tool’s batch upload converts the statement. The conversion generates the Tier 2 file and the Tier 3 reconciliation worksheet.
Step 3: Verify the Conversion
The reconciliation worksheet shows row count, ending balance, and date range. The bookkeeper verifies the conversion matches the source PDF. The recon cutoff tool’s verification step takes 1-2 minutes per statement.
Step 4: Archive in the Cloud
The 3 tiers go into the cloud folder: original PDF, converted file, reconciliation worksheet. The recon cutoff tool’s archive feature uploads all 3 in one step.
Step 5: Update the Audit Log
The audit log tracks: client, entity, year, statement date, conversion date, archive date, archive location. The log is what the bookkeeper refers to when the IRS asks for a specific statement. The recon cutoff tool’s audit log is searchable by client, entity, year, and date range.
The 30-Day Audit Response
When the IRS sends an audit notice, the bookkeeper has 30 days to respond. The 5-step response uses the archive.
Step 1: Read the notice. The notice specifies the tax year, the entity, and the items under audit. The bookkeeper identifies which entities and years are affected.
Step 2: Pull the archive. The recon cutoff tool’s audit log identifies the archive location for the affected entity and year. The bookkeeper pulls all 3 tiers from the cloud folder.
Step 3: Reconcile the affected transactions. The reconciliation worksheet shows which transactions matched and which didn’t. The bookkeeper explains the unmatched transactions to the IRS.
Step 4: Prepare the response. The response includes the original PDF, the converted file, the reconciliation worksheet, and any additional documentation. The response is filed via the IRS audit portal or by mail.
Step 5: Follow up. The IRS might ask follow-up questions. The bookkeeper responds within 30 days. The recon cutoff tool’s archive feature makes the follow-up faster because all the documents are already organized.
The Common Mistakes
3 mistakes bookkeepers make on audit prep.
Archiving only the converted file. The converted file is what you reconcile against. The source PDF is what the auditor asks for. Archiving only the converted file is the most common cause of audit failure.
Not keeping 5+ years. The standard 3-year audit window closes fast. The 6-year window for substantial understatement closes slower. Most bookkeepers don’t keep 5 years, which covers the standard window plus a buffer. The 7-year rule is the safe default.
Storing archives in personal accounts. The archive should be in a business or firm account, not a personal account. The personal account might be inaccessible if the bookkeeper leaves the firm. The recon cutoff tool’s archive feature uses the firm’s cloud storage, not the bookkeeper’s personal account.
The Cloud Storage Cost
Cloud storage for 7 years of statements costs about $10-30 per month per bookkeeper. The cost is offset by the time saved during an audit. An audit response without a proper archive takes 40-60 hours. The same response with a proper archive takes 8-12 hours. The time savings cover the storage cost many times over.
For the broader bookkeeper workflow, see the bank statement workflow for bookkeepers pillar. For client onboarding, see the client onboarding guide . For 1099, see the 1099 contractor guide . 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 bookkeeper-resource cluster on this site. The consolidated hub, covering onboarding, monthly close, year-end, client deliverables, and multi-entity workflows, lives in the complete bookkeeper workflow guide.
For related reading on the broader clusters, the covers credit-card-side mechanics, and the covers bank-account-side mechanics. 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 PDF Bank Statements Into Workable Spreadsheets
Your bank statement is a mess of numbers, but your books shouldn't be. Use our converter to get Excel, CSV, or QBO files — ready for QuickBooks.
Try It Free Now
