BR-62:Seller electronic address must have a scheme identifier
Fix: Add a valid EAS schemeID attribute to the Seller cbc:EndpointID element. Invoice Navigator infers the correct scheme from the seller's country and VAT/registration ID and inserts it automatically. Upload your invoice to fix this automatically.
Peppol BIS Billing 3.0 requires that the Seller electronic address (BT-34) — the cbc:EndpointID on cac:AccountingSupplierParty — carries a schemeID attribute. Without it, the address cannot be resolved on the Peppol network and the invoice is rejected before it reaches the buyer.
Engine Classification
deterministic_lookup
Confidence: 92% · 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, BR-62 fires. The schemeID must be a value from the Peppol Electronic Address Scheme (EAS) code list (e.g. 0088 GLN, 0106 Dutch KvK, 0184 Danish CVR, 0192 Norwegian ORG, 0208 Belgian CBE, 9930 German VAT). element under @schemeID. If the attribute is missing or empty on cac: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: The Schematron assertion checks: cbc:EndpointID/@schemeID. If the attribute is missing or empty on cac:AccountingSupplierParty/cac:Party/cbc:EndpointID, BR-62 fires. The schemeID must be a value from the Peppol Electronic Address Scheme (EAS) code list (e.g. 0088 GLN, 0106 Dutch KvK, 0184 Danish CVR, 0192 Norwegian ORG, 0208 Belgian CBE, 9930 German VAT).
Why This Error Matters
Every Peppol Access Point rejects invoices that fail BR-62. Without a schemeID the Peppol SMP lookup cannot resolve the seller's participant identifier, so the invoice cannot be routed. For ERP vendors this is one of the most common validation failures when first onboarding to Peppol.
BR-62 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Invoice cannot be routed on the Peppol network. Access Point rejects at ingress. No delivery to buyer, no chance of payment until re-issued.
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
Before / After
<cac:AccountingSupplierParty>
<cac:Party>
<cbc:EndpointID>12345678</cbc:EndpointID>
</cac:Party>
</cac:AccountingSupplierParty><cac:AccountingSupplierParty>
<cac:Party>
<cbc:EndpointID schemeID="0106">12345678</cbc:EndpointID>
</cac:Party>
</cac:AccountingSupplierParty>Technical Reference
The Schematron assertion checks: cbc:EndpointID/@schemeID. If the attribute is missing or empty on cac:AccountingSupplierParty/cac:Party/cbc:EndpointID, BR-62 fires. The schemeID must be a value from the Peppol Electronic Address Scheme (EAS) code list (e.g. 0088 GLN, 0106 Dutch KvK, 0184 Danish CVR, 0192 Norwegian ORG, 0208 Belgian CBE, 9930 German VAT).Code Example
<cbc:EndpointID schemeID="0106">12345678</cbc:EndpointID>Common Causes
- ·ERP exports EndpointID as plain text without the schemeID attribute
- ·Legacy UBL 2.0 templates that predate the Peppol EAS requirement
- ·Custom XML builders that only set element text, not attributes
- ·Copy of German EndpointID (VAT) without the required 9930 schemeID
- ·Manual XML edits that stripped the attribute
Seeing this in production? The API handles BR-62 automatically. See the fix response →
ERP-Specific Causes
Commonly Seen In
Frequently Asked Questions
The Seller electronic address (BT-34) must carry a schemeID attribute identifying which Peppol Electronic Address Scheme the endpoint belongs to. The invoice fails if the attribute is missing or empty.
Pick the EAS code that matches the seller's identifier: 0088 for GLN, 0106 for Dutch KvK, 0184 for Danish CVR, 0192 for Norwegian ORG, 0208 for Belgian CBE, 9930 for German VAT, and so on. The full list is maintained by OpenPeppol as the EAS code list.
Yes. When the seller country and identifier type are known, the correct EAS code is deterministic. Invoice Navigator applies the schemeID automatically with a confidence of 0.92.
BR-62 applies to the seller (BT-34), BR-63 to the buyer (BT-49). Same requirement, different party. Invoices often fail both together.
SAP's classic UBL output map treats EndpointID as a plain element and does not populate attributes unless the Peppol-specific mapping is configured in the electronic document framework.
Related Errors
Related Content
Last updated: 5 August 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.