EN 16931 core rules
BR-31: Document level allowance amount (BT-92) is required
What this rule requires
Document level allowance amount (BT-92) is required.
ExampleEN 16931 (UBL)
An invoice built like a valid one, except for this:
<cac:AllowanceCharge>
<cbc:ChargeIndicator>false</cbc:ChargeIndicator>
<cbc:AllowanceChargeReason>Volume discount</cbc:AllowanceChargeReason>
<cac:TaxCategory>
<cbc:ID>S</cbc:ID>
<cbc:Percent>19.00</cbc:Percent>
<cac:TaxScheme>
<cbc:ID>VAT</cbc:ID>
</cac:TaxScheme>
</cac:TaxCategory>
</cac:AllowanceCharge>The validator says: Document level allowance amount (BT-92) is required and the document does not contain it.
How to fix it
Add Document level allowance amount to the invoice.
Frequently asked questions
- What does BR-31 mean?
- Document level allowance amount (BT-92) is required. The rule runs under EN 16931 (UBL), Peppol BIS 3.0, and XRechnung 3.0 (UBL).
- How do I fix BR-31?
- Add Document level allowance amount to the invoice. In UBL the element is /Invoice/cac:AllowanceCharge[cbc:ChargeIndicator=false]/cbc:Amount.
Runs under these profiles
- EN 16931 (UBL)
- Peppol BIS 3.0
- XRechnung 3.0 (UBL)
Element path
- Document level allowance amount (BT-92)UBL /Invoice/cac:AllowanceCharge[cbc:ChargeIndicator=false]/cbc:AmountCII /CrossIndustryInvoice/SupplyChainTradeTransaction/ApplicableHeaderTradeSettlement/SpecifiedTradeAllowanceCharge[ChargeIndicator/Indicator=false]/ActualAmountRead from what WorkAlio's CII parser accepts — there is no CII writer yet, so this path is not independently verified the way the UBL path is.