Bank statement to Google Sheets

This page suits a PDF from an old account, a statement a client sent or a paper statement you photographed. The converter reads transactions into a table; Google Sheets is where you can filter, annotate or share the reviewed data. Sonomir does not create a spreadsheet in your Google account, access Drive or maintain a live bank feed. You choose where to import the downloaded file.

If online banking already provides the period as CSV, use that source file instead. It avoids recognition errors and normally needs no paid conversion. If you need monthly synchronisation, a dedicated bank-feed service or spreadsheet add-on may be the better fit. This is an occasional file-conversion workflow, not ongoing bookkeeping automation.

Choose the full transaction CSV for one table, or the Excel workbook when you also want the Balance checks and Statement summary sheets. The named accounting CSV layouts are for QuickBooks Online, Xero or YNAB; they deliberately leave out review columns and are not the best starting point for a detailed spreadsheet review.

First inspect the extracted dates, descriptions and amounts on this page. Finish any remaining statement pages before importing a complete period. Download the full CSV, open a blank Google spreadsheet and choose File → Import → Upload. Select the file and import into a new sheet so that existing work is not overwritten. Check the delimiter if the preview puts everything into one column.

For an Excel workbook, the same import menu can create a spreadsheet or insert its worksheets. Google's Excel-to-Sheets instructions were checked on 7 October 2026. The Google support discussion of CSV uploads recommends the Sheets import menu rather than opening a Drive preview. These are checked instructions; a Sonomir file has not yet passed a recorded import in a Google account here.

After import, confirm the row count and a known outgoing payment and deposit. The Amount column is signed: money out is negative and money in is positive. Balance is the printed running balance, not a second amount to add. Use the header row when sorting so that merchant names, dates and amounts stay on their original transaction rows.

The full transaction CSV writes an unambiguous date as YYYY-MM-DD. Your spreadsheet locale can affect how Sheets interprets and displays it, so inspect a date whose day is greater than twelve as well as one that could be ambiguous. A formatted date display is not necessarily the same as the underlying value. If the source never supplied a clear year or day/month order, the review file keeps the printed wording; do not use a guess to build a timeline.

Text that could begin a spreadsheet formula is protected in the CSV. Descriptions can contain commas and quotation marks; the writer quotes those fields so they remain one cell. If all the values appear in a single column, revisit the import separator instead of deleting punctuation from merchant names.

Several statement PDFs can share one review workbook, with a Statement column identifying each source. Keep accounts and currencies distinguishable. Do not add GBP and USD into one total or treat a credit-card liability like a current-account cash balance. The converter does not calculate exchange rates or assign tax categories. When your destination is accounting software instead, choose the Xero CSV or QuickBooks import workflow.

A matching balance check establishes arithmetic consistency, not that every row is correct. The 6 October fictional-photo test lost reference digits in two descriptions while the totals still passed. Compare important amounts and long references with the source, and inspect a scan before accepting it. The bank statement review guide explains the checks; old statements to Excel covers rebuilding an archive.

For three pages with the daily two-page allowance unused, one page is paid: $0.25 at the $5-pack rate or $0.30 at the $3-pack rate. Paid processing includes CSV and Excel. The minimum purchase is $3, unused credits remain in your wallet, and taxes are shown at checkout. A free-only result charges 2 credits for CSV or 4 for Excel once; copying or downloading plain text is free.

ProperSoft offers local desktop conversion and a subscription can suit frequent use better. Here, the statement is processed in the cloud. Once you import a file into Google Sheets, that copy is governed by your Google sharing and storage choices. Deleting the Sonomir result does not delete a spreadsheet you created elsewhere. Review who can access the spreadsheet before sharing financial records.

Upload a bank statement — the PDF your bank emailed, a scan, or phone photos of the pages — and every transaction comes back as a row: date, description, money out, money in, a signed amount and the running balance. Transactions from every page land in one table, so a twelve-page statement is one list, not twelve fragments to stitch together.

Then comes the part that matters: the tool checks its own work. It adds up what it read and compares the result with the balances printed on the statement. When they agree to the cent, the extracted amounts are consistent with those balances. Offsetting errors can still cancel out, so a passing check is a useful review aid, not proof of accuracy. When they do not, it tells you by how much and flags the rows where the running balance breaks, so you check three lines instead of three hundred.

Two independent checks run on every statement.

