How do I fix DE-R-023-1?

Invoice Navigator automatically fixes this issue by correcting the `cbc:PaymentMeansCode` element in your Invoice (DE-R-023-1). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is DE-R-023-1 a critical error?

Yes, DE-R-023-1 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can DE-R-023-1 be automatically fixed?

Many instances of DE-R-023-1 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.

errorDEUEN 16931

`DE-R-023-1`:Credit transfer details missing. When payment code 30 or 58 (credit...

Credit transfer details missing. When payment code 30 or 58 (credit transfer) is used, the Credit Transfer group (BG-17) with bank account details must be provided.

Severity

Fatal

Rule set

EN 16931

Country

DEU

Fix type

AUTO-FIX

Confidence

80%

Engine Classification

Ensure delivery postal code is present for XRechnung

Confidence: 80% · Applied automatically in pipeline

What is DE-R-023-1?

DE-R-023-1 is a fatal validation rule defined in the EN 16931 specification (DEU national rules). It validates the PostalZone 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:PostalZone

Get API Access Test This Error ↓

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-1 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.

Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.

Validator Behavior

·Causes invoice rejection
·Rejected by XRechnung endpoints
·Error returned: DE-R-023-1
·Specification: EN 16931

Before / After

Failing XML

<cac:PaymentMeans>
  <cbc:PaymentMeansCode>INVALID_CODE</cbc:PaymentMeansCode>
</cac:PaymentMeans>

Corrected XML

<cac:PaymentMeans>
  <cbc:PaymentMeansCode>VALID_CODE</cbc:PaymentMeansCode>
</cac:PaymentMeans>

Technical Reference

XPath//cac:Delivery/cac:DeliveryLocation/cac:Address/cbc:PostalZone

SpecEN 16931

Operationset_default

StrategyEnsure delivery postal code is present for XRechnung

Common Causes

·Credit transfer payment code but no BG-17 provided
·BT-81 code 30 or 58 requires CREDIT TRANSFER group
·cac:PaymentMeans code for bank transfer missing account
·Payment method is credit transfer but no bank details
·BG-17 cac:PayeeFinancialAccount required for wire transfer

Seeing this in production? The API handles DE-R-023-1 automatically. See the fix response →

Related Errors

BR-49

A Payment instruction (BG-16) shall specify the Payment means type code (BT-81)

BR-50

A Payment account identifier (BT-84) shall be present if Credit transfer...

DE-R-024-1

Payment card details missing. When payment code 48, 54, or 55 (payment card)...

Last updated: 27 February 2026

Share this guide:

Handle DE-R-023-1 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

DE-R-023-1:Credit transfer details missing. When payment code 30 or 58 (credit...