CII-SR-046:GlobalID present without schemeID attribute
Fix: Add a schemeID attribute from ISO 6523 (party identifiers) or UNTDID 7143 (item identifiers) to every ram:GlobalID that lacks one. Provide the required value in the free validator.
CII-SR-046 is a fatal EN 16931 Schematron assertion on the CII binding used by ZUGFeRD and Factur-X. If ram:GlobalID is present, it must carry a schemeID attribute. Formal test: not(ram:GlobalID) or (ram:GlobalID/@schemeID).
Engine Classification
Business data required · Explicit input workflow · No assumptions made
What is CII-SR-046?
CII-SR-046 is a fatal validation rule defined in the cii-d16b specification.
When this rule fires, the invoice is rejected by Peppol access points and never reaches the buyer.
Why This Error Matters
Without a scheme identifier, the numeric value of GlobalID is ambiguous — the same digits could be a GLN, GTIN, or internal code, and receivers cannot resolve which registry to consult.
CII-SR-046 is a hard failure — the invoice must be corrected and re-sent before it can reach the recipient.
Validator Behavior
- ·Causes invoice rejection
- ·Fails CII schema validation
- ·Error returned: CII-SR-046
- ·Specification: cii-d16b
Before / After
<ram:SpecifiedTradeProduct><ram:GlobalID>4012345678901</ram:GlobalID><ram:Name>Industrial Widget</ram:Name></ram:SpecifiedTradeProduct>
<ram:SpecifiedTradeProduct><ram:GlobalID schemeID="0160">4012345678901</ram:GlobalID><ram:Name>Industrial Widget</ram:Name></ram:SpecifiedTradeProduct>
Technical Reference
Seeing this in production? The API handles CII-SR-046 automatically. See the fix response →
Frequently Asked Questions
A ram:GlobalID element is missing its schemeID attribute. EN 16931 rejects GlobalID values that are not tied to a registered scheme.
For parties, ISO 6523 ICD codes (0088 GLN, 0060 DUNS, 0184 DK CVR, 0106 KVK). For items, UNTDID 7143 entries, most commonly 0160 for GTIN.
Only if the identifier is not business-critical. Many buyers rely on GlobalID for automated matching, so adding the correct schemeID is preferred.
Yes. Both formats use the same EN 16931 CII Schematron layer, and the rule also applies to Peppol BIS 3.0 CII profile validation.
SAP, Dynamics 365 Finance, Odoo, and DATEV — usually because the ERP stores the identifier without capturing its ICD scheme.
Related Content
Last updated: 20 April 2026
Validate your invoice
Drop your XML here to check for CII-SR-046
Fix CII-SR-046 with guided input
Upload your invoice and we'll ask for the missing data, then apply a safe, auditable fix.