BR-44:Invoice line charge reason required
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 non-compliant and will be rejected by Peppol access points and national validation services. The sending system receives a rejection response and the invoice does not reach 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. Invoices that trigger this rule are rejected at the access point and never reach the recipient. In Peppol networks, this means your sending system receives an MLR (Message Level Response) with a rejection status. The invoice must be corrected and re-sent, adding delay to your payment cycle.
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.
See Also
Related Errors
Last updated: 27 February 2026
Handle BR-44 Automatically in Your Pipeline
The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.