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

UBL-SR-16

The buyer identifier (BT-46) appears more than once — the customer party may carry only one PartyIdentification/ID.

Rule
UBL-SR-16 — 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 normbill invoice model has no buyer identifier; generated XML never contains a buyer cac:PartyIdentification.

How to fix it

Keep a single cac:PartyIdentification/cbc:ID under the customer party.

UBL-SR-16 auf Deutsch — was bedeutet der Fehler?

Der KoSIT-Validator lehnt die Rechnung ab, weil die Käuferkennung (BT-46) mehrfach vorkommt — nur eine PartyIdentification/ID ist bei der Käuferpartei erlaubt.

So beheben Sie den Fehler

Behalten Sie genau eine cac:PartyIdentification/cbc:ID bei der Käuferpartei.

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.