A card payment is announced alongside another payment means
When `Payment means type code` (BT-81) announces a card (48, 54 or 55), the `CREDIT TRANSFER` (BG-17) and `DIRECT DEBIT` (BG-19) groups must not be provided.
Only the issuer holds this value: Factlint reports it and never fabricates it. Test your invoice to find out whether it is affected.
Common searches around this code
These phrases mirror what an integrator searches for: code, syntax, rule, business field and correction.
Test your file with this error in mind
Upload the invoice involved: the report will say whether this code appears, where it appears in the document, and whether Factlint can only report it or also fix it.
To automate this check in an ERP flow, call the validation API and link every returned code to its public page.
Why this error happens
The same exclusivity requirement as BR-DE-23-b, seen from the card side. It often fires because the seller's IBAN is written systematically, whatever means was chosen.
How to fix it
Emit only the block for the payment means actually chosen. Factlint does not remove a payment block (rule 1).
XML correction example
<ram:TypeCode>48</ram:TypeCode> … <ram:PayeePartyCreditorFinancialAccount>
<ram:TypeCode>48</ram:TypeCode> … <ram:ApplicableTradeSettlementFinancialCard>