What decimals and units do
Each numeric fact points to a unit. Amounts use an ISO 4217 currency code, such as iso4217:EUR or iso4217:GBP. Ratios, percentages and counts use xbrli:pure, a unit with no dimension. Units must come from the XBRL International Unit Type Registry (EBA rule 2.23).
The decimals setting says how far the reported value can be from the true one. In the EBA’s words, a fact with decimals n is “correct to n decimal places”: the gap is at most 0.5 x 10 to the minus n (rule 2.18). So decimals 2 means within half a cent, -3 within 500, and INF means exact as written.
An example: one amount, reported right and wrong
The EBA filing rules show one amount, €2,560,561.43, and how it may be sent (rule 3.3). The value is always in euros, never in thousands of euros. The decimals setting says how accurate it is.
- 2560561.43, decimals INF
- Exact
- 2560561.43, decimals 2
- Within 0.005
- 2560561.43, decimals -3
- Within 500
- 2561000, decimals -3
- Within 500: allowed, but the EBA would rather you sent the value you know
<s2md_met:mi256 contextRef="c-15" unitRef="u-1" decimals="-3">2560561.43</s2md_met:mi256> <!-- €2,560,561.43, accurate to within 500 -->
Wrong: thousands in the valueShowHide
<s2md_met:mi256 contextRef="c-15"
unitRef="u-1" decimals="-3">2561</s2md_met:mi256>
<!-- u-1 is iso4217:EUR: this says €2,561, give or take 500 -->The value table is the EBA’s, from rule 3.3 of the Filing Rules v5.9. The fact markup follows the EIOPA ARB 2.10.0 public sample served by Line4 Check (unit u-1 is iso4217:EUR); the amount is the EBA’s example, not the sample’s.
What the EBA requires
The EBA sets a minimum decimals value for each data type in rule 2.18. Truncating to thousands is not allowed with decimals -3, because the reported value could then be up to 1,000 out, more than the 500 that -3 promises. Rounding to the nearest thousand is allowed.
Rule 2.18 also asks firms not to adjust numbers so that totals appear to add up. “The validation checks will take into account the declared accuracy”: the EBA’s rules use interval arithmetic, so a correctly rounded total passes.
Decimals and units in xBRL-CSV
In xBRL-CSV the same rules apply, but decimals and the currency are usually set once for the whole report in parameters.csv, and each column in the taxonomy’s metadata points to one of them. The EBA requires the decimals property on every numeric fact (rule 2.18, missingDecimalsProperty).
Line4 read the parameters in the 42 EBA public sample packages it holds. 40 set baseCurrency to iso4217:EUR and decimalsMonetary to -3. The 2 remuneration gap packages set no currency or monetary decimals at all, only integer and percentage decimals (0 and 4).
What the public samples show
Line4 counted every numeric fact in the 75 XML sample filings its free checker serves: 16 EIOPA Solvency II, 5 Bank of England insurance, 22 Bank of England banking and 32 Bank of England statistical returns.
What it means for supervisors
Publish the minimum decimals for each data type, and say whether a breach rejects the filing or only warns. Firms that truncate to thousands with decimals -3 send numbers that are wrong by the rule’s own definition, and a checker should tell them so in plain words.
When you write validation rules, compare values using their stated decimals, not exact equality. Otherwise correctly rounded returns fail and firms learn to adjust their numbers, which the EBA asks them not to do.
Where AI fits, and where people decide
AI can spot the pattern behind a failure: a return reported in thousands, a percentage sent as 9.31 instead of 0.0931, or one template in the wrong currency. It can then explain the fix in the firm’s own terms.
Whether a value is accurate enough is set by the regulator’s rules, and the check is arithmetic on the stated decimals, run the same way every time and kept with the filing.
- 1Have you published a minimum decimals value for each data type?
- 2Do your rules compare values within their stated decimals?
- 3Will your checker catch amounts reported in thousands?
- 4Are percentages checked to be ratios, not multiplied by 100?
- 5Do you say which data points use the currency of denomination?
Where Line4 fits
Line4 is SupTech software for financial regulators. It collects returns in XBRL, Excel and CSV by portal, API or MCP, validates them against your taxonomies and rules at the point of submission (see XBRL software for regulators), and puts AI to work reading them, with supervisors making every decision. If you work with a standard we have not yet run in production, we will say so plainly and show you how we would approach it.
Questions
What does decimals mean in XBRL?
How accurate a reported number is. A fact with decimals n is correct to n decimal places, so decimals 2 means within half a cent, decimals -3 within 500 and INF exact. It does not change the size of the number.
Is decimals -3 the same as reporting in thousands?
No. With decimals -3 the value is still sent in units, such as 2560561, and decimals says it is accurate to within 500. Sending 2561 for €2.56 million is wrong: it means €2,561.
What is the difference between decimals and precision?
Both describe accuracy in XBRL 2.1. Decimals counts places from the decimal point; precision counts significant figures. The EBA allows only decimals (rule 2.17), and none of the 161,474 numeric facts in the public samples Line4 checked uses precision.
What unit is used for percentages in XBRL?
xbrli:pure, the unit with no dimension. The value is a ratio: 12.34% is sent as 0.1234. The EBA requires at least 4 decimals for percentages.
What currency codes does XBRL use?
ISO 4217 codes in the iso4217 namespace, such as iso4217:EUR, iso4217:GBP and iso4217:USD. The unit must be the currency itself, with no scaling such as thousands.
Can a filing report the same amount in two currencies?
Not in EBA reporting. Rule 2.16.1 forbids facts that are duplicates apart from their unit, because it is unclear whether they are alternatives, equivalents or a set.
What is the minimum decimals for amounts in EBA reports?
At least -4 from 1 April 2025, and at least -6 for the funding plans, ESG, Pillar 3 and REM_DBM modules (EBA Filing Rules v5.9, rule 2.18). Integers use 0 and percentages at least 4.
What are the rules on decimals and units outside Europe, for example at the SEC?
Much the same as the EBA’s. The SEC’s EDGAR XBRL Guide (November 2026) says US dollar amounts must use one unit whose measure is iso4217:USD, and filers must not define units such as “thousands of USD”. It also says decimals is not a scale factor: an amount rounded to thousands has decimals -3, an exact one INF, and using precision instead is an error. Line4 runs these checks before a file is sent, by each regulator’s own rules.
