Home › Blog › Import Bank Statements into Capium

Import Bank Statements into Capium Accounting Software — Complete UK Guide (2026)

23 July 2026 · 11 min read · BankScan AI Team

It's 10pm. Your office phone stopped ringing hours ago, but your monitor is still glowing. Capium is open on one screen — client ledgers waiting for you. On the other screen, a stack of bank statement PDFs from clients who bank somewhere Capium's feed doesn't reach. You've already spent the last forty minutes retyping transactions from one PDF into a CSV, cross-referencing each amount against the original statement. And you haven't even started on the next client yet.

If this scene feels uncomfortably familiar, you're far from alone. Capium is one of the UK's most widely used cloud accounting and practice management platforms — purpose-built for small-to-mid accounting practices that need accounts production, tax, company secretarial, and practice management in one place. Thousands of UK firms run their entire practice on Capium. And yet, when you search online for practical help on importing bank statements into Capium, there's surprisingly little out there. Guides for Xero and QuickBooks are everywhere. Capium? Almost silent.

That's a problem, because Capium's bank import process — while functional — has sharp edges. The bank feed doesn't cover every UK bank (building societies, we're looking at you). PDF statements are a non-starter. And the CSV format has to be just so or the import fails without telling you exactly why. When you're processing client statements at the end of a long day, those rough edges are what turn a five-minute task into an hour-long ordeal.

This guide covers every method for importing bank statements into Capium — the bank feed, manual CSV imports, the exact formatting Capium expects, the errors that catch people out, and how to automate the whole process so you stop losing evenings to data entry. Whether you're a sole practitioner with a handful of Capium clients or a growing firm processing hundreds of statements a month, you'll find something here that gets you home before 11pm.

Every hour spent manually typing bank transactions into Capium is an hour you're not billing clients. Let's fix that.

Why Capium Users Struggle with Bank Statement Imports

Before we get into the step-by-step, it's worth understanding why Capium bank imports cause so much late-night frustration. Capium is a genuinely well-designed practice management system — it handles the full workflow from client onboarding through accounts production to tax filing. But its bank import functionality was built as part of that broader system, not as a standalone bank-feed-first platform the way some newer cloud-only tools were. The result: when the feed works, it's fantastic. When it doesn't, you're on your own.

The Bank Feed Gap Nobody Talks About

Capium's bank feed covers most major UK high-street banks — Barclays, HSBC, Lloyds, NatWest, Santander, TSB, and the other usual names. But the coverage has gaps, and those gaps have a nasty habit of being exactly the banks your clients actually use:

Capium users on UK bookkeeping forums consistently raise the bank feed coverage gap as their number one import pain point. One user put it bluntly: "Capium bank feed is great for Barclays and NatWest clients. The moment a client banks with Nationwide, I'm back to 1998 — manually retyping transactions from a PDF."

The PDF-Only Problem

Many UK banks — particularly for business accounts — provide statements exclusively as PDFs. HSBC Business, Nationwide Business, Virgin Money, and most building societies fall into this category. Capium does not accept PDF bank statements directly. You must convert them to CSV first — and that conversion step is where the time disappears.

The CSV Formatting Minefield

Even when you manage to get a CSV from the bank, Capium is particular about how that CSV should look. Date formatting, column ordering, decimal handling, multi-line descriptions — any one of these being wrong can cause the import to fail, and Capium's error messages won't always tell you what needs fixing. You're left staring at a failed import, trying to guess which of the five possible formatting problems tripped you up.

Reality check: A typical small Capium practice with 25 clients might deal with 8-10 different banks across those clients. Capium's bank feed covers perhaps half of those reliably. The other half — that's your manual import workload. If you process three unsupported-bank statements a week at 25 minutes each, that's 65 hours a year of unbillable CSV formatting. That's over a week and a half of your working year — spent not on client work, not on practice development, not on anything billable. Just formatting spreadsheet columns so Capium will accept them.

Step-by-Step: Importing Bank Statements into Capium

Let's walk through the actual import process — from receiving a client's bank statement to seeing clean, reconciled transactions in Capium. Follow these steps in order and you'll dodge the most common frustrations.

1

