The document-level charge has no reason · BR-38
- Severity · Error
- Applies to · UBL / CII
- Editorial review pending
The document-level charge needs a reason in text (BT-104) or code form (BT-105). 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=true()]/cbc:AllowanceChargeReason or cbc:AllowanceChargeReasonCode · CII ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeAllowanceCharge[ram:ChargeIndicator/udt:Indicator=true()]/ram:Reason or ram:ReasonCode
Rule text and source
Paraphrase · Each document-level charge must carry at least one of the two reason fields, text or code.
Message to the sender
Subject: Invoice {invoiceNumber} – The document-level charge has no reason
Hello,
could you clarify a detail on your invoice {invoiceNumber} dated {issueDate} (BR-38)? The document-level charge needs a reason in text (BT-104) or code form (BT-105). 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 shipping fee of EUR 10. Both reason fields are absent. Adding the text “Shipping fee for the order” supplies the reason.
Related rules
- BR-36 · The document-level charge has no amountError
- BR-37 · The document-level charge has no VAT categoryError
- BR-AE-01 · VAT breakdown missing or duplicated (reverse charge)Error
- BR-AE-04 · Seller or buyer tax identifier missing (reverse charge, charge)Error
- BR-AE-07 · VAT rate must be 0 % (reverse charge, charge)Error
Business terms
BG-21
Rule versions
CEN · EN 16931 (KoSIT) 1.3.16
CEN · EN 16931 1.3.17