BR-DE – XRechnung

BR-DE-25-a: direct debit without mandate information (BG-19)

ErrorXRechnung business rule (KoSIT)

The rule's own wording

[BR-DE-25-a] Wenn BT-81 "Payment means type code" einen Schlüssel für Lastschriften enthält (59), muss genau BG-19 "DIRECT DEBIT" übermittelt werden.

Source: KoSIT XRechnung, version 3.0.2 (Schematron 2.6.0)

Meaning of the rule

Your invoice names the direct debit (code 59) as the means of payment but contains no details of the direct debit mandate. XRechnung requires the group BG-19 in this case, with the mandate reference, the creditor identifier or the account to be debited, so that the customer can trace on what basis their account is charged. Without the group the recipient rejects the invoice, because the announced collection is not substantiated.

What usually goes wrong

The payment code 59 was set without copying the mandate from the customer master.
The software writes the mandate reference only into the invoice text, not into the payment entry.
The mandate is not stored in the customer master.

The fix in the XML

With code 59 add the group BG-19: in UBL cac:PaymentMandate with cbc:ID for the mandate reference and cac:PayerFinancialAccount for the debited account, in CII ram:DirectDebitMandateID in the payment terms and the creditor identifier in the CreditorReferenceID.

Before – invalid

<cac:PaymentMeans>
  <cbc:PaymentMeansCode>59</cbc:PaymentMeansCode>
</cac:PaymentMeans>

After – corrected

<cac:PaymentMeans>
  <cbc:PaymentMeansCode>59</cbc:PaymentMeansCode>
  <cac:PaymentMandate>
    <cbc:ID>MANDATE-2024-0031</cbc:ID>
    <cac:PayerFinancialAccount>
      <cbc:ID>DE75512108001245126199</cbc:ID>
    </cac:PayerFinancialAccount>
  </cac:PaymentMandate>
</cac:PaymentMeans>

Questions and answers

Which detail of BG-19 is the minimum?

In UBL the PaymentMandate group with the mandate reference is enough; the debited account is usual and helpful for the customer.

Why does the creditor identifier sit elsewhere in CII than in UBL?

CII carries the creditor identification as CreditorReferenceID in the settlement details; both syntaxes map the same group BG-19, only in different places.

EN 16931 fields

BG-19
BT-81
BT-89
BT-90
BT-91

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:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = '59'] | /cn:CreditNote/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = '59']
UBL · Schematron test: cac:PaymentMandate
CII · Context (XPath): /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans[normalize-space(ram:TypeCode) = '59']
CII · Schematron test: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:DirectDebitMandateID or /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:CreditorReferenceID or ram:PayerPartyDebtorFinancialAccount/ram:IBANID

Explanation written on 14 September 2026

Search