How do I fix BR-DEX-13?

Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-13). You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Is BR-DEX-13 a critical error?

Yes, BR-DEX-13 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted.

Can BR-DEX-13 be automatically fixed?

Yes, BR-DEX-13 can be automatically corrected. The fix is applied without modifying financial fields.

Error codes · XRechnung · Germany

BR-DEX-13In your invoicing software

Die maximale Anzahl zulässiger Nachkommastellen für das Element "Third party...

This is the rejection, word for word: „[BR-DEX-13] Too many decimals in third party amount. Third party payment amount (BT-DEX-002) can have at most 2 decimal places.“

What to have readyNothing. The file has to be re-exported from your invoicing software; we check it again afterwards.

What we doInvoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-DEX-13).

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

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

After

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

Element order is part of the rule: if the element sits in the wrong place, the validator rejects with BR-DEX-13.

What the finding looks likeExample

FindingStructure invalid · BR-DEX-13

Location//ext:UBLExtensions//cbc:InvoicedQuantity

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check

Often appears together with

BR-DE-01Invalid Leitweg-ID Format BR-DE-02Payment terms text recommended BR-DE-1Eine Rechnung (INVOICE) muss Angaben zu "PAYMENT INSTRUCTIONS" (BG-16)...