Error Guide

🇩🇪 BR-DEX-13: Die maximale Anzahl zulässiger Nachkommastellen für das Element "Third party... in Germany

ErrorMandatoryAuto-fixable

Too many decimals in third party amount. Third party payment amount (BT-DEX-002) can have at most 2 decimal places.

Quick Facts

Severity

Error (rejection)

Ruleset

XRechnung (Germany)

Fix Confidence

75%

Mandate

B2B Mandatory

Fix Type

Automatic

Why This Matters in Germany

Germany requires e-invoicing using XRechnung (UBL), XRechnung (CII), ZUGFeRD 2.x. Invoices with this error will be rejected. They cannot be processed for Germany compliance.

Invoice Navigator automatically fixes this error. No manual intervention needed.

Invoice Navigator covers 147 XRechnung 3.0.2 rules for Germany.

How to Fix BR-DEX-13

1
Find the missing or empty field
Check cbc:InvoicedQuantity at //ext:UBLExtensions//cbc:InvoicedQuantity. This field is required but is either missing or empty.
2
Set the required value
Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-13).
3
Re-validate your invoice
Upload the corrected invoice to confirm BR-DEX-13 is resolved.

Example: Before & After

Before (invalid)

<Invoice>
  <!-- Issue: Third party payment amount (BT-DEX-002) can have at most 2 d -->
</Invoice>

After (fixed)

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

Germany E-Invoicing Requirements

Phase

Status

Scope

B2G

Live (Nov 2020)

All federal suppliers

B2B receiving

Live (Jan 2025)

All German businesses

B2B sending

Jan 2027

>€800K annual revenue

B2B sending

Jan 2028

All businesses

Common 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

Fix BR-DEX-13 automatically

Upload your invoice and let Invoice Navigator auto-remediate this error.

Try the Validator Germany Guide →