BR-DEX – XRechnung extension

BR-DEX-12: third party payment without a description (BT-DEX-003)

ErrorXRechnung business rule (KoSIT)

The rule's own wording

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

Source: KoSIT XRechnung, version 3.0.2 (Schematron 2.6.0)

The fix in the XML

Enter in every cac:PrepaidPayment group cbc:InstructionID with a short description of the payment, for example the name of the funding body and the reference, in addition to cbc:ID for the kind and cbc:PaidAmount for the amount.

Before – invalid

<cac:PrepaidPayment>
  <cbc:ID>Subsidy</cbc:ID>
  <cbc:PaidAmount currencyID="EUR">300.00</cbc:PaidAmount>
</cac:PrepaidPayment>

After – corrected

<cac:PrepaidPayment>
  <cbc:ID>Subsidy</cbc:ID>
  <cbc:PaidAmount currencyID="EUR">300.00</cbc:PaidAmount>
  <cbc:InstructionID>Subsidy of the city of Beispielstadt, decision 2026-0451</cbc:InstructionID>
</cac:PrepaidPayment>

Meaning of the rule

Your invoice contains a third party payment, but without the description the extension requires for every such payment. Next to the kind and the amount, a text must say what it is about, for example which funding body pays or on what basis. The recipient needs this detail to match the amount with their records and to settle the rest correctly. Without the description the group is incomplete and the invoice is rejected.

What usually goes wrong

Only the kind and the amount of the payment were captured, the description field stayed empty.
The description stands in the free text of the invoice instead of the group.
The software does not know the field and leaves it out.

Questions and answers

How detailed must the description be?

One sentence is enough: who pays and what the payment refers to. The rule only checks that the field is not empty.

How do kind and description differ?

The kind in cbc:ID is a short type such as subsidy; the description in cbc:InstructionID explains the concrete case to the recipient.

EN 16931 fields

BT-115
BT-113

Check your invoice

The XRechnung validator reports this rule with the line number and location – right in your browser, without upload.

Open the XRechnung validator

The rule in detail

UBL · Context (XPath): /ubl:Invoice/cac:PrepaidPayment[$isExtension]
UBL · Schematron test: cbc:InstructionID[boolean(normalize-space(xs:string(.)))]

Explanation written on 14 September 2026

Search