DE-R-023-2:Conflicting payment information. When payment code 30 or 58 (credit transfer) is used, card payment (BG-18) and direct d
Fix: 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.
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 rejected by Peppol access points and never reaches 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 — the invoice must be corrected and re-sent before it can reach the recipient.
Validator Behavior
- ·Causes invoice rejection
- ·Rejected by PEPPOL Access Points
- ·Rejected by XRechnung endpoints
- ·Error returned: DE-R-023-2
- ·Specification: PEPPOL_BIS
How to Fix It
Find the missing or empty field
Check cbc:StreetName at //cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:StreetName. This field is required but is either missing or empty.
Set the required value
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.
Re-validate your invoice
Upload the corrected invoice to confirm DE-R-023-2 is resolved.
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 →
Frequently Asked Questions
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.
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. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, DE-R-023-2 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of DE-R-023-2 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for DE-R-023-2
Fix DE-R-023-2 with one click
Upload your invoice and we'll suggest a fix for your review before applying it.