BR-44:Invoice line charge reason required
Fix: Invoice Navigator automatically fixes this Invoice compliance issue by updating the relevant XML elements (BR-44). Upload your invoice to fix this automatically.
An invoice line charge (BG-28) is missing both a reason text and reason code. At least one must be provided to explain this line surcharge.
Engine Classification
Add default scheme ID (GTIN/EAN) for item standard identifier
Confidence: 85% · Applied automatically in pipeline
What is BR-44?
BR-44 is a fatal validation rule defined in the EN 16931 specification. It validates the @schemeID element under StandardItemIdentification > ID 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/cac:StandardItemIdentification/cbc:ID/@schemeID
Why This Error Matters
Invoice rejected. Each charge must be explained for buyer verification.
BR-44 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-44
- ·Specification: EN 16931
How to Fix It
Find line charge
Locate the cac:AllowanceCharge with ChargeIndicator=true within cac:InvoiceLine that is missing reason
Add reason code
Insert <cbc:AllowanceChargeReasonCode>SAA</cbc:AllowanceChargeReasonCode> (SAA = Shipping and handling)
Or add reason text
Alternatively add <cbc:AllowanceChargeReason>Service charge</cbc:AllowanceChargeReason>
Before / After
<Invoice> <!-- Issue: Each Invoice line charge shall have an Invoice line charge r --> </Invoice>
<Invoice> <!-- Issue resolved per EN 16931 --> </Invoice>
Technical Reference
//cac:InvoiceLine/cac:Item/cac:StandardItemIdentification/cbc:ID/@schemeIDCode Example
<cac:AdditionalDocumentReference>
<cbc:ID>DOC-001</cbc:ID>
<cbc:DocumentDescription>Technical specifications</cbc:DocumentDescription>
<cac:Attachment>
<cbc:EmbeddedDocumentBinaryObject mimeCode="application/pdf" filename="specs.pdf">
<!-- Base64 content -->
</cbc:EmbeddedDocumentBinaryObject>
</cac:Attachment>
</cac:AdditionalDocumentReference>Common Causes
- ·Line charge missing reason text or code
- ·Neither ChargeReason nor ReasonCode provided
- ·Line surcharge applied without categorization
- ·Template missing line charge reason field
- ·Reason not required in source line item charge
Seeing this in production? The API handles BR-44 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Additional document references should include a description.
Add description to document attachments. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
BR-44 is a warning that may not always cause rejection, but it indicates a potential compliance issue that should be addressed to ensure full compatibility.
Many instances of BR-44 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including attachment should have description.
BR-44 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-44
Auto-fix BR-44 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.