Sign convention is the single most common substantive error in ESEF filings, and the reason is almost always conflation. Three different layers of the standard each carry their own notion of sign, and a preparer who treats them as one ends up flipping the canonical fact value to chase a pair of parentheses on the rendered page. Every downstream consumer then reads the filing inverted, silently, until somebody runs a calc check and the numbers do not add up.
The first layer is the canonical XBRL value. This is the signed number a consumer parses out of an ix:nonFraction. It follows the as-reported mathematical fact: positive when the value is positive, negative when negative. The sign attribute on the inline tag is purely a formatting helper for parentheses notation. It does not flip the meaning of the value, only the parsed sign of the rendered text.
The second layer is the concept's balance attribute, declared once on the concept itself as debit or credit. Balance drives arithmetic in the calculation linkbase. A credit-balance child rolling into a debit-balance parent uses weight=-1; a same-balance roll-up uses weight=+1. This is where the calc tree lives. Tag a credit-balance concept with the same sign as a debit-balance one and the calc tree breaks for everyone, even though the rendered page looks fine.
The third layer is the preferredLabel role on a presentation arc. This is purely a display instruction. The negatedLabel role from the Label Role Registry tells a renderer to flip the visible sign of a fact while leaving the canonical value entirely alone. Cost of Sales as a credit-balance concept gets tagged as a positive number, the calc tree expects positive, and the presentation arc carries preferredLabel set to negatedLabel so the printed page shows the value in parentheses. That is the recommended pattern across ESEF, US-GAAP, and IFRS reporting, and it is the only one that survives audit.
The rule of thumb that prevents the most damage: never invert a canonical sign to fix rendering. Fix rendering with preferredLabel. Fix arithmetic with calc weights and balance. Keep the three layers separate.
Three different things often confused: the canonical XBRL value's sign, the concept's balance attribute, and the preferredLabel role used for display. They live in different layers.
Canonical sign follows the as-reported mathematical fact. sign='-' on the inline tag negates the parsed value when parentheses formatting is used.
Balance is on the concept declaration. It governs what direction the value contributes in calc trees: weight=1 with balance debit, weight=-1 with credit, etc.
preferredLabel is on the presentation arc and only affects display: negatedLabel flips the visible sign without changing the canonical value.
The single most common ESEF substantive error is conflating these: tagging a credit-balance concept with the same sign as a debit-balance one to make rendering work, breaking the calc tree silently for everyone downstream.
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.