Test data for German e-invoices
Free package for development and testing: 8 linked cases as XRechnung 3.0 (UBL) with a matching bank statement (camt.053) and 15 error variants with the expected finding. All fictitious, all validated, free to use (CC0).
ZIP, 61 KB · version 1.0, 2026-11-22 · 23 cases, 40 XML files · licence CC0 1.0 · no sign-up
What it is for
- Invoice intake: read invoice, credit note (381) with reference and corrected invoice (384) and link them correctly.
- Payment matching: match camt.053 incoming payments to invoices, with discount, partial payment, credit-note offset and combined payment.
- Validation and error messages: does your software catch the rule violations and show understandable messages?
- Business errors: duplicate invoice number, credit note without a valid reference, underpayment, discount after the deadline, double payment. No Schematron check finds these.
Cases (8)
Each folder holds the documents and a bank statement of the seller. The expected result (open amount, matching) is in vorgaenge.json, machine-readable.
| Folder | Case | Documents |
|---|---|---|
k01-rechnung-zahlung | Invoice 19 %, paid in full | invoice WB-2026-0101 (EUR 705.08) |
k02-steuersaetze-19-7 | Mixed VAT rates 19 % and 7 %, paid in full | invoice SH-2026-0202 (EUR 1036.58) |
k03-skonto | Invoice with early-payment discount (2 % within 14 days), paid after 10 days with deduction | invoice WB-2026-0103 (EUR 6509.06) |
k04-teilzahlungen-behoerde | Invoice to a public authority (Leitweg-ID), paid in two instalments | invoice SH-2026-0204 (EUR 6342.70) |
k05-gutschrift-mit-bezug | Invoice, credit note (381) referencing it, payment of the difference | invoice WB-2026-0105 (EUR 3128.99) credit note WB-GS-2026-0011 (EUR 345.70) |
k06-korrekturrechnung-384 | Invoice, corrected invoice (384) replacing it, only the correction is paid | invoice SH-2026-0206 (EUR 1570.80) corrected invoice SH-2026-0207 (EUR 1309.00) |
k07-reverse-charge-13b | Construction service under reverse charge (AE), paid net | invoice BB-2026-0307 (EUR 6304.70) |
k08-sammelzahlung | Two invoices to a public authority, one combined payment | invoice WB-2026-0108 (EUR 539.90) invoice WB-2026-0109 (EUR 660.45) |
Error variants (15)
8 files break a KoSIT validation rule (EN 16931 or XRechnung); each triggers at least the rule named. 7 cases are valid file by file and only wrong in context.
| File/folder | Type | What is wrong | Expected finding |
|---|---|---|---|
f01-summe-positionen | rule | Sum of line amounts (BT-106) does not match the lines | BR-CO-10 |
f02-steuersumme | rule | Total VAT (BT-110) is not the sum of the VAT breakdown | BR-CO-14 |
f03-ohne-buyer-reference | rule | Buyer reference / Leitweg-ID (BT-10) missing | BR-DE-15 |
f04-skonto-format | rule | Discount term with comma instead of dot (#SKONTO#…PROZENT=2,00#) | BR-DE-18 |
f05-ueberweisung-ohne-iban | rule | Payment means credit transfer (58) without payee account (BG-17) | BR-DE-23-a |
f06-kaeufer-ohne-plz | rule | Buyer post code (BT-53) missing | BR-DE-9 |
f07-steuerbasis-falsch | rule | VAT category taxable amount (BT-116) does not match the lines | BR-S-08 |
f08-ohne-kontakt-email | rule | Seller contact e-mail (BT-43) missing | BR-DE-7 |
f09-doppelte-rechnungsnummer | business | Two different invoices from the same seller with the same number WB-2026-0950 | Detect duplicate: same seller VAT ID + same invoice number (BT-1), different content |
f10-gutschrift-ohne-rechnung | business | Credit note references invoice WB-2026-0999 in BG-3, which does not exist in the package | Reference cannot be resolved: do not offset automatically, needs clarification |
f11-unterzahlung | business | Payment 50.00 EUR below the invoice amount, no discount and no credit note | Partially paid: 50.00 EUR open, do not close the invoice |
f12-skonto-nach-frist | business | Discount deducted although payment came after 21 days (term 14 days) | Discount not justified: 18.42 EUR open |
f13-verwendungszweck-ohne-nummer | business | Amount matches, but the remittance text contains no invoice number | Only matchable via amount, payer and date: suggest with confirmation, not automatically |
f14-gutschrift-hoeher-als-rechnung | business | Credit note for 3 units against an invoice for 2 units: credit exceeds the invoice | Credit (160.65) larger than invoice (107.10): review, do not offset automatically |
f15-doppelt-bezahlt | business | The same invoice is paid twice (two entries, different EndToEndId) | Overpayment 535.50 EUR: do not match the second payment, refund or credit balance |
How the package is checked
- Every invoice and credit note with the eRechio validation core: XML schema (UBL 2.1) and the official KoSIT rules (rule set XRechnung 3.0.2 · KoSIT 2026-08-31 · e17455c9cb03), the same core as in the validator and the API.
- Every bank statement against the ISO 20022 schema camt.053.001.08.
- The fictitious VAT IDs carry a wrong check digit and were looked up in VIES: all “invalid”. The result is in
pruefprotokoll.json. - Generated by our own generator with a fixed seed (20261122); the same version yields byte-identical files.
Limits
Only XRechnung 3.0 in UBL syntax, only incoming payments as camt.053, amounts in euro. No CII/ZUGFeRD, no pain.001, no ledger export. VAT rates, exemption reasons and discounts are examples for technical tests, not a statement on correct taxation and not tax or legal advice.
Custom test data? A generator via API or MCP (your industry, VAT rates, error variant, seed, CII) is not built. If you would need it, tell us what for. Validating invoices via API already exists: eRechio API.
Frequently asked questions
Can I use the files in my own test suite or product?
Yes. The package is released under CC0 1.0 (public domain dedication): copy, change and ship it, including commercially, without attribution.
Are the companies, VAT IDs and IBANs real?
No. All companies and addresses are invented and e-mail addresses end in .example. German VAT IDs deliberately have a wrong check digit (the VIES lookup says “invalid”), IBANs are published example IBANs, the Leitweg-ID is from the 991 test range.
Why is there a bank statement with every case?
Because matching payments to invoices is where real systems break: discounts, partial payments, credit notes, combined payments. Each case has the expected result in vorgaenge.json, so you can assert your matching logic automatically.
Is CII / ZUGFeRD included?
Not in version 1.0: the invoices are XRechnung 3.0 in UBL syntax. If you need CII, ZUGFeRD, pain.001 or ledger exports, tell us what for.
Validate an invoice: XRechnung validator · create one: create an XRechnung · rules explained: error codes