To convert bank statements to Google Sheets, download each statement's activity from online banking as a CSV, set the spreadsheet's locale to match the bank's date format, then use File, Import with the comma separator. A PDF statement has no direct route into Sheets, so convert it to rows first and import the result.
Importing a bank statement CSV into Google Sheets
Importing a bank statement CSV into Google Sheets uses File, Import, which reads the file into a new or existing spreadsheet and splits each line at the separator you choose. A CSV download from online banking is the cleanest source, because every transaction is already one row with separate date, description and amount fields.
The Google Sheets help page on importing data sets lists the steps and options. The step list below follows it, with the choice to make at each point for a bank statement.
Step list: File, Import for a bank statement CSV
- Download the CSV from online banking. Pick one account and one period, such as checking XXXX-4821 for March 2026 (an example account).
- Open a spreadsheet in Google Sheets on a computer, and open or create the sheet for that account.
- Set the locale first if the bank uses a date order different from the spreadsheet's. The locale section below covers this.
- Click File, then Import. Choose the CSV. Google's page says the file must not be password-protected.
- Choose an import location. For a first month, choose Insert new sheets so the month gets its own tab. To add a later month under earlier ones, choose Append rows to current sheet, as long as the columns are in the same order.
- Choose the separator. Pick Comma for a CSV. Google's page also offers Detect automatically, Tab and Custom.
- Click Import.
- Check the result. Confirm dates sort in date order, the amount column adds up with SUM, and the row count matches the statement.
Google's page lists the file types Sheets imports, including .csv, .txt, .tsv, .xls and .xlsx. PDF is not on the list.
After import, delete any header or summary rows the bank added above the transactions. If you appended a second month, delete its repeated column headings as well.
Can Google Sheets read a bank statement PDF?
Google Sheets cannot import a bank statement PDF: PDF is not among the file types its import accepts. Google Drive can run text recognition on a PDF and open it as a Google Doc, but that route is built for text, not tables, so the statement's columns usually arrive as loose lines.
The Google Drive help page on converting PDF and image files to text gives the workaround: right-click the file in Drive, then select Open with, then Google Docs. The same page sets two limits that matter for statements. Files must be 2 MB or smaller, and "Lists, tables, columns, footnotes, and endnotes are not likely to be detected."
A bank statement is mostly a table. After the Docs conversion, a line of the transaction list may come through as one run of text, or the date, description and amount may land on separate lines. Rebuilding the columns from that text takes longer than starting from a CSV, and a dropped line is easy to miss.
The better route is to turn the PDF into rows first, in a tool that keeps the table, then import that CSV or Excel file into Sheets. The steps for that conversion are in converting the bank statement PDF to Excel step by step. Schema CPA can also take the PDFs a client sends and export each statement's transactions as a CSV, which File, Import then reads like any bank download.
Google Sheets locale settings for bank statement dates and amounts
A Google Sheets spreadsheet's locale sets its default date, currency and number formats. A bank statement exported in day-month-year order, or with commas as decimal separators, needs a spreadsheet locale that uses the same conventions, or 04/05 and 1.250,00 will not mean what the bank meant.
The Google Sheets help page on locale and time zone gives the steps: open the spreadsheet, go to File, then Settings, choose a Locale in the General section, and save. Google says the change "changes the spreadsheet's default currency, date, and number formatting," and that it applies to the whole spreadsheet for everyone who uses it, without changing anyone's language setting.
Set the locale before importing, so the spreadsheet's conventions match the bank's from the first row. Fixing a column of misread dates after import means checking every row by hand, while choosing the locale first takes ten seconds.
A quick check after import uses three rows. Pick a row dated on the 13th or later of a month, such as 14/03/2026 for 14 March 2026, and confirm Sheets shows a real date. Pick a row with a negative amount and confirm it subtracts. Then add the amount column to the opening balance and compare the total with the statement's closing balance.
Mixed sources need care. A firm that keeps one sheet for a client's US checking account and another for an account at a bank in a day-month-year country should keep them in separate spreadsheets, each with its own locale, since locale is set per spreadsheet.
Is Google Sheets safe for client bank statements?
Whether Google Sheets is acceptable for client bank statements depends on the firm's own data policy and on how each spreadsheet is shared. A bank statement holds account numbers, balances, payees and spending patterns, so the sharing setting on the file matters as much as the tool.
The Google Drive help page on sharing files describes the settings to check. Under General access, Restricted means only people you have added can open the file, while Anyone with the link means anyone who has the link can use the file "without signing in to their Google Account." Each person added gets a role: Viewer, Commenter or Editor.
For client statements, Restricted access with named people is the setting that matches how most firms treat client files. The same Google page says owners can stop viewers and commenters from downloading, printing or copying, and that on a work or school account, an administrator may stop files from being shared outside the organization.
Firm policy comes first. If the firm's written policy requires client records to stay in specific systems, a personal Google account is the wrong place for them, however the sharing is set. How firms receive and hold client files is covered in the client portals and security category.
When Google Sheets is the wrong home for bank statements
Google Sheets is the wrong home for bank statements when the history is large, when the rows must feed Excel workpapers, or when several people rebuild the same tables by hand. In those cases Sheets adds a step the firm then has to undo, and converting directly to Excel or CSV saves the round trip.
Size is the first limit. The Google Drive help page on file size limits says spreadsheets created in or converted to Sheets can hold up to 20 million cells or 100 MB. A single client rarely reaches that, but a firm that keeps every client's multi-year history in one spreadsheet can.
Workflow is the more common reason. If the firm's tie-outs, lead sheets and adjusting entries all live in Excel, every Sheets file has to be downloaded and checked again after conversion. Card and loan statements add their own columns: the credit card statement to Excel guide separates charges, payments, interest and fees, and the loan statement to Excel guide splits each payment into principal, interest and escrow.
Sheets does suit some jobs well. A small client who keeps their own books in a shared spreadsheet, or a quick review of one month's activity, fits it. For a full year across several accounts, the workflow on the Schema CPA homepage shows statements collected, read, reconciled and exported to Excel or CSV in one pass.