BR-DEX-11:Missing third party payment amount. When using third party payment group...
Missing third party payment amount. When using third party payment group (BG-DEX-09), the amount (BT-DEX-002) is required.
Engine Classification
Ensure sub-invoice item name is present in XRechnung extension
Confidence: 75% · Applied automatically in pipeline
What is BR-DEX-11?
BR-DEX-11 is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It validates the Name element under Item 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: //ext:UBLExtensions//cac:Item/cbc:Name
Why This Error Matters
Invoice will be rejected. XRechnung extension rules for German invoices must be followed for proper processing by German public sector recipients.
BR-DEX-11 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: BR-DEX-11
- ·Specification: XRechnung (Germany)
Before / After
<Invoice> <!-- Issue: When using third party payment group (BG-DEX-09), the amount --> </Invoice>
<Invoice> <!-- Issue resolved per XRechnung (Germany) --> </Invoice>
Technical Reference
//ext:UBLExtensions//cac:Item/cbc:NameCommon Causes
- ·Third party payment group missing amount
- ·BG-DEX-09 present but BT-DEX-002 amount not transmitted
- ·Third party payment section without amount value
- ·Payment amount field not mapped in export
- ·XRechnung extension requires payment amount
Seeing this in production? The API handles BR-DEX-11 automatically. See the fix response →
Related Errors
Last updated: 27 February 2026
Handle BR-DEX-11 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.