Get the Bank Statement in Digital Form

Access your client's online banking (or request the statement from them). Navigate to the account and statement period you need. Look for an export option:

Practice tip: For recurring clients, get read-only access to their online banking. It eliminates the monthly email chase for statements, keeps you GDPR-compliant with direct auditable access, and lets you download statements the moment they're available — rather than waiting for the client to remember.

2

Convert PDF Statements to CSV

Capium does not accept PDF bank statements directly. If your client's bank only provided a PDF — and this is the case for the majority of UK business accounts — you must convert it to CSV first. Your options:

3

Format the CSV for Capium

This is the step that makes or breaks your import. Capium expects a clean, flat CSV with these characteristics:

Save as CSV UTF-8 — not CSV Macintosh or CSV MS-DOS, which can introduce encoding issues. Double-check there are no empty rows, no merged cells, and the header row appears exactly once at the top.

Time reality: Manual CSV formatting for a 100-transaction statement takes about 15-25 minutes. With BankScan AI, formatting is automatic — under 30 seconds for any UK bank format, with all dates, descriptions, and amounts correctly structured for Capium.

4

Import the CSV into Capium

In Capium, navigate to the client's bank transactions area. The exact path depends on your Capium module, but you'll typically find the import function under the bank screen or transaction entry screen. Look for "Import Bank Statement" or "Import Transactions."

The Capium import process will guide you through:

Critical: Capium typically shows an import preview before finalising. Read every value in that preview. If a date displays as an error, if amounts look off, or if descriptions are truncated — cancel and fix your CSV. Undoing a bad import is dramatically harder than catching it at the preview stage.

5

Verify the Imported Transactions

After the import completes, do a quick sanity check before you move on to reconciliation:

Two minutes of verification now saves you from a reconciliation nightmare later — especially at month-end when the trial balance doesn't balance and you can't trace the error because you didn't spot-check the import.

Common Capium Import Errors — and How to Fix Them

Capium error messages during import can be frustratingly generic. Here are the specific problems Capium users hit most often, with the fix for each one.

❌ "Date format not recognised"

Capium requires DD/MM/YYYY. If your CSV contains dates in US format (MM/DD/YYYY), ISO format (YYYY-MM-DD), or text-format dates like "15 March 2026", the import may either reject the file outright or — worse — silently swap the month and day so 03/05/2026 becomes 5th March instead of 3rd May.

✅ Fix: In Excel, select the date column. Go to Format Cells > Custom > Type: dd/mm/yyyy. Check that a date like 03/05/2026 is interpreted as 3rd May (UK), not 5th March (US). If dates are stored as text, use =DATEVALUE() to convert before reformatting. Save as CSV UTF-8 and re-import.

❌ "Unexpected column mapping — cannot identify fields"

During the Capium column mapping step, if your CSV has extra columns the system doesn't expect, or column labels that don't clearly indicate what each column contains, Capium may fail to auto-detect the mapping and either reject the file or require manual mapping intervention.

✅ Fix: Strip your CSV down to essential columns: Date, Description, Money In, Money Out, and optionally Balance. Remove any extra columns from the bank's export — transaction type codes, branch references, cheque numbers, sort codes — that Capium doesn't need. Keep the header row clean with clear labels.

❌ "Duplicate transaction detected — import blocked"

Capium checks incoming transactions against existing entries using date, amount, and description matching. If you're re-importing a corrected CSV after a failed first attempt, Capium may flag previously imported transactions as duplicates and block them — even though you need them imported.

✅ Fix: Before re-importing a corrected CSV, undo or delete the previous import from Capium's bank screen. If the previous import was partially successful, manually remove those transactions before re-importing the corrected file. For genuinely similar transactions (two payments of the same amount on consecutive days, for example), Capium should handle them without issue.

❌ "Amount fields contain non-numeric values"

If your CSV's amount columns contain £ signs, comma separators (£1,250.00), trailing text like "CR" or "DR", or inconsistent decimal formatting, Capium treats the values as text rather than numbers — and the import fails.

