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.

Is BR-62 a critical error?

Yes, BR-62 is a critical error that will cause invoice rejection. It must be fixed before submission.

Can BR-62 be automatically fixed?

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.

errorEN 16931

`BR-62`:The Seller electronic address (BT-34) shall have a Scheme identifier.

The Seller Electronic Address (BT-34) is missing its Scheme Identifier. What type of address is this (PEPPOL ID, GLN, email)?

Severity

Fatal

Rule set

EN 16931

Country

All EU

Fix type

AUTO-FIX

Confidence

80%

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

Get API Access Test This Error ↓

Why This Error Matters

Invoice rejected. The scheme tells receivers how to interpret and route the electronic address.

BR-62 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.

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

Before / After

Failing XML

<cac:Contact>
  <!-- cbc:ElectronicMail is missing -->
</cac:Contact>

Corrected XML

<cac:Contact>
  <cbc:ElectronicMail>valid-value</cbc:ElectronicMail>
</cac:Contact>

Technical Reference

XPath//cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

SpecEN 16931

Operationset_default

StrategyEnsure seller electronic address (endpoint) is present per EN16931 BR-62

Common 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 →

Handle BR-62 Automatically in Your Pipeline

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

Get API Access View API Documentation

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