errorpeppol-bis-3
BR-16:Invoice line must have an identifier
Each invoice line must have a unique line identifier (ID).
Fix this in your source system
MANUALLine identifiers must be unique and consistent with your accounting system. Automatic assignment could break document references and audit trails.
See the step-by-step instructions below to fix this error manually.
Why This Error Matters
Invoice rejected. Without line items, there is no description of goods/services being invoiced.
How to Fix It
1
Number lines
Use sequential numbers (1, 2, 3...) or your internal line references
2
Ensure uniqueness
Each line must have a different ID within the invoice
3
Keep consistent
Line IDs should match your internal order/invoice line numbers
Code Example
<cac:InvoiceLine>\n <cbc:ID>1</cbc:ID>\n <cbc:InvoicedQuantity unitCode="C62">10</cbc:InvoicedQuantity>\n <!-- rest of line -->\n</cac:InvoiceLine>Technical Details
XPath: /Invoice/cac:InvoiceLine/cbc:IDCommon Causes
- Header-only invoice exported without line details
- InvoiceLine elements failed to export from source
- Summary invoice created without itemization
- Export template missing InvoiceLine section entirely
- Line items filtered out due to zero-value or invalid data
Commonly Seen In
All invoicing software
Frequently Asked Questions
Each invoice line must have a unique line identifier (ID).
Add a unique ID to each invoice line. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-16 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-16 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 must have an identifier.
BR-16 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
Last updated: 18 January 2026
Share this guide: