Bank of America Statement to CSV: Beyond 90 Days

Most people meet this problem the same way. You sign in to Bank of America to pull a year of transactions for your accountant, you set the date range back, and the transaction view politely declines to go there. Bank of America documents that online banking displays your transactions for the last 90 days. Your statements go back further. Your export does not.

There is a second cliff behind the first one. Statements are self-serve online for 18 months; beyond that Bank of America keeps copies for 7 years but you have to order them rather than download them. So the data you need exists, is yours, and arrives as a PDF. This post covers the native download while it lasts, what to do past those lines, and how to prove the CSV you end up with actually reconciles against the statement it came from.

Quick answer

Two ways to get Bank of America transactions into CSV:

1. The online banking download. From the account activity view you can filter transactions, choose a time period and start a download. This is the fast path when your period is inside the window online banking still displays.
2. Convert the statement PDF. For older periods, for closed accounts, or when someone wants the bank-issued statement rather than an export you generated, the record is a PDF. Upload it to a converter like BankStatementKit, which extracts the transactions and balance-checks the result against the statement's own printed totals.

Rule of thumb: inside 90 days, use the download. Outside it, the statement PDF is the only complete record you have.

Convert a Bank of America statement to CSV

Option 1: Bank of America's built-in transaction download

1. Sign in to Bank of America online banking on a desktop browser.
2. Open the account and go to its activity view.
3. Use the Filter by choices to select the transactions you want to export.
4. Select the More dropdown menu, choose a time period if you want one, and then select Start download.
5. Open the resulting file in Excel or Google Sheets.

Where the built-in download stops

• 90 days of displayed transactions. Bank of America documents that after you enrol, online banking displays your transactions for the last 90 days. Loan files and tax years do not fit in 90 days.
• 18 months of self-serve statements. Statements outlast the transaction view, but not indefinitely: Bank of America documents viewing, printing and downloading up to 18 months of statements online. And they are PDFs, which will not open in a spreadsheet.
• 7 years on request, not on demand. Copies are retained for 7 years, but past the 18-month mark you order them rather than download them — which means waiting, and still receiving a document rather than data.
• No login, no download. A closed account, an account tied to a business you have left, or a statement a client forwarded you gives you nothing to sign in to.
• An export is not a statement. Underwriters and auditors routinely want the bank-issued statement itself. If you have to supply the PDF anyway, deriving the CSV from it keeps the two provably consistent.

Every one of those routes ends at a PDF.

Option 2: Convert the Bank of America PDF statement to CSV

1. Download the statement PDF from the statements and documents area, or use one you were sent.
2. Upload it. Bank of America statement PDFs are typically not encrypted — the login is the access control — so there is usually no password to enter. If a file does ask, supply it at upload and it is unlocked in memory and never written to disk.
3. The transactions are read into seven standard columns: Date, Narration, Reference, Value Date, Debit, Credit, Balance.
4. Check the verification label, then download the CSV.

Convert a Bank of America statement

Uploads are limited to 20MB or 50 pages, which matters here because these statements run long — the cheque-image pages alone can add several.

Why Bank of America PDFs trip up generic converters

Worth clearing up one thing first: Bank of America does not make you infer direction from context. Debits are printed with a minus sign in the Amount column. The sign-flip problem that plagues other US statements is not the issue here. The issues are structural, and there are three.

Section totals look exactly like transactions. The month is split into named blocks — Deposits and other additions, Withdrawals and other subtractions, Checks, Service fees — and each one closes with its own total line: Total deposits and other additions, Total withdrawals and other subtractions, and so on. Those lines carry a plausible amount in the amount column. A converter that harvests every row with a number in it appends all four to your transaction list and inflates the file, quietly, by exactly the value of the month.

The Checks block is a two-up table. Cheques are not printed as one list. They run as Date / Check # / Amount, and that three-column group is repeated twice across the page width, so a single visual row holds two unrelated cheques. Read it naively left-to-right and you either merge two cheques into one row or interleave the sequence into nonsense. Bank of America also appends an asterisk to a cheque number to mark a gap in the sequence, which a strict numeric parse will reject outright.

Whole pages are photographs. The cheque images are full-page scans with no text layer at all. Text-only extraction returns nothing from them — not an error, just silence — and it is easy to mistake a converter that skipped two pages for one that found nothing there to skip. Those pages need OCR, which happens automatically here.

The column mapping is described further on the Bank of America statement converter page.

Prove the CSV matches the statement

There is no running balance beside each transaction and, on a personal checking statement, no daily balance table either. What replaces them is better than people expect, because the Account summary is itemised rather than aggregate.

1. The Account summary, category by category. It prints a beginning balance, then separate lines for deposits and other additions, withdrawals and other subtractions, checks, and service fees, then an ending balance. Every one of those is a check you can run independently. A grand total that happens to balance can still hide a withdrawal misfiled as a deposit; four category totals cannot. Note that the first and last lines embed dates — beginning balance on a date, ending balance on a date — which also confirms you have the period you think you have.
2. The per-section Total lines. Each block restates its own total at the end. Sum your extracted rows for that block and it must match. This localises a problem to one section instead of the whole statement, so you know whether to go looking in the cheques or the electronic withdrawals.

Then the arithmetic has to close: beginning balance, plus additions, minus subtractions, minus cheques, minus fees, equals ending balance. Bank of America even prints a reminder that the ending balance already reflects the subtraction of service fees — a detail worth honouring, since double-subtracting them is an easy way to manufacture a discrepancy that is not really there.

Doing all this by hand across a year of statements is most of an afternoon. BankStatementKit runs the checks on every conversion and labels the result VERIFIED, DISCREPANCY or FAILED, with a discrepancy pointing at where the numbers stop reconciling.

FAQ

The bottom line

Inside 90 days, Bank of America's own download is the right tool and costs you nothing. Outside it — which is where most tax, lending and bookkeeping work actually lives — the statement PDF is the record, and past 18 months you may be ordering it rather than downloading it. Verify whatever you extract, because section totals that read like transactions and a two-up cheque table are precisely the arrangement that produces a CSV that looks correct and is not.