errorEN 16931

BR-25:Invoice line item name required

Each Invoice line shall contain the Item name (BT-153). This describes the goods or services being invoiced.

Severity
Fatal
Rule set
EN 16931
Country
All EU
Fix type
INPUT REQUIRED
Confidence
80%
Category
identifier

Engine Classification

Business data required · Explicit input workflow · No assumptions made

Required input: Seller Electronic Address, Scheme ID

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 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:AccountingSupplierParty/cac:Party/cbc:EndpointID

Get API AccessTest This Error ↓

Why This Error Matters

Invoice rejected. Buyers must be able to identify what they are being charged for.

BR-25 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-25
  • ·Specification: EN 16931

How to Fix It

1.

Get Peppol ID

Your registered Peppol participant ID

2.

Add scheme

Common: 0088 (GLN), 0184 (PEPPOL), 0106 (NL KVK)

3.

Format correctly

Scheme in schemeID attribute, ID in element value

Before / After

Failing XML
<cac:Item><cbc:Name></cbc:Name></cac:Item>
Corrected XML
<cac:Item><cbc:Name>Consulting Services - January 2026</cbc:Name></cac:Item>

Technical Reference

XPathXPath: /Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID
SpecEN 16931
StrategyRequires user input: Name/description of the item or service. Cannot auto-derive because this describes the actual goods/services delivered.

Code 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

Peppol-enabled systems

Frequently Asked Questions

The seller must have an electronic address (endpoint) for Peppol routing.

Add seller EndpointID with scheme identifier. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.

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.

Many instances of BR-25 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including seller electronic address required.

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.

See Also

EN 16931 Validator

Check your invoice now

Related Errors

BR-26

Each Invoice line (BG-25) shall contain the Item net price (BT-146).

BR-62

The Seller electronic address (BT-34) shall have a Scheme identifier.

Last updated: 27 February 2026

Share this guide:

Handle BR-25 Automatically in Your Pipeline

The compliance engine auto-remediates this error with controlled safety policies and evidence pack generation.

Get API AccessView API Documentation