BR-DE-23-b: Card or direct debit details are not allowed for a credit transfer
Official message
[BR-DE-23-b] Wenn BT-81 "Payment means type code" einen Schlüssel für Überweisungen enthält (30, 58), dürfen BG-18 und BG-19 nicht übermittelt werden.
[BR-DE-23-b] Wenn BT-81 "Payment means type code" einen Schlüssel für Überweisungen enthält (30, 58), dürfen BG-18 und BG-19 nicht übermittelt werden.
- 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, BG-19
What does this mean?
If a credit transfer is the payment means (code 30 or 58 in BT-81), no payment card information (BG-18) and no direct debit information (BG-19) may be provided. The invoice contains such information.
Typical causes
The credit transfer payment means additionally contains a card number or a debited account (BT-91).
Mandate reference (BT-89) or creditor identifier (BT-90) are filled in although payment is made by credit transfer. In CII these document-level details also count as direct debit information.
A direct debit template was reused for an invoice paid by credit transfer.
How to fix the error
For payment by credit transfer, remove card details (BT-87, BT-88) as well as mandate reference (BT-89), creditor identifier (BT-90) and debited account (BT-91).
If payment is actually made by direct debit, use payment means code 59 instead.
Generate and validate the invoice again.
In E-Rechnungsfreund
In the invoice form ("Experte" view), section "Zahlungsmittel (BG-16)" (payment means), clear the fields "Karten-PAN (BT-87)", "Karteninhaber (BT-88)" and "Lastschrift-Konto (BT-91)" of the payment means with code 30 or 58.
In section "Zahlungsinformationen / SEPA" (payment information), clear the fields "Mandatsreferenz SEPA (BT-89)" and "Gläubiger-ID SEPA (BT-90)".
Example
Wrong
<ram:ApplicableHeaderTradeSettlement>
<ram:CreditorReferenceID>DE98ZZZ09999999999</ram:CreditorReferenceID>
...
<ram:SpecifiedTradeSettlementPaymentMeans>
<ram:TypeCode>58</ram:TypeCode>
<ram:PayeePartyCreditorFinancialAccount>
<ram:IBANID>DE02120300000000202051</ram:IBANID>
</ram:PayeePartyCreditorFinancialAccount>
</ram:SpecifiedTradeSettlementPaymentMeans>
</ram:ApplicableHeaderTradeSettlement>
Correct
<ram:ApplicableHeaderTradeSettlement>
...
<ram:SpecifiedTradeSettlementPaymentMeans>
<ram:TypeCode>58</ram:TypeCode>
<ram:PayeePartyCreditorFinancialAccount>
<ram:IBANID>DE02120300000000202051</ram:IBANID>
</ram:PayeePartyCreditorFinancialAccount>
</ram:SpecifiedTradeSettlementPaymentMeans>
</ram:ApplicableHeaderTradeSettlement>
For developers: test expression per syntax
XRechnung (CII) (CII)
Context: /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans[normalize-space(ram:TypeCode) = ('30','58')]
not(ram:ApplicableTradeSettlementFinancialCard) and not(/rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradePaymentTerms/ram:DirectDebitMandateID or /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:CreditorReferenceID or ram:PayerPartyDebtorFinancialAccount/ram:IBANID)
XRechnung (UBL) (UBL)
Context: /ubl:Invoice/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = ('30','58')] | /cn:CreditNote/cac:PaymentMeans[normalize-space(cbc:PaymentMeansCode) = ('30','58')]
not(cac:CardAccount) and not(cac:PaymentMandate)
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.