Each Invoice line charge (BG-28) shall contain an Invoice line charge reason (BT-144) or an Invoice line charge reason code (BT-145), or both.
Both Reason and ReasonCode are missing from the charge. As a result, the invoice line contains neither a textual explanation nor a reason code for the charge.
An invoice line charge must be traceable through a reason, a reason code, or both. This information explains why the charge is applied.
The reason for an invoice line charge is missing. You can provide it as text, as a reason code, or with both entries.
- Add
AbstractTradeAllowanceCharge.ReasonorTradeCharge.ReasonCodefor the charge. - Check that the entry is in the appropriate
SpecifiedTradeAllowanceChargefor the invoice line. - Generate the invoice again and validate it once more.
<ram:SpecifiedTradeAllowanceCharge> <ram:ChargeIndicator> <udt:Indicator>true</udt:Indicator> </ram:ChargeIndicator> </ram:SpecifiedTradeAllowanceCharge>
<ram:SpecifiedTradeAllowanceCharge> <ram:ChargeIndicator> <udt:Indicator>true</udt:Indicator> </ram:ChargeIndicator> <ram:Reason>Livraison express</ram:Reason> <ram:ReasonCode>ABC</ram:ReasonCode> </ram:SpecifiedTradeAllowanceCharge>
ChargeReasonCodes(Line level charge: BT-145)TradeCharge.ReasonCode(Line level charge: BT-145)AbstractTradeAllowanceCharge.Reason(Line level charge: BT-144)TradeLineItem.SpecifiedTradeAllowanceCharges(BG-28)AbstractTradeAllowanceCharge(Line level charge: BG-28)
Technical details
The check runs for ChargeIndicator with the value true and passes if Reason or ReasonCode is present in the parent SpecifiedTradeAllowanceCharge.
The rule applies to a charge in SpecifiedTradeAllowanceCharge within an invoice line's settlement data. The ChargeIndicator element identifies the entry as a charge.
rule/@context)assert/@test)