errorbusinessDEUEN 16931

DE-R-017:Invalid invoice type code. German invoices only allow specific type codes:...

Fix: Invoice Navigator automatically fixes this issue by correcting the `cbc:InvoiceTypeCode` element in your Invoice (DE-R-017). Upload your invoice to fix this automatically.

Invalid invoice type code. German invoices only allow specific type codes: 326 (partial), 380 (commercial), 384 (corrected), 389 (self-billed), 381 (credit note), 875-877 (construction).

Severity
Fatal
Rule set
EN 16931
Country
DEU
Fix type
AUTO-FIX
Confidence
80%
Category
structural

Engine Classification

Ensure seller postal code is present for XRechnung compliance

Confidence: 80% · Applied automatically in pipeline

What is DE-R-017?

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

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-017 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

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

How to Fix It

1.

Find the missing or empty field

Check cbc:PostalZone at //cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:PostalZone. This field is required but is either missing or empty.

2.

Set the required value

Invoice Navigator automatically fixes this issue by correcting the `cbc:InvoiceTypeCode` element in your Invoice (DE-R-017).

3.

Re-validate your invoice

Upload the corrected invoice to confirm DE-R-017 is resolved.

Before / After

Failing XML
<Invoice>
  <cbc:InvoiceTypeCode>INVALID_CODE</cbc:InvoiceTypeCode>
</Invoice>
Corrected XML
<Invoice>
  <cbc:InvoiceTypeCode>VALID_CODE</cbc:InvoiceTypeCode>
</Invoice>

Technical Reference

XPath//cac:AccountingSupplierParty/cac:Party/cac:PostalAddress/cbc:PostalZone
SpecEN 16931
Operationset_default
StrategyEnsure seller postal code is present for XRechnung compliance

Common Causes

  • ·Invoice type code not valid for German e-invoicing
  • ·BT-3 must be 326, 380, 384, 389, 381, 875, 876, or 877
  • ·cbc:InvoiceTypeCode contains unsupported value
  • ·German validation limits allowed invoice types
  • ·UNTDID 1001 code not in XRechnung permitted list

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

Frequently Asked Questions

Invalid invoice type code. German invoices only allow specific type codes: 326 (partial), 380 (commercial), 384 (corrected), 389 (self-billed), 381 (credit note), 875-877 (construction).

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

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

Many instances of DE-R-017 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

Share this guide:

Validate your invoice

Drop your XML here to check for DE-R-017

Auto-fix DE-R-017 in seconds

Upload your invoice and we fix this error automatically. Financial fields are never touched.