Bank statement to KashFlow
Turn any bank's PDF statement into a clean CSV — or an OFX/QIF file — that KashFlow imports straight into the bank account. No manual entry. Any UK or international bank, scanned or digital, balance-validated.
Any bank · scanned or digital · balance-validated · CSV / OFX / QIF
Get PDF statements into KashFlow without retyping
KashFlow (IRIS KashFlow) imports bank statements through its bank screen — upload a CSV, OFX or QIF and it lists the transactions to reconcile. Bank feeds handle the going-forward flow for supported banks, but they miss accounts, take time to authorise, and won't cover the historical months you only hold as PDF statements. Typing those in, line by line, is exactly the slow work that delays your VAT return and your reconciliation.
FlowParse reads every transaction off the PDF — date, description and a signed amount — and writes a clean CSV, or a standards-compliant OFX / QIF bank-feed file, that imports straight into KashFlow. Debits and credits are normalised to a single signed amount, dates are parsed as DD/MM/YYYY, and every statement is balance-validated before the file is built.
Because extraction is AI-based rather than template-based, it reads any bank's layout — Barclays, HSBC, Lloyds, NatWest, Santander, Starling, Monzo, Revolut and Wise statements all convert to a KashFlow-ready file, as do international banks.
Two ways in
In the file
From PDF to KashFlow in three steps
1 · Upload the PDF
Drop your PDF bank statement — digital or scanned, any bank, any number of pages.
2 · AI builds the file
FlowParse extracts every transaction, signs the amounts, validates balances and writes a CSV.
3 · Import into KashFlow
Bring the file into the matching account in KashFlow and reconcile — no manual entry.
How to import into KashFlow
Convert: upload the PDF to FlowParse, review the editable preview, and download the CSV (or OFX/QIF). Every row is a transaction with a date, a description and a signed amount.
Import: in KashFlow open the Bank account, choose to import a statement, and upload the file. For a CSV, map Date, Description and Amount; for OFX/QIF, KashFlow reads the fields automatically. Then reconcile and code the transactions as usual — because amounts are signed, the running balance matches the statement.
Self-employed or a small limited company filing VAT through KashFlow? The same data also exports to Excel for your records and supports Self Assessment prep.
What lands in the CSV
| Column | From the statement |
|---|---|
| Date | Transaction date (DD/MM/YYYY) |
| Description | Payee / narrative (extra columns kept here) |
| Amount | Signed — money out negative, money in positive |
Works with any bank's PDF
Because extraction is AI-based rather than template-based, FlowParse reads layouts it has never seen — ideal for accounts KashFlow's feeds don't cover and for historical months:
Reconciling a whole year? Use Smart Merge to consolidate first, then export once.
Why convert instead of typing it in
In KashFlow, a bank reconciliation that won't balance usually traces back to a typing slip or a feed gap — a missed line on a long statement, a wrong sign on a refund, a duplicated payment. Converting the PDF removes the typing and the balance check proves the period is complete before it reaches KashFlow, so the account reconciles on the first attempt.
It also matters at tax time: KashFlow feeds your VAT return and, for the self-employed, your Self Assessment figures, so a missed or mis-signed transaction has real consequences. Validated conversion keeps the numbers underneath your filing correct — and Making Tax Digital means those numbers need to be right, not roughly right.
KashFlow bank imports and the gaps feeds leave
KashFlow supports both live bank feeds and file import (CSV, OFX and QIF), which covers most day-to-day banking once a feed is authorised. The two familiar gaps remain: coverage — not every account, card or international bank is on a feed — and history, because a feed starts from the day it's connected, so earlier months needed for catch-up or a late return aren't there. For both, the PDF statement is the source of truth, and turning it into a clean import file is the whole job. FlowParse outputs the columns KashFlow expects with DD/MM/YYYY dates and a single signed amount, so the import just works.
Once the statement is in, KashFlow lists each transaction to reconcile and code, and its bank rules can auto-code recurring items. The quality of that step depends on the description arriving intact, which is why FlowParse keeps the full narrative and packs any extra statement columns into the description rather than dropping them. A clean first import means less manual coding every month after — and a reconciliation that balances rather than a hunt for a penny.
For UK freelancers, contractors and small limited companies, this connects straight to tax. KashFlow feeds VAT under Making Tax Digital and, for sole traders, the figures behind Self Assessment, so a missed or mis-signed line isn't just untidy — it flows into a filing. Converting statements with a balance check keeps those numbers correct, and the same extracted data also exports to Excel and supports Self Assessment prep. Reconciling many months at once? Smart Merge consolidates them first.
Validated before it reaches KashFlow
A bad import means a reconciliation that never balances. Before the file is built, FlowParse checks the data so what lands in KashFlow is complete and correct:
See the validation engine and reconciliation tools.
Accuracy, security and MTD confidence
Because KashFlow's figures flow into your VAT return, accuracy isn't optional. FlowParse reads each statement by meaning rather than a fixed template, so any UK or international bank layout is handled and scanned statements are OCR'd first. Every statement is balance-validated before it becomes a file, and amounts are signed (money out negative), so the running balance matches and a misread line is flagged rather than quietly wrong.
On privacy, FlowParse processes documents in EU data centres, deletes the original PDF as soon as extraction completes, encrypts the extracted data (deletable on demand), and never trains models on your documents — the full posture is on the security page. For a sole trader or small company handling its own books, converting a statement is safe, not a risk.
Here's the everyday case: a contractor doing their own KashFlow bookkeeping has a business account on a feed but a second account and a card the feed doesn't cover, plus a few early months from before they connected. They convert those PDFs to a clean CSV, import, and reconcile — the balance lines up and the VAT and Self Assessment figures underneath are complete and correct.
Because one upload also yields a full Excel workbook, nothing is lost: KashFlow holds the transactions it needs, while the workbook keeps every original column for your records or your accountant. One conversion, both outputs, any bank, any month — no retyping.
One upload, every format
The same extraction powers every export — so if you also run QuickBooks, Quicken, Xero or just need a spreadsheet, take the same statement to the format you need without re-uploading.
Take the same data to Excel, QuickBooks or Xero.
| Format | Best for |
|---|---|
| CSV | Importing this statement into KashFlow |
| Excel (.xlsx) | A full workbook with every source column for your records |
| CSV | A simple, editable table for any tool or import wizard |
| OFX / .QBO / .QFX | Bank-feed files for QuickBooks, Quicken and OFX apps |
| Xero / Sage / Wave | Tailored CSV layouts for other accounting software |
Who imports statements into KashFlow this way
Anyone who reconciles a KashFlowbank or card account from statements rather than a live feed — because the feed doesn't cover the account, hasn't been set up yet, or the months they need predate it. A few of the most common:
Freelancers
Catch up KashFlow bank accounts in minutes and reconcile for VAT.
Contractors
Bring in statements from banks KashFlow can't auto-connect.
Small limited companies
Backfill historical months only available as PDFs.
Accountants
Standardise client PDFs into a clean KashFlow import.
Bookkeepers
Catch up KashFlow accounts before the VAT quarter-end.
Sole traders
Get a year of statements into KashFlow ready for tax.
Any bank → one KashFlow-ready file
Upload statements from every account you reconcile — FlowParse turns each into a clean file KashFlow imports.
Tips for a clean import into KashFlow
A statement import goes smoothly when the data underneath is complete and correctly signed. A few habits make every KashFlow import reconcile on the first pass:
- Convert the full statement period rather than a partial export, so the opening and closing balances are present for the validation check to confirm nothing is missing.
- Import each statement period once — or use the OFX file where KashFlow supports it, since it de-duplicates by a per-transaction ID if you re-import.
- Match the KashFlow account's currency to the statement you're importing; FlowParse preserves the amounts and signs exactly as the bank reported them.
- Review the fields the validation report flags in the editable preview before you download — clean statements pass automatically, so you only check the exceptions.
- Reconciling a whole year? Consolidate the statements with Smart Merge first, then import a single clean, balance-checked set into KashFlow.
Frequently asked questions
How do I import a bank statement into KashFlow?
Convert the PDF with FlowParse to a CSV (Date, Description, Amount) or an OFX/QIF file, then in KashFlow open the bank account, import a statement and upload the file. Map the columns for CSV, or let KashFlow read OFX/QIF automatically, then reconcile.
Does KashFlow import CSV, OFX or QIF?
KashFlow imports bank statements from CSV, OFX and QIF. FlowParse can build each from the same upload, so you use whichever your workflow prefers — OFX/QIF carry per-line detail, CSV is simplest to eyeball.
Can I convert statements from any UK bank?
Yes — Barclays, HSBC, Lloyds, NatWest, Santander, Starling, Monzo, Revolut and Wise all convert, plus international banks, because extraction is AI-based rather than per-bank templates.
Will the running balance match in KashFlow?
Yes. Amounts are signed (money out negative) and the whole statement is balance-validated before import, so KashFlow's running balance lines up with the statement.
Is it accurate enough for VAT and MTD?
FlowParse reaches around 98% field-level accuracy on standard layouts and balance-validates every statement, so the figures feeding your VAT return under Making Tax Digital are complete and correctly signed. You review only the flagged fields.
Can I import historical statements for Self Assessment?
Yes. Convert any PDF you have, including older months only offered as PDFs, and import them to KashFlow to complete the year before you file.
Is it free to try?
You can convert within the monthly page allowance and preview the transactions first; OFX and accounting exports are part of the paid plans for ongoing volume.
Can I convert statements from any bank for KashFlow?
Yes. FlowParse uses AI extraction rather than per-bank templates, so PDF statements from UK banks (Barclays, HSBC, Lloyds, NatWest, Monzo, Starling), US banks (Chase, Bank of America, Wells Fargo, Capital One), and EU and neobanks (Wise, N26, Revolut) all convert to a KashFlow-ready file. A layout the tool has never seen is read correctly on the first try.
Are scanned or photographed statements supported?
Yes. Image-only PDFs run through OCR first, then the AI structures the recognised text into transactions before building the file for KashFlow. Any low-confidence field is flagged so you can check it before importing.
How are debits and credits handled?
They are normalised into a single signed amount — money out negative, money in positive — with the correct transaction type, so the imported balance reconciles against your account.
Is the conversion accurate?
FlowParse reaches around 98% field-level accuracy on standard statement formats, and every file is balance-validated (opening balance + transactions = closing balance) with per-field confidence scores you can review before importing into KashFlow.
Can I review the transactions before importing?
Yes. An editable preview lets you correct any value, and the validation report flags duplicates, low-confidence fields and balance breaks before you download the file — so nothing wrong reaches your books.
Do I also get other formats from the same upload?
Yes. One upload can export Excel, CSV, OFX and the Intuit-tagged .QBO and .QFX for QuickBooks and Quicken, plus Xero, Sage, Zoho Books, NetSuite and MYOB — so multi-tool firms convert once and export everywhere.
Where are my bank statements processed and stored?
FlowParse processes documents in EU data centres, deletes the original PDF as soon as extraction completes, stores only the extracted data (encrypted, and deletable on demand), and never uses your documents to train models. So converting a statement for KashFlow is safe, not a privacy trade-off — the full posture is on the security page.
What happens with multi-page or very long statements?
They're stitched into one continuous list and any weak page is retried automatically, so nothing is dropped at a page break. The balance check then confirms the whole statement — first page to last — was captured before the file is built.
Can I automate converting statements for KashFlow at volume?
Yes. The same conversion runs over the bank statement API: send a PDF and receive structured JSON or a ready-to-import file per page, with the balance validation built in. That lets high-volume teams turn statement intake for KashFlow into a pipeline step instead of a manual task.
Do I have to enter any transactions by hand?
No. FlowParse extracts every line from the PDF and writes them into the file, so KashFlow loads the transactions in one import instead of you typing each one. You only review the few fields the validation report flags.