Klarbon reads bank statement files such as CAMT.053, MT940, CODA and OFX, up to 20 MB per file, and writes CSV, Excel (XLSX), CAMT.053, MT940 and OFX. Every statement is checked so that the opening balance plus the transactions equals the closing balance before you can download it. The preview is free; unlocking costs one credit per started 500 transactions, with every format included.
Which files can Klarbon read?
Structured bank files, the kind your online banking exports for accounting software. Klarbon reads them and writes them in another format, for example CODA to CAMT.053; reading is in beta. It does not read CSV files, and reading PDF statements is not available yet.
| Input | Read? | Limit |
|---|---|---|
| CAMT.053, CAMT.052, CAMT.054, MT940, MT942, OFX, QFX, QIF, CODA, CFONB 120, Norma 43, BAI2 | in beta | 20 MB, 1 credit per started 500 transactions |
| PDF statement, scanned or not | not yet | |
| CSV | no |
Every file goes through the balance check.
Which formats can Klarbon write?
| Output | What it is | Typical use |
|---|---|---|
| CSV | Plain text table (RFC 4180) separated by semicolons, with a decimal comma; layouts for Lexware Office (lexoffice) and sevdesk | spreadsheets and accounting tools with a CSV import |
| Excel (XLSX) | Spreadsheet (ECMA-376), one row per transaction, amounts as numbers | working with the figures yourself |
| CAMT.053 | ISO 20022 bank-to-customer statement in XML (ISO 20022), version camt.053.001.02 | accounting software in most of Europe |
| MT940 | Swift customer statement in tagged text (Swift) | older and German or Dutch accounting tools |
| OFX | Open Financial Exchange 2.2 in XML (Financial Data Exchange) | tools that import bank data in OFX |
In beta, Klarbon also writes CODA, CFONB 120, Norma 43, CAMT.052, CAMT.054, QFX and QIF; these are marked beta in the tool. One unlock covers every format, so you can download several.
Which format should I choose?
The one your software's import screen names. If it offers both, CAMT.053 carries more structured detail than MT940. Some products accept only files issued by a bank, so test one short statement before you convert a whole year. If your bank offers its own export for the period, that is the most reliable choice.
What is in each transaction?
Where the file has them: booking date, value date, signed amount and currency, counterparty name and IBAN, description, reference and the balance after the transaction. Klarbon does not add information that is not in the file.
What are the limits?
Up to 20 MB per file. A file too large to process can be exported again for shorter periods and converted separately. Unlocking costs one credit per started 500 transactions: a file with 120 transactions is one credit, one with 1,200 transactions three. See prices.
Related
Frequently asked questions
Which bank statement files can Klarbon read?
Bank statement files such as CAMT.053, MT940, OFX or CODA, up to 20 MB each, to write them in another format; reading them is in beta. Reading PDF statements is not available yet, and CSV files are not read.
Which formats can Klarbon write?
CSV, Excel (XLSX), CAMT.053 (version camt.053.001.02), MT940 and OFX 2.2. In beta also CODA, CFONB 120, Norma 43, CAMT.052, CAMT.054, QFX and QIF. One unlock includes every format.
Which format should I choose for my accounting software?
The one your software's import screen names. CAMT.053 and MT940 suit most European accounting tools, OFX suits tools that read bank feeds in that format, and CSV or Excel are for spreadsheets and custom imports.
Can Klarbon read a PDF or scanned statement?
Not yet. Reading statement PDFs and scans is not available yet. Download a CAMT.053 or MT940 file from your online banking instead.
Does Klarbon support my bank?
If your bank exports one of the files Klarbon reads, such as CAMT.053, MT940, CODA or OFX, yes. Every statement goes through the same balance check.
Sources
- ISO 20022, message definitions (camt.053) iso20022.org
- Swift, standards resources (MT messages) swift.com
- Financial Data Exchange, OFX Work Group financialdataexchange.org
- IETF, RFC 4180: Common Format and MIME Type for CSV Files rfc-editor.org
- Ecma International, ECMA-376 Office Open XML ecma-international.org