BR-25EN 16931fatalbusiness

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.

Where is this in my invoice?

Shown on a sample invoice. The marked row is the field this rule checks; on your own invoice it sits in the same place.

Sample invoice · not your document

Invoice

SAMPLE-INV-001 · issued 4 Jan 2026 · due 4 Feb 2026 · EUR

Seller

Seller nameSample Supplier B.V.

Seller streetHerengracht 100

Seller postcode1015 BS

Seller cityAmsterdam

Seller countryNL

Seller VAT numberNL123456789B01

Seller registration number12345678

Seller electronic addressNL123456789B01

Buyer

Buyer nameSample Buyer NV

Buyer streetRue de la Loi 42

Buyer postcode1000

Buyer cityBrussels

Buyer countryBE

Buyer VAT numberBE0123456789

Buyer electronic addressBE0123456789

Invoice details

Invoice numberSAMPLE-INV-001

Issue date4 Jan 2026

Due date4 Feb 2026

Invoice type380

CurrencyEUR

Buyer referencePO-12345

Payment

Payment method30

Payment IBANNL91ABNA0417164300

Line items

No.	Item	Quantity	Unit price	VAT rate (%)	Line amount
1	Consulting Services BR-25	1	€100.00	21%	€100.00

Totals

Sum of line amounts€100.00

Total without VAT€100.00

Total VAT€21.00

Total with VAT€121.00

Amount due€121.00

VAT breakdown

VAT category	VAT rate (%)	Taxable amount	VAT amount
S	21%	€100.00	€21.00

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

See this rule against your own invoice: every finding is pinned to the row it concerns.

Check your invoice Run this check in CI

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

Input required

Confidence

80%

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

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 of the invoiced item or service.

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.

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.

Validate your invoice

Drop your XML here to check for BR-25

Upload XML

Fix BR-25 with guided input

Upload your invoice and we'll ask for the missing data, then apply a safe, auditable fix.

Fix it now Automate via API