SchemaGuard by Ironbark Digital · EN 16931 / Peppol / XRechnung Reference
← All 294 EN 16931 / Peppol Rules & Live Validator
FATAL Official EN 16931 / Peppol / CIUS Rule BT/BG Fields: BT-144, BT-145

BR-44 — E-Invoice Validation Rule & Fix

Fixture ID: lineAllowanceEmpty · XPath: /ubl:Invoice/cac:InvoiceLine[1]/cac:AllowanceCharge[2]/cbc:AllowanceChargeReason

1. Why This Rule Triggers (Diagnostic Message)

The invoice line charge at lines[0].charges[0], on line 1 (id "1"), states neither a reason (BT-144) nor a reason code (BT-145). Every BG-28 group must carry at least one. A line level adjustment is harder to query than a document level one, because it disappears into the line net amount: the buyer sees a line total that does not equal quantity x price and has no way to find out why unless you say.

2. How to Fix BR-44

Set lines[0].charges[0].reason to a short description, or lines[0].charges[0].reasonCode to a UNCL 7161 code, or both. Under XRechnung, prefer the free text: the mandated visualisation renders the code verbatim, so a buyer looking at the rendered invoice sees the bare code and not what it means.

3. Valid Code / Payload Example

"charges": [{ "amount": 12.50, "reason": "Handling", "reasonCode": "SH" }]
Test & Validate XML / JSON in Live SchemaGuard Validator →