How do I fix DE-R-005?

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

Is DE-R-005 a critical error?

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

Can DE-R-005 be automatically fixed?

Many instances of DE-R-005 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-005`:Seller contact name required (XRechnung)

German XRechnung invoices must include a contact person name (BT-41) in the Seller Contact group (BG-6).

Severity

Fatal

Rule set

EN 16931

Country

DEU

Fix type

INPUT REQUIRED

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Contact Person Name

What is DE-R-005?

DE-R-005 is a fatal validation rule defined in the EN 16931 specification (DEU national rules). It checks whether seller contact name required (xrechnung).

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.

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-005 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-005
·Specification: EN 16931

Before / After

Failing XML

<cac:Contact>
  <cbc:Name><!-- invalid or missing value --></cbc:Name>
</cac:Contact>

Corrected XML

<cac:Contact>
  <cbc:Name>correct-value</cbc:Name>
</cac:Contact>

Technical Reference

SpecEN 16931

StrategyRequires seller contact person name — business-specific data

Common Causes

·German invoice missing seller contact point
·BT-41 Seller contact point not provided
·cbc:Name in seller contact empty or absent
·Contact person name required for XRechnung
·German public sector needs named contact

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

Handle DE-R-005 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-005:Seller contact name required (XRechnung)