BR-17:Invoice line item name required
Each invoice line must have an item name describing what is being invoiced.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Item Name
What is BR-17?
BR-17 is a fatal validation rule defined in the EN 16931 specification. It validates the Name element under InvoiceLine > Item 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: XPath: /Invoice/cac:InvoiceLine/cac:Item/cbc:Name
Why This Error Matters
Invoice rejected. Buyer cannot identify who to pay when it differs from the seller.
BR-17 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.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-17
- ·Specification: EN 16931
How to Fix It
Describe item
Clear description of goods or services
Be specific
Include relevant details for identification
Add to Item
Place in Item/Name element
Before / After
<cac:PartyName> <cbc:Name><!-- invalid or missing value --></cbc:Name> </cac:PartyName>
<cac:PartyName> <cbc:Name>correct-value</cbc:Name> </cac:PartyName>
Technical Reference
XPath: /Invoice/cac:InvoiceLine/cac:Item/cbc:NameCode Example
<cac:Item>
<cbc:Name>Professional consulting services - December 2024</cbc:Name>
</cac:Item>Common Causes
- ·PayeeParty section added but PartyName not filled
- ·Factoring company not fully configured in system
- ·Third-party payment setup missing payee name
- ·Template includes payee structure but name field empty
- ·Payment to different entity configured without name
Seeing this in production? The API handles BR-17 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
Each invoice line must have an item name describing what is being invoiced.
This requires user input to resolve. Provide the correct value for `cbc:Name` (BT-59). Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, BR-17 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.
BR-17 requires specific business data to resolve. Invoice Navigator detects the error and guides you through providing the needed information, then applies the fix with full audit documentation.
BR-17 is commonly seen in exports from All invoicing software. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Content
Last updated: 3 March 2026
Resolve BR-17 with Guided Input
The compliance engine detects this error and prompts for the required business data before applying a safe, auditable fix.