✅ Fix: In Excel, use Find & Replace (Ctrl+H) to remove all £ signs and commas from amount columns. Ensure every value in the column uses consistent decimal places (two decimal places is the safest). Verify Money In and Money Out columns contain positive numbers only — Capium captures debit/credit classification by which column the value is in, not by whether there's a minus sign. Save as CSV and re-import.

❌ "Transactions with missing dates or amounts"

When a bank statement has multi-line transaction descriptions, each description line becomes its own row in a manual CSV conversion — but those continuation rows have no date and no amount. Capium sees these as incomplete transactions and rejects them, or flags them as errors during import.

✅ Fix: In Excel, scan for rows that are description continuations (no date, no amount). Use TEXTJOIN or CONCATENATE to merge the continuation text into the previous row's description field. Delete the now-empty continuation rows. For long statements, this is the single biggest timesink — BankScan AI merges multi-line descriptions automatically for all 16+ UK bank formats in under 30 seconds.

Capium vs Other Accounting Software: Bank Statement Imports Compared

If your practice uses Capium alongside other tools — or if you're evaluating Capium as a new platform — it helps to see how its bank import stacks up honestly against the alternatives:

Feature Capium Xero QuickBooks Sage FreeAgent Iris
Bank feed (Open Banking) ✅ Major banks ✅ Broad coverage ✅ Broad coverage ✅ Via bank feeds ✅ Via Open Banking ✅ Major banks
Building society feed support ⚠️ Limited ⚠️ Limited ⚠️ Limited ⚠️ Limited ⚠️ Limited ⚠️ Limited
Challenger bank feed support ⚠️ Intermittent ✅ Good ✅ Good ⚠️ Intermittent ✅ Good ⚠️ Intermittent
CSV import flexibility 🟠 Moderate 🟢 Flexible 🟢 Flexible 🟠 Moderate 🟢 Flexible 🟠 Strict
PDF import supported ❌ No ❌ No ❌ No ❌ No ❌ No ❌ No
Date format accepted DD/MM/YYYY only DD/MM/YYYY, YYYY-MM-DD DD/MM/YYYY, MM/DD/YYYY DD/MM/YYYY (varies) DD/MM/YYYY, YYYY-MM-DD DD/MM/YYYY only
Multi-currency import ✅ Yes ✅ Yes ✅ Yes ✅ Yes ✅ Yes ✅ Yes
Bulk import (merge CSVs) ❌ No ❌ No ⚠️ Via apps ❌ No ❌ No ❌ No
Practice management integration ✅ Built-in ⚠️ Via Xero HQ ⚠️ Via QBOA ⚠️ Via Sage for Accountants ⚠️ Limited ✅ Built-in
Manual effort for unsupported banks 🟠 Moderate 🟠 Moderate 🟠 Moderate 🔴 High 🟢 Low 🔴 High

The pattern across every platform is the same: no accounting software accepts PDF bank statements directly, and every platform's bank feed has coverage gaps. Capium's import is workable but moderately strict about formatting — more prescriptive than Xero or FreeAgent, roughly comparable to Sage. Where Capium really shines compared to stand-alone bookkeeping tools is its practice management integration — bank imports flow directly into your broader workflow, from the client's bank screen through accounts production to tax. The key to a smooth Capium import experience is simply having your CSV correctly formatted before you hit upload. Get that right, and the rest falls into place.

Automating Capium Bank Statement Imports with BankScan AI

If you've read this far, you've probably noticed the theme: manual CSV formatting is the bottleneck in every Capium import workflow. Every bank formats statements differently. Every CSV export has its own quirks. And every time you sit down to import statements into Capium, you spend more time cleaning data than actually doing bookkeeping.

BankScan AI was purpose-built to eliminate that bottleneck for UK accountants and bookkeepers. Here's how it works specifically for Capium users:

How It Works

  1. Upload any bank statement: Drag and drop PDFs, CSVs, or scanned paper statements from any UK bank. BankScan AI's AI models have been trained on the statement layouts of 16+ UK banks — including the notoriously difficult formats from HSBC Business, Nationwide, and building society statements that cause the most Capium import headaches.
  2. Automatic formatting: The AI identifies the bank and statement layout, merges multi-line descriptions into single rows, fills in grouped date headers, separates debits and credits from running balances, and applies Capium-compatible formatting — all in under 30 seconds per statement.
  3. Download Capium-ready CSV: Export as CSV formatted exactly as Capium expects: DD/MM/YYYY dates, clean single-line descriptions, positive-only amount columns with no currency symbols, and consistent two-decimal-place formatting throughout.
  4. Batch processing: Upload statements for multiple clients or multiple months in one session. BankScan AI processes everything in parallel and returns individually formatted CSVs — no file merging, no cross-contamination between client data.

What This Means for Your Capium Practice

What BankScan AI Does

  • Outputs CSV formatted to Capium's exact requirements — DD/MM/YYYY dates, single-line descriptions, positive-only amounts
  • Handles all 16+ UK bank formats from a single upload screen — you don't need to remember which bank needs which formatting tweak
  • Colour-coded confidence indicators on every transaction — green (high confidence), amber (review suggested), red (needs attention)
  • Merges multi-line descriptions into single rows automatically — the single biggest time-saver for PDF-to-Capium conversion
  • Batch processing for multiple clients and multiple months — upload everything at once, download individually formatted CSVs
  • GDPR-compliant — UK-based infrastructure, encrypted in transit and at rest, no permanent data storage after processing
  • Free first conversion — no credit card needed, test it with a real client statement

