How to Import Bank Statements into FreeAgent — Complete UK Guide (2026)

It is 10pm. You have a client's VAT return due tomorrow. FreeAgent's bank feed stopped syncing three weeks ago and nothing you do will bring it back. Now you are staring at a PDF bank statement, a blank spreadsheet, and the sinking realisation that your evening is about to disappear into manual CSV formatting.

If this sounds familiar, you are not alone. FreeAgent has over 150,000 UK users — mostly freelancers, contractors, and small business owners — and its bank feed is a genuine source of frustration. NatWest, RBS, and Mettle give FreeAgent to their business customers for free, which means there is a massive overlap between FreeAgent users and people whose bank feeds randomly stop working.

This guide covers every method of getting bank statements into FreeAgent in 2026: what the bank feed actually does, why CSV imports fail, how to fix them, and how to pre-clean bank statements from 22+ UK banks for seamless FreeAgent import.

Understanding FreeAgent's Bank Import Options

FreeAgent gives you three ways to get bank transactions into your account. Each has strengths and genuine limitations. Knowing which to use — and when — saves you from the 10pm panic scenario above.

1. Bank Feed (Open Banking)

FreeAgent's preferred method. When it works, transactions from your bank appear in FreeAgent automatically, usually within 24 hours. The feed uses Open Banking APIs to connect directly to your bank. It requires you to re-authorise the connection every 90 days, and this is where most problems start — missed re-authorisation means the feed goes silent. Some banks (notably Revolut, some business accounts, and certain building societies) do not support FreeAgent's bank feed at all.

2. Manual Statement Upload

FreeAgent accepts CSV, OFX, QIF, and TSV files. You download a statement from your bank's online portal, then upload it into FreeAgent. This is the fallback when the bank feed fails — and for many UK banks, it is the only option besides typing everything in by hand. The problem: each bank exports statements in its own format, and FreeAgent is picky about what it accepts.

3. Manual Entry

Typing transactions one at a time. For a business with three transactions a month, this is fine. For anyone with actual banking activity, it is a last resort.

Common FreeAgent Import Errors (and Why They Happen)

When a CSV upload fails in FreeAgent, the error message is rarely helpful. Here are the real reasons imports fail, based on what we see processing thousands of UK bank statements:

Date Format: DD/MM/YYYY or Nothing

FreeAgent insists on DD/MM/YYYY. If your CSV contains any other date format — YYYY-MM-DD (common in digital bank exports), MM/DD/YYYY (common in US-formatted tools), or mixed formats — the import will fail silently or assign transactions to the wrong dates. A statement dated 05/03/2026 should be 5 March. If your spreadsheet software has helpfully "corrected" it to 3 May, FreeAgent will import it as May, and your reconciliation will be a mess.

Column Mapping Confusion

FreeAgent expects columns in a specific order when it cannot automatically detect headers: Date, Description, Amount. If your CSV has columns in a different order — or has extra columns like running balance, transaction type codes, or bank reference numbers — FreeAgent will either reject the file or map amounts to the wrong column. The most dangerous scenario: FreeAgent reads the running balance column as the transaction amount, creating a reconciliation nightmare.

Multi-Line Transaction Descriptions

Several UK banks (HSBC, Barclays, Lloyds) wrap transaction descriptions across multiple lines in their PDF statements. When these are exported to CSV by generic tools, each line becomes its own row, producing phantom transactions with no amounts and descriptions split across cells. FreeAgent cannot process these mangled CSVs.

Amount Sign Confusion

FreeAgent expects positive values for money received (credits) and negative values for money spent (debits) in a single Amount column. Many banks export separate Credit and Debit columns instead, which FreeAgent does not handle natively. You must merge these into a single Amount column with correct positive/negative values before importing.

How to Prepare Bank Statements for FreeAgent Import

Here is the step-by-step process for getting any UK bank statement into FreeAgent, whether the bank feed is working or not:

1. Get your bank statement — Download it from your bank's online portal as a PDF or CSV. If your bank offers a "FreeAgent-compatible export" option, use it — but most do not. If you have a scanned or photographed paper statement, you will need OCR to extract the data first.
2. Convert to a clean CSV — If your bank exported a CSV directly, check the date format and column order against FreeAgent's requirements. If your bank only provides PDF statements, use BankScan AI's FreeAgent converter to extract the transactions into a properly formatted CSV. This step handles multi-line descriptions, date format correction, and Credit/Debit column merging automatically.
3. Verify the CSV — Open the CSV in a spreadsheet. Confirm that all dates are DD/MM/YYYY, the Amount column uses negative values for debits and positive for credits, there is no running balance column, and the total of transactions matches your statement's closing balance. This two-minute check prevents most import problems.
4. Upload to FreeAgent — In FreeAgent, go to Banking → Bank Accounts, select the relevant account, and click "Upload a Statement". Follow the prompts to map columns if FreeAgent does not auto-detect them, then review the imported transactions before confirming.

