The document-level allowance has no reason · BR-33
- Severity · Error
- Applies to · UBL / CII
- Editorial review pending
The document-level allowance needs a reason in text (BT-97) or code form (BT-98). Both forms can appear together.
As of
Who can correct it?
The sender can correct the invoice.
How to fix it
- Explain the agreed reason in plain text or use the matching standard reason code.
- XML fields in the affected group · UBL cac:AllowanceCharge[cbc:ChargeIndicator=false()]/cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode · CII ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge[ram:ChargeIndicator/udt:Indicator=false()]/ram:Reason or ram:ReasonCode
Rule text and source
Paraphrase · Each document-level allowance must carry at least one of the two reason fields, text or code.
Message to the sender
Subject: Invoice {invoiceNumber} – The document-level allowance has no reason
Hello,
could you clarify a detail on your invoice {invoiceNumber} dated {issueDate} (BR-33)? The document-level allowance needs a reason in text (BT-97) or code form (BT-98). Explain the agreed reason in plain text or use the matching standard reason code.
Could you send us the corrected invoice?
Thank you and kind regardsExample
The invoice lists a document-wide discount of EUR 10. Both reason fields are absent. Adding the text “Discount on the whole order” supplies the reason.
Related rules
- BR-31 · The document-level allowance has no amountError
- BR-32 · The document-level allowance has no VAT categoryError
- BR-51 · The invoice contains a full payment card numberError
- BR-AE-01 · VAT breakdown missing or duplicated (reverse charge)Error
- BR-AE-03 · Seller or buyer tax identifier missing (reverse charge, allowance)Error
Business terms
BG-20
Rule versions
CEN · EN 16931 (KoSIT) 1.3.16
CEN · EN 16931 1.3.17