Currency, shares, ratios, per-share amounts, square metres, energy. The same number can mean wildly different things depending on the unit you attach to it. XBRL handles this with a simple but strict mechanism: every numeric fact points (via `unitRef`) at an `xbrli:unit` declared once and reused many times.
A unit is either a single measure or a divide expression. A single measure is a QName like `iso4217:EUR` (a euro), `iso4217:USD` (a dollar), `xbrli:pure` (a unitless ratio or multiplier), or `xbrli:shares` (a count of shares). A divide expression is the structural way to say "currency per share" or "kilowatt-hours per square metre", with an `xbrli:unitNumerator` and an `xbrli:unitDenominator` each carrying their own measures.
The currency rule is sharper than it looks. XBRL 2.1 §4.8.2 requires that any concept of type `monetaryItemType` use a measure in the iso4217 namespace, full stop. `my:euros` does not pass. Neither does a creative `local:revenue-eur`. A monetary fact that is not iso4217-measured is invalid even when the value is correct, and the validator will be right to reject it.
Pure numbers, ratios, and dimensionless multipliers use `xbrli:pure`. Share counts use `xbrli:shares`. Earnings per share, the canonical per-unit example, uses `xbrli:divide` with iso4217 over `xbrli:shares`. A few specialised taxonomies define custom units (energy, area, weight) and accept them only when both the taxonomy and the regulator have signed off; in most regimes, you stay within the standard set.
Two implementation reflexes save real time. First, the unit `id` is opaque. Calling it `u-eur` while declaring `iso4217:USD` inside is permitted by the schema and disastrous in practice; the fact reports USD regardless of the friendly name. Audit the `xbrli:measure` content, not the id. Second, mismatches between concept type and unit are a classic AI-authoring defect: a percentage tagged with iso4217:EUR, a per-share number tagged with `xbrli:pure`. The validator usually catches it; a careful reader catches it faster.
Monetary facts must use a unit whose single measure is in the iso4217 namespace, like iso4217:EUR or iso4217:USD. Anything else is a measure-namespace error.
Pure numbers (ratios, multipliers) use xbrli:pure. Share counts use xbrli:shares. Per-share amounts use xbrli:divide combining iso4217 and xbrli:shares.
Custom units are valid only when the taxonomy defines them and the regulator accepts them. Most regimes restrict you to the standard set.
A unit is declared once per id and reused by many facts. Inline reports keep units in ix:resources.
Mismatched unit and concept (a percentage tagged in EUR, a per-share number tagged in pure) is a typical AI-generation defect that passes superficial checks.
<xbrli:unit id="u-eur-per-share">
<xbrli:divide>
<xbrli:unitNumerator>
<xbrli:measure>iso4217:EUR</xbrli:measure>
</xbrli:unitNumerator>
<xbrli:unitDenominator>
<xbrli:measure>xbrli:shares</xbrli:measure>
</xbrli:unitDenominator>
</xbrli:divide>
</xbrli:unit>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.