What does BR-62 mean?

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.

Which schemeID should I use?

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.

Can BR-62 be auto-fixed?

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.

Is BR-62 the same as BR-63?

BR-62 applies to the seller (BT-34), BR-63 to the buyer (BT-49). Same requirement, different party. Invoices often fail both together.

Why does SAP produce invoices without the schemeID?

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.

Error codes · EN 16931

BR-62In your invoicing software

Seller electronic address must have a scheme identifier

This is the rejection, word for word: „[BR-62] 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.“

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).

What to have readySeller Peppol EAS code

What we doAdd 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.

Choose the rejected invoiceor drop it here

XRechnung XML or ZUGFeRD PDF. Checking is free · corrected file €1.90 · the first every 30 days is free · no sign-up.

If you enter it yourself in your invoicing software

Before

<cac:AccountingSupplierParty>
  <cac:Party>
    <cbc:EndpointID>12345678</cbc:EndpointID>
  </cac:Party>
</cac:AccountingSupplierParty>

After

<cac:AccountingSupplierParty>
  <cac:Party>
    <cbc:EndpointID schemeID="0106">12345678</cbc:EndpointID>
  </cac:Party>
</cac:AccountingSupplierParty>

Element order is part of the rule: if the element sits in the wrong place, the validator rejects with BR-62.

What the finding looks likeExample

FindingStructure invalid · BR-62

From youSeller Peppol EAS code

ThenRe-export

ProofSHA-256 and /verify link after the check

Often appears together with

BR-63Buyer electronic address must have a scheme identifier PEPPOL-EN16931-R010Buyer electronic address (EndpointID) MUST be provided PEPPOL-EN16931-R020Seller electronic address missing