Account
English

BR-DE-25-a: If BT-81 "Payment means type code" contains a code for direct debits (59), exactly…

XRechnung rule · Error · UBL / CII

StandardXRechnung 3.0.2 (KoSIT, German CIUS of EN 16931)SeverityError: the invoice is rejectedSyntaxUBL, CIIBusiness terms
  • BG-19 Direct debit
  • BT-81 Payment means type code
Applies toXRechnung in UBL or CII syntax, including ZUGFeRD / Factur-X PDFs with the XRECHNUNG profile. Invoices to German public authorities (federal, state and municipal) must pass it.

Official rule text

[BR-DE-25-a] If BT-81 "Payment means type code" contains a code for direct debits (59), exactly BG-19 "DIRECT DEBIT" must be transmitted.

Official text (German): Wenn BT-81 "Payment means type code" einen Schlüssel für Lastschriften enthält (59), muss genau BG-19 "DIRECT DEBIT" übermittelt werden.

Why this error occurs

This rule only applies when another field has a certain value (for example a payment means code or an invoice type). Your file triggers the condition but does not provide the data that then becomes mandatory, or provides data that is then forbidden.

How to fix it

Either change the triggering value so the condition no longer applies, or add/remove the dependent elements as the rule text describes. Check the condition in the XPath test above to see exactly which value triggers it.

What the validator checks

Checked element (context):

UBL

/ubl:Invoice/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = '59'] | /cn:CreditNote/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = '59']

Test (XPath):

cac:PaymentMandate

CII

/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans[normalize-space(ram:TypeCode) = '59']

Test (XPath):

/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:DirectDebitMandateID or                     /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:CreditorReferenceID or                     ram:PayerPartyDebtorFinancialAccount/ram:IBANID

Check your invoice

Drop your XML or PDF on the validator and every failed rule is linked to its page here. Free, no account, the file is not stored.

Check your invoice →

Same check via API:

curl -F file=@invoice.xml https://einvoicechecker.com/v1/validate

Related rules

Frequently asked questions

What does BR-DE-25-a mean?

BR-DE-25-a is a xrechnung rule: If BT-81 "Payment means type code" contains a code for direct debits (59), exactly BG-19 "DIRECT DEBIT" must be transmitted.

Will my invoice be rejected because of BR-DE-25-a?

Yes. BR-DE-25-a is flagged "fatal"; validators (KoSIT, Peppol access points, the German ZRE/OZG-RE portals) reject the invoice until it is fixed.

Which formats does BR-DE-25-a apply to?

XRechnung in UBL or CII syntax, including ZUGFeRD / Factur-X PDFs with the XRECHNUNG profile. Invoices to German public authorities (federal, state and municipal) must pass it. Syntax: UBL and CII.

Source: XRechnung 3.0.2, schematron 2.6.0 (KoSIT, September 2026). Catalogue generated from the official schematron on 2026-10-14.