CSV input
Convert CSV to MT940
Prepare existing CSV transactions directly for MT940 without PDF extraction or OCR.
Drop your CSV file here
Upload a CSV with booking date, amount and description. MT940/CAMT.053 additionally require an account identifier, currency and a reliable balance basis.
1 credit per started block of 50 transactions
1–50 transactions = 1 credit, 51–100 = 2 credits, and so on. CSV input is billed by transaction count rather than PDF pages.
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
Additional data for statement formats
MT940 and CAMT.053 represent account statements, so KontoCSV also requires an account identifier, currency and reliable balance basis. Missing statement metadata is not invented.
- IBAN or account identifier
- ISO currency
- Opening/closing balance or consistent running balances
Move directly from CSV to the target format
Export CSV from the bank, card or payment provider.
Upload the CSV and review the target profile.
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 MT940 billed?
1–50 transactions = 1 credit, 51–100 = 2 credits, and so on. CSV input is billed by transaction count rather than PDF pages.
Why does MT940 need account and balance data?
MT940 and CAMT.053 represent account statements, so KontoCSV also requires an account identifier, currency and reliable balance basis. Missing statement metadata is not invented.