Line4 logoLine4

Search line4.ai

XBRL contexts: who reported and for what date

Every fact in an XBRL filing points to a context, which says three things: who the fact is about (an identifier and its scheme, usually an LEI), the date or period it refers to, and any dimension members such as a line of business. Regulators fix all three. Under the EBA’s filing rules every context in a report has the same identifier and the same reference date, as an instant, and dimensions go only in the scenario, never the segment. Outside Europe, the SEC uses the company’s CIK as the entity identifier and puts dimensions in the segment, the reverse of the EBA.

Check the contexts in a filing, free in your browser →

EBA, EIOPA and Bank of England filing rules. Nothing is uploaded.

Guide · 7 min read · Updated 21 November 2026 · By Jess Luper

What a context holds

In XBRL 2.1 the context “contains information about the Entity being described, the reporting Period and the reporting scenario, all of which are necessary for understanding a business fact”. Facts do not repeat this information. Each fact carries a contextRef that points to a context defined once in the report.

01EntityAn identifier and a scheme: a URI naming the system the identifier comes from. XBRL International is not a naming authority, so the regulator decides which scheme is valid.
02PeriodAn instant, a start and end date, or forever.
03ScenarioOptional. In supervisory filings it holds the dimension members that say which cell of a template the fact fills.
101,601contexts in 75 public EIOPA and Bank of England sample filings: every one an instant, every one with the LEI scheme, none with a segmentLine4 count of the XML samples served by Line4 Check, November 2026
61 of 75of those samples hold at least one duplicated context (2,434 in all), which the EBA says a report should not containLine4 count of the same samples; EBA XBRL Filing Rules v5.9, rule 2.7 →
53 of 55EBA public xBRL-CSV sample packages identify the firm as LEI + .CON; the 2 MiCA samples use LEI-token + .INDLine4 read of the parameters.csv in each EBA sample package

An example: one context from a Solvency II sample

This context is from EIOPA’s public quarterly solo sample (taxonomy 2.10.0), as served by Line4 Check. Three of the sample’s amounts point to it. The identifier is a dummy LEI.

What the context says
Who
Scheme http://standards.iso.org/iso/17442 (the LEI), identifier ABCDEFGHIJ0123456789
When
An instant: 31 December 2026, a whole day with no time or time zone
Which cell
Two explicit members, on the dimensions EIOPA codes BL and VG
Not there
No segment: dimensions are only in the scenario
Facts that point to it

<s2md_met:mi263 contextRef="c-15" decimals="-3" unitRef="u-1">7190.932</s2md_met:mi263> <s2md_met:mi276 contextRef="c-15" decimals="-3" unitRef="u-1">5460.941</s2md_met:mi276>

The context, defined onceShow<xbrli:context id="c-15"> <xbrli:entity> <xbrli:identifier scheme="http://standards.iso.org/iso/17442" >ABCDEFGHIJ0123456789</xbrli:identifier> </xbrli:entity> <xbrli:period> <xbrli:instant>2026-12-31</xbrli:instant> </xbrli:period> <xbrli:scenario> <xbrldi:explicitMember dimension="s2c_dim:BL">s2c_LB:x119</xbrldi:explicitMember> <xbrldi:explicitMember dimension="s2c_dim:VG">s2c_AM:x80</xbrldi:explicitMember> </xbrli:scenario> </xbrli:context>

Copied from eiopa-sample-qrs-2-10-0.xbrl. The figures are dummy values.

Who the report is about: the entity identifier

The LEI is “a unique 20-character alphanumeric code” defined by ISO 17442 (GLEIF). In XBRL its scheme URI is http://standards.iso.org/iso/17442. The EBA notes that earlier editions of its rules misspelt it as standard.iso.org, without the final s, and asks filers to switch to the correct form (rule 3.6, incorrectLeiScheme).

For reference dates from 31 December 2022, and modules without _con or _ind in their name, the EBA adds a qualifier after the LEI and uses the scheme https://eurofiling.info/eu/rs. The reporting subject is written in upper case (rule 3.6).

01LEI.CONThe highest level of consolidation.
02LEI.INDThe individual entity.
03LEI.CRDLIQSUBGRPA liquidity subgroup, using the LEI of the subgroup parent.
04IssuerID-TokenID.INDA MiCA report, for example LEIIDENTIFIERABCDEFG-TOKENABC.IND.
05AggregatesCountry code + 000 + .MEMSTAAGGALL for member state aggregates, or an authority code + .AUTALL (IT-BI.AUTALL for MREL decisions).
The context is the who and the when behind every number. Get it wrong and every fact in the filing is about the wrong firm or the wrong date.

When: one reference date, as an instant

XBRL lets each fact have its own period, and lets a period be forever. The EBA chose to tie the XBRL period to the report’s reference date instead. Other dates, such as an event date or an applicable period, are carried by dimensions (rule 2.13).

01One dateAll periods in a report MUST refer to the same reference date instant (multiplePeriodsUsed).
02Instants onlyAll periods MUST be instants (nonInstantPeriodUsed), and forever MUST NOT be used (rule 2.11).
03Whole daysDates are xs:date, with no time and no time zone (rule 2.10).

The other EBA context rules

The EBA filing rules v5.9 group these under “Context related rules” (2.6 to 2.15). Some are MUST and reject a filing; others are SHOULD.

