E-invoice error explained

BR-CO-16: Amount due for payment does not match

The amount due (BT-115) must follow from the gross total (BT-112), minus amounts already paid (BT-113), plus a rounding amount (BT-114).

What the rule checks

The amount due (BT-115) must follow from the gross total (BT-112), minus amounts already paid (BT-113), plus a rounding amount (BT-114). The check compares to the cent.

Official rule text

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

Source: KoSIT configuration XRechnung 3.0.2 (31 Jan 2026).

Typical causes

  • A prepayment was subtracted from the amount due, but BT-113 is missing.
  • Cash discount was subtracted from the amount due. Skonto belongs in the payment terms (BT-20).
  • The amount was rounded to 5 cents without a rounding amount in BT-114.
  • On a final invoice the deducted progress invoices do not match BT-113.

How to fix it

Set ram:DuePayableAmount to ram:GrandTotalAmount – ram:TotalPrepaidAmount + ram:RoundingAmount. Write every payment already received to ram:TotalPrepaidAmount, and name the progress invoices in the invoice reference on a final invoice.

Example

Wrong (CII)

<ram:GrandTotalAmount>1130.50</ram:GrandTotalAmount>
<ram:DuePayableAmount>630.50</ram:DuePayableAmount>

Right (CII)

<ram:GrandTotalAmount>1130.50</ram:GrandTotalAmount>
<ram:TotalPrepaidAmount>500.00</ram:TotalPrepaidAmount>
<ram:DuePayableAmount>630.50</ram:DuePayableAmount>

In Dynamics 365, Business Central and Finance

Sales / Project Operations: Sales and Project Operations have no e-invoice output out of the box. In the WBS Invoice Accelerator for Dynamics 365 the Accelerator computes every total of the e-invoice from the lines it writes to the file. If this rule appears for a file from the Accelerator, send the whole message to WBS. On final invoices the Accelerator writes the deducted down payment and progress invoices to BT-113.

Related error codes

Check your invoice for free. The validator shows every finding with an explanation and its location in the XML.