EIOPA 2.8.2 Hotfix to 2.10.0: what changes, who is affected, and why?

Start with the reporting period

A reporting team closing 2026 can also be preparing its first 2027 cycle. These are separate release decisions. EIOPA identifies 2.8.2 as applicable through Q4 and annual 2026, with 2.10.0 beginning at Q1 2027. The month in which someone uploads a file does not, by itself, determine the taxonomy. Check the entity, competent authority, entry point, reporting frequency and reference period together. See the full EIOPA Q&A 3504 answer and EIOPA release register.

For a synthetic calendar-year insurer, this means keeping the annual 2026 work tied to the appropriate 2.8.2 package while rehearsing Q1 2027 separately. A single folder named “2027 submissions” would hide that distinction. A better preparation sheet records both the reference period and the expected submission date.

Why the reporting model is changing

EIOPA's March 2026 final report connects the reporting changes to the Solvency II review and a reduction in reporting burden. The report contains proposed implementing technical standards submitted to the Commission. A final taxonomy package and an adopted legal requirement are different publication events. Before deciding that an exemption applies to your undertaking, check the adopted requirements and the competent authority's instructions. See the final report.

The practical opportunity is to stop preparing information that is no longer required for the relevant scope, while retaining enough explanation to show why. That calls for a reviewed applicability decision, rather than deleting a workbook because a template disappeared from a list.

Comparison matrix

This is a preparation map, not an exhaustive list of changed cells. The official release notes explain the main changes, while the change log provides the item-level comparison.

Read the change log without mistaking every row for a new requirement

The workbook separates dictionary, framework, table and business-rule changes. Several rows can describe properties of one object. Consequently, a row count is not a count of new reporting obligations, unique templates, or checks.

For example, Framework rows 4–9 identify added S.22.07 table variants. Table row 327 changes the annual solo content-list reference from S.22.06 to S.22.07. Business rule rows 5616–5633 update the related BV341 descriptions. Read those changes together before deciding what your reporting process must do.

Another useful example is S.37.02.04.02 C0050: Table row 1919 changes its natural-key description from optional to mandatory. Business rule BV792 descriptions also change how issuer-sector fields are referenced. These are reasons to inspect field meaning and conditions in the annotated templates. Simply reusing yesterday's source column is insufficient.

Those worksheet positions refer to the file checked on 17 September 2026. Search by identifier if EIOPA publishes an updated workbook; do not build your import around a fixed spreadsheet row number.

A ratio can move because its definition changed

Consider a simplified, synthetic S.37.02 group-reporting example. A specific exposure of EUR 20 million divided by EUR 1,000 million in total assets is 2%. Using EUR 200 million of total exposures reported for the template as the denominator gives 10%. The exposure is unchanged. This illustrates the denominator change described in section V of the 2.10.0 release notes; it is not a complete filing calculation or evidence that the underlying exposure increased. Confirm the denominator's source and applicable instructions before comparing periods.

Inspect the actual volatility-adjustment fields

The video follows the change-log reference into selected annual template variants. In the 2.8.2 Hotfix annotated workbook, S.22.06.01.01 cell D6 describes the C0040 field in terms of the reporting currency. In the 2.10.0 annotated workbook, S.22.07.01.01 cell C5 describes C0040 for euro. The adjacent headers D5:F5 cover asset credit-spread sensitivity, best-estimate interest-rate sensitivity and a portfolio risk-corrected spread.

These selected cells explain why an unchanged column code alone cannot establish compatibility. Check currency basis, source calculations, dimensions and applicability against the full definitions and instructions. The displayed extracts are reflowed for readability and contain no filing values. This annual-scope example does not establish that the same templates are required for Q1 reporting, and it is not a complete migration mapping.

NACE already needs attention before 2027

The 2.8.2 optional Hotfix addresses the availability of NACE 2.0 and 2.1 in source data. Its instructions distinguish lines for which 2.0 remains available from lines requiring the new classification. It retains existing schemas and entry points while adding the transitional fields. See the Hotfix release notes.

Ask your data provider which classification each field contains, when that changed, and whether the original classification remains available. Keep their answer with the mapping evidence. A renamed spreadsheet header is weak evidence of a classification conversion.

A practical rehearsal in SolvencyBridge

Start with the taxonomy preparation guide for the source-to-export workflow.

SolvencyBridge retains the source of imported values alongside approved mappings, giving a reporting team a traceable mapping to revisit when a denominator definition changes. Supported validation findings link back to the affected source cell, so the team can investigate the cause and rerun the check. A reviewer approves and locks the reviewed snapshot. Exports are generated from that approved snapshot, keeping the delivered figures tied to the version the reviewer signed off.

For the synthetic annual 2026 / Q1 2027 example:

1. Record the annual 2026 scope and applicable release in the preparation plan.
2. Create a separate Q1 2027 preparation row with the responsible reviewer.
3. Inventory the source sheets and fields used by each affected template.
4. Mark compatibility as unconfirmed until the field definitions, dimensions and units have been compared.
5. Rehearse using synthetic data and keep unresolved items visible.
6. Review the current result before relying on an export.

The first video works through a synthetic denominator example and selected official template extracts, then shows the public taxonomy guide. It does not demonstrate a completed migration or a successful authority submission. The later migration walkthrough will show the supported successor-draft workflow using a controlled dataset and a recorded product version.

Passing checks is only part of the review

A useful rehearsal leaves an explanation of what was checked, what changed and what still needs an owner. A clean result from implemented validations cannot establish that every regulatory requirement was checked. Retain separate responsibility for unsupported checks, authority-specific instructions and the external submission outcome.

If a reviewer finds an unexpected movement, investigate the source, mapping and applicable requirement before adjusting the reported value. The goal is a defensible explanation of the result, not merely a quiet validation screen.

Turn this into a work plan

Before comparing the ratio across periods, identify the denominator's source, check its definition against the applicable instructions, and document why the result changed. Give that check an owner and keep the source evidence with the explanation.

Choose Request a free trial to assess product fit. Bring your authority, reporting scope, next reference period and current source formats to the conversation. Use synthetic examples when discussing a problematic mapping; do not submit sensitive filing data through the public enquiry form.