BR-DEX-11: XRechnung Extension rule BR-DEX-11

BR-DEX-11 belongs to the XRechnung Extension, which adds sub-invoice lines (BG-DEX-01), third-party payments (BG-DEX-09) and wider identifier lists to XRechnung; it applies only to a document whose specification identifier (BT-24) declares the extension. Below: the message, the cause and the fix.

The message validators print

BR-DEX-11 is a rule of the XRechnung 3.0 rules (xrechnung-schematron 2.6.0 (XRechnung 3.0.2)) for UBL. It is an error (fatal): a validator rejects the invoice.

UBL
[BR-DEX-11] Das Element "Third party payment amount" BT-DEX-002 muss übermittelt werden, wenn die Gruppe "THIRD PARTY PAYMENT" (BG-DEX-09) übermittelt wird.

What it checks

BR-DEX-11 belongs to the XRechnung Extension, which adds sub-invoice lines (BG-DEX-01), third-party payments (BG-DEX-09) and wider identifier lists to XRechnung; it applies only to a document whose specification identifier (BT-24) declares the extension. Its published text: « Das Element "Third party payment amount" BT-DEX-002 muss übermittelt werden, wenn die Gruppe "THIRD PARTY PAYMENT" (BG-DEX-09) übermittelt wird. »

Why invoices fail it

A document declares the extension identifier without using the extension’s structures as specified, or uses them in a plain XRechnung.

How to fix it

Follow the XRechnung Extension specification of KoSIT for the structure named in the message, or use the plain XRechnung identifier when no extension element is needed.

This explanation covers the whole BR-DEX family (15 rules, overview), so this page is not indexed.

The rule as published

Where the rule applies (context) and what must hold (test), unmodified from XRechnung 3.0.2 schematron 2.6.0. An assert fails when its test is false.

Text and test: © KoSIT, Apache License 2.0. Quoted unmodified; the explanations on this page are Veriport’s.

UBL · XRechnung 3.0.2 schematron (UBL) 2.6.0 · assert · error
context: /ubl:Invoice/cac:PrepaidPayment[$isExtension]
test:    cbc:PaidAmount[boolean(normalize-space(xs:string(.)))]

Check your own invoice

Drop your XRechnung, ZUGFeRD or Peppol file into a free validator (Peppol BIS, XRechnung, Factur-X): each runs the same rule files and links every finding to its rule page. From your own code, POST /einvoice/validate (reference) returns the same check as JSON, each finding with an explanation field pointing here (5 calls a check, anonymous within the daily allowance).

Sources