Account
English
DeutschFrançaisPolskiNederlands
CheckerXRechnungZUGFeRDFactur-XPeppolUBLKSeFAPIPricingAccount

BR-DE-24-a: If BT-81 "Payment means type code" contains a code for card payments (48, 54, 55),…

XRechnung rule · Error · UBL / CII

StandardXRechnung 3.0.2 (KoSIT, German CIUS of EN 16931)SeverityError: the invoice is rejectedSyntaxUBL, CIIBusiness terms
  • BG-18 Payment card information
  • 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-24-a] If BT-81 "Payment means type code" contains a code for card payments (48, 54, 55), exactly BG-18 "PAYMENT CARD INFORMATION" must be transmitted.

Official text (German): Wenn BT-81 "Payment means type code" einen Schlüssel für Kartenzahlungen enthält (48, 54, 55), muss genau BG-18 "PAYMENT CARD INFORMATION" übermittelt werden.

Why this error occurs

The value is present but does not match the required pattern: wrong date format, an IBAN with a wrong check digit, an e-mail address without a valid structure, a URL without scheme, or a text with forbidden characters.

How to fix it

Correct the value so it matches the format named in the rule: dates as YYYY-MM-DD in UBL and YYYYMMDD with format="102" in CII, IBANs without spaces and with a valid checksum, e-mail addresses with exactly one @, URLs starting with http:// or https://.

What the validator checks

Checked element (context):

UBL

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

Test (XPath):

cac:CardAccount

CII

/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans[normalize-space(ram:TypeCode) = ('48','54','55')]

Test (XPath):

ram:ApplicableTradeSettlementFinancialCard

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-24-a mean?

BR-DE-24-a is a xrechnung rule: If BT-81 "Payment means type code" contains a code for card payments (48, 54, 55), exactly BG-18 "PAYMENT CARD INFORMATION" must be transmitted.

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

Yes. BR-DE-24-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-24-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.