BR-DEX-13:Die maximale Anzahl zulässiger Nachkommastellen für das Element "Third party...
Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-13). Upload your invoice to fix this automatically.
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 rejected by Peppol access points and never reaches 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 — the invoice must be corrected and re-sent before it can reach the recipient.
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)
How to Fix It
Find the missing or empty field
Check cbc:InvoicedQuantity at //ext:UBLExtensions//cbc:InvoicedQuantity. This field is required but is either missing or empty.
Set the required value
Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-13).
Re-validate your invoice
Upload the corrected invoice to confirm BR-DEX-13 is resolved.
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 →
Frequently Asked Questions
Too many decimals in third party amount. Third party payment amount (BT-DEX-002) can have at most 2 decimal places.
Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-13). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, BR-DEX-13 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of BR-DEX-13 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Errors
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for BR-DEX-13
Auto-fix BR-DEX-13 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.