Deposits in one section, withdrawals in another, cheques in a third, and the balances collected into a daily ledger at the end. Here is what that structure means when you want the whole month in one sheet.
The structure is the reason the numbers land where they do.
Deposits and other additions, withdrawals and other subtractions, cheques, and service fees are four separate lists, each with its own heading and its own subtotal. Dropped into one sheet they become one chronological list again, which is usually what you wanted — but the subtotal lines are not transactions, and they are left out rather than imported as phantom rows.
Near the end the statement prints a small table of dates and balances. It is not attached to the transactions, so it cannot be used row by row, but it is the best cross-check available on this statement: pick any date in that table and compare it with the running total you build in the spreadsheet.
Without a balance on each line, the row-by-row check does not run, and the page tells you so. The totals block still does real work: money in, money out, and the net change for the period, which must equal the ending balance minus the beginning balance printed on the first page.
The cheques section lists numbers rather than payees, often with a gap marker where a number is missing from the sequence. Those markers are not transactions either; the reader keeps the numbered rows and drops the asterisks.
No column headings were found, so the columns were identified from the running balance alone. Check a few rows before you rely on it.
| Date | Description | Debit | Credit | Balance |
|---|
They are already read and checked in this tab. A pass unlocks every row of every file you convert over the next 7 days, in this browser.
The workbook carries a second sheet, Warnings: every row whose balance does not follow from the row above, with the balance your statement shows next to the one the arithmetic expects. It says so plainly when there is nothing to check.
Two of these routes are faster than any converter.
In online banking, open the account and look for Download transactions. Bank of America offers a spreadsheet file and a Quicken or QuickBooks file for the transactions it still holds online. Where that covers your period, it beats reading a PDF — nothing has to be interpreted at all.
Statements older than the download window, a closed account, or a PDF sent to you by someone else. That is what this page is for, and it is where a reader that reports its own uncertainty matters more than one that does not.
For QuickBooks Desktop or Quicken, statement to QBO produces the .qbo or .ofx file from the same PDF. QuickBooks checks the bank id inside that file against its own list, so put yours in the field on that page.
Statements change, and yours may not look like this. Drop it anyway: the reader works from the layout in front of it rather than from a template per bank, and the balance check reports what it actually found.
Something else? Write to support@ocrsnip.com.
Yes. Which section a transaction came from decides its direction: money in stays positive, money out negative, in the signed Amount column every accounting import understands. The full detail preset also keeps them as separate debit and credit columns if you prefer to read it that way.
That is exactly what it is good for. Build a running total in the spreadsheet, then compare it with a few dates from that table. If they agree, the month was read correctly; if not, the date where they part tells you which row to look at.
Yes — a scan or a photo saved as PDF goes through OCR in this tab. It is slower and less certain, so read the figures once against the paper. The scan language can be changed in the drop zone if the statement is not in English.
Drop it and the page asks for the password, the way a PDF reader would. It is used here to open the file and then forgotten: never sent, never saved, never written into the spreadsheet.