1. Opening + money in − money out = closing. The opening and closing balances are read from the statement's summary or its first and last lines. If the transactions read in between do not produce the closing balance exactly, something is missing or wrong, and the difference is shown.
2. Row by row. Where the statement prints a running balance, each one must equal the previous balance plus that line's money in minus its money out. A break points straight at the problem: the flagged row, or the one just above it.

The arithmetic is done in whole cents, never in floating point, so a check cannot pass by rounding. Statements listed newest-first are recognised, and so are card and loan statements, where the balance is money owed and runs the other way.

A passing check shows that the extracted amounts agree with the balances that were read. It cannot rule out offsetting errors, omitted pairs of transactions, or incorrectly read balances. Check dates and descriptions, compare the row count with the source, and review important amounts before importing.

The Excel workbook has three sheets:

• Transactions — one row per transaction, in the order printed, with the page it came from and a Check column that says why a row was flagged.
• Balance checks — each check, whether it passed, and the numbers behind it.
• Statement summary — bank, the last four digits of the account, period, currency, opening and closing balances, totals, and whether it reconciles.

Amounts are stored as numbers, not text, so SUM works straight away. Dates are written as year-month-day when the statement makes the year clear, which sorts correctly everywhere. Choose the full transaction CSV to keep the review columns, or a QuickBooks Online, Xero or YNAB CSV layout for its documented import fields. All layouts share one CSV purchase for the same result. Accounting layouts leave out balances and check notes; each statement has a separate file, and multiple files download as a ZIP.

Upload several PDFs at once — twelve monthly statements, say — and they come back in one workbook with a Statement column, plus a summary row for each.

A PDF downloaded from online banking often already contains its text. That text is read with its printed column positions before a model turns it into records. This avoids recognising letters and digits from pixels, but the model can still misinterpret a column or a wrapped description.

A scanned statement, or photos of printed pages, is read from the image. That works well on a flat, straight, well-lit page. It struggles with faint thermal-style printing, pages shot at an angle, and folds across the amount columns. The balance check is your safety net here: if a digit was misread, the running balance breaks at that row.

Photos uploaded together are treated as the pages of one statement, in the order you chose them. Each PDF is its own statement.

It is built for current, checking and savings account statements, and reads card and loan statements too. It is not built for investment or brokerage statements, where a row is a holding rather than a movement of cash. If your bank locks its statements with a password, enter it when the page asks: the PDF is unlocked in your browser, the password never leaves your device, and only the unlocked copy is uploaded. Without the password the tool cannot open it and will not try to get around it.

It has not been tested against a named list of banks, and this page will not pretend otherwise. Statement layouts vary enormously; what the tool offers instead is a result you can verify. If the checks pass, the extracted numbers agree with the balances read from the source. If they fail on your bank's layout, the job tells you so plainly.

We compared the model's extracted rows with labelled, fictional statements: separate debit and credit columns, signed amounts, German decimal commas, Indian number grouping, wrapped descriptions, a dense multi-page list, a credit card, scans and phone photos. These are synthetic examples, not a certification for any named bank.

The eight text-PDF cases and two scanned-PDF cases matched every labelled date, description, amount and direction in this run. A photographed statement lost a digit from two transaction descriptions even though its balance checks passed. Review the source rows, especially long reference numbers in photos. Results can vary between runs; this test does not establish an accuracy percentage for your files, mixed-currency support or successful imports into accounting software.

Compare QBO, QFX, OFX and QIF before importing. The Xero CSV page explains its preset, while password-protected statements covers opening a PDF with your own password. For spreadsheet review, use Google Sheets. Each route uses the same converter; no accounting-app import pass is claimed.

Statements are sensitive, so here is exactly what happens. The uploaded file is sent to the reading model and deleted from storage when the job ends, whether it succeeded or not. Only the last four digits of an account number are kept. The transactions you see are stored with your job so the download still works if you come back later; use Delete this result to remove it sooner. Nothing you upload is ever published.

The first 2 pages a day are free, with the balance checks, and you can copy every row you see. That is enough to see whether the tool reads your bank's layout correctly before you pay anything.

Past that, pages are $0.25 each (5 credits, at the $5-pack rate), and a statement with paid pages gets every download free: Excel, CSV, QBO, QFX, QIF and OFX. With the two free pages still available, a six-page statement costs 20 credits for the other four pages, workbook included. If you have no credits, the smallest purchase is $3 for 50 credits, before any applicable tax; the statement uses $1.20 of it and 30 credits remain. A statement that fits inside the free pages pays only for its download: 4 credits for the workbook, 2 for the other formats, once per job. Credits never expire, there is no subscription, and a job that fails is not charged.