How do I fix BR-DEX-10?

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.

Is BR-DEX-10 a critical error?

Yes, BR-DEX-10 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can BR-DEX-10 be automatically fixed?

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.

errorDEUXRechnung (Germany)

`BR-DEX-10`:Missing third party payment type. When using third party payment group...

Missing third party payment type. When using third party payment group (BG-DEX-09), the payment type (BT-DEX-001) is required.

Severity

Fatal

Rule set

XRechnung (Germany)

Country

DEU

Fix type

AUTO-FIX

Confidence

75%

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 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:LineExtensionAmount

Get API Access Test This Error ↓

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. 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-10
·Specification: XRechnung (Germany)

Before / After

Failing XML

<Invoice>
  <!-- Issue: When using third party payment group (BG-DEX-09), the paymen -->
</Invoice>

Corrected XML

<Invoice>
  <!-- Issue resolved per XRechnung (Germany) -->
</Invoice>

Technical Reference

XPath//ext:UBLExtensions//cbc:LineExtensionAmount

SpecXRechnung (Germany)

Operationrecalculate

StrategyRecalculate sub-invoice line extension amounts in XRechnung extension

Common 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 →

Related Errors

BR-DE-01

Invalid Leitweg-ID Format

BR-DE-02

Payment terms text recommended

BR-DE-1

Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16)...

Last updated: 27 February 2026

Share this guide:

Handle BR-DEX-10 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API Access View API Documentation

BR-DEX-10:Missing third party payment type. When using third party payment group...