DE-R-023-2:Conflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct d
Conflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct debit (BG-19) groups must not be provided.
Engine Classification
Requires user confirmation before application
What is DE-R-023-2?
DE-R-023-2 is a fatal validation rule defined in the PEPPOL_BIS specification (DEU national rules). It validates the StreetName element under DeliveryLocation > Address in the UBL invoice XML.
When this rule fires, the invoice is non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach the buyer.
Target path: //cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:StreetName
Why This Error Matters
Invoice will be rejected by German XRechnung validators. German e-invoicing has specific format requirements for payment details, contact information, and attachments.
DE-R-023-2 is a hard failure. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
Validator Behavior
- ·Causes invoice rejection
- ·Rejected by PEPPOL Access Points
- ·Rejected by XRechnung endpoints
- ·Error returned: DE-R-023-2
- ·Specification: PEPPOL_BIS
XML Example
Generic example based on the rule's target XPath. Your actual XML structure may differ.
<!-- Missing or empty element triggers cbc:StreetName error --> <cbc:StreetName></cbc:StreetName>
<!-- Provide the required value --> <cbc:StreetName>VALID_VALUE</cbc:StreetName>
Technical Reference
//cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:StreetNameCommon Causes
- ·Credit transfer has card or direct debit info present
- ·BT-81 code 30/58 must not include BG-18 or BG-19
- ·Payment method conflict: credit transfer with card details
- ·Incompatible payment groups for wire transfer
- ·BG-18/BG-19 present when only BG-17 allowed
Seeing this in production? The API handles DE-R-023-2 automatically. See the fix response →
Last updated: 27 February 2026
Handle DE-R-023-2 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.