Default members exist because filings would otherwise be drowning in trivial repetition. A primary item like Revenue does not carry a "geography" dimension when reported at the consolidated level, but the taxonomy still wants to position the consolidated number in a hypercube that has geography as one of its axes. Declare a default member for the geography dimension (typically a "Total" or "All Geographies" member) and the implicit assumption falls into place: when the dimension is absent from a context, the default is what the consumer should substitute.
The mechanics are minimal. A dimension-default arc in the definition linkbase names exactly one member as the default for one dimension. There is no flag on the member itself, no annotation on the fact: just one arc, one default. The rule is implicit by design.
Two errors come straight out of breaking that rule. xbrldie:DefaultValueUsedInInstanceError fires at the instance level when a context redundantly emits the default member. This happens constantly in machine-generated tagging because authors think "the default member is what we want, so let's emit it". XBRL Dimensions disagrees: the default is precisely what you do not emit, because emitting it changes nothing and now your context disagrees with the implicit-form context that another preparer used for the same fact, breaking duplicate-fact detection at OIM level.
xbrldte:TooManyDefaultMembersError fires at the DTS level, meaning the linkbase or schema is broken: somewhere, two dimension-default arcs point at different members of the same dimension. There can only be one default. Two are an authoring bug, usually introduced when an extension taxonomy redeclares a default that the base taxonomy already supplied.
A subtle defect surfaces when chasing duplicate-fact errors that look impossible. Two facts with the same concept and context, one with the default member emitted explicitly, one without. Per OIM they are the same fact and the consumer collapses them. The validator might not always notice, but the explicit one is still wrong on its own merits. Drop the explicit member. The reported value is unchanged. The validator goes quiet. The consumer sees one fact, as it should.
A dimension may declare exactly one default member via a dimension-default arc. The default is implicit when the explicit dimension is absent from the context.
Never emit the default member explicitly. Doing so triggers xbrldie:DefaultValueUsedInInstanceError.
If a taxonomy has more than one default member declared for the same dimension, you have a DTS-level error: xbrldte:TooManyDefaultMembersError.
Defaults make filings more compact (no need to repeat the trivial member) and let calc trees roll up across the default unambiguously.
When debugging duplicate-fact errors, check whether one of the alleged duplicates carries an explicit default member while the other does not. The OIM treats them as the same fact, but emitting the default is still an error.
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.