Skip to main content
used by 263 tax offices
All CSV converters

Convert CSV to QBO for QuickBooks

Turn existing bank transaction CSV files into QuickBooks .QBO transaction files for manual QuickBooks Online upload without PDF extraction or OCR.

Upload CSV and create QBO

Drop CSV or XLSX files here

One CSV shows a transaction preview. Multiple CSV/XLSX files form a batch with a file list, verified transaction counts and total credits. Successful exports can be downloaded together as a ZIP. MT940/CAMT.053 require account details and balances per file.

EU infrastructure
trusted by 263 tax firms
Direct CSV workflow without OCR
31,000+ conversions
Made in Germany
SSL encryption
No subscription
CSV input

What data does the CSV need?

A transaction date and amount must be identifiable. Description/reference is recommended; separate debit and credit columns are supported.

  • Date / booking date
  • Amount or debit/credit
  • Description / reference

QBO

Turn existing bank transaction CSV files into QuickBooks .QBO transaction files for manual QuickBooks Online upload without PDF extraction or OCR.

  • .QBO / OFX 1.02
  • Stable FITID transaction IDs
  • Account + currency metadata
  • QuickBooks manual upload: max. 350 KB / 1,000 transactions

Move directly from CSV to the target format

1

Export CSV from the bank, card or payment provider.

2

Upload the CSV and review the target profile.

3

Review the generated file before importing it.

Frequently asked questions

Does the CSV need one exact column layout?

A transaction date and amount must be identifiable. Description/reference is recommended; separate debit and credit columns are supported.

How is CSV to QBO billed?

1–50 transactions = 1 credit, 51–100 = 2 credits, and so on. CSV input is billed by transaction count rather than PDF pages.

Does CSV to QBO generate stable FITIDs for repeat imports?

Yes. KontoCSV derives QBO transaction identifiers (FITIDs) from the account, date, amount and available transaction details rather than CSV row numbers. QuickBooks can use them to recognize previously imported transactions. Changed source details can produce a different FITID, so duplicate prevention is not guaranteed.