One of the smaller but more punishing edges of iXBRL is the gap between what the reader sees on the page and what the consumer parses. A Spanish report writes 1.234,56 to mean one thousand two hundred thirty-four point five six. A US filing writes 1,234.56 for the same number. Both are correct in their locale; both render perfectly in any browser. But the consumer needs a single canonical form, and that is what the format attribute on an inline fact is for.
format names a transformation from the XBRL Transformation Registry. TRR 4 is the current Recommendation, dated 2022-02-16, with namespace http://www.xbrl.org/inlineXBRL/transformation/2022-02-16. Every transformation maps a rendered text pattern to a canonical XBRL lexical value. Pick the right one and the consumer reads the same number you intend the reader to read. Pick the wrong one and the rendered text looks correct while the canonical value is silently nonsense.
The numeric transformations cover the locale spread. ixt:numdotdecimal parses 1,234.56 (dot decimal, comma grouping). ixt:numcommadecimal parses 1.234,56 (comma decimal, dot grouping). ixt:numunitdecimal handles values like "12.3 millones" by stripping unit text. ixt:zerodash maps a single dash character to the integer zero, which matters because financial statements love using a dash for "no movement"; ESEF Reporting Manual section 2.2.5 endorses ixt:fixed-zero for the same purpose. ixt:nocontent emits an empty value when the visible text is decorative and not part of the fact.
Date transformations come in dozens of variants because dates are even messier than numbers. ixt:datedaymonthyear handles 31/12/2025; ixt:datemonthdayyear handles 12/31/2025; ixt:dateyearmonthday handles 2025-12-31. There are English-localised versions like ixt:datedaymonthyearen, and combinations for partial dates such as ixt:datemonthyear and ixt:dateyearmonth. There is even ixt:dateerayearmonthdayjp for Japanese era-year notation.
Boolean transformations are the simplest: ixt:booleantrue and ixt:booleanfalse, plus locale-named variants in TRR 4. The cost of getting this layer wrong is the cost of any silent corruption in regulated reporting: nobody notices for a long time, and then everybody does.
The format attribute names a transformation from the Transformation Registry. TRR 4 is current (Recommendation, namespace http://www.xbrl.org/inlineXBRL/transformation/2022-02-16).
Numeric transformations include ixt:numdotdecimal (1,234.56 with dot decimal), ixt:numcommadecimal (1.234,56 with comma decimal), ixt:numunitdecimal, ixt:zerodash (treats a dash as zero), ixt:nocontent.
Date transformations include ixt:datedaymonthyear, ixt:datemonthdayyear, ixt:dateyearmonthday, ixt:datedaymonthyearen, ixt:datemonthyear, ixt:dateyearmonth, ixt:dateerayearmonthdayjp.
Boolean transformations include ixt:booleantrue, ixt:booleanfalse. Language-specific names are listed in TRR 4.
Pick the wrong transformation and the canonical XBRL value is wrong; a Spanish '1.234,56' parsed with ixt:numdotdecimal becomes the integer 1, not the intended decimal.
<!-- A Dutch report writes "1.234,56" for 1234.56 -->
<ix:nonFraction name="ifrs-full:Revenue"
contextRef="c-2025"
unitRef="u-eur"
decimals="2"
format="ixt:numcommadecimal">1.234,56</ix:nonFraction>3 questions. Press 1 to 4 to select, Enter to confirm.
Completing this quiz marks the section done in your progress.
Tip: press 1 to 4 to select, Enter to confirm.