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

PEPPOL-COMMON-R050 — E-Invoice Validation Rule & Fix

Fixture ID: peppolBadAbn · XPath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

1. Why This Rule Triggers (Diagnostic Message)

The Seller electronic address (BT-34) is "51824753557" under scheme "0151", which identifies the Australian Business Number (ABN). A value in that scheme must be exactly eleven digits, weighted and summed to a multiple of 89, and this one is not. The ABN's modulus-89 construction subtracts one from the first digit before weighting, which is why an otherwise plausible eleven-digit number fails: the algorithm is deliberately not a plain checksum, so that a random number almost never validates. Peppol flags this fatal: the identifier is what an access point resolves to find your counterparty, so a value in the wrong form is undeliverable. This is a Peppol BIS Billing 3.0 profile rule: it applies because profile is "peppol-bis-3". It does not apply to the en16931, xrechnung-ubl or xrechnung-cii profiles, whose validators will accept the same document.

2. How to Fix PEPPOL-COMMON-R050

Correct seller.electronicAddress, or change its scheme identifier if the value belongs to a different register. A failing check digit or length almost always means a digit was transposed, dropped or added in transcription — compare it against the source register rather than re-typing it.

3. Valid Code / Payload Example

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