Skip to main content

Reference

Markdown export

BR-CO-25 Positive amount due requires payment due date or payment terms

EN 16931 validation artefacts 1.3.16 removed this rule, and current validators (XRechnung configuration 2026-08-31, Peppol BIS 3.0.21) no longer report it. Older rule sets required: when Amount due for payment (BT-115) is greater than zero, either the Payment due date (BT-9) or the Payment terms (BT-20) must be present.

Problem Description

WARNING

EN 16931 calculation and consistency rule (BR-CO)

Interactive pipeline

Click a stage to see what it checks, or type a rule ID to light up the stage that reports it.

Try:

BR-CO-25 EN 16931 calculation rule

Reported in stage 2: EN 16931 rules.

Retired: the EN 16931 artefacts 1.3.16 removed this rule, and current validators no longer report it.

Stage 2 · What it checks

  • The core business terms are present (BR-01 to BR-65).
  • Totals add up and related fields agree (BR-CO); codes and decimals are valid (BR-CL, BR-DEC).
  • Each VAT category is consistent: S, Z, E, AE, K, G, O, L, M (BR-S, BR-Z, BR-AE, BR-IC …).

Example codes

Typical fix

Recalculate totals and VAT from the line data, and correct the VAT category in the source data.

A validator checks an e-invoice in stages. First the file must be well-formed XML that matches the UBL or CII schema (XSD). Then the EN 16931 business rules run: BR core rules, BR-CO calculations, BR-CL code lists, BR-DEC decimals and VAT-category rules such as BR-S. Next come the national or network rules that BT-24 selects: BR-DE for XRechnung, PEPPOL-EN16931 for Peppol BIS Billing. The report lists every failed rule: one error means reject, warnings alone still mean accept. BR-CO-25: EN 16931 calculation rule, reported in the stage “EN 16931 rules”. Rule sets: KoSIT validator 1.6.3 with the XRechnung configuration of 31 Aug 2026 (EN 16931 artefacts 1.3.16), Peppol BIS Billing 3.0.21.

Context and Significance

Without a due date or payment terms, the buyer’s accounts payable system cannot schedule the payment. The validator looks for cbc:DueDate or cac:PaymentTerms/cbc:Note in UBL, and for ram:DueDateDateTime or ram:Description in ram:SpecifiedTradePaymentTerms in CII. The error often occurs when the payment terms appear only on the PDF and are not exported to the XML. The rule does not apply when BT-115 is zero or negative, for example for a fully prepaid invoice.

Solution

Whenever BT-115 is greater than zero, add BT-9 (a fixed due date) or BT-20 (payment terms text such as "Payable within 30 days net").

Quick actions

Validate XMLConvert invoice

Valid Examples

  • BT-115 = 119.00, BT-9 = 2026-05-30
  • BT-115 = 119.00, BT-20 = "Payable within 14 days net"

Invalid Examples

  • BT-115 = 119.00 with neither BT-9 nor BT-20 present
  • BT-115 > 0 and BT-9 left empty while BT-20 is also empty

Affected Fields

BT-115 Amount due for payment
BT-9 Payment due date
BT-20 Payment terms

Validation Tools

Official KoSIT Validator

Run the official KoSIT validator with the XRechnung configuration to check EN 16931 and XRechnung rules.

Convert PDF to XRechnung

Find validation errors during conversion and review each correction.