Amount due for payment

Error BR-CO-16 EN 16931

Amount due for payment (BT-115) = Invoice total amount with VAT (BT-112) -Paid amount (BT-113) +Rounding amount (BT-114).

Mandatory rule: As long as it is violated, the invoice is invalid and will be rejected by validators.
What is wrong

DuePayableAmount does not equal the invoice total including VAT minus the amount already paid plus the rounding amount. If TotalPrepaidAmount or RoundingAmount is absent, the missing amount is not included in the calculation.

What the rule means

The amount due is calculated from the invoice total including VAT, less amounts already paid and adjusted by the rounding amount. This makes the stated amount due reflect the remaining balance.

Affected fields BT-115 BT-112 BT-113 BT-114
Please reconcile the amount due for payment

The amount due does not match the invoice total, amounts already paid and the rounding amount. You can adjust the amounts so that the outstanding payment is correct.

What to do
  1. Calculate DuePayableAmount from GrandTotalAmount minus TotalPrepaidAmount plus RoundingAmount.
  2. Include only the amounts whose elements are present in the invoice.
  3. Check the DuePayableAmount, GrandTotalAmount, TotalPrepaidAmount and RoundingAmount properties.
  4. Generate the invoice again and validate it again.
What it looks like
✗ Triggers the message
<ram:SpecifiedTradeSettlementHeaderMonetarySummation>
  <ram:GrandTotalAmount>120.00</ram:GrandTotalAmount>
  <ram:TotalPrepaidAmount>20.00</ram:TotalPrepaidAmount>
  <ram:RoundingAmount>0.01</ram:RoundingAmount>
  <ram:DuePayableAmount>100.00</ram:DuePayableAmount>
</ram:SpecifiedTradeSettlementHeaderMonetarySummation>
✓ Correct
<ram:SpecifiedTradeSettlementHeaderMonetarySummation>
  <ram:GrandTotalAmount>120.00</ram:GrandTotalAmount>
  <ram:TotalPrepaidAmount>20.00</ram:TotalPrepaidAmount>
  <ram:RoundingAmount>0.01</ram:RoundingAmount>
  <ram:DuePayableAmount>100.01</ram:DuePayableAmount>
</ram:SpecifiedTradeSettlementHeaderMonetarySummation>
Check in FactoorSharp
  • FacturXInvoice.DuePayableAmount (BT-115)
  • FacturXInvoice.GrandTotalAmount (BT-112)
  • FacturXInvoice.RoundingAmount (BT-114)
  • FacturXInvoice.TotalPrepaidAmount (BT-113)
Different severity at KoSIT
  • Information EN16931 XRechnung Extension (UBL Invoice) – overwrites CEN severity level "fatal" to enable Third Party Payment calculations (BR-DEX-09)
Technical details

The XPath check compares DuePayableAmount with GrandTotalAmount minus TotalPrepaidAmount plus RoundingAmount. It also accounts for cases where either or both optional total elements are absent.

Where the rule applies

The rule applies to DuePayableAmount, GrandTotalAmount, TotalPrepaidAmount and RoundingAmount in SpecifiedTradeSettlementHeaderMonetarySummation.

Context (rule/@context)
//ram:SpecifiedTradeSettlementHeaderMonetarySummation
Test expression (assert/@test)
(xs:decimal(ram:DuePayableAmount[1]) = xs:decimal(ram:GrandTotalAmount[1]) - xs:decimal(ram:TotalPrepaidAmount[1]) + xs:decimal(ram:RoundingAmount[1])) or ( (xs:decimal(ram:DuePayableAmount[1]) = xs:decimal(ram:GrandTotalAmount[1]) + xs:decimal(ram:RoundingAmount[1])) and not(ram:TotalPrepaidAmount) ) or ( (xs:decimal(ram:DuePayableAmount[1]) = xs:decimal(ram:GrandTotalAmount[1]) - xs:decimal(ram:TotalPrepaidAmount[1])) and not(ram:RoundingAmount) ) or ( (xs:decimal(ram:DuePayableAmount[1]) = xs:decimal(ram:GrandTotalAmount[1])) and not(ram:TotalPrepaidAmount) and not(ram:RoundingAmount) )
Changes in the KoSIT validation rules
  • 2023-01-312023-01-31 · ChangedSwitched off rules BR-CO-16 and UBL-CR-470 in UBL Extension scenario for Third Party Payment implementation