BR-33:Document level allowance reason required
Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-33). Upload your invoice to fix this automatically.
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.
Engine Classification
Add default item name when missing per EN16931 BR-33
Confidence: 85% · Applied automatically in pipeline
What is BR-33?
BR-33 is a fatal validation rule defined in the EN 16931 specification. It validates the Name element under Item in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: //cac:InvoiceLine/cac:Item/cbc:Name
Why This Error Matters
Invoice rejected. Buyer needs to understand what the allowance is for.
BR-33 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
- ·Error returned: BR-33
- ·Specification: EN 16931
How to Fix It
Find allowance
Locate the cac:AllowanceCharge with ChargeIndicator=false that is missing reason
Add reason code
Insert <cbc:AllowanceChargeReasonCode>95</cbc:AllowanceChargeReasonCode> (95 = Discount)
Or add reason text
Alternatively add <cbc:AllowanceChargeReason>Discount</cbc:AllowanceChargeReason>
Before / After
<Invoice> <!-- Issue: Each Document level allowance shall have a Document level al --> </Invoice>
<Invoice> <!-- Issue resolved per EN 16931 --> </Invoice>
Technical Reference
//cac:InvoiceLine/cac:Item/cbc:NameCode Example
<cac:InvoiceLine>
<cbc:ID>1</cbc:ID>
<!-- line content -->
</cac:InvoiceLine>
<cac:InvoiceLine>
<cbc:ID>2</cbc:ID>
<!-- next line -->
</cac:InvoiceLine>Common Causes
- ·Document allowance has no reason text or code
- ·AllowanceChargeReason and ReasonCode both empty
- ·Generic discount applied without categorization
- ·Export template missing reason field mapping
- ·Allowance reason not mandatory in source system
Seeing this in production? The API handles BR-33 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
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.
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.
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.
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.
Related Errors
Related Content
Last updated: 27 February 2026
Validate your invoice
Drop your XML here to check for BR-33
Auto-fix BR-33 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.