BR-62:The Seller electronic address (BT-34) shall have a Scheme identifier.
Fix: The Seller Electronic Address (BT-34) is missing its Scheme Identifier. What type of address is this (PEPPOL ID, GLN, email)? Upload your invoice to fix this automatically.
The Seller Electronic Address (BT-34) is missing its Scheme Identifier. What type of address is this (PEPPOL ID, GLN, email)?
Engine Classification
Ensure seller electronic address (endpoint) is present per EN16931 BR-62
Confidence: 80% · Applied automatically in pipeline
What is BR-62?
BR-62 is a fatal validation rule defined in the EN 16931 specification. It validates the EndpointID element under 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: //cac:AccountingSupplierParty/cac:Party/cbc:EndpointID
Why This Error Matters
Invoice rejected. The scheme tells receivers how to interpret and route the electronic address.
BR-62 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Invoice Navigator can automatically correct this error in your pipeline. The fix is applied with full audit evidence, so your compliance trail remains intact.
Validator Behavior
- ·Causes invoice rejection
- ·Error returned: BR-62
- ·Specification: EN 16931
How to Fix It
Find the missing or empty field
Check cbc:EndpointID at //cac:AccountingSupplierParty/cac:Party/cbc:EndpointID. This field is required but is either missing or empty.
Set the required value
The Seller Electronic Address (BT-34) is missing its Scheme Identifier. What type of address is this (PEPPOL ID, GLN, email)?
Re-validate your invoice
Upload the corrected invoice to confirm BR-62 is resolved.
Before / After
<cac:Contact> <!-- cbc:ElectronicMail is missing --> </cac:Contact>
<cac:Contact> <cbc:ElectronicMail>valid-value</cbc:ElectronicMail> </cac:Contact>
Technical Reference
//cac:AccountingSupplierParty/cac:Party/cbc:EndpointIDCommon Causes
- ·Seller electronic address without scheme identifier
- ·EndpointID missing schemeID attribute
- ·Electronic address value present but scheme not specified
- ·Template missing schemeID on seller endpoint
- ·Endpoint scheme stored separately from address value
Seeing this in production? The API handles BR-62 automatically. See the fix response →
Frequently Asked Questions
The Seller Electronic Address (BT-34) is missing its Scheme Identifier. What type of address is this (PEPPOL ID, GLN, email)?
The Seller Electronic Address (BT-34) is missing its Scheme Identifier. What type of address is this (PEPPOL ID, GLN, email)? You can also use Invoice Navigator's compliance engine to correct this automatically in your pipeline.
Yes, BR-62 is a critical error that will cause invoice rejection. It must be fixed before submission.
Many instances of BR-62 can be automatically corrected using Invoice Navigator's compliance engine. The fix is applied in your pipeline with full audit evidence.
Related Content
Last updated: 14 April 2026
Validate your invoice
Drop your XML here to check for BR-62
Auto-fix BR-62 in seconds
Upload your invoice and we fix this error automatically. Financial fields are never touched.