BR-DEX-10:Missing third party payment type. When using third party payment group...
Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-10). Upload your invoice to fix this automatically.
Missing third party payment type. When using third party payment group (BG-DEX-09), the payment type (BT-DEX-001) is required.
Engine Classification
Recalculate sub-invoice line extension amounts in XRechnung extension
Confidence: 75% · Applied automatically in pipeline
What is BR-DEX-10?
BR-DEX-10 is a fatal validation rule defined in the XRechnung (Germany) specification (DEU national rules). It validates the LineExtensionAmount 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:LineExtensionAmount
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-10 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-10
- ·Specification: XRechnung (Germany)
How to Fix It
Identify the calculation mismatch
Check cbc:LineExtensionAmount at //ext:UBLExtensions//cbc:LineExtensionAmount. The value does not match the expected sum or formula result.
Recalculate the value
Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-10).
Re-validate your invoice
Upload the corrected invoice to confirm BR-DEX-10 is resolved. Calculation errors can cascade — check related totals too.
Before / After
<Invoice> <!-- Issue: When using third party payment group (BG-DEX-09), the paymen --> </Invoice>
<Invoice> <!-- Issue resolved per XRechnung (Germany) --> </Invoice>
Technical Reference
//ext:UBLExtensions//cbc:LineExtensionAmountCommon Causes
- ·Third party payment group missing payment type
- ·BG-DEX-09 present but BT-DEX-001 type not transmitted
- ·Third party payment section incomplete
- ·Payment type code not mapped in export
- ·XRechnung extension requires payment type
Seeing this in production? The API handles BR-DEX-10 automatically. See the fix response →
Frequently Asked Questions
Missing third party payment type. When using third party payment group (BG-DEX-09), the payment type (BT-DEX-001) is required.
Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-10). You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, BR-DEX-10 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of BR-DEX-10 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-10
Auto-fix BR-DEX-10 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.