BR-CL-07 — E-Invoice Validation Rule & Fix

Fixture ID: badObjectScheme · XPath: /ubl:Invoice/cac:AdditionalDocumentReference/cbc:ID/@schemeID

1. Why This Rule Triggers (Diagnostic Message)

The scheme identifier on the invoiced object identifier (BT-18-1) is "NOPE", which is not in the UNTDID 1153 restriction EN 16931 applies — 818 codes, so a plausible-looking abbreviation is very unlikely to be one of them by accident. The object identifier says what the invoice is *about* when that is not a purchase order: a contract, a meter, a vehicle, a case file. Without a scheme the receiver has a string; with the wrong scheme it has a string it will confidently misinterpret.

2. How to Fix BR-CL-07

Set invoicedObjectIdentifier.schemeId to a UNTDID 1153 reference qualifier: "CT" contract number, "ON" order number, "AAJ" delivery order number, "VN" vendor order number, "MG" meter number, "IV" invoice number. Omit the scheme entirely rather than inventing one — the identifier is then emitted without @schemeID, which this rule does not bind.

3. Valid Code / Payload Example

"invoicedObjectIdentifier": { "schemeId": "MG", "value": "1234567890" }