Every fact in an XBRL report stands inside a context, the way a statement at a deposition stands inside an oath, a date, and the name of the speaker. Without context, a number is just decoration. With context, the same number becomes "this entity, this period, this segment", which is the unit a downstream system can compare to anything else.
A context carries two non-negotiable parts and one optional one. The non-negotiable parts are entity and period. Entity lives in `xbrli:identifier`, which has a `scheme` URI and a value: the scheme says which authority issues the identifier (LEI, CIK, KvK), and the value is the identifier itself. Period lives in `xbrli:period`, and takes one of three shapes: `xbrli:instant` for a point in time, a pair of `xbrli:startDate` and `xbrli:endDate` for a duration, or `xbrli:forever` for facts that have no temporal bound (and which Dutch SBR forbids outright via FR-NL-3.04).
Concept type drives period type. Balance-sheet concepts are instant by declaration: assets, liabilities, equity, cash. Income statement, OCI, cash flow, and changes-in-equity flows are duration. The schema is the source of truth via the `periodType` attribute, and an instance that disagrees with the concept's declaration triggers either a schema error or a downstream `xbrldie:PrimaryItemDimensionallyInvalidError`.
The optional part is dimensional. `xbrli:context` may carry an `xbrli:segment`, an `xbrli:scenario`, or both, and inside those go the `xbrldi:explicitMember` and `xbrldi:typedMember` elements that supply dimensional values. ESEF Reporting Manual §2.1.3 forbids `xbrli:segment` and permits `xbrli:scenario` only. EDGAR and SBR have their own placement rules. Mixing the two within one instance is structurally wrong even when each looks defensible in isolation.
Identifier scheme constancy is the audit pattern that catches the most subtle mistakes. Every `xbrli:identifier` in one instance must use the same `scheme` URI. ESEF binds it to the LEI scheme `http://standards.iso.org/iso/17442`. SEC binds it to the CIK scheme `http://www.sec.gov/CIK`. SBR binds it to a KvK URN. Mix two schemes in one instance and consumers index facts by (scheme, value), so the same legal entity becomes two distinct entity keys, duplicate detection breaks silently, and the only signal is a quiet drop in fact count weeks later.
Every context carries an entity (xbrli:identifier with a scheme URI and a value) and a period (instant, duration via startDate/endDate, or forever).
Balance-sheet concepts are instant by declaration. Income-statement, OCI, cash-flow, and changes-in-equity flows are duration. The concept's periodType in the schema is the source of truth.
ESEF forbids xbrli:segment; it permits xbrli:scenario for dimension members. SEC and SBR have their own placement rules. Mixing segment and scenario in the same instance is a structural error.
Identifier scheme constancy matters: every xbrli:identifier in one instance must use the same scheme URI. Mixing schemes silently breaks duplicate-fact detection because consumers treat differently-schemed entities as different.
ESEF uses the LEI scheme http://standards.iso.org/iso/17442. SEC uses the CIK scheme http://www.sec.gov/CIK. SBR uses the KvK scheme. Pick one per regime and never mix.
<xbrli:context id="c-Group-2025">
<xbrli:entity>
<xbrli:identifier scheme="http://standards.iso.org/iso/17442">
529900T8BM49AURSDO55
</xbrli:identifier>
</xbrli:entity>
<xbrli:period>
<xbrli:startDate>2025-01-01</xbrli:startDate>
<xbrli:endDate>2025-12-31</xbrli:endDate>
</xbrli:period>
</xbrli:context>4 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.