errorcountryDEUxrechnung

BR-DE-25:XRechnung invoice type restriction

Fix: Use allowed codes: 326, 380, 384, 389, 381.

XRechnung restricts allowed invoice type codes.

Severity
Fatal
Rule set
xrechnung
Country
DEU
Fix type
BLOCKED

Engine Classification

Financial or legal field · Modification blocked by policy

Reason: XRechnung only allows specific invoice type codes (380 for Invoice, 381 for Credit Note, 384 for Corrected Invoice, 389 for Self-billed Invoice, 875/876 for partial invoices). Change the invoice type code in your source system to a supported value.

What is BR-DE-25?

BR-DE-25 is a fatal validation rule defined in the xrechnung specification (DEU national rules). It validates the InvoiceTypeCode element under Invoice in the UBL invoice XML.

When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.

Target path: XPath: /Invoice/cbc:InvoiceTypeCode

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

Why This Error Matters

XRechnung has limited type codes.

BR-DE-25 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.

Validator Behavior

  • ·Causes invoice rejection
  • ·Rejected by XRechnung endpoints
  • ·Error returned: BR-DE-25
  • ·Specification: xrechnung

How to Fix It

1.

Check type code

InvoiceTypeCode value

2.

Use allowed code

380 (invoice), 381 (credit), 384 (corrected), 389 (self-billing), 326 (partial)

XML Example

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

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

Technical Reference

XPathXPath: /Invoice/cbc:InvoiceTypeCode
Specxrechnung

Common Causes

  • ·Using unsupported code

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

Frequently Asked Questions

XRechnung restricts allowed invoice type codes.

Use allowed codes: 326, 380, 384, 389, 381. 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-25 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-25 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.

Related Errors

Related Content

Last updated: 3 March 2026

Share this guide:

Validate your invoice

Drop your XML here to check for BR-DE-25

Detect BR-DE-25 before submission

This error involves a financial field that can't be auto-modified. We'll flag it with a clear diagnosis so you can fix it at the source.