BR-25:Invoice line item name required
Fix: This requires user input to resolve. Provide the correct value for `cbc:Name`. Provide the required value in the free validator.
Each Invoice line shall contain the Item name (BT-153). This describes the goods or services being invoiced.
Engine Classification
Business data required · Explicit input workflow · No assumptions made
Required input: Item Name
What is BR-25?
BR-25 is a fatal validation rule defined in the EN 16931 specification. It validates the EndpointID element under AccountingSupplierParty > Party in the UBL invoice XML.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Target path: XPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID
Why This Error Matters
Invoice rejected. Buyers must be able to identify what they are being charged for.
BR-25 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-25
- ·Specification: EN 16931
How to Fix It
Get Peppol ID
Your registered Peppol participant ID
Add scheme
Common: 0088 (GLN), 0184 (PEPPOL), 0106 (NL KVK)
Format correctly
Scheme in schemeID attribute, ID in element value
Before / After
<cac:Item><cbc:Name></cbc:Name></cac:Item>
<cac:Item><cbc:Name>Consulting Services - January 2026</cbc:Name></cac:Item>
Technical Reference
XPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointIDCode Example
<cac:Party>
<cbc:EndpointID schemeID="0106">12345678</cbc:EndpointID>
<!-- Rest of party info -->
</cac:Party>Common Causes
- ·Item Name field not mapped in export template
- ·Product description used but Name field left empty
- ·Generic line item created without product details
- ·Export template missing Item/Name field mapping
- ·Product master data incomplete - name not filled
Seeing this in production? The API handles BR-25 automatically. See the fix response →
Commonly Seen In
Frequently Asked Questions
The seller must have an electronic address (endpoint) for Peppol routing.
This requires user input to resolve. Provide the correct value for `cbc:Name`. Invoice Navigator detects this error and prompts for the required business data before applying a safe fix.
Yes, BR-25 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-25 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-25 is commonly seen in exports from Peppol-enabled systems. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.
Related Errors
Related Content
Last updated: 15 April 2026
Validate your invoice
Drop your XML here to check for BR-25
Fix BR-25 with guided input
Upload your invoice and we'll ask for the missing data, then apply a safe, auditable fix.