How do I fix DE-R-001?

This requires user input to resolve. Provide the correct value for `cac:PaymentMeans` (BG-16) (DE-R-001). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is DE-R-001 a critical error?

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

Can DE-R-001 be automatically fixed?

Many instances of DE-R-001 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-001`:Payment instructions missing

German invoices must include payment instructions — how the buyer should pay. This typically means a bank account (IBAN) and payment method code (e.g. SEPA Credit Transfer).

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: Payment Method, IBAN, Account Name (optional)

What is DE-R-001?

DE-R-001 is a fatal validation rule defined in the EN 16931 specification (DEU national rules). It validates the PaymentMeansCode element under PaymentMeans 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: /Invoice/cac:PaymentMeans/cbc:PaymentMeansCode

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

How to Fix It

Before / After

Failing XML

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

Corrected XML

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

Technical Reference

XPath/Invoice/cac:PaymentMeans/cbc:PaymentMeansCode

SpecEN 16931

Operationset_default

StrategyPrompt user for payment method and bank account details, then create the PaymentMeans element

Common Causes

·German invoice missing payment instructions group
·BG-16 PAYMENT INSTRUCTIONS not present
·cac:PaymentMeans element required for XRechnung
·Payment method not specified in invoice
·German validation requires explicit payment info

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

Related Errors

BR-49

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

Last updated: 27 February 2026

Share this guide:

Handle DE-R-001 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-001:Payment instructions missing