Live demo

Create a ZUGFeRD invoice

This demo shows the Facturexa.ZugferdCreator.dll in action.

Enter invoice header data and invoice lines and generate a ZUGFeRD XML file from them. The form is prefilled with an official example invoice; you can choose further examples below. Depending on the selected profile, exactly the fields supported by that profile are shown (MINIMUM < BASIC WL < BASIC < COMFORT/XRECHNUNG < EXTENDED).

🔒 Entered data is only processed in memory and is not stored (Privacy policy).

1 Invoice data
2 Code preview
3 ZUGFeRD file
4 ZUGFeRD validation

The examples are taken unchanged from FeRD's ZUGFeRD 2.5.2 package (Apache License 2.0). Switching replaces all entries in the form with the selected example.

Invoice data

Please enter a date in the format DD.MM.YYYY.
Please enter a date in the format DD.MM.YYYY.
Please enter a date in the format DD.MM.YYYY.
Please enter a date in the format DD.MM.YYYY.

Seller

Only without a contact name: name and department together are not allowed (CII-SR-465); the name takes precedence.

Buyer

Only without a contact name: name and department together are not allowed (CII-SR-466); the name takes precedence.

Delivery address (BG-15, if different from buyer)

Different payee (BG-10)

Seller tax representative (BG-11)

Payment details

Please enter a date in the format DD.MM.YYYY.

Invoice notes (BG-1)

Subject code (BT-21)Note (BT-22)

Further references

Please enter a date in the format DD.MM.YYYY.
Please enter a date in the format DD.MM.YYYY.

Additional supporting documents (BG-24)

IDNameType codeDate

Documents & other

Please enter a date in the format DD.MM.YYYY.

Document-level allowances/charges (BG-20/BG-21)

TypeReasonReason code Basis%Amount Tax rateTax cat.

Exemption reasons per tax group (BG-23)

The tax amounts are calculated from the lines. Here, only enter the exemption reason and code per category and rate (required e.g. for exempt, reverse charge, intra-community supply and export); the basis is not used.

Basis%CategoryTypeExemption reasonReason code

Invoice lines

Name (BT-153) Quantity (BT-129) Unit Unit price (BT-146) Tax rate % (BT-152) Tax cat. (BT-151) Discount % (BT-138) Note (BT-127)
Please enter a date in the format DD.MM.YYYY.
Please enter a date in the format DD.MM.YYYY.
Please enter a date in the format DD.MM.YYYY.
Item attributes (BG-32)
Item classification (BT-158)
Line allowances/charges (BG-27/BG-28, in addition to discount %)
Please enter a date in the format DD.MM.YYYY.
Included items/components (kit/bundle)
Please enter a date in the format DD.MM.YYYY.
Please enter a date in the format DD.MM.YYYY.
Please enter a date in the format DD.MM.YYYY.
Item attributes (BG-32)
Item classification (BT-158)
Line allowances/charges (BG-27/BG-28, in addition to discount %)
Please enter a date in the format DD.MM.YYYY.
Included items/components (kit/bundle)

Manual totals (MINIMUM/BASIC WL only)

According to the specification, MINIMUM and BASIC WL contain no individual invoice lines — only header data and totals. Enter the net total and at least one tax line instead.

Tax lines (BG-23)

Basis%CategoryTypeExemption reasonReason code

Generated C# code

This is how the Facturexa library builds the invoice object (EInvoice) from your input and writes it as ZUGFeRD XML.

C# – Erstellen.cs

ZUGFeRD validation

The ZUGFeRD XML created in step 3 is now validated by the Facturexa Validator against the official rule sets (XSD schema and the official Schematron of the respective profile). The finished XML file is validated deliberately – exactly what eventually reaches the recipient.

Integrate this invoice creation DLL into your own software

The Facturexa Zugferd Creator generates the ZUGFeRD XML right inside your .NET application, the Validator checks it – both in one license.