Skip to content

Invoice and bank format glossary

Plain definitions of e-invoice and bank statement formats: XRechnung, ZUGFeRD, Factur-X, UBL, CII, Peppol BIS, EN 16931, MT940, CAMT.053, OFX and more.

On this page

This glossary explains the file formats behind e-invoices and bank statements in plain language: what each one is, who maintains it, where it is used and what Klarbon can do with it. E-invoice formats build on the European standard EN 16931 and are written in one of two XML syntaxes, UBL or CII. Bank statements come as MT940, CAMT.053, OFX, CODA or CSV.

Each entry says what Klarbon does with the format today. Many formats here are explained for reference only, and Klarbon does not open them yet.

E-invoice standards and syntaxes

Orders and delivery notes

E-invoice formats in Europe

E-invoice formats outside Europe

Signatures, envelopes and containers

Documents, images and spreadsheets

Bank statement formats

Payment files and payment codes

Accounting, tax and audit files

Comparisons

All pages (139)

Frequently asked questions

What is the difference between an e-invoice format and a syntax?

A syntax, such as UBL or CII, is the XML language. A format such as XRechnung or Peppol BIS is a set of rules for invoices written in that language, built on the European standard EN 16931.

Which bank statement format should I use?

The one your accounting software imports. CAMT.053 and MT940 are the common choices in Europe, OFX for tools that read it, and CSV or Excel for spreadsheets.

Does an entry in this glossary mean Klarbon supports the format?

No. Each entry says what Klarbon does with that format today, whether it works, is in beta or is not supported yet.

Updated 5 November 2026