What bank statements does an auditor actually need?

Every statement for every account that had activity during the period under review, with no missing months, including accounts that closed or opened mid-year and rarely used accounts like old savings accounts. Auditors ask for a full list of accounts held during the period, not just the ones actively used in daily bookkeeping.

How far back can I request old bank statements if I no longer have online access?

Most banks can retrieve archived statements on request even after online access to older periods has expired, but the request can take several business days to fulfill. Request anything missing as soon as you know an audit is coming, since a late statement request is one of the most common things that stalls an audit at the last minute.

What makes a bank reconciliation audit-ready?

A reconciliation that was actually performed monthly by matching real transactions, showing the book balance, the bank statement ending balance, and every reconciling item like outstanding checks or deposits in transit. A reconciliation that was plugged once at year-end typically doesn't hold up when an auditor traces it line by line against the statement.

Getting Audit-Ready: Prep Your Bank Statements Before the Accountant Calls

An audit runs on source documents, and for cash that means the bank statement. Here's how to check for gaps, tie every reconciliation to the actual balance, and hand over a package that doesn't generate a single follow-up email.

What auditors and accountants actually expect

An audit or year-end review isn't testing whether your books are perfect — it's testing whether every number can be traced back to a source document. For cash and bank activity, that source document is the bank statement, and the first thing an auditor does is confirm that every account on your balance sheet actually reconciles to a statement they can see.

That means the request you'll get isn't "send your bank statements" in the vague sense. It's every statement, for every account that had activity, for every month in the period under review, with no gaps. Auditors flag missing months immediately because a gap is exactly where an error — or something worse — tends to hide.

Completeness: every month, every account

Before you send anything, build a simple checklist: one row per bank and credit card account, one column per month in the audit period. Mark off each statement as you locate it. Anything left blank is a gap you need to fill before the auditor finds it for you.

Watch for accounts that closed or opened mid-year, accounts under a former DBA or entity name, and old savings or money market accounts that rarely get used but still technically belong to the business. Auditors ask for a full list of accounts held during the period, not just the ones you actively use — an account you forgot to mention is worse than one with a small balance.

If a bank has purged online access to statements older than 12 or 24 months, request archived statements directly from the bank now. That request can take days to fulfill, and it's the single most common thing that stalls an audit at the last minute.

Tying transactions to the statement balance

Every bank account on the balance sheet needs a reconciliation showing the book balance, the bank statement ending balance, and the reconciling items between them — outstanding checks, deposits in transit, bank fees not yet recorded. An auditor will pick a sample of months and trace the reconciliation line by line back to the statement.

This is where loose bookkeeping gets exposed fast. If a reconciliation was done once at year-end by plugging a number rather than monthly by matching actual transactions, the reconciling items won't hold up under a transaction-level trace. Redo any reconciliation you're not confident in before the auditor asks — it's far cheaper to fix now than to explain later.

Large or unusual transactions get extra scrutiny. Anything that doesn't obviously match a known category — a large wire, a round-number transfer, a payment to an unfamiliar payee — should have a one-line explanation ready before it's asked about, backed by an invoice, contract, or other support.

Organizing a clean audit package

Auditors work faster, and ask fewer follow-up questions, when the package is organized before it lands in their inbox. A clean structure:

One folder per account, statements in month order, files named with the account and period so nothing needs to be opened to identify it.
A completeness checklist showing every account and every month accounted for.
Bank reconciliations for each month, with reconciling items documented.
Supporting documentation for any large or unusual transactions, indexed by date.

PDF statements are the standard format banks provide, but they're painful to work from when you're building the reconciliation and completeness checklist by hand across a dozen accounts. Converting the PDFs to a verified spreadsheet first — matching every transaction against the statement's own balance — gives you a working ledger you can sort, total, and check for gaps before the auditor ever opens a file, instead of finding a missing month mid-review.

Common gaps that slow an audit down

The same handful of issues come up on nearly every audit that runs long:

A missing month buried in the middle of the period, not caught until the auditor's sample lands on it.
A reconciliation that was never actually done monthly, only estimated at year-end.
An account the business stopped using but never closed, left off the account list entirely.
Large transactions with no documentation trail, requiring a scramble to track down an invoice or contract after the fact.
Statements requested from the bank too late, after online access to older periods has already expired.

None of these are hard to prevent. They just require doing the completeness check and reconciliation review before the audit starts, not during it. If you're prepping a package that spans several banks, converting each institution's statements to a consistent spreadsheet format makes it far easier to spot a missing month across accounts that otherwise look nothing alike.