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-25

The deliver-to party name (BT-70) appears more than once — cac:Delivery may carry only one DeliveryParty/PartyName/Name.

Rule
UBL-SR-25 — 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 deliver-to party; generated Delivery elements only carry the delivery date.

How to fix it

Keep a single deliver-to party name inside cac:Delivery.

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

Der KoSIT-Validator lehnt die Rechnung ab, weil der Name des Warenempfängers (BT-70) mehrfach vorkommt — cac:Delivery darf nur einen DeliveryParty/PartyName/Name tragen.

So beheben Sie den Fehler

Behalten Sie genau einen Warenempfänger-Namen innerhalb von cac:Delivery.

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.