How do I fix DE-R-020?

Invoice Navigator automatically fixes this issue by correcting the `cbc:Note` element in your Invoice. You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.

Is DE-R-020 a critical error?

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

Can DE-R-020 be automatically fixed?

Many instances of DE-R-020 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-020`:Debited account identifier (BT-91) should contain a valid IBAN if code 59...

Invalid debit IBAN format. When payment means code 59 (SEPA direct debit) is used, the debited account (BT-91) must contain a valid IBAN.

Severity

Fatal

Rule set

EN 16931

Country

DEU

Fix type

AUTO-FIX

Confidence

80%

Engine Classification

Ensure buyer postal code is present for XRechnung compliance

Confidence: 80% · Applied automatically in pipeline

What is DE-R-020?

DE-R-020 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 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:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:PostalZone

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-020 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.

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

Before / After

Failing XML

<cac:PaymentTerms>
  <cbc:Note>INVALID_CODE</cbc:Note>
</cac:PaymentTerms>

Corrected XML

<cac:PaymentTerms>
  <cbc:Note>VALID_CODE</cbc:Note>
</cac:PaymentTerms>

Technical Reference

XPath//cac:AccountingCustomerParty/cac:Party/cac:PostalAddress/cbc:PostalZone

SpecEN 16931

Operationset_default

StrategyEnsure buyer postal code is present for XRechnung compliance

Common Causes

·SEPA direct debit missing valid debtor IBAN
·BT-91 debited account not valid IBAN format
·Payment means code 59 requires IBAN in debit account
·Customer bank account not in IBAN format for SEPA
·cbc:ID in cac:PaymentMandate/cac:PayerFinancialAccount invalid

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

Related Errors

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-020 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-020:Debited account identifier (BT-91) should contain a valid IBAN if code 59...