How do I fix DE-R-030?

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

Is DE-R-030 a critical error?

DE-R-030 is a warning that may not always cause rejection, but indicates a compliance issue.

Can DE-R-030 be automatically fixed?

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

warningDEUEN 16931

`DE-R-030`:Creditor identifier missing. When direct debit (BG-19) is used, the bank...

Creditor identifier missing. When direct debit (BG-19) is used, the bank assigned creditor identifier (BT-90) is required for SEPA direct debit.

Severity

Warning

Rule set

EN 16931

Country

DEU

Fix type

AUTO-FIX

Confidence

75%

Engine Classification

Add delivery date (defaults to invoice date) when delivery section present

Confidence: 75% · Applied automatically in pipeline

What is DE-R-030?

DE-R-030 is a warning validation rule defined in the EN 16931 specification (DEU national rules). It validates the ActualDeliveryDate element in the UBL invoice XML.

This is a soft validation failure. The invoice may pass initial transmission, but non-compliant values in this field can cause problems during tax audits, buyer-side processing, or downstream VAT reconciliation.

Target path: //cac:Delivery/cbc:ActualDeliveryDate

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-030 is a soft failure. The invoice may pass initial validation, but the non-compliant field can cause issues at the receiving end — tax authorities may flag it during audits, buyer ERP systems may fail to process it, or VAT reconciliation may produce mismatches. Fixing warnings before they accumulate prevents larger compliance gaps.

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

·Generates validation warning
·Rejected by XRechnung endpoints
·Error returned: DE-R-030
·Specification: EN 16931

Before / After

Failing XML

<cac:PaymentMeans>
  <cac:PaymentMandate><!-- invalid or missing value --></cac:PaymentMandate>
</cac:PaymentMeans>

Corrected XML

<cac:PaymentMeans>
  <cac:PaymentMandate>correct-value</cac:PaymentMandate>
</cac:PaymentMeans>

Technical Reference

XPath//cac:Delivery/cbc:ActualDeliveryDate

SpecEN 16931

Operationset_default

StrategyAdd delivery date (defaults to invoice date) when delivery section present

Common Causes

·Direct debit group missing creditor identifier
·BT-90 required when BG-19 is present
·SEPA mandate missing bank creditor ID
·cbc:ID in cac:PaymentMandate absent
·Direct debit needs creditor identification number

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

Related Errors

BR-67

An Invoice shall contain maximum one Payment Mandate (BG-19).

DE-R-031

If the group "DIRECT DEBIT" (BG-19) is delivered, the element "Debited...

Last updated: 27 February 2026

Share this guide:

Handle DE-R-030 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-030:Creditor identifier missing. When direct debit (BG-19) is used, the bank...