What It Does Not Do

  • Direct API integration with Capium (Capium's API architecture does not support third-party bank transaction injection)
  • Automatic transaction categorisation in Capium — you still review and categorise within Capium's interface
  • Replace the Capium bank feed — where the feed works, keep using it; BankScan AI fills the gaps

For a practice with 25 Capium clients, the time maths is straightforward: if you manually format three statements a week for unsupported banks at 25 minutes each, that's roughly 65 hours a year gone to CSV formatting. With BankScan AI's 30-second processing, the same workload takes under five minutes total. The other 64+ hours go back to billable client work — or, realistically, getting home before 10pm.

Stop Formatting CSVs for Capium. Start Reconciling Client Accounts.

Upload any UK bank statement — PDF or CSV, from any bank — and get a Capium-ready CSV in under 30 seconds. Handles all 16+ UK bank formats, multi-line descriptions, grouped dates, and column mapping automatically. Free first conversion, no credit card needed.

Try BankScan AI Free →

Practical Checklist: From Client PDF to Reconciled Capium Transactions

⬜ Before You Start

⬜ Processing the Statement

⬜ Importing into Capium

⬜ Post-Import Verification

Golden rule for Capium imports: Never delete the original bank statement PDF after importing into Capium. File it in your practice management system alongside the imported data. If HMRC ever queries a specific transaction, you need the original source document — not just the imported records. BankScan AI does not store your data after processing, so your original PDF remains your single source of truth.

Formatting Bank Statements from Specific UK Banks for Capium

Different UK banks produce statements with different formatting quirks — and Capium needs consistent formatting regardless. Here's a practical reference for the banks your clients are most likely to use:

Bank CSV Export? Date Format Key Issue for Capium Import Readiness
Barclays ✅ Personal & Business DD/MM/YYYY Multi-line descriptions in business statements 🟠 Needs formatting
HSBC ⚠️ Personal only; Business = PDF DD/MM/YYYY Grouped dates, multi-line descriptions, embedded balance column 🔴 Requires conversion
Lloyds ✅ Yes DD/MM/YYYY Extra header rows in some CSV exports 🟠 Needs formatting
NatWest ✅ Yes DD/MM/YYYY Column order varies by account type 🟠 Needs formatting
Santander ✅ Yes DD/MM/YYYY Semicolon separators on some account types 🟠 Needs formatting
Nationwide ⚠️ Personal only; Business = PDF DD/MM/YYYY No CSV export for business — PDF conversion required 🔴 Requires conversion
Metro Bank ✅ Yes Sometimes US format Date format inconsistency — always verify before importing 🔴 Check dates
Monzo Business ✅ Yes DD/MM/YYYY Limited Capium feed; manual CSV import the standard path 🟠 Needs formatting
Starling Bank ✅ Yes DD/MM/YYYY Feed may work; CSV is a reliable fallback when it doesn't 🟢 Generally clean
Revolut Business ✅ Yes DD/MM/YYYY Multi-currency columns — Capium expects GBP-only or explicit currency mapping 🟠 Needs formatting
🔴 Red — Needs Conversion
PDF-only banks: HSBC Business, Nationwide Business, building societies. No CSV export available — must convert PDF to CSV before Capium import.
🟠 Amber — Needs Formatting
CSV available but needs cleanup: date format fixes, multi-line description merging, extra header removal, or column reordering for Capium compatibility.
🟢 Green — Direct Import
Clean CSV export or working Capium bank feed. Upload and go — minimal or no manual formatting required before Capium import.

The mix of bank formats across a typical practice is exactly why a universal converter matters. A Capium practice with 25 clients might deal with 8-10 different banks. Remembering each bank's specific formatting needs — and doing it manually every month — is where the hours evaporate. BankScan AI handles every one of these formats in a single tool. Upload whatever the client sends; get back a Capium-ready CSV every time.

Capium and the Bigger Picture: Bank Statement Automation in Your Practice

Getting bank statements into Capium efficiently isn't just about saving time on the current month's import. It's about the compounding effect across your entire practice workflow:

Month-End Close Acceleration

When bank statement data flows into Capium quickly and accurately, your entire month-end close accelerates. Bank statement automation at month-end means faster client reporting, earlier invoice issuance, and a practice that closes the books before the 15th — not scrambling into the 20th because manual imports held everything up.

Client Onboarding Speed

New client onboarding typically requires importing 6-12 months of historical bank statements — across multiple accounts and potentially multiple banks. Converting that volume manually can take days. With BankScan AI's batch processing, the same work completes in under an hour. Your new client sees a practice that's efficient, modern, and ready to go from day one.

Tax Season Resilience

January's self-assessment rush tests every practice's systems. When multiple clients send last-minute bank statements — in multiple formats, from multiple banks — the practice that can process them in minutes rather than hours is the practice that stays ahead of the deadline without burning out its staff. Read our guide on bank statement conversion during tax season for a full workflow breakdown.

Audit Trail Integrity

A clean Capium import — with every transaction properly dated, described, and categorised — creates an audit trail you can trust. When HMRC asks questions, you're not hunting through spreadsheets trying to reconstruct what happened. The data is where it should be, in the format it should be, backed by the original source documents. Our guide to HMRC audit preparation for bank statements covers this in more detail.

Frequently Asked Questions

Does Capium accounting software support automatic bank feeds?

Yes — Capium supports automatic bank feeds for a range of UK banks through its integrated bank feed functionality. Major high-street banks including Barclays, Lloyds, HSBC, NatWest, Santander, and TSB are generally well supported. However, coverage is not universal. Building societies including Nationwide often lack reliable feed support for business accounts. Challenger banks like Monzo and Starling have limited or intermittent business account connectivity. And some business current accounts restrict Open Banking access even at supported banks. When the Capium feed doesn't cover a specific bank — or when the 90-day re-authorisation expires — manual CSV import is the required fallback. Capium users on UK bookkeeping forums consistently cite the bank feed coverage gap as their top frustration, particularly for business accounts and building society clients.

What CSV format does Capium require for bank statement imports?

Capium requires a clean, flat CSV file with the following structure: Date in DD/MM/YYYY format (Capium is strict about UK date format — US dates and ISO dates cause errors), Description as a single line per transaction (no multi-line wrapping — continuation lines must be merged), Money In as positive credits with no £ symbol and no comma separators, Money Out as positive debits with no £ symbol and no commas, and optionally a Balance column with plain numeric values. The date format is the most common point of failure — Capium accepts DD/MM/YYYY only. Amount columns must contain plain numbers with decimal points (e.g. 1250.00, never £1,250.00). Any multi-line transaction descriptions from PDF statements must be merged into single rows before import. BankScan AI auto-formats any UK bank statement to this exact Capium-compatible structure in under 30 seconds.

Why is my Capium bank statement CSV import failing?

The five most common causes of Capium CSV import failure: (1) Date format mismatch — Capium requires DD/MM/YYYY; US-format and ISO-format dates cause rejection or silent misreading. (2) Multi-line descriptions — transaction descriptions split across multiple CSV rows break the one-row-per-transaction expectation. (3) Currency symbols and commas — £ signs and comma separators in amount columns cause Capium to interpret values as text rather than numbers. (4) Extra or unexpected columns — additional columns from the bank's CSV export confuse Capium's column mapping. (5) Duplicate detection — Capium flags transactions it believes were already imported, which can block legitimate new entries from a corrected re-import. Check each of these systematically before retrying.

How do I import PDF bank statements into Capium accounting software?

Capium does not accept PDF bank statements directly. You must convert PDFs to CSV first before importing. This is the biggest workflow bottleneck for Capium users — many UK business accounts (HSBC Business, Nationwide Business, Virgin Money, building societies) provide statements only as PDFs with no CSV export option. Manual copy-paste from PDF to spreadsheet to CSV typically takes 20-45 minutes per statement and is error-prone. Adobe Acrobat's PDF-to-Excel export gets about 70% of the work done but still leaves multi-line description splits and date formatting issues. The fastest approach: BankScan AI converts any UK bank PDF to Capium-ready CSV in under 30 seconds, with automatic handling of multi-line descriptions, grouped dates, OCR for scanned statements, and correct column formatting. Free first conversion available.

Does Capium integrate with all UK banks?

Capium integrates with most major UK high-street banks via its bank feed: Barclays, HSBC, Lloyds, NatWest, Santander, TSB, Bank of Scotland, Halifax, RBS, and Ulster Bank are generally supported. Notable gaps: Nationwide (limited or no feed for business accounts), Metro Bank (intermittent support), Monzo and Starling (limited business account connectivity), Virgin Money (inconsistent), and most building society accounts. For these unsupported banks, manual CSV import is the standard workflow. If your Capium practice has clients across multiple banks, a universal converter like BankScan AI eliminates the per-bank formatting problem — one tool handles all 16+ UK bank formats with consistent Capium-compatible output every time.

Can I bulk import multiple bank statements into Capium at once?

Capium does not natively support merging multiple statement files into one bulk import. Your options: (1) Merge all statements into one CSV with a single header row, sorted by date, and import as a single file — faster but riskier, as one formatting error voids the entire import. (2) Import each statement CSV individually — slower but creates a cleaner audit trail with per-statement confirmation. (3) Use BankScan AI's batch processing to convert all statements to Capium-ready CSVs in one session, then import them individually. For new client onboarding with 6-12 months of historical statements across multiple accounts and banks, batch conversion reduces what would be hours of manual per-bank formatting to minutes of upload time.

How does Capium's bank import compare to Xero, QuickBooks, and Sage?

Capium's bank import is functional and fit-for-purpose, sitting in the middle range of the UK accounting software spectrum. Compared to Xero and FreeAgent (more flexible CSV import, broader date format acceptance), Capium is moderately stricter about formatting. Compared to Sage and Iris (similarly strict, high manual effort for unsupported banks), Capium is roughly comparable. Capium's standout advantage is its integrated practice management — bank imports flow directly into your broader practice workflow, from the client's bank screen through accounts production, tax, and company secretarial, all within one platform. The key to a smooth Capium import experience is having your CSV correctly formatted before upload. BankScan AI produces Capium-compatible CSVs from any UK bank format in under 30 seconds, eliminating the formatting bottleneck that affects every platform.

What happens when my Capium bank feed stops working?

When a Capium bank feed goes silent — most commonly because the 90-day Open Banking re-authorisation has expired — you will typically notice when month-end reconciliation reveals missing transactions rather than through an active alert. To recover: (1) Ask your client to log in to their online banking and re-authorise the feed within Capium. (2) While the feed is being restored, use CSV import to bridge the gap for the missing period. (3) Once re-authorised, the feed should backfill the missed transactions. Practice tip: set a recurring calendar reminder at 80-day intervals for each client with an active Capium feed, prompting them to re-authorise before expiry. For clients who repeatedly miss re-authorisation deadlines, maintain a CSV import backup workflow using BankScan AI to ensure transaction continuity even when the feed is down.

Last updated: 23 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.