What triggers a BR-63 error?

The buyer's EndpointID element (BT-49) is missing its schemeID attribute or the attribute value is empty.

Which EAS code do I use for the buyer?

Use the code that matches the buyer's registered identifier type: 0088 GLN, 0106 Dutch KvK, 0184 Danish CVR, 0192 Norwegian ORG, 0208 Belgian CBE, 9930 German VAT, and so on.

Is BR-63 auto-fixable?

Yes when the buyer's country is known. Invoice Navigator applies the correct EAS code deterministically with 0.90 confidence. If country cannot be inferred, the fixer asks for it.

What is the difference between BR-62 and BR-63?

BR-62 checks the seller endpoint (BT-34). BR-63 checks the buyer endpoint (BT-49). Both must carry a schemeID; failures often occur together.

Why does my Dynamics 365 export fail BR-63?

The default Electronic Reporting configuration for Peppol Sales Invoice does not populate schemeID for buyer records unless the customer master has the Peppol EAS lookup enabled.

Error codes · EN 16931

BR-63In your invoicing software

Buyer electronic address must have a scheme identifier

This is the rejection, word for word: „[BR-63] Peppol BIS Billing 3.0 requires the Buyer electronic address (BT-49) — the cbc:EndpointID on cac:AccountingCustomerParty — to carry a schemeID attribute. Without it, the receiver Access Point cannot resolve the buyer participant and the invoice is rejected on ingress.“

Schematron assertion: cac:AccountingCustomerParty/cac:Party/cbc:EndpointID/@schemeID must be present and non-empty. Value must come from the Peppol Electronic Address Scheme (EAS) code list. A missing or blank schemeID triggers BR-63.

What to have readyBuyer Peppol EAS code

What we doAdd a valid EAS schemeID attribute to the Buyer cbc:EndpointID element. Invoice Navigator infers the code from the buyer's country and identifier type 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:AccountingCustomerParty>
  <cac:Party>
    <cbc:EndpointID>DE123456789</cbc:EndpointID>
  </cac:Party>
</cac:AccountingCustomerParty>

After

<cac:AccountingCustomerParty>
  <cac:Party>
    <cbc:EndpointID schemeID="9930">DE123456789</cbc:EndpointID>
  </cac:Party>
</cac:AccountingCustomerParty>

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

What the finding looks likeExample

FindingStructure invalid · BR-63

From youBuyer Peppol EAS code

ThenRe-export

ProofSHA-256 and /verify link after the check

Often appears together with

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