Create an invoice for Germany
ONE QUICK STEP
Where is your business based?
Pick your location and we will set up the invoice for you. You can change it later.
Somewhere else? See supported locations.
Want to see an example first? OPEN +
Pick one to open a completed sample in the editor. Every name and figure is fictional.
What Stampbench does for Germany
The deepest coverage in the product. The German CIUS runs 56 rules: the 40 European core rules plus 16 BR-DE rules covering the Leitweg-ID, the buyer reference, seller contact details and the German payment-means requirements. Both syntaxes German invoices actually arrive in are read — UBL and the CII XML inside ZUGFeRD / Factur-X — and generation emits the XRechnung 3.0 customization id.
Formats available here
UBL 2.1 carrying the XRechnung 3.0 customization id, validated against the European core plus the 16 German BR-DE rules. This is the deepest coverage in the product.
UBL 2.1 declaring the plain EN 16931 customization id, validated against the 40 core rules and the full VAT category families. The right choice whenever a customer or their portal asks for an EN 16931-compliant invoice and no national profile applies.
An ordinary business invoice: the same structured model, the same exact arithmetic, a printable document and canonical JSON — but no national e-invoicing standard is claimed and no compliance verdict is given, because Stampbench has no ruleset for it. Use this where a plain invoice is what the customer wants.
Not a structured e-invoicing standard. Stampbench will check the totals arithmetic but cannot tell you whether the document satisfies any legal requirement.
Stampbench reads and validates CII, the syntax inside ZUGFeRD and Factur-X, and the playground handles those documents today. It cannot write them: the engine has a UBL writer and no CII writer.
No CII writer exists in @stampbench/core. Validation of ZUGFeRD / Factur-X documents you already have works today — use the playground.
The Peppol BIS rules are a further customisation on top of EN 16931, and Stampbench does not implement them. Generated UBL carries the Peppol billing process id (BT-23) because XRechnung requires it, which is not the same thing as being Peppol BIS validated.
No Peppol BIS ruleset and no network transmission. Neither is on this page.
What else Stampbench covers for Germany·API documentation·Validate an invoice you already have