BR-DE-25:XRechnung invoice type restriction
XRechnung restricts allowed invoice type codes.
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 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:InvoiceTypeCode
Why This Error Matters
XRechnung has limited type codes.
BR-DE-25 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-25
- ·Specification: xrechnung
How to Fix It
Check type code
InvoiceTypeCode value
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.
<!-- Missing or empty element triggers cbc:InvoiceTypeCode error --> <cbc:InvoiceTypeCode></cbc:InvoiceTypeCode>
<!-- Provide the required value --> <cbc:InvoiceTypeCode>VALID_VALUE</cbc:InvoiceTypeCode>
Technical Reference
XPath: /Invoice/cbc:InvoiceTypeCodeCommon 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 Content
Last updated: 3 March 2026
Detect BR-DE-25 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.