Which sample should I use?
Take the format your customer or your software asks for. A German public-sector buyer asks for XRechnung; a PDF that people read and software processes is ZUGFeRD or Factur-X; an invoice sent over the Peppol network is Peppol BIS Billing. The two bank statements show what Klarbon reads from a structured bank file; Open in Klarbon loads them into the CAMT.053 to Excel converter or the MT940 to Excel converter.
How do I try a sample in Klarbon?
Choose Open in Klarbon or Check in Klarbon beside the file. The tool opens with the sample already loaded, exactly as if you had chosen it on your device. The drop zones of the Open, Check and Convert tools also have a "No file to hand? Try a sample invoice" link that loads the sample suited to that page.
Where do the files come from?
Published test files keep their publisher's name and licence: the KoSIT XRechnung test suite, the Mustangproject library, the French FNFE-MPE examples, the Simplerinvoicing test files and the Polish Ministry of Finance's KSeF test templates. Klarbon made the others with invented parties, account numbers and tax numbers. None of them is a customer document.
Sample files
-
Peppol BIS Billing 3.0 invoice
A complete Peppol BIS Billing 3.0 invoice in UBL, made by Klarbon with invented parties and identifiers.
Download peppol-bis-billing.xml Open in Klarbon Check in Klarbon
-
XRechnung in UBL syntax
Business case 01.01a from the official KoSIT XRechnung test suite, as UBL XML, with placeholder parties.
-
XRechnung in CII syntax
The same KoSIT business case 01.01a as UN/CEFACT CII XML, so you can compare the two syntaxes.
-
ZUGFeRD and Factur-X hybrid PDF
A readable PDF with the invoice XML embedded, profile EN 16931, from the tests of the Mustangproject library.
Download zugferd-factur-x.pdf Open in Klarbon Check in Klarbon
-
French e-invoice in UBL
The commented UBL example FNFE-MPE publishes for the French e-invoicing reform, an EN 16931 invoice with French identifiers.
-
SI-UBL 2.0 (NLCIUS) invoice
A Simplerinvoicing SI-UBL 2.0 test invoice that follows the Dutch NLCIUS rules, from the phive-rules test files.
-
FatturaPA invoice
An ordinary FatturaPA invoice between businesses (FPR12), made by Klarbon with invented parties, not signed or sent to the SdI.
-
Facturae 3.2.2 invoice
An unsigned Facturae 3.2.2 invoice, made by Klarbon with invented parties and dummy tax identifiers.
-
KSeF FA(3) invoice
A basic FA(3) VAT invoice from the Polish Ministry of Finance's KSeF client test templates, with fictional NIP numbers.
-
CIUS-PT invoice
A UBL invoice with the CIUS-PT 2.1.1 identifier, made by Klarbon with invented Portuguese parties.
-
RO e-Factura (CIUS-RO) invoice
A UBL invoice with the Romanian CIUS-RO identifier, made by Klarbon with invented parties, not sealed by ANAF.
-
CAMT.053 bank statement
A CAMT.053.001.02 end-of-day statement with two transactions, made by Klarbon with the widely published example IBAN.
-
MT940 bank statement
An MT940 statement with two transactions, made by Klarbon with the widely published example IBAN.
Frequently asked questions
Are these real invoices?
No. Each file is a published test example or a file Klarbon made with invented parties, account numbers and tax numbers. Do not pay, book or forward them.
Can I use the files to test my own software?
Yes, under the licence shown beside each file. The Apache-2.0 and MIT files ask you to keep their licence notice with them; the files Klarbon made are CC0-1.0, with no conditions.
Does Open in Klarbon upload the sample?
Not an invoice. The page loads the file from klarbon.app into your browser and opens it there, as if you had chosen it on your device. A bank statement is read on Klarbon's servers by the statement converter during the request, then deleted, and the read counts towards the day's free reads. Check in Klarbon sends an invoice to Klarbon's checks like any file you check, and it counts towards the day's free checks.
Will a sample stay valid?
A sample shows its format as its publisher designed it. Rule sets get new versions, so treat a sample as an example of the format rather than a template that stays valid for ever, and check your own invoices against the current rules.
Sources
- KoSIT, XRechnung test suite github.com
- Mustangproject, ZUGFeRD and Factur-X library github.com
- FNFE-MPE, France RFE examples github.com
- phive-rules, Simplerinvoicing test files github.com
- Ministry of Finance of Poland, KSeF client test templates github.com
- OpenPeppol, Peppol BIS Billing 3.0 docs.peppol.eu
Related
- Open any e-invoice. Check it. Convert it.
- Klarbon help centre
- E-invoice tools
- E-invoice viewer: open and read an e-invoice
- E-invoice validator: check an e-invoice
- Convert a CAMT.053, MT940 or OFX bank statement to Excel
- What is XRechnung?
- What is ZUGFeRD?
- What is Peppol BIS?
- Convert a bank CSV to MT940 or CAMT.053
- Open a Norma 43 bank statement file
- Check a Portuguese invoice QR code
- Open a Romanian e-Factura invoice