errorDEUxrechnung

BR-DE-04:Invalid XRechnung CustomizationID

XRechnung invoices must use the correct specification identifier for the version.

Severity
Fatal
Rule set
xrechnung
Country
DEU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: The XRechnung CustomizationID specifies the format version and must be set correctly in your invoicing software. Update your ERP/invoicing system to use the correct XRechnung specification identifier for the target version (e.g., urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0).

What is BR-DE-04?

BR-DE-04 is a fatal validation rule defined in the xrechnung specification (DEU national rules). It validates the CustomizationID element under Invoice 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: XPath: /Invoice/cbc:CustomizationID

This error requires manual correction — financial fields are protected by policy.Get API Access

Why This Error Matters

German government portals (ZRE, OZG-RE) validate the CustomizationID strictly.

BR-DE-04 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: BR-DE-04
  • ·Specification: xrechnung

How to Fix It

1.

Check version

XRechnung 3.0 is current for 2024+

2.

Use correct ID

urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0

3.

Update template

Ensure your export uses current version

XML Example

Generic example based on the rule's target XPath. Your actual XML structure may differ.

Before
<!-- Missing or empty element triggers cbc:CustomizationID error -->
<cbc:CustomizationID></cbc:CustomizationID>
After
<!-- Provide the required value -->
<cbc:CustomizationID>VALID_VALUE</cbc:CustomizationID>

Technical Reference

XPathXPath: /Invoice/cbc:CustomizationID
Specxrechnung

Code Example

<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0</cbc:CustomizationID>

Common Causes

  • ·Old XRechnung version
  • ·Using Peppol ID instead
  • ·Typo in specification

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

Commonly Seen In

All German invoicing software

Frequently Asked Questions

XRechnung invoices must use the correct specification identifier for the version.

Use the correct XRechnung 3.0 CustomizationID. This error involves a protected field — Invoice Navigator flags it in your pipeline so your team can correct it at the source.

Yes, BR-DE-04 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.

BR-DE-04 involves a financial or legal field that cannot be auto-modified by policy. Invoice Navigator detects and flags this error immediately, but the correction must be made manually in your ERP or invoicing software.

BR-DE-04 is commonly seen in exports from All German invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Related Content

Last updated: 3 March 2026

Share this guide:

Detect BR-DE-04 Before Submission

This error involves a financial or legal field that cannot be auto-modified. The compliance engine flags it immediately with a clear diagnosis so your team can fix it at the source.