What causes the BR-33 error?

Each invoice line must have a unique identifier.

Add unique ID to each invoice line. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

Is BR-33 a critical error?

Yes, BR-33 is a critical error that will cause invoice rejection. It must be fixed before submission to ensure your invoice is accepted by the recipient's system.

Can BR-33 be automatically fixed?

Many instances of BR-33 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invoice line identifier required.

Which accounting software causes BR-33?

BR-33 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Error codes · EN 16931

BR-33In your invoicing software

Document level allowance reason required

This is the rejection, word for word: „[BR-33] A document level allowance (discount) is missing both a reason text (BT-97) and reason code (BT-98). At least one must be provided to explain why this discount exists.“

XPath: /Invoice/cac:AllowanceCharge[cbc:ChargeIndicator='false']/cbc:AllowanceChargeReasonCode or cbc:AllowanceChargeReason. Code 95 = Discount (UNCL5189).

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-33).

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: Each Document level allowance shall have a Document level al -->
</Invoice>

After

<Invoice>
  <!-- Issue resolved per EN 16931 -->
</Invoice>

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

What the finding looks likeExample

FindingStructure invalid · BR-33

Location//cac:InvoiceLine/cac:Item/cbc:Name

From youA re-exported file

ThenRe-export

ProofSHA-256 and /verify link after the check

Often appears together with

BR-14Invoice total amount with VAT required UBL-CR-003Disallowed element: cbc:ProfileExecutionID