Fix BR-DE-25-b: Direct debit with account or card data

BR-DE-25-b in your own invoice? Upload the file and find every error in seconds.

What does BR-DE-25-b mean?

With payment means 59 (SEPA direct debit) the payment means must not contain an account for credit transfer (BG-17) or card data (BG-18). In CII the BIC of payee and payer count as well. The debtor IBAN (BT-91), however, belongs there. The rule comes from KoSIT (XRechnung) and is an error there. For ZUGFeRD our validator only reports it as info.

Common causes of BR-DE-25-b

The software writes your own IBAN into the invoice as for a credit transfer.
The BIC of your own account is still in the payment means.

How to fix BR-DE-25-b

Find the faulty spot in the XML. Open the XML of the invoice and go to field BT-81 along this XPath://ram:SpecifiedTradeSettlementPaymentMeans[ram:TypeCode='59']
Apply the fix. With payment means 59 (SEPA direct debit) this payment means must not contain an account for credit transfer (BG-17, 'ram:PayeePartyCreditorFinancialAccount') or card data (BG-18), and in CII no BIC either ('ram:PayeeSpecifiedCreditorFinancialInstitution', 'ram:PayerSpecifiedDebtorFinancialInstitution'). Remove them; the debtor IBAN ('ram:PayerPartyDebtorFinancialAccount') stays. For ZUGFeRD the validator only reports the rule as info; it applies to XRechnung.
Validate again. Save the file and validate it again to check that BR-DE-25-b is no longer reported.

Concrete fix

With payment means 59 (SEPA direct debit) this payment means must not contain an account for credit transfer (BG-17, 'ram:PayeePartyCreditorFinancialAccount') or card data (BG-18), and in CII no BIC either ('ram:PayeeSpecifiedCreditorFinancialInstitution', 'ram:PayerSpecifiedDebtorFinancialInstitution'). Remove them; the debtor IBAN ('ram:PayerPartyDebtorFinancialAccount') stays. For ZUGFeRD the validator only reports the rule as info; it applies to XRechnung.

XPath//ram:SpecifiedTradeSettlementPaymentMeans[ram:TypeCode='59']

Before / after: the XML example

This is the spot in question before and after the fix (Cross Industry Invoice, ZUGFeRD/Factur-X).

Wrong

<ram:SpecifiedTradeSettlementPaymentMeans>
  <ram:TypeCode>59</ram:TypeCode>
  <ram:PayerPartyDebtorFinancialAccount>
    <ram:IBANID>DE89370400440532013000</ram:IBANID>
  </ram:PayerPartyDebtorFinancialAccount>
  <ram:PayeePartyCreditorFinancialAccount>
    <ram:IBANID>DE02120300000000202051</ram:IBANID>
  </ram:PayeePartyCreditorFinancialAccount>
</ram:SpecifiedTradeSettlementPaymentMeans>

Correct

<ram:SpecifiedTradeSettlementPaymentMeans>
  <ram:TypeCode>59</ram:TypeCode>
  <ram:PayerPartyDebtorFinancialAccount>
    <ram:IBANID>DE89370400440532013000</ram:IBANID>
  </ram:PayerPartyDebtorFinancialAccount>
</ram:SpecifiedTradeSettlementPaymentMeans>

Frequent questions about BR-DE-25-b

Where do I give my own IBAN with a direct debit?

Not in the payment means: with a direct debit the buyer does not pay, you collect the amount. The creditor ID (BT-90) and the mandate reference (BT-89) show who collects.

What does BR-DE-25-a check?

The first part of the same rule: with direct debit the direct debit data must be in the invoice (BG-19).

Related error codes

Check BR-DE-25-b automatically

Instead of digging through the XML by hand you can validate your ZUGFeRD or XRechnung file online: upload the PDF or the XML and you get every error with rule ID, affected field, fix and XPath, as a readable report or as JSON through the API.

Validate online now Back to the lexicon