BR-DEX-13:Die maximale Anzahl zulässiger Nachkommastellen für das Element "Third party...
Too many decimals in third party amount. Third party payment amount (BT-DEX-002) can have at most 2 decimal places.
Engine Classification
Ensure sub-invoice quantity is present in XRechnung extension
Confidence: 75% · Applied automatically in pipeline
What is BR-DEX-13?
BR-DEX-13 is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It validates the InvoicedQuantity element 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//cbc:InvoicedQuantity
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-13 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-13
- ·Specification: XRechnung (Germany)
Before / After
<Invoice> <!-- Issue: Third party payment amount (BT-DEX-002) can have at most 2 d --> </Invoice>
<Invoice> <!-- Issue resolved per XRechnung (Germany) --> </Invoice>
Technical Reference
//ext:UBLExtensions//cbc:InvoicedQuantityCommon Causes
- ·Third party payment amount has too many decimals
- ·BT-DEX-002 exceeds 2 decimal places maximum
- ·Payment amount not rounded to 2 decimals
- ·Currency precision too high for amount field
- ·Calculation produced more than 2 decimal places
Seeing this in production? The API handles BR-DEX-13 automatically. See the fix response →
Related Errors
Last updated: 27 February 2026
Handle BR-DEX-13 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.