01One subjectAll identifiers and schemes in a report MUST be identical (rule 2.9, multipleIdentifiers). A group is reported as one subject.
02Prescribed schemeThe scheme MUST be one the supervisor prescribes, and the identifier one it accepts (rule 2.8).
03No segmentxbrli:segment MUST NOT be used (rule 2.14). The scenario may hold only explicit and typed members (rule 2.15).
04No clutterUnused and duplicated contexts SHOULD NOT be present (rule 2.7), and context ids SHOULD be short and carry no meaning (rule 2.6).

Contexts in xBRL-CSV

An xBRL-CSV report has no context elements. The entity and the reference date are set once for the whole report in parameters.csv, and the dimensions come from the columns and the taxonomy’s metadata. The EBA applies the same scheme and identifier rules there (rule 2.8) and the same whole-day date rule (rule 2.10).

Line4 read the parameters in the 55 EBA public sample packages it holds. Each names the firm in an entityID parameter: 53 as rs:DUMMYLEI123456789012.CON, and the 2 MiCA samples as rs:DUMMYLEI123456789012-TOKENABC.IND. Each sets one refPeriod, such as 2024-12-31.

What the public samples show

Line4 counted every context 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. Between them they hold 101,601 contexts and 180,205 references to them.

01Who and whenEvery file has one identifier, always under the LEI scheme, and one reference date. Every context is an instant.
02DimensionsNo context uses a segment. Almost every context carries a scenario. Each file has between 1 and 12 without one, for the filing indicators and the facts that need no dimensions.
03Duplicates61 files hold at least one context identical to another, 2,434 in all. The 2.10.0 EIOPA samples hold none; the older 2.8.2 ones hold 1,745.
04Unused568 contexts in 7 files are never referred to, 286 of them in one EIOPA 2.8.2 sample.

What it means for supervisors

Publish the scheme and identifier format you accept, including the qualifier for consolidated and individual reports, and say which spelling of the LEI scheme you will take. Check the identifier against the firm the filing was sent for: a valid LEI for the wrong entity is the error that matters.

Check that the reference date matches the period you asked for before running any other rule. A return for the wrong date can pass every validation rule and still be useless.

Where AI fits, and where people decide

AI can explain a context failure in the filer’s terms: a missing .CON, an LEI under the old misspelt scheme, or a return dated the last day of the wrong quarter. It can also suggest which firm an unfamiliar identifier belongs to.

Whether the identifier, scheme and date are acceptable is set by the regulator’s rules and checked the same way every time, with the result kept with the filing.

Put it to workBefore your next filing season
  1. 1Have you published the identifier scheme and format you accept?
  2. 2Do you check the identifier matches the firm the filing came from?
  3. 3Is the reference date checked before any other rule runs?
  4. 4Do you reject periods that are not instants, or forever?
  5. 5Will your checker flag duplicated and unused contexts as warnings?

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 is a context in XBRL?

The part of an XBRL report that says who a fact is about, the date or period it refers to, and any dimension members. Each fact points to a context with its contextRef attribute, so this information is written once and shared by many facts.

What is the LEI scheme URI in XBRL?

http://standards.iso.org/iso/17442, with standards in the plural. The EBA notes that older editions of its filing rules wrote standard.iso.org by mistake and asks filers to use the correct form.

What do .CON and .IND mean in an EBA entity identifier?

The level the report is for. LEI.CON is the highest level of consolidation and LEI.IND is the individual entity. From reference date 31 December 2022, for modules without _con or _ind in their name, they are used with the scheme https://eurofiling.info/eu/rs (EBA Filing Rules v5.9, rule 3.6).

Can an XBRL report have more than one entity identifier?

XBRL allows it, but supervisors generally do not. Under EBA rule 2.9 all identifiers and schemes in a report must be identical; a group is reported as one subject.

Why are all periods instants in EBA and EIOPA filings?

Because the EBA ties the XBRL period to the report’s reference date (rule 2.13). Other dates, such as the start of a reporting period, are carried by dimensions. All 101,601 contexts in the 75 EIOPA and Bank of England samples Line4 checked are instants.

What is the difference between segment and scenario in an XBRL context?

Both can hold dimension members: segment sits inside the entity and scenario sits beside it. The EBA forbids segment (rule 2.14) and allows only explicit and typed members in the scenario (rule 2.15).

Is a duplicated context an error?

In EBA reporting it is a SHOULD NOT, not a rejection: a report should not contain duplicated or unused contexts (rule 2.7). Line4 found duplicates in 61 of 75 public sample filings.

How do contexts work outside Europe, for example at the SEC?

The building blocks are the same, the rules differ. At the SEC the entity identifier is the company’s CIK, with the scheme http://www.sec.gov/CIK, and every context must carry the registrant’s own CIK. Dimensions go in segment, because the SEC bans scenario: the reverse of the EBA, which bans segment and puts dimensions in scenario. A US listed company reports eliminations between subsidiaries in a context with the ConsolidationItemsAxis set to ConsolidationEliminationsMember. Line4 checks contexts against each regulator’s own rules, wherever the filing comes from.

Share this guideShare on LinkedIn
Was this useful?

For supervisors

New guides and Insights, by email

One short email when we publish something worth your time, from Jess Luper. No spam, unsubscribe any time.