To scan a bank statement to Excel cleanly, scan at 300 dpi in grayscale, save each statement as one PDF with every page in order, and turn on deskew if the software offers it. Keep the page flat, uncropped and free of staples and shadows. A clean scan gives OCR digits it can read and columns that line up.
Scanner settings for bank statements: resolution, color and file type
The scanner settings that matter for a bank statement are resolution, color mode and file type. Use 300 dpi, grayscale and PDF, with one file per statement. That combination keeps small digits sharp, keeps shaded rows readable, and keeps the pages of one statement together for the conversion to Excel.
Resolution. Three hundred dots per inch is the common floor for text that will be read by software. Canon's scanner manual for MF Toolbox scan settings gives 300 dpi as the guide for printing or creating a searchable PDF, against 75 dpi for viewing on screen. The US National Archives rule for agencies digitizing permanent paper records, 36 CFR 1236.50, sets a minimum of 300 ppi for modern textual records. Bank statements are not federal records, but the number is a sensible floor for any typed page that has to be read accurately. Go higher only if the statement uses very small print.
Color mode. The same federal rule allows color or grayscale for textual records. For statements, grayscale is the safer default. Many statements shade alternate rows or print totals on a tinted band. A pure black-and-white scan sets every pixel to black or white, so light digits on a gray band can disappear or fill in. Grayscale keeps the shades, and the digits stay separate from the background. Color adds file size and helps only when the statement uses color to carry meaning, such as red for overdrawn balances.
File type. Save as PDF, not JPEG or PNG. A PDF holds many pages in one file, which keeps a statement's pages together. Microsoft's guidance on inserting scanned text into Word suggests scanning a document as a PDF with the scanner's own software, or using the OCR application that came with the scanner if there is one.
Scanner settings checklist for one statement
These are example settings for one month of a fictional client's checking account, Harbor Federal XXXX-4821. Adjust the names to your own scanner's labels.
- Resolution: 300 dpi (400 dpi for print smaller than the usual statement font)
- Color mode: grayscale
- File type: PDF, multi-page
- One PDF per statement period, named like
harbor-federal-4821-2026-03.pdf - Deskew or auto-straighten: on, if offered
- Blank page removal: off, then check by eye (see the multi-page section)
- Duplex: on only if the backs have printing
- Auto-crop: on only if it leaves the full margin; otherwise scan the full page size
Can you scan bank statements with a phone?
You can scan bank statements with a phone if you use a document-scanning mode, not the plain camera. Scanning modes find the page edges, flatten the perspective and save a PDF. Good light from above, a flat page on a dark surface and the phone held square to the paper matter more than the phone model.
Google Drive's Android app is one example with a built-in scanner. Its help page on scanning documents with Google Drive walks through the steps: tap the camera icon, line the document up inside the blue crop line, take the photo in manual or auto capture, adjust with Crop & Rotate, Filter (including grayscale) and Clean, tap Add for each further page, then Done, and save with .pdf as the format. Other scanning apps follow a similar pattern.
What makes a phone scan read well:
- Light. Even light from above, with no lamp to one side. A shadow across the amount column is the most common reason a phone scan misreads.
- Flat page. A folded statement bows at the creases, and the rows curve. Press it flat under a sheet of clear glass or plastic if it will not lie down.
- Contrast. A dark table under a white page lets the app find the edges.
- Square angle. Hold the phone directly above the page. A tilted shot makes the far rows smaller than the near ones, which throws off column alignment.
- Grayscale filter. Pick grayscale over a "black and white" or "document" filter when the statement has shaded rows, for the same reason as on a scanner.
Phone-capture variant of the checklist
- Document-scanning mode, not the camera roll
- Overhead light, no shadow on the page
- Page flat, on a dark surface, phone square above it
- Grayscale filter
- Every page added to the same scan, in order
- Saved as PDF, one file per statement
Getting clients to do this at home is a separate job. Short instructions, sent at the right moment, make more difference than any setting, and the client document collection category covers how to ask clients for phone scans and where those files should land.
Scanning multi-page bank statements into one file
Scanning a multi-page bank statement into one file means every page of one statement period goes into one PDF, in page order, with nothing from another month mixed in. One file per statement lets the converter read the beginning balance on page 1 and the ending balance on the last page, and check that the rows in between add up.
Page order. Statements print "Page 2 of 4" for a reason. Feed pages in order, and check the page count against the last page's footer before saving. A page out of order does not change totals, but it scrambles the running balance and makes the first mismatched row hard to find.
Duplex backs. Many statements print a reconciliation form, a disclosures page or a check image summary on the back of a page. Use duplex scanning only when the backs carry content you need. Scanning blank backs doubles the page count and adds empty pages between the transactions.
Blank pages. Automatic blank-page removal is convenient, but it can delete a page that is mostly white, such as a last page with one transaction and a balance summary. Leave it off and remove truly blank pages by hand, or turn it on and check the page count against the statement's footer afterwards.
One statement, one period. Do not scan a year of statements into one PDF. When twelve months share a file, a missing month is hard to spot, and one bad page affects the whole year's read. Twelve files, named by account and period, show a gap at a glance.
Check images. Some statements append pages of check images. These are pictures of the checks, not transactions, and the totals do not depend on them. Keep them in the file so the record is whole, but expect the converter to treat them as images.
Bank statement scanning mistakes that ruin the Excel rows
Bank statement scanning mistakes ruin Excel rows by distorting the table the converter has to rebuild. A skewed page tilts the columns, a shadow hides digits, a crop cuts off the balance column, and a staple tears a row. Each mistake can produce a sheet whose characters look right but whose rows do not add up.
Skew. A page fed at an angle tilts every row. On a narrow statement table, the right end of a row can drift into the line below by the time it reaches the balance column. Deskew corrects small angles. For larger ones, rescan.
Shadows and glare. Phone scans pick up a shadow from the phone or the hand, and glossy paper reflects light. Either one lowers the contrast of the digits underneath. Google's guidance on converting PDF and photo files to text asks for sharp images with even lighting and clear contrast, and text at least 10 pixels high.
Cropped margins. Auto-crop and tight manual crops sometimes trim the left date column or the right balance column. A statement missing its running balance loses the row-by-row check. Leave white space around the table.
Staples, folds and torn corners. A staple through the top corner lifts the page and casts a shadow along the first rows. A fold across the table bends the scan line. Remove staples, flatten folds, and tape torn pages before scanning.
Low resolution to save space. A 150 dpi scan looks fine on screen and reads worse. Small, condensed statement fonts lose the detail that separates 3 from 8.
Marked-up copies. Highlighter, ticks and handwritten notes are ink the converter cannot tell apart from the bank's printing. Scan a clean copy when one exists.
For rotating, deskewing and tidying pages after they are already scanned, see how to rotate and clean up scanned client documents. Firms setting a scanning standard for tax forms as well as statements will find the same principles applied in tax source document scanning.
What happens after the scanned bank statement reaches Excel?
After the scanned bank statement reaches Excel, two steps remain: OCR turns the page images into characters and rows, and a review proves those rows match the statement. A scan is a picture until OCR runs on it, and an OCR result is a draft until its totals tie to the statement's own balances.
The OCR step reads the digits and rebuilds the table from their positions. It is where look-alike digits, lost decimal points and drifting columns enter the sheet. How it reads the page, and where it goes wrong, is covered in what bank statement OCR reads and what it only infers.
The review step is the balance check. Beginning balance plus deposits minus withdrawals should equal the ending balance printed on the statement, and each row's running balance should follow from the one before. If the sheet passes, the scan was good enough. If it fails, the size of the gap usually points to the row.
Before running either step, confirm the file really is a scan. A statement downloaded from online banking and then printed and rescanned is a scan; the original download is not. The difference changes the route, and telling a scanned bank statement PDF from a digital one shows the three quick tests.
Once the sheet ties out, many firms need it as a CSV for an import. The steps, including the right encoding and how to keep check numbers intact, are in converting a bank statement to CSV.
Schema CPA accepts the scans and phone photos clients send through the same upload link, reads each statement page, checks that balances carry from one month to the next, and exports the rows to Excel or CSV. The document categories on the homepage list the statement types it reads.