It's 10pm on a Wednesday. Your client's VAT return is due on Friday and you've just received the final bank statement — a PDF from HSBC Business. You open Google Sheets, create a fresh tab, and start copying transactions line by line from the PDF. By row 37, the dates have rearranged themselves into American format. By row 52, a multi-line description has split across three cells and thrown every subsequent row out of alignment. You delete the sheet and start again. It's now 10:40pm and you've made zero progress.
If this sounds familiar, you already know the score: Google Sheets is brilliant for UK bookkeeping — until you need to get a bank statement into it. CSV imports that scramble your dates. PDF copy-paste that produces unreadable gibberish. Amount columns that Google Sheets refuses to recognise as numbers. And that's before you even begin the reconciliation.
Google Sheets shouldn't be this hard. It's free, it's collaborative, it's accessible from any device, and thousands of UK sole practitioners, bookkeepers, and small accounting firms use it as their primary bookkeeping tool. But when RocketStatements published their Google Sheets import guide on July 22nd, they confirmed what many of us already suspected: there's a real, underserved audience of UK bookkeepers who need practical, step-by-step help getting bank statements into Google Sheets — not a five-minute YouTube tutorial that glosses over the formatting chaos that actually happens.
This guide covers everything: CSV import settings that work for UK bank formats, the PDF-to-Sheets conversion methods that don't waste your evening, the specific Google Sheets formatting fixes for bank data, formulas that automate reconciliation, and the tool that turns a 45-minute copy-paste ordeal into a 60-second upload. Whether you're a sole trader doing your own books, a bookkeeper managing multiple client spreadsheets, or an accountant who uses Sheets for ad-hoc analysis, you'll find the workflow that gets you home before 11pm.
Stop spending your evenings fighting with spreadsheet formatting. Here's how to import bank statements into Google Sheets properly.
Why UK Bookkeepers Use Google Sheets for Bank Statements
Before we dive into the how, let's address the why. Google Sheets isn't the obvious choice for bank statement processing — Xero, QuickBooks, and Sage dominate the conversation. But for a surprisingly large group of UK bookkeepers and accountants, Google Sheets is the tool that's actually open on their screen at 10pm.
Free, Accessible, and Already Installed
The maths is straightforward: Xero starts at £16/month, QuickBooks from £14/month, Sage from £12/month. For a sole practitioner with five clients, that's a manageable expense. For a bookkeeper with a dozen micro-business clients — each of whom might process 15-30 transactions a month — paying for full accounting software for every client is hard to justify. Google Sheets costs nothing. It works on any device with a browser. And it's already installed the moment you create a Google account.
Built for Collaboration
Unlike desktop Excel files that bounce between email inboxes as attachments, Google Sheets lets you and your client view the same data simultaneously. Your client uploads their bank statement CSV into a shared folder. You open it, format it, reconcile it. They can see your notes and adjustments in real time. No version control nightmares. No "which file is the latest one?" confusion. For bookkeepers working remotely with clients across the UK, this alone is worth the switch.
Flexibility That Accounting Software Doesn't Offer
Accounting software enforces a specific structure. That's useful for standard bookkeeping but frustrating when you need something bespoke — a custom cash flow forecast, a rental income schedule by property, a CIS deduction tracker. Google Sheets gives you complete freedom to structure your data how you need it. You can import bank statements into one tab, run your analysis in another, and build client-facing summaries in a third — all in one file, with no software-enforced constraints.
The Reality Check
Google Sheets' strength — flexibility — is also its weakness. Unlike Xero or QuickBooks, which have bank feed integrations that pull transactions automatically, Google Sheets gives you a blank grid. Every transaction must be imported, formatted, and verified manually. The flexibility is the point. The manual overhead is the price. The trick is knowing the import methods that minimise that overhead.
Method 1: Import Bank Statement CSV into Google Sheets (Step by Step)
The CSV import method is the simplest approach — when your bank provides a CSV download, and when that CSV is well-formatted. Unfortunately, "well-formatted bank CSV" is a phrase that makes experienced UK bookkeepers laugh. Let's walk through the process, including the cleanup steps that actually make it work.
Download the CSV from Your Bank
Log in to your (or your client's) online banking. Navigate to the account and statement period you need. Look for an export or download option — it's usually labelled "Export," "Download transactions," or "Save as."
- Most UK high-street banks offer CSV export: Barclays, Lloyds, NatWest, Santander, Halifax, TSB, and Monzo all provide CSV downloads for personal and business accounts.
- HSBC Business and Nationwide Business are the notable exceptions — both provide PDF statements only for business accounts, with no CSV option. If your client banks with either, skip to Method 2 (PDF conversion).
- Challenger banks (Starling, Revolut, Tide) generally provide clean CSV exports. Starling's CSV output is particularly well-formatted — one of the few UK banks that doesn't need significant cleanup before Google Sheets import.
Critical: Always download the full statement period as one file. Downloading transactions month by month means you'll need to merge multiple CSVs later, which introduces its own formatting headaches.
Import the CSV into Google Sheets
Open Google Sheets and create a new blank spreadsheet (or open your existing client workbook). Then:
- File > Import > Upload — drag your CSV file or browse to it.
- In the import dialogue, under "Import location," choose "Replace current sheet" for a fresh start, or "Append to current sheet" if you're adding to existing data.
- Under "Separator type," select "Detect automatically" — Google Sheets usually gets this right. But if your import looks wrong (everything in one column), try again with "Comma" or "Semicolon" (Santander sometimes uses semicolons).
- Leave "Convert text to numbers, dates, and formulas" set to "Yes."
- Click "Import data."
At this point, you'll either see something that looks approximately correct — or a mess. Honestly, it's usually the latter. The next two steps are where the real work happens.
Fix the Formatting (The Step Nobody Talks About)
Bank CSVs rarely import cleanly into Google Sheets. Here's what to check and how to fix each issue:
- Dates are wrong: If dates display as US format (month/day/year instead of day/month/year), go to File > Settings > Locale and set it to United Kingdom. Then reselect the date column and go to Format > Number > Date. If dates are still wrong, they may be stored as text — you'll need to convert them (see the formatting issues section below).
- Amounts display as text: If numbers are left-aligned and won't sum, Google Sheets hasn't recognised them as numbers. Select the column, use Ctrl+H (Find and replace) to remove any £ signs and comma separators. If amounts contain trailing spaces or invisible characters, use =VALUE(TRIM(CLEAN(A2))) in a helper column to force conversion.
- Multi-line descriptions split across rows: Many bank CSVs wrap long transaction descriptions across two or more rows. The continuation rows have no date and no amount. Google Sheets imports these as separate, incomplete rows. Merge them manually using =TEXTJOIN(" ", TRUE, B2:B4) or delete the continuation rows if they contain redundant information.
- Extra header rows: Some banks (Lloyds is a regular offender) include account summary info or blank rows before the actual column headers. Delete everything above the first proper header row, then reapply column formatting.
- Decimal inconsistency: Some transactions show as whole numbers (250) and others as decimals (250.00) in the same column. Select the column and apply Format > Number > Custom number format > #,##0.00 to standardise.
Realistic time: 15-25 minutes for a 100-transaction statement. Less for Starling and Monzo (clean CSVs). More for Lloyds and Barclays business accounts (extra rows, description splits).
Verify the Imported Data
Before you do anything else, sanity-check your data against the original statement:
- Transaction count: Does the number of data rows match the statement? Count the rows (excluding headers) and compare.
- Total credits and debits: Use =SUM() on your Money In and Money Out columns. The net (credits minus debits) should roughly match the difference between the statement's opening and closing balance. If it's way off, something went wrong during import.
- Spot-check 5 random rows: Open the original bank statement and compare the date, description, and amount of 5 transactions directly against your Google Sheets data. If even one doesn't match, there's a structural problem that needs fixing.
Five minutes of verification now saves you from a reconciliation disaster later — especially at month-end when the trial balance doesn't balance and you can't find the error because you didn't spot-check the import.
Method 2: Import PDF Bank Statements into Google Sheets
This is the workflow that causes the 10pm frustration. When your client's bank only provides PDF statements — and HSBC Business, Nationwide Business, Virgin Money, and most building societies all fall into this category — you have three options. Only one of them is fast.
Manual Copy-Paste (The "I'll Just Do It Quickly" Lie)
Open the PDF, select the transaction table, copy, paste into Google Sheets. What happens next is predictable: dates split across cells, multi-line descriptions become separate rows, amounts lose their decimal points, and the whole thing looks like someone dropped a filing cabinet down a staircase.
Time: 30-60 minutes per statement. Accuracy: Low — you'll miss things. Recommended? Only for statements with fewer than 10 transactions. Beyond that, the cleanup time exceeds every other method.
Adobe Acrobat or Free PDF-to-Excel Converters
Export the PDF to Excel (using Acrobat Pro or a free online converter), then upload the resulting Excel file into Google Sheets. This gets you about 60-70% of the way — the transaction table is roughly intact, but:
- Multi-line descriptions still split across rows
- Dates may be garbled (grouped date headers from HSBC statements are particularly bad)
- Running balance columns often misalign
- Scanned statements (image-based PDFs) produce nothing at all — OCR tools embedded in PDF readers are not designed for statement extraction
Time: 20-35 minutes per statement (including cleanup). Accuracy: Moderate — you still need to review every row. Recommended? Acceptable if you're doing one statement a month. Painful if you're doing three a day.
BankScan AI — 60 Seconds from PDF to Google Sheets-Ready File
BankScan AI was built specifically for UK bank statement PDFs — the exact formats that break generic converters. Upload any UK bank PDF and download a clean Excel or CSV file that imports perfectly into Google Sheets:
- 16+ UK bank formats: Trained on HSBC Business (grouped dates, multi-column layouts), Nationwide (running balance quirks), Barclays, Lloyds, NatWest, Santander, Monzo, Starling, Revolut, and more.
- Automatic formatting: Dates output as DD/MM/YYYY, amounts as clean numbers with no £ signs or commas, multi-line descriptions merged into single rows, grouped date headers filled in.
- OCR for scanned statements: Image-based PDFs (photographed or scanned paper statements) are processed with OCR — manual copy-paste produces nothing on these files.
- Colour-coded confidence: Every transaction is flagged green (high confidence), amber (review suggested), or red (needs attention) so you know where to focus your review time.
Time: Under 60 seconds. Accuracy: High — trained on real UK bank statement layouts. Recommended? If you process more than one PDF statement a month, this is the only method that doesn't eat your billable hours. Free first conversion, no credit card needed.
Common Google Sheets Formatting Issues with Bank Statements
Google Sheets is powerful, but its automatic type detection — the feature that tries to guess whether your data is a date, number, or text — is the single biggest source of bank statement import frustration. Here are the specific problems that catch people out, with the actual fixes.
❌ Date Format Chaos — UK Dates Become US Dates
This is the most common complaint in UK bookkeeping forums. You import a CSV with dates like 03/05/2026 (3rd May) and Google Sheets silently converts them to 5th March because your locale setting defaults to United States. Even worse, if some dates in your CSV are ambiguous (03/05 could be either) and others aren't (15/07 can only be day/month), Google Sheets applies different interpretations to different rows — and you won't notice until reconciliation doesn't balance.
❌ Amounts Displayed as Text — SUM() Returns £0.00
Bank CSVs frequently include £ symbols, comma separators (£1,250.00), or trailing text like "CR" and "DR" in amount columns. Google Sheets sees these as text strings, not numbers. The amounts look right visually, but =SUM() returns zero — and you don't notice until your totals don't match the statement.
❌ Multi-Line Transaction Descriptions Splitting Across Rows
This is the nightmare specific to PDF-to-Sheets conversion. A single bank transaction with a two-line description (e.g. "CARD PAYMENT TO AMAZON\nMARKETPLACE, LUXEMBOURG") becomes two rows in Google Sheets. The second row has no date, no amount, and just the continuation text. Your transaction count doubles, your totals break, and every single split row must be manually merged.
❌ Leading Zeros Disappearing from Account Numbers and Sort Codes
Sort codes like 04-12-36 become 4-12-36. Account numbers like 00123456 become 123456. Google Sheets treats numeric-looking strings as numbers and strips leading zeros — a problem when you're using sort codes and account numbers for reference or reporting.
❌ Google Sheets Auto-Formatting Transaction References as Dates
Some bank transaction references look like dates to Google Sheets. A reference like "MAR26" or "JAN1" gets auto-converted to a date, replacing your useful reference with something like "01/03/2026." This is rare but infuriating when it happens because you don't expect it.
How to Automate Bank Statement Import into Google Sheets
The manual CSV import → format → verify workflow works, but repeating it every month for every client is where the time disappears. Here's how to build a repeatable system that handles the heavy lifting.
Step 1: Standardise Your Source Data
The root cause of most Google Sheets import problems isn't Google Sheets — it's the inconsistency of bank statement formats. Every bank formats statements differently. Every CSV export has its own quirks. You can't build an efficient Google Sheets workflow on top of wildly inconsistent input data. Standardise first:
- All bank statements → one clean format: Use BankScan AI to convert any bank statement — PDF, CSV, or scanned image — into a clean, consistently formatted Excel or CSV file. Same column structure, same date format, same cleaned amounts, regardless of which bank the statement came from. This step alone eliminates 80% of your Google Sheets formatting work.
- Save to a shared Google Drive folder: Keep all converted statements in a client-specific folder structure (e.g. /ClientName/BankStatements/2026/07-July/). Consistent file naming (e.g. "2026-07_Barclays_Business.csv") makes them easy to find and import.
Step 2: Use =IMPORTRANGE() for Multi-Sheet Workbooks
If you maintain a master Google Sheets workbook with separate tabs for each month's bank statements, use =IMPORTRANGE() to pull cleaned data from your source files rather than copying and pasting:
=IMPORTRANGE("https://docs.google.com/spreadsheets/d/xxxxx", "Sheet1!A:F")
This links your analysis sheet to the source data — when you update the source, the analysis updates automatically. No manual re-import. No version control issues.
Step 3: Build a Google Sheets Template That Works Every Time
Create a master Google Sheets template with pre-configured formatting, formulas, and conditional formatting rules. Each month, copy the template, import your standardised bank data into it, and skip the setup. Your template should include:
- Pre-formatted columns: Date (DD/MM/YYYY), Description (text), Money In (£#,##0.00), Money Out (£#,##0.00), Category (text), Reconciled (checkbox).
- Header row with =SUM() totals: Below your column headers (or in a frozen top section), add =SUM() for Money In and Money Out so you can instantly verify totals against the bank statement.
- Conditional formatting: Green fill for Money In > 0, red fill for Money Out > 0, amber fill for rows where the Reconciled checkbox is unchecked.
- Data validation dropdowns: Add a dropdown list for the Category column (e.g. Sales, Expenses, Bank Charges, Director Loan, VAT) using Data > Data validation.
With standardised input data and a pre-built template, a monthly bank statement import that used to take 45 minutes becomes a 5-minute process: download from BankScan AI → import into Google Sheets template → verify totals → start reconciling.
Bank Statement Analysis in Google Sheets
Getting the data into Google Sheets is only half the job. Once it's there, clean and properly formatted, Google Sheets' analysis tools turn raw transactions into useful insight.
Pivot Tables for Income and Expenditure by Category
Once you've added a Category column to your imported transactions (even a rough one — "Sales," "Expenses," "Bank Charges," "Director Loan," "VAT"), create a pivot table (Data > Pivot table) to see totals by category. Set Category as the rows, Money In and Money Out as the values (summarised by SUM), and you have an instant income/expenditure breakdown. Add a month column (extracted from the date using =TEXT(A2,"YYYY-MM")) as a column field to see trends over time.
Charts That Clients Actually Understand
Most clients' eyes glaze over at rows of spreadsheet data. A simple chart communicates the same information in seconds:
- Monthly income vs expenditure bar chart: Select your pivot table, Insert > Chart, choose "Column chart." One glance tells a client whether they're spending more than they're earning.
- Bank balance over time line chart: Plot the running balance column against the date column. Shows the cash flow story — the dips before VAT payments, the peaks after client invoices are paid.
- Expense breakdown pie chart: Summarise Money Out by category in a pivot table, then create a pie chart. Clients see at a glance where their money is going.
Automated Reconciliation with =VLOOKUP() and Conditional Formatting
If you maintain accounting records (or a cash book) in a separate sheet within the same workbook, you can automate the reconciliation check:
- In your bank statement sheet, add a "Matched" column.
- Use =IF(ISNA(VLOOKUP(A2, 'AccountingRecords'!$A$2:$B$500, 2, FALSE)), "UNMATCHED", "MATCHED") where A2 is the bank transaction amount and AccountingRecords contains your internal transaction records.
- Apply conditional formatting: any row with "UNMATCHED" in the Matched column gets a red border or amber fill.
- Filter to show only unmatched rows — these are the transactions that need investigation.
This takes 10 minutes to set up once and saves 30 minutes of manual cross-referencing every month thereafter.
Cash Flow Forecasting with =SUMIFS()
Once you have a few months of categorised bank data in Google Sheets, forecasting becomes practical:
=SUMIFS(MoneyOut, Category, "Rent", Date, ">="&DATE(2026,1,1), Date, "<="&DATE(2026,1,31))
This formula sums all rent payments in January 2026. Extend the date ranges across future months and you have a basic cash flow forecast built entirely in Google Sheets — no forecasting software required.
Google Sheets vs Accounting Software for Bank Statements: What's Actually Faster?
The honest comparison, based on how UK bookkeepers actually work:
| Factor | Google Sheets | Xero / QuickBooks / Sage |
|---|---|---|
| Cost | Free | £12-£38/month per licence |
| Bank feed (auto-import) | ❌ None — manual import only | ✅ Open Banking feeds for most major banks |
| PDF statement handling | Requires external conversion | Requires external conversion (no platform accepts PDFs directly) |
| Unsupported bank handling | Same workflow for all banks — CSV import | Manual CSV import — same as Google Sheets |
| Flexibility | Complete — any structure, any formula, any chart | Constrained — must work within the platform's structure |
| Collaboration | Real-time, free, no licence for viewers | Varies — usually requires a paid account to access data |
| MTD compliance | Manual — no direct HMRC submission | Built-in MTD for VAT and MTD for Income Tax reporting |
| Time per statement (CSV available) | 15-25 mins (formatting + import) | 5-10 mins (feed auto-imports, CSV cleanup still needed) |
| Time per statement (PDF only) | 30-45 mins (conversion + formatting + import) | 25-40 mins (conversion + formatting + import — PDFs affect all platforms equally) |
| Best for | Sole traders, micro-businesses, ad-hoc analysis, bookkeepers with cost-sensitive clients | VAT-registered businesses, growing firms, practices needing MTD compliance and audit trails |
The pattern is clear: Google Sheets wins on cost and flexibility. Accounting software wins on automation and compliance. The smart workflow for many UK bookkeepers is to use both — Google Sheets for analysis, reporting, and client-friendly summaries, with the raw bank data standardised by BankScan AI before it enters either system.
How BankScan AI Makes Google Sheets Bank Statement Imports Actually Fast
If you've read this far, the pattern is clear: the bottleneck in every Google Sheets bank statement workflow isn't Google Sheets itself — it's the inconsistent, poorly formatted data coming from UK banks. Fix that input, and everything downstream gets faster.
BankScan AI solves the input problem. Here's the workflow that takes your Google Sheets bank statement imports from 45 minutes to 60 seconds:
- Upload any bank statement: PDF, CSV, or scanned image — from any UK bank. BankScan AI's models are trained on the specific statement layouts of 16+ UK banks, including the formats that break generic converters: HSBC Business grouped dates, Nationwide running balance layouts, Barclays multi-line descriptions, and building society statement quirks.
- Download a clean file: In under 60 seconds, get an Excel or CSV file with properly formatted DD/MM/YYYY dates, single-line descriptions, clean numeric amounts with no symbols or commas, and consistent decimal formatting throughout. No manual cleanup needed.
- Import directly into Google Sheets: File > Import > Upload. The data arrives clean. Dates import correctly. Amounts sum immediately. No manual formatting fixes. No hunting for split description rows. Just clean, ready-to-use bank data.
- Batch processing for multiple statements: Upload statements for multiple clients or multiple months in one session. BankScan AI processes everything in parallel and returns individually formatted files — no merging, no cross-contamination.
What BankScan AI Does
- Outputs clean Excel/CSV formatted for Google Sheets — DD/MM/YYYY dates, single-line descriptions, numeric amounts
- Handles all 16+ UK bank formats from one upload screen — no bank-specific formatting knowledge required
- Colour-coded confidence indicators — green (OK), amber (review), red (needs attention) on every transaction
- Merges multi-line descriptions automatically — the single biggest time-saver for PDF-to-Sheets conversion
- OCR for scanned and image-based statements — no manual typing from photographed paper statements
- GDPR-compliant — UK-based infrastructure, encrypted, no permanent data storage after processing
- Free first conversion — test it with a real client statement, no credit card needed
What It Does Not Do
- Direct integration with Google Sheets (you download the file and import it — the import step takes 10 seconds)
- Automatic transaction categorisation (you still apply categories within Google Sheets — but at least you're starting with clean data)
- Replace the need for accounting software for VAT-registered businesses (BankScan AI is a data preparation tool, not accounting software)
Stop Wrangling Bank Statement Data. Start Using It.
Upload any UK bank statement — PDF or CSV, from any bank — and get a clean, Google Sheets-ready Excel or CSV file in under 60 seconds. Handles all 16+ UK bank formats, multi-line descriptions, grouped dates, OCR for scanned statements, and column mapping automatically. Free first conversion, no credit card needed.
Try BankScan AI Free →Practical Checklist: From Bank Statement PDF to Clean Google Sheets Data
⬜ Before You Start
- Confirm you have the full statement period — not fragments from different downloads
- Note the statement's opening balance, closing balance, and date range for post-import verification
- Check your Google Sheets locale: File > Settings > Locale > United Kingdom
- If the statement is a PDF from HSBC Business, Nationwide Business, or a building society — prepare for conversion (CSV export not available for these banks)
⬜ Preparing the Data for Google Sheets
- If PDF: convert using BankScan AI (under 60 seconds) or your preferred PDF converter
- If CSV from the bank: open and check for multi-line description splits, extra header rows, and currency symbols in amount columns
- If scanned/image-based statement: use BankScan AI's OCR — manual copy-paste produces no usable data from image PDFs
- Confirm date column is consistently DD/MM/YYYY — no US dates, no ISO dates, no text dates
- Confirm amount columns are clean numbers — no £ signs, no comma separators, no "CR" or "DR" text
- Confirm one row per transaction — merge any multi-line description continuations into single rows
⬜ Importing into Google Sheets
- File > Import > Upload your cleaned file
- Separator type: Detect automatically (or Comma for CSV, leave default for Excel)
- Convert text to numbers, dates, and formulas: Yes
- After import: immediately check the first 5 rows of dates and amounts for correctness
- Apply column formatting: Date (DD/MM/YYYY), Amounts (£#,##0.00), Descriptions (plain text)
⬜ Post-Import Verification
- Transaction count: does it match the original statement?
- Sum credits and debits: does the net match the opening/closing balance difference?
- Spot-check 5 random transactions directly against the original bank statement
- Check for any rows with blank dates or amounts — these are likely broken description continuations
- If balance column was imported: verify the final row matches the statement's closing balance
UK Bank Format Compatibility for Google Sheets Imports
Not all UK bank statements are equally easy to get into Google Sheets. Here's the practical reference for the banks your clients use most:
| Bank | CSV Export Available? | Date Format (CSV) | Key Google Sheets Issue | Ease of Import |
|---|---|---|---|---|
| Barclays | ✅ Personal & Business | DD/MM/YYYY | Multi-line descriptions in business statements; extra header rows in some exports | 🟠 Moderate — needs cleanup |
| HSBC | ⚠️ Personal only; Business = PDF | DD/MM/YYYY (personal) | Business: no CSV export — PDF conversion required. Grouped dates, multi-column layouts in PDF | 🔴 Difficult — requires PDF conversion |
| Lloyds | ✅ Personal & Business | DD/MM/YYYY | Extra header rows; account summary info before column headers | 🟠 Moderate — needs header cleanup |
| NatWest | ✅ Personal & Business | DD/MM/YYYY | Column order varies by account type; some exports include transaction codes as extra columns | 🟠 Moderate — check column order |
| Santander | ✅ Yes | DD/MM/YYYY | Semicolon separators on some account types — Google Sheets may put everything in one column | 🟠 Moderate — check separator type |
| Nationwide | ⚠️ Personal only; Business = PDF | DD/MM/YYYY (personal) | Business: PDF-only, no CSV option. Personal: running balance column sometimes misaligns on import | 🔴 Difficult — PDF conversion for business |
| Monzo | ✅ Personal & Business | DD/MM/YYYY | Generally clean CSV — one of the most import-friendly UK banks | 🟢 Easy — minimal cleanup |
| Starling | ✅ Personal & Business | DD/MM/YYYY | Clean CSV export — imports with minimal formatting issues | 🟢 Easy — minimal cleanup |
| Revolut | ✅ Yes | DD/MM/YYYY | Multi-currency transactions — GBP amounts may be mixed with EUR/USD; filter before import | 🟠 Moderate — filter currency first |
| Tide | ✅ Yes | DD/MM/YYYY | CSV generally clean; occasional extra columns for transaction categories | 🟢 Easy — minor column removal |
| Metro Bank | ✅ Yes | Sometimes US format | Date format inconsistency — always verify before import; US dates silently corrupt data | 🔴 Check dates carefully |
| Virgin Money | ⚠️ Inconsistent | DD/MM/YYYY (when available) | PDF-only for many account types; limited CSV availability | 🔴 Difficult — often requires PDF conversion |
The mix of formats across a typical client base is exactly why standardisation matters. A BankScan AI account turns every one of these formats into the same clean, Google Sheets-ready output — regardless of whether the source was a clean Monzo CSV or a PDF from HSBC Business. Same process, same result, 60 seconds.
Frequently Asked Questions
Can I import PDF bank statements directly into Google Sheets?
No, not directly. Google Sheets does not parse PDF files — if you try to open a PDF, you'll get an error or a jumbled text dump. PDFs must be converted to Excel or CSV first. Manual copy-paste from PDF to Sheets works for very short statements (fewer than 10 transactions) but becomes unreliable beyond that. For regular PDF-to-Sheets workflows, BankScan AI converts any UK bank PDF to a clean, Google Sheets-ready file in under 60 seconds — including scanned and image-based statements that manual copy-paste cannot process at all.
Why does Google Sheets keep changing my bank statement dates to US format?
This happens because Google Sheets defaults to the United States locale, which interprets dates as MM/DD/YYYY. When your CSV contains a date like 03/05/2026 (3rd May), Sheets reads it as 5th March. The fix: go to File > Settings > Locale and set it to United Kingdom. This must be done before import — changing it afterwards does not retroactively fix dates that were already imported and corrupted. If your dates are already broken (day and month swapped), you'll need to manually correct them or re-import the file with the correct locale set.
How do I import multiple bank statements into one Google Sheets file?
Several approaches: (1) Use File > Import > Append to current sheet for each subsequent CSV — this adds new rows below existing data. Ensure all files have identical column headers before appending. (2) Import each statement into a separate tab within the same workbook, then use =QUERY() or ={Sheet1!A2:F; Sheet2!A2:F} to combine them into a single master tab. (3) Convert all statements to clean CSV using BankScan AI first, then combine the files into one CSV using a text editor or terminal (cat file1.csv file2.csv > combined.csv) — but remove the header row from all but the first file. (4) Use Google Apps Script for automated import and merging if you process high volumes regularly.
Can I link my bank account directly to Google Sheets for automatic imports?
Google Sheets does not have a built-in bank feed or Open Banking integration. There are third-party add-ons (like Tiller, BankStatementConverter, or SheetAI) that offer some level of bank connection or scheduled CSV import, but these typically work with US banks only and have limited or no UK bank support. For UK bank statements, direct automated import into Google Sheets is not currently available through Open Banking APIs. The closest you can get to automation is: standardise your bank statements with BankScan AI (60 seconds per statement), save to a Google Drive folder, and use =IMPORTRANGE() to pull data into your master analysis sheet. For true automated bank feeds, you need accounting software like Xero or QuickBooks that supports Open Banking.
Is Google Sheets suitable for HMRC-compliant bookkeeping?
Google Sheets can form part of a compliant record-keeping system, but with important caveats. Under MTD for VAT and MTD for Income Tax, HMRC requires digital records that are kept using functional compatible software. A Google Sheets spreadsheet on its own is not functional compatible software — it cannot submit directly to HMRC. However, you can use Google Sheets as your digital record-keeping system alongside bridging software that submits to HMRC, or export data from Sheets into MTD-compatible software for submission. For businesses not yet mandated for MTD for Income Tax (below the £50,000 threshold in 2026), Google Sheets is a practical, low-cost record-keeping tool, provided you maintain proper audit trails and retain original source documents. Read our MTD digital record-keeping guide for the full requirements.
What's the fastest way to get a PDF bank statement into Google Sheets?
The fastest method, end to end: (1) Upload the PDF to BankScan AI. (2) Download the clean Excel/CSV file (under 60 seconds). (3) In Google Sheets, File > Import > Upload the file. (4) Verify the first few rows of dates and amounts — they'll import correctly because the data is already standardised. Total time: under 2 minutes for a complete, formatted, verified bank statement import. The alternative — manual copy-paste or generic PDF converters — takes 30-45 minutes and still requires cleanup. If you process more than one PDF statement a month, the time difference alone justifies the workflow change.
Last updated: 25 July 2026. BankScan AI supports 16+ UK bank formats — read our UK bank statement formats guide or browse our complete import guides for Xero, QuickBooks, Sage, FreeAgent, KashFlow, and Iris.