Skip to content

BR-DE-24-a: Payment card information (BG-18) is missing for card payment

Official message

[BR-DE-24-a] 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.

XRechnung (CII) · Error · Message language: German · Version: xrechnung-3.0.2-validator-configuration-2026-08-31

[BR-DE-24-a] 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.

XRechnung (UBL) · Error · Message language: German · Version: xrechnung-3.0.2-validator-configuration-2026-08-31
Severity
Error The invoice is invalid and may be rejected by the recipient.
Applies to
XRechnung (CII), XRechnung (UBL)
Affected fields
BT-81, BG-18

What does this mean?

If a card payment is the payment means (code 48, 54 or 55 in BT-81), the group "Payment card information" (BG-18) must be provided. It is missing for the payment means concerned.

Typical causes

A card payment code was selected, but no card number was entered.
The code was selected by mistake although payment is made by credit transfer or direct debit.

How to fix the error

For card payment, add the card details, at least the payment card primary account number (BT-87); according to the note on BT-87 in EN 16931 the full card number must not be included in the invoice for security reasons.
CII: ram:SpecifiedTradeSettlementPaymentMeans/ram:ApplicableTradeSettlementFinancialCard, UBL: cac:PaymentMeans/cac:CardAccount.
If payment is not made by card, select the matching payment means code.
Generate and validate the invoice again.

In E-Rechnungsfreund

In the invoice form ("Experte" view), section "Zahlungsmittel (BG-16)" (payment means), fill in "Karten-PAN (BT-87)" and, if needed, "Karteninhaber (BT-88)" for the payment means with code 48, 54 or 55, or correct the "Zahlungscode (BT-81)".

Example

Wrong

<ram:SpecifiedTradeSettlementPaymentMeans>
  <ram:TypeCode>54</ram:TypeCode>
</ram:SpecifiedTradeSettlementPaymentMeans>

Correct

<ram:SpecifiedTradeSettlementPaymentMeans>
  <ram:TypeCode>54</ram:TypeCode>
  <ram:ApplicableTradeSettlementFinancialCard>
    <ram:ID>1234</ram:ID>
    <ram:CardholderName>Max Mustermann</ram:CardholderName>
  </ram:ApplicableTradeSettlementFinancialCard>
</ram:SpecifiedTradeSettlementPaymentMeans>
For developers: test expression per syntax

XRechnung (CII) (CII)

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

ram:ApplicableTradeSettlementFinancialCard

XRechnung (UBL) (UBL)

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

cac:CardAccount

Related validation rules

  • BR-DE-1: Payment instructions (BG-16) are missing
  • BR-DE-10: Deliver to city (BT-77) is missing
  • BR-DE-11: Deliver to post code (BT-78) is missing
  • BR-DE-14: VAT category rate (BT-119) is missing in the VAT breakdown
  • BR-DE-15: Buyer reference (BT-10) is missing
  • BR-DE-16: Seller VAT ID, tax number or tax representative is missing

Last updated:
Explanation of the validation rule, not legal or tax advice.