Validation rules
BR-CO-25 — EN 16931 rule
An amount is due but neither a due date (BT-9) nor payment terms (BT-20) are present.
- Rule
BR-CO-25— official EN 16931 / XRechnung rule- Severity
- error
- Business term
BT-9— Due date- Field in your JSON
invoice.due_date
How to fix it
Set invoice.due_date or invoice.payment.terms.
BR-CO-25 auf Deutsch — was bedeutet der Fehler?
Es ist ein Zahlbetrag offen, aber weder ein Fälligkeitsdatum (BT-9) noch Zahlungsbedingungen (BT-20) sind angegeben.
So beheben Sie den Fehler
Setzen Sie invoice.due_date oder invoice.payment.terms.
Dieselbe Regel, gemappt auf Ihr JSON, kommt von der XRechnung API.
Related rules
UBL-SR-45— The payment due date inside cac:PaymentMeans appears more than once — cbc:PaymentDueDate is allowed at most…BR-CO-26— The seller carries none of: VAT identifier (BT-31), legal registration identifier (BT-30) or seller…BR-CO-24— An invoice line charge (BG-28) carries neither a reason text (BT-144) nor a reason code (BT-145) — at least…BR-CO-23— An invoice line allowance (BG-27) carries neither a reason text (BT-139) nor a reason code (BT-140) — at…BR-CO-22— A document-level charge (BG-21) carries neither a reason text (BT-104) nor a reason code (BT-105) — at least…BR-CO-21— A document-level allowance (BG-20) carries neither a reason text (BT-97) nor a reason code (BT-98) — at…
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.
Or try it live: drop any XRechnung XML on the free validator — same KoSIT-backed report, no account.
Generate a valid XRechnung from JSON with the XRechnung API — the 422 names this field instead of the Schematron code.