errorpeppol-bis-3

BR-01:Invoice must have specification identifier

Every Peppol BIS invoice must include a specification identifier (CustomizationID) that indicates which profile the invoice conforms to.

Why This Error Matters

Invoice rejected immediately. Receiver cannot identify the standard being used.

How to Fix It

1

Identify the correct profile

For Peppol BIS Billing 3.0, use urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0

2

Add to invoice

Insert the CustomizationID element as a child of the Invoice element

3

Validate

Re-run validation to confirm the error is resolved

Before & After Fix(BR-01)

Before (Invalid)
<cbc:CustomizationID></cbc:CustomizationID>
After (Valid)
<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>

Compare the invalid XML structure with the corrected version. The fix ensures compliance with validation rules.

Code Example

<cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>

Technical Details

XPath: /Invoice/cbc:CustomizationID

Common Causes

  • Invoice exported without standard EN16931 header section
  • ERP template missing CustomizationID specification field
  • Manual XML creation without required boilerplate elements
  • Export configuration not set for PEPPOL/EN16931 format
  • Conversion from legacy format omitted specification identifier

Common Causes by Software

SAP

Why this happens

Document number range not configured for billing type

How to fix it

Configure number range in SPRO → Sales → Billing → Define Number Range

Where to find it

Transaction SNRO → Object VBELN

DATEV

Why this happens

Belegkreis (document range) not assigned

How to fix it

Configure Belegkreis in Stammdaten → Belegkreise

Where to find it

Stammdaten → Belegarten → Belegkreise

Microsoft Dynamics 365

Why this happens

Number sequence missing for sales invoice journal

How to fix it

Set up number sequence: Organization administration → Number sequences → Generate

Where to find it

General ledger → Setup → Journals → Invoice journal

Using a different software?

Validate your invoice to get specific fix guidance.

Validate Your Invoice

Commonly Seen In

SAP →OracleMicrosoft DynamicsCustom ERP

Frequently Asked Questions

Every Peppol BIS invoice must include a specification identifier (CustomizationID) that indicates which profile the invoice conforms to.
Add the correct CustomizationID element to your invoice header. You can also use Invoice Navigator's automatic Fixer tool to correct this instantly.
Yes, BR-01 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-01 can be automatically corrected using Invoice Navigator's Fixer tool. Upload your invoice and the tool will identify and fix common issues, including invoice must have specification identifier.
BR-01 is commonly seen in exports from SAP, Oracle, Microsoft Dynamics, Custom ERP. These software packages sometimes generate invoices that need adjustment to meet full compliance standards.

Related Errors

BR-02

Invoice must have an invoice number

BR-03

Invoice must have an issue date

Last updated: 16 January 2026

Share this guide: