PlaygroundAPIPricingSign inDEGet API key
Loading…

Compliant e-invoices in one POST request. Generate, validate and parse XRechnung and ZUGFeRD / Factur-X. Made in Germany, hosted in the EU.

ProductPlaygroundPricingSign inGet API key
ResourcesDocumentationInteractive referenceOpenAPI specTypeScript SDK (npm)ChangelogStatusSupport
RechtlichesImpressumDatenschutzAGBAVV
© 2026 VIBOA UG (haftungsbeschränkt) · HannoverDE · EN

Not legal or tax advice. XRechnung® is a standard of KoSIT; ZUGFeRD® of FeRD. Names used for format identification only.

DocumentationAuthenticationYour first invoiceThe 422 reportQuotas & limitsTest vs. live keys
API referencePOST…/generatePOST…/validatePOST…/parse
ReferenceError codesValidation rulesInteractive referenceOpenAPI spec↗@normbill/xrechnung↗Status

Validation rules

BR-AG-01

Lines or document-level allowances/charges use VAT category "M" (IPSI, Ceuta/Melilla) but the VAT breakdown (BG-23) has no IPSI entry.

Rule
BR-AG-01 — official EN 16931 / XRechnung rule
Severity
error
Detected by
tier 3 — KoSIT validator (authoritative)
Reachability
Only reachable when validating your own XML — normbill-generated documents cannot trigger it

The engine derives one breakdown entry per category and rate in use, so generated documents always contain it; only XML submitted to /v1/invoices/validate can miss it.

How to fix it

Add a cac:TaxSubtotal with category "M" to cac:TaxTotal in your XML.

BR-AG-01 auf Deutsch — was bedeutet der Fehler?

Positionen oder Nachlässe/Zuschläge verwenden die Kategorie "M" (IPSI, Ceuta/Melilla), aber die Umsatzsteueraufschlüsselung (BG-23) enthält keinen IPSI-Eintrag. Von normbill erzeugte Dokumente enthalten ihn immer; die Meldung betrifft extern erzeugtes XML.

So beheben Sie den Fehler

Ergänzen Sie in Ihrem XML ein cac:TaxSubtotal mit der Kategorie "M" in cac:TaxTotal.

Official sources

  • XRechnung specification (KoSIT / xeinkauf.de)
  • KoSIT validator on GitHub and the XRechnung validator configuration

Every 422 from the API lists the rule id, the path in your request JSON, a plain-language message and a suggested fix — see the docs overview for the report format.