Identifier scheme constancy sounds like a paperwork rule. It is actually one of the highest-leverage audit checks you can run, because it catches a class of error that produces silent failures rather than loud ones, and silence is exactly what you do not want when a million-row dashboard is downstream.
The rule itself is simple. Every `xbrli:identifier` in a single instance must use the same `scheme` URI. ESEF binds the scheme to the LEI URI `http://standards.iso.org/iso/17442`. The SEC binds it to the CIK URI `http://www.sec.gov/CIK`. Dutch SBR binds it to a KvK URN. There is no parent-versus-subsidiary exception. There is no carve-out for foreign segments. One regime, one scheme, one filing.
The reason the rule matters is that consumers index facts by the pair (scheme, value), not by value alone. Two facts with identical entity values but different schemes look like two different entities. A consolidated total tagged once under LEI and once under an internal URN does not deduplicate cleanly; instead it leaks two competing entity keys into every downstream join. Nothing throws. Things just slowly drift.
The patterns that produce mixed schemes are unglamorous. Copy-paste from the prior year when the regime changed. A subsidiary's local identifier scheme that escaped templating. An author who decided that the LEI and a custom internal URN should both appear "for completeness". Each of these is a real defect even when no validator screams.
When a filing legitimately spans multiple entities (a group with operating segments, a parent with subsidiaries that are themselves reportable), the right machinery is dimensions. The entity identifier on the context stays the parent's; the segment information rides as explicit-member dimensions in `xbrli:segment` or `xbrli:scenario` per the regime's rules. The structure expresses "this is the parent reporting about its subsidiary" without smuggling a second identifier scheme into the file.
The audit technique itself takes about ten seconds. Extract every `xbrli:identifier` element, list the distinct `scheme` attribute values, confirm there is exactly one and that it matches the regulator's expected URI for the regime. Anything else is a scheme-constancy violation, and the fix happens in the authoring tool, not the validator's exception list.
A regulator picks one identifier scheme for a regime. Every fact in your filing must use that scheme. No exceptions for parent-subsidiary tags.
ESEF binds the scheme to the LEI URI. SEC binds it to CIK. Dutch SBR binds it to a KvK URN.
When a filing has facts from multiple entities (group plus segment), the dimensions carry the segment information; the entity identifier is still the parent's.
If you see two distinct schemes in one instance, you have either an authoring error or a paste-from-prior-year accident. Both fail the same way.
The audit pattern is to grep all xbrli:identifier@scheme values in the report and confirm they are identical and match the regulator's expected URI.
3 questions. Druk op 1 tot 4 om te kiezen, Enter om te bevestigen.
Door deze quiz af te ronden, markeer je deze sectie als voltooid.
Tip: kies met 1 tot en met 4 en bevestig met Enter.