Bank statement to Exact Online
Turn a PDF rekeningafschrift into a clean CSV, OFX or Excel of dated, signed transactions for Exact Online — for the accounts and months where you only have a PDF. Any bank, scanned or digital, balance-validated.
Any bank · scanned or digital · balance-validated · CSV / OFX / Excel
Get PDF statements into an Exact Online workflow
Exact Online reads bank statements natively as MT940 and CAMT.053 — the ISO 20022 files Dutch banks deliver for connected accounts — and that's the right path whenever your bank provides them. The gap is everything a bank feed doesn't cover: a foreign account that only issues a PDF rekeningafschrift, a card from a smaller issuer, or the historical months you're loading during an implementation. For those, there is no MT940 to download — only a PDF.
FlowParse turns that PDF into usable data. Upload the rekeningafschrift and it extracts every mutatie — date, omschrijving and a signed amount — into a clean CSV, an OFX bank-feed file, or a full Excel workbook, balance-validated end to end. Use it to reconcile (afletteren), to import where Exact accepts CSV, or as the complete source your accountant works from.
To be clear about formats: FlowParse does not manufacture MT940 or CAMT.053 — those come straight from your bank for supported accounts. What it does is recover the transactions from a PDF into clean, correctly-signed rows when no MT940 exists. Because extraction is AI-based, ING, Rabobank, ABN AMRO and international banks all convert the same way.
Two ways in
In the file
From PDF to Exact Online 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 Exact Online
Bring the file into the matching account in Exact Online and reconcile — no manual entry.
How to use the file with Exact Online
Convert: upload the PDF rekeningafschrift to FlowParse, review the editable preview, and download the CSV (or OFX / Excel). Every row is a mutatie with a date, an omschrijving and a signed amount.
Reconcile or import: for a connected Dutch account, keep using Exact's native MT940 / CAMT.053 feed. For the accounts and months where you only have a PDF, use the FlowParse CSV to import where Exact accepts it, or as the clean, complete transaction list to reconcile (afletteren) against — so nothing from those periods is missing from your grootboek.
Loading supplier invoices too? FlowParse also reads invoices, so inkoopfacturen and afschriften run through one tool. The same data exports to Excel and to other systems, so a multi-tool finance team converts once.
What lands in the CSV
| Column | From the statement |
|---|---|
| Date | Transaction date, normalised |
| Description | omschrijving / counterparty (extra columns kept here) |
| Amount | Signed — money out negative, money in positive |
| Reference | Kenmerk / reference where present |
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 Exact Online's feeds don't cover and for historical months:
Reconciling a whole year? Use Smart Merge to consolidate first, then export once.
Why recover the PDF instead of skipping the period
In Exact Online, a period you can't afletteren cleanly is a hole in the grootboek: a foreign account or a pre-connection month left out because there was no MT940 for it. Typing those transactions in by hand is slow and error-prone; skipping them leaves the reconciliation and the BTW figures incomplete.
Converting the PDF closes the hole. The balance check (opening + transactions = closing) confirms every line was captured before you reconcile, and the amounts are already signed, so the running balance matches. You get the missing periods in cleanly rather than leaving them out — without waiting for an MT940 that will never arrive.
Exact Online, MT940/CAMT.053 and where a PDF converter fits
Exact Online's bank import is genuinely strong: it ingests MT940 and CAMT.053 (ISO 20022) directly, and for connected Dutch accounts those files arrive automatically or by download from the bank. When they exist, use them — they are structured, bank-issued and de-duplicated, and no converter improves on that. FlowParse is deliberately honest here: it does not generate MT940 or CAMT.053, because forging a bank-issued format from a PDF would be the wrong thing to do. Its job starts exactly where those files run out.
That boundary is where a lot of real work lives. A Dutch company with a foreign subsidiary, an account at a bank outside its connectivity plan, a card from a smaller issuer, or two years of history to seed during an Exact implementation — all of these arrive as PDF rekeningafschriften with no MT940 behind them. FlowParse reads each mutatie into a clean CSV (Date, omschrijving, signed Amount) or an OFX bank-feed file, keeps the counterparty and reference detail intact, and balance-validates the period. You import where Exact accepts a CSV, or reconcile (afletteren) against the clean list, and the grootboek is complete.
Because the output is standard and portable, there's no lock-in: the same extracted data feeds Exact, a spreadsheet, or another system equally well, and it also exports to Excel with every original column preserved for the audit file. For teams that also process purchase invoices, the same engine reads invoices, so statement and invoice intake share one pipeline. The broader collect-convert-validate-reconcile pattern is laid out in the bank statement processing guide.
Validated before it reaches Exact Online
A bad import means a reconciliation that never balances. Before the file is built, FlowParse checks the data so what lands in Exact Online is complete and correct:
See the validation engine and reconciliation tools.
Accuracy, security and completing the grootboek
Accuracy is what makes recovering a PDF worthwhile rather than risky. FlowParse reads each rekeningafschrift by meaning rather than a fixed template, so Dutch and international layouts are handled and scanned afschriften are OCR'd before structuring. Every statement is balance-validated before it becomes a file, and amounts are signed (money out negative), so the periods you bring in reconcile against the account instead of introducing a new discrepancy.
On data handling, 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 an accountant handling client afschriften, that's a stance you can sign off.
A common scenario: a controller implementing Exact Online needs to seed two years of opening bank history across a Dutch current account (connected, MT940 available going forward) and a foreign EUR account that only issues PDFs. The connected account uses the native feed; the foreign account's PDFs go through FlowParse — each balance-validated — and the whole opening position is complete and correct before any afletteren begins.
Because one upload also yields a full Excel workbook, the recovered periods keep every original column for the audit trail, while Exact holds the transactions it needs. One conversion, both outputs — and an honest line between what the bank issues and what a converter should recover.
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 Exact Online |
| 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 Exact Online this way
Anyone who reconciles a Exact Onlinebank 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:
Finance teams
Recover PDF-only accounts and months Exact's feeds don't cover.
Accountants
Complete client grootboek from statements with no MT940.
Controllers
Seed opening bank history during an Exact Online go-live.
Multi-entity groups
Bring foreign-subsidiary PDF afschriften into Exact.
Bookkeepers
Reconcile card and second-account statements cleanly.
Importers/exporters
Convert international statements Exact can't feed.
Any bank → one Exact Online-ready file
Upload statements from every account you reconcile — FlowParse turns each into a clean file Exact Online imports.
Tips for a clean import into Exact Online
A statement import goes smoothly when the data underneath is complete and correctly signed. A few habits make every Exact Online 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 Exact Online supports it, since it de-duplicates by a per-transaction ID if you re-import.
- Match the Exact Online 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 Exact Online.
Frequently asked questions
Does FlowParse create MT940 or CAMT.053 for Exact Online?
No — and deliberately so. MT940 and CAMT.053 are bank-issued ISO 20022 files; where your bank provides them for a connected account, use Exact's native import. FlowParse recovers transactions from a PDF rekeningafschrift into a clean CSV, OFX or Excel for the accounts and months where no MT940 exists.
How do I get a PDF statement into Exact Online then?
Convert the PDF with FlowParse to a CSV of Date, Description and signed Amount, then import it where Exact accepts CSV, or use it as the clean transaction list to reconcile (afletteren) against for that period. The balance check confirms the period is complete first.
Can I convert statements from any bank?
Yes — ING, Rabobank, ABN AMRO and international banks all convert, because extraction is AI-based rather than per-bank templates. Scanned afschriften are OCR'd first.
Are debits and credits signed correctly?
Yes. Money out and money in are normalised into a single signed amount, and every statement is balance-validated (opening + transactions = closing) so the recovered period reconciles.
Can I recover historical afschriften for an implementation?
Yes. Convert any PDF you hold, including years of history, to seed opening bank data in Exact Online before reconciling — useful when only connected accounts have MT940.
Will I lose the omschrijving or reference detail?
No. The full omschrijving and any reference (kenmerk) are preserved, and the matching Excel export keeps every original column 1:1 for the audit 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 Exact Online?
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 Exact Online-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 Exact Online. 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 Exact Online.
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 Exact Online 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 Exact Online 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 Exact Online 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 Exact Online loads the transactions in one import instead of you typing each one. You only review the few fields the validation report flags.