How do I fix DE-R-011?

This requires user input to resolve. Provide the correct value for `cac:Address` (BT-78). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is DE-R-011 a critical error?

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

Can DE-R-011 be automatically fixed?

Many instances of DE-R-011 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-011`:The element "Deliver to post code" (BT-78) shall be provided if the group...

Delivery postal code is missing. When a delivery address is provided in German invoices, the delivery postal code (BT-78) is required.

Severity

Fatal

Rule set

EN 16931

Country

DEU

Fix type

INPUT REQUIRED

Confidence

85%

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Seller email

What is DE-R-011?

DE-R-011 is a fatal validation rule defined in the EN 16931 specification (DEU national rules). It validates the ElectronicMail element under Party > Contact 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:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ElectronicMail

Get API Access Test This Error ↓

Why This Error Matters

Invoice will be rejected by German XRechnung validators. Germany has additional mandatory fields beyond EN16931 baseline, including seller contact details, complete addresses, and buyer reference (Leitweg-ID).

DE-R-011 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 XRechnung endpoints
·Error returned: DE-R-011
·Specification: EN 16931

Before / After

Failing XML

<cac:DeliveryLocation>
  <cac:Address>INVALID_CODE</cac:Address>
</cac:DeliveryLocation>

Corrected XML

<cac:DeliveryLocation>
  <cac:Address>VALID_CODE</cac:Address>
</cac:DeliveryLocation>

Technical Reference

XPath//cac:AccountingSupplierParty/cac:Party/cac:Contact/cbc:ElectronicMail

SpecEN 16931

Operationset_value

StrategySet valid seller contact email for XRechnung (requires user input)

Common Causes

·Delivery address provided but post code missing
·BT-78 Deliver to post code required when BG-15 used
·cbc:PostalZone in delivery address empty or absent
·Partial delivery address invalid for XRechnung
·German validation requires delivery postal code

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

Related Errors

BR-57

Each Deliver to address (BG-15) shall contain a Deliver to country code (BT-80)

DE-R-010

The element "Deliver to city" (BT-77) shall be provided if the group...

Last updated: 27 February 2026

Share this guide:

Handle DE-R-011 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-011:The element "Deliver to post code" (BT-78) shall be provided if the group...