For bulk processing — if you handle multiple client accounts or several months of statements — BankScan AI's batch converter processes multiple statements at once and outputs FreeAgent-ready CSVs for all of them in a single workflow.

Bank-Specific FreeAgent Import Challenges

Every UK bank exports statements differently. Here is what to watch for with the banks most commonly used by FreeAgent customers:

NatWest / RBS / Mettle

These banks are the trio that offer FreeAgent free to business account holders, so their users are disproportionately affected by import problems. NatWest's bank feed through FreeAgent is generally reliable, but when it fails, the CSV exports from NatWest's online banking platform include a Running Balance column that FreeAgent frequently misinterprets as the transaction amount. Remove this column before importing. Mettle (NatWest's digital business account) does not offer CSV downloads in-app — you must use the web portal.

Monzo (17-Column CSV)

Monzo exports CSVs with 17 columns. FreeAgent needs 3. Every column beyond those three — category, merchant ID, local currency amount, notes and tags, receipt URL — is a potential source of mapping errors. Monzo's CSV needs significant column pruning before FreeAgent will accept it, and the Date column must be reformatted from Monzo's default ISO format to DD/MM/YYYY.

HSBC (Multi-Line Descriptions)

HSBC statements wrap transaction descriptions across multiple lines. Converting HSBC statements for FreeAgent import means merging these lines back into single transactions, which generic tools consistently fail to do. HSBC also uses DD/MM/YYYY dates by default (good for FreeAgent) but some CSV exports add a timestamp suffix that must be stripped.

Barclays (Invisible Formatting Characters)

Barclays PDF statements contain embedded control characters that survive conversion into CSV. These invisible characters cause FreeAgent to reject the file entirely, often with no clear error message. Cleaning Barclays statements requires stripping these characters before FreeAgent will accept the CSV.

Revolut (Multi-Currency Statements)

Revolut statements are uniquely challenging for FreeAgent because transactions may be in multiple currencies, with both an original currency amount and a GBP equivalent. Importing Revolut into FreeAgent means deciding which amount to use (GBP equivalent is usually correct for UK tax reporting) and stripping the extraneous currency columns that FreeAgent cannot process.

Method Comparison: Getting Bank Statements into FreeAgent

Manual CSV formatting is free in cash terms but expensive in time — at UK bookkeeping rates of £25–£45/hour, a 30-minute CSV formatting job costs between £12.50 and £22.50 in billable time. For a freelancer doing their own books at 10pm, it is even worse: every hour fixing CSV formatting is an hour you cannot bill to a client.

Frequently Asked Questions

Can I import a scanned bank statement PDF into FreeAgent?

FreeAgent cannot read PDF bank statements directly — it only accepts CSV, OFX, QIF, or TSV files for statement imports. To import a scanned or PDF bank statement into FreeAgent, you must first convert the PDF to a FreeAgent-compatible CSV using a tool with OCR capability. BankScan AI extracts transaction data from scanned and digital bank statement PDFs and outputs a clean CSV formatted specifically for FreeAgent's import requirements.

What CSV format does FreeAgent require for bank statement imports?

FreeAgent expects a CSV with columns in this order: Date (DD/MM/YYYY), Description, Amount. The Amount column should use positive values for money in and negative values for money out. Do not include a running balance column — it is the single most common cause of import failures. Headers are optional but if included should match FreeAgent's expected names. BankScan AI's FreeAgent CSV export formats to this specification automatically.

Why has my FreeAgent bank feed stopped working?

FreeAgent bank feeds use Open Banking and require re-authorisation every 90 days. When the feed stops, it's usually because the 90-day consent period expired, the bank updated its security and needs a fresh connection, or the bank's Open Banking API is experiencing an outage. Go to Banking → Bank Accounts → select the account → Reconnect. If the feed remains unreliable — or your bank does not support it — CSV import is the most reliable fallback.

How do I fix the date format error when importing into FreeAgent?

This is the #1 cause of FreeAgent import failures. FreeAgent requires DD/MM/YYYY. If your CSV contains YYYY-MM-DD (common in digital bank exports) or MM/DD/YYYY (common with US-formatted tools), FreeAgent will reject it or assign wrong dates. Open your CSV, ensure every date cell uses DD/MM/YYYY, and check that 05/03/2026 stays 5 March (not 3 May) before saving. BankScan AI handles date formatting automatically for every supported UK bank.

Is my bank data secure when using a third-party converter for FreeAgent imports?

It depends entirely on the tool. Free online converters often store uploaded files on their servers with no clear data retention policy — a genuine UK GDPR risk when the files contain account numbers, sort codes, and full transaction histories. BankScan AI encrypts all data in transit and at rest, automatically deletes files after processing, and is designed specifically for handling sensitive UK financial documents. Always check the privacy policy before uploading client financial data to any service.

Last updated: 5 June 2026. Have a question about importing bank statements into FreeAgent? Visit BankScan AI or read our other guides for UK accountants.