SchemaGuard by Ironbark Digital · EN 16931 / Peppol / XRechnung Reference
← All 294 EN 16931 / Peppol Rules & Live Validator
FATAL Official EN 16931 / Peppol / CIUS Rule BT/BG Fields: BT-34

BR-62 — E-Invoice Validation Rule & Fix

Fixture ID: blankEndpointScheme · XPath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID/@schemeID

1. Why This Rule Triggers (Diagnostic Message)

The seller electronic address (BT-34) must have a scheme identifier. The bare value "x" is ambiguous — the same string can be a VAT number under one scheme and a GLN under another, and the receiving access point resolves it by scheme.

2. How to Fix BR-62

Set electronicAddress.schemeId to the Peppol EAS code, e.g. "9930" for a German VAT identifier, "0204" for a Leitweg-ID, "0088" for a GLN.

3. Valid Code / Payload Example

"electronicAddress": { "schemeId": "9930", "value": "x" }
Test & Validate XML / JSON in Live SchemaGuard Validator →