BR-63: what it means and how to fix it

The buyer's electronic address must have a scheme identifier.

RuleBR-63
StandardEN 16931-1, the European standard for electronic invoices
SeverityError (the invoice is not conformant)
ConcernsBT-49: Buyer electronic address

How to fix it

Add the scheme, for example EM for an e-mail address.

Where the field is in the XML

TermCII (XRechnung-CII, ZUGFeRD, Factur-X)UBL (XRechnung-UBL, Peppol)
BT-49
Buyer electronic address
ram:BuyerTradeParty/ram:URIUniversalCommunication/ram:URIID[@schemeID]cac:AccountingCustomerParty/cac:Party/cbc:EndpointID[@schemeID]

Check your own file for this rule

Up to 5 MB. Read in memory for this one request and not stored.

From your code

curl -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/xml" \
  --data-binary @invoice.xml "https://agent-data-tools.revmesh2074.workers.dev/einvoice/validate"

The answer lists every broken rule with its number, the field, a message with the figures from your file and the fix. E-invoice API: validate, convert to JSON, and create XRechnung or ZUGFeRD XML from JSON.

Questions

What does BR-63 mean?

The buyer's electronic address must have a scheme identifier. It is a rule of EN 16931-1, the European standard for electronic invoices.

How do I fix BR-63?

Add the scheme, for example EM for an e-mail address.

Is BR-63 an error or a warning?

An error: a validator reports the invoice as not conformant, and a recipient that validates incoming e-invoices can reject it.

Rule numbers are those of EN 16931-1; the explanation is ours. Not tax or legal advice.