Bank statement to Fortnox
Turn any bank's PDF statement (kontoutdrag) into a clean CSV or OFX file for Fortnox — every transaction, signed amount and running saldo in SEK. No manual entry. Any Swedish or international bank, scanned or digital, balance-validated.
Any bank · scanned or digital · balance-validated · CSV / OFX
Get PDF kontoutdrag into Fortnox without retyping
Fortnox is built around automatic bank feeds (bankkoppling / Open Banking): connect a Swedish account and transactions flow in for bokföring and avstämning. That's ideal when the account is supported — but feeds don't reach every account, an international bank often isn't on the list, and the historical months you need for a late year-end only exist as PDF kontoutdrag. Typing those in, line by line, is slow and a common source of reconciliation errors.
FlowParse reads every transaction off the PDF — date, text/meddelande and a signed amount in SEK — and writes a clean CSV or a standards-compliant OFX file you can bring into Fortnox instead of keying each line. Every statement is balance-validated (opening balance + transactions = closing balance) before the file is built.
Because extraction is AI-based rather than template-based, it reads any bank's layout — Swedbank, Handelsbanken, SEB, Nordea and the neobanks all convert the same way, as do international banks for companies that trade across borders. Note that SIE is Sweden's format for exchanging the ledger with your revisor at year-end — not raw bank statements; for those, a clean CSV or OFX is the right shape.
Two ways in
In the file
From PDF to Fortnox 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 Fortnox
Bring the file into the matching account in Fortnox and reconcile — no manual entry.
How to bring statements into Fortnox
Convert: upload the PDF kontoutdrag to FlowParse, review the editable preview, and download the CSV (or OFX). Every row is a transaction with a date, a text/meddelande and a signed amount in SEK.
Bring in and reconcile: where Fortnox offers a live bankkoppling for your bank, use it for ongoing feeds; use the FlowParse CSV/OFX for the accounts it can't reach and for historical catch-up, then match and reconcile (avstämning) in Fortnox as usual. Because amounts are already signed, the running saldo lines up with the statement.
Recording supplier invoices too? FlowParse also reads invoices and receipts, so leverantörsfakturor and kontoutdrag run through one tool. The full transaction detail is also kept in Excel for your records.
What lands in the Fortnox file
| Column | From the statement |
|---|---|
| Date | Transaction date, normalised |
| Text | Payee / meddelande (extra columns kept here) |
| Amount | Signed in SEK — 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 Fortnox'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 Fortnox, an avstämning that won't balance usually traces back to a typing slip or a feed gap — a missed line, a wrong sign on a refund (återbetalning), a duplicated payment. Converting the PDF removes the typing and the balance check proves the period is complete before it reaches Fortnox, so the account reconciles on the first attempt.
For moms reporting and year-end (bokslut), that reliability compounds: a redovisningskonsult can bring in a year of statements across several accounts in minutes and spend time on review and advice, not data entry. Reconciling many months at once? Smart Merge consolidates them into one clean set first.
Fortnox bank feeds, file import and the gaps between them
Fortnox's automatic bankkoppling works well for supported Swedish banks once it's set up, pulling transactions in for bokföring and bank reconciliation. It leaves the familiar two gaps, though: coverage — not every account, card or international bank is connectable — and history, because a live feed starts from the day you connect, so earlier months needed for a late bokslut simply aren't there. For both, the PDF kontoutdrag is the source of truth, and FlowParse turns it into clean, dated, signed transactions in SEK that you can import or use for avstämning.
It helps to name the formats precisely. SIE (SIE4) is the Swedish standard for exchanging accounting data — the whole ledger — typically handed to a revisor at year-end; it is not a bank-statement format. Bank movements come in through the feed or via a transaction file, which is why FlowParse outputs a clean CSV (Date, Text, Amount) and an OFX bank-feed file rather than SIE. Debits and credits are merged into one signed amount, Bankgiro and autogiro references are kept, and dates are normalised so nothing is misread.
For Swedish bookkeepers and accounting consultants, the payoff lands hardest at moms deadlines and bokslut. Instead of keying months of transactions across several accounts, you convert each kontoutdrag, let the balance check confirm nothing's missing, and bring the transactions into Fortnox — turning a day of data entry into a few minutes of upload-and-review. The same extracted data also exports to Excel, so a client who later changes tools never forces a re-upload.
Validated before it reaches Fortnox
A bad import means a reconciliation that never balances. Before the file is built, FlowParse checks the data so what lands in Fortnox is complete and correct:
See the validation engine and reconciliation tools.
Accuracy, security and a year-end catch-up
Accuracy is what keeps a Fortnox avstämning from becoming a hunt for a difference. FlowParse reads each kontoutdrag by meaning rather than fixed coordinates, so Swedish and international layouts are handled without per-bank templates, and scanned statements are OCR'd before structuring. Every statement is balance-validated before it becomes a file, with low-confidence fields flagged in an editable preview — so what reaches Fortnox is complete and correctly signed in SEK.
Bank data is sensitive, so 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 uses your documents to train models — the full posture is on the security page. For a redovisningskonsult handling several clients, that's one less thing to worry about at a busy time of year.
Bokslut is where this earns its keep. Picture a consultant onboarding a client onto Fortnox with two years of history across a företagskonto, a savings account and a card, none of them on a live feed. Instead of keying months of transactions, they convert each kontoutdrag, the balance check confirms each period is complete, and they bring in clean transactions ready to reconcile — the whole back-history caught up in an afternoon.
Because the same upload also yields a full Excel workbook, nothing is lost: Fortnox holds the transactions it needs for bokföring, while the workbook keeps every original column for the verifikation trail or the revisor. One conversion, both outputs, any bank.
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 Fortnox |
| 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 Fortnox this way
Anyone who reconciles a Fortnoxbank 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:
Swedish bookkeepers
Catch up Fortnox accounts in minutes and reconcile for moms.
Redovisningskonsulter
Bring client bank history into Fortnox without re-keying.
Small businesses
Import statements from accounts Fortnox feeds don't cover.
Startups
Get neobank and multi-currency statements into Fortnox cleanly.
Importers/exporters
Convert international bank statements for Fortnox.
Revisorer
Standardise mixed-bank PDFs before bokslut and review.
Any bank → one Fortnox-ready file
Upload statements from every account you reconcile — FlowParse turns each into a clean file Fortnox imports.
Tips for a clean import into Fortnox
A statement import goes smoothly when the data underneath is complete and correctly signed. A few habits make every Fortnox 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 Fortnox supports it, since it de-duplicates by a per-transaction ID if you re-import.
- Match the Fortnox 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 Fortnox.
Frequently asked questions
How do I import a bank statement into Fortnox?
Convert the PDF kontoutdrag with FlowParse to a clean CSV (Date, Text, Amount in SEK) or an OFX file, then bring it into Fortnox for the matching account and reconcile. For supported banks use the live bankkoppling; use FlowParse for unsupported accounts and historical catch-up.
Does Fortnox use SIE for bank statements?
No. SIE is Sweden's format for exchanging the whole ledger with a revisor at year-end, not raw bank statements. Bank movements come in via the feed or a transaction file, so FlowParse outputs a clean CSV and an OFX bank-feed file — the right shape for Fortnox.
Can I convert statements from any Swedish bank?
Yes — Swedbank, Handelsbanken, SEB, Nordea and the neobanks all convert, as do international banks, because extraction is AI-based rather than per-bank templates.
Are amounts kept in SEK and signed correctly?
Yes. Amounts are extracted in Swedish kronor and normalised to a single signed value (money out negative, money in positive), and the whole statement is balance-validated so the saldo reconciles.
Can I convert credit-card statements too?
Yes. Credit-card PDF statements convert the same way — each line becomes a dated, signed transaction — so card spending is recorded alongside bank activity.
Can I import historical statements for bokslut?
Yes. Convert any PDF you hold, including older months only available as PDFs, and bring them into Fortnox to complete the year before you reconcile or close.
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 Fortnox?
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 Fortnox-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 Fortnox. 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 Fortnox.
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 Fortnox 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 Fortnox 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 Fortnox 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 Fortnox loads the transactions in one import instead of you typing each one. You only review the few fields the validation report flags.