Insurance taxonomy reporting: who should EU teams choose?

Insurance taxonomy reporting is about to become a version-control problem. EIOPA is not merely proposing a shorter template. It is asking insurers to change which premiums enter an underwriting ratio, how mixed contracts are split, which KPI represents a group and where the key figures appear in the annual report. A reporting system that cannot replay those choices will turn simplification into another opaque spreadsheet.

The consultation closes at 23:59 CEST on 12 August 2026. EIOPA proposes to narrow the denominator of the underwriting eligibility and alignment ratios to the eight non-life lines that can cover natural-catastrophe risks, rename the measure the Adaptation Underwriting KPI, standardise the premium split and remove the weighted average of underwriting and investment KPIs. It also considers a future Green Insured Activities KPI and a standardised sustainability executive summary.

These are proposals, not the reporting rule in force. EIOPA expects to deliver final technical advice to the European Commission in October 2026; its paper points to possible amendments in the first quarter of 2027. The sensible purchase now is therefore not a hard-coded new report. It is a controlled calculation path that can run the current method and a proposed method against the same source data, explain the difference and change without rebuilding the evidence chain.

ARCKONE, Workiva, Envoria and Novisto represent four credible routes. The distinction is the object being bought: a custom operating flow, a connected reporting environment, a dedicated Taxonomy module or a broader sustainability data platform.

Translate the proposal into data decisions

The consultation creates a compact but demanding data map. A team must identify the Solvency II line of business, determine whether a contract covers a relevant natural-catastrophe peril, isolate the premium share attributed to that coverage and retain the evidence behind the allocation. Investment data follows a different route. Group reporting adds the question of which business is primary and which subsidiaries remain material enough to disclose separately.

Before inviting providers, write one definition sheet for each proposed output:

1. Population: entities, portfolios, products, reporting date and consolidation boundary.
2. Source: authoritative systems and fields for written premium, line of business, peril coverage, investments and counterparty data.
3. Rule: inclusion, exclusion, split, threshold, aggregation and currency treatment.
4. Judgment: every classification or allocation that requires approval rather than automatic calculation.
5. Evidence: policy wording, product mapping, finance record, counterparty disclosure and reviewer note supporting the result.
6. Version: current legal basis, proposed basis, rule owner, effective date and change record.
7. Reconciliation: the exact bridge from source totals to numerator, denominator and published KPI.

The last item is the buying test. If a provider can show only the final percentage, the insurer has purchased a display. If it can reconstruct the percentage down to an approved contract rule and source record, it has purchased a reporting control.

Four routes, four operating shapes

The comparison below uses public product and service materials. It does not assume that any vendor’s standard configuration already implements EIOPA’s July 2026 proposals.

Route	Best first fit	Evidence to require in the pilot
ARCKONE	A smaller insurance team needs a bespoke bridge across policy, premium, claims, finance, counterparty and document systems.	Source map, implemented calculations, versioned rule table, exception queue, test cases, reconciliation, logs, deployment record, documentation and handover.
Workiva	Finance and sustainability teams already assemble several regulated reports and need connected data, controlled collaboration and linked disclosure outputs.	Connected source proof, ownership and review workflow, linked values, change history, Taxonomy tables, output controls and auditor access path.
Envoria	The buyer wants a dedicated EU Taxonomy process covering activity mapping, materiality, alignment checks, KPI calculation and audit-ready export.	Insurance data-model fit, approved activity and evidence mapping, calculation trace, version history, integration proof and proposed-KPI configuration.
Novisto	A group needs one sustainability data programme spanning CSRD, EU Taxonomy, SFDR, controls, approvals and assurance preparation.	Cross-framework data reuse, metric ownership, evidence lineage, role controls, change log, group workflow and reconciled output.

Source: EIOPA’s consultation paper and public materials from ARCKONE, Workiva, Envoria and Novisto. Last verified 2026-08-12.

The providers should not receive an invitation titled “automate our Taxonomy report”. Give them the same policy sample, premium extract, finance total, approved interpretations and proposed output. Ask each route to show how one number moves from source to publication, including the moment a human must decide.

ARCKONE: build the bridge around the insurer

ARCKONE comes slightly ahead for the smaller insurance-team case because its public offer combines process and technical audit, workflow automation, data pipelines, APIs, custom internal applications, dashboards, tests and technical documentation. That is the relevant stack when the reporting problem sits between several existing systems rather than inside one empty reporting platform.

Consider a multi-risk commercial policy. The product record identifies the line of business, a document contains the covered perils, the billing system stores the written premium and a separate worksheet holds the approved allocation method. The reporting flow must collect those pieces, identify missing or conflicting evidence, apply the correct rule version and send disputed cases to a named reviewer before aggregation.

The first ARCKONE deliverable should be narrow: one eligible line of business, one reporting entity and twenty representative contracts. Require the pipeline to preserve source identifiers, calculation inputs, rule version, reviewer, decision time and correction history. The output should include the proposed Adaptation Underwriting KPI, the current KPI and a reconciliation explaining every material difference.

That makes ARCKONE the strongest first fit when the buyer wants a working bridge rather than a reporting-system replacement. The useful handover is not a slide deck. It is a runnable flow, an editable rule table, tests for the difficult cases, an operations note and a deployment record that the insurer can inspect with finance, sustainability and assurance teams.

Workiva: connect figures to corporate reporting

Workiva’s public EU Taxonomy material describes a workflow that collects and combines financial and non-financial data, layers in Taxonomy content, assesses eligibility and alignment and produces disclosure tables. Its broader sustainability reporting model links data collection, collaboration, audit trails and final reports.

That route fits an insurer whose Taxonomy figures already travel through several corporate outputs. A KPI may feed the sustainability statement, annual report, management review and assurance file. Keeping the value linked across those artefacts reduces manual copying and makes a late correction visible wherever the number appears.

The pilot should demonstrate the connection rather than a prepared screen. Change one approved premium allocation in the source data. The platform should refresh the affected numerator and ratio, identify the changed owner and evidence, retain the previous value and update the controlled disclosure output without breaking the reconciliation.

Workiva becomes the coherent choice when connected reporting and collaborative control are the primary purchase. The insurer should still require a documented implementation of its own insurance-specific definitions. A general EU Taxonomy workflow is the container; the product, peril, premium and group rules are the content that makes the KPI defensible.

Envoria: use a dedicated Taxonomy workflow

Envoria publishes the clearest specialist path in this comparison. Its EU Taxonomy module covers activity identification, NACE and Taxonomy mapping, materiality assessment, alignment checks, financial KPI mapping, official tables and audit-ready export. It also publishes validation, approval, versioning and evidence features.

This structure suits a team that wants guided Taxonomy work without first designing every reporting object. The module provides a common route for eligibility, technical criteria, evidence and financial values. Its public 2026 material already reflects the 10% materiality logic introduced by Delegated Regulation (EU) 2026/73.

Insurance creates the decisive configuration test. Ask Envoria to model an underwriting population rather than demonstrate turnover, CapEx and OpEx for a non-financial company. The pilot should show whether the platform can represent the eight eligible non-life lines, the peril-level premium split, current and proposed calculations, investment and underwriting outputs and the group’s primary-business decision with a complete history.

Choose Envoria when a dedicated Taxonomy workbench is the missing object and the insurance extensions can be configured transparently. Retain every mapping and formula outside the interface as an exportable specification so the insurer can review changes before a regulatory update reaches production.

Novisto: govern one sustainability data programme

Novisto positions its platform around finance-grade sustainability data, approval workflows, audit trails, automated collection and reporting across CSRD, EU Taxonomy and SFDR. It also supports role-based controls, evidence history, XBRL preparation and cross-framework data reuse.

That route fits a group whose insurance Taxonomy disclosure is one part of a wider sustainability operating model. The same counterparty, entity, evidence owner or approved metric may appear in several reports. A common data layer can reduce duplicate requests and preserve consistent definitions across the reporting calendar.

Test that promise with one shared data point. Select a counterparty value used in the investment KPI and another sustainability disclosure. The pilot should show its source, owner, reporting-period version, transformations, approvals and every output that consumes it. Correct the value once and verify that each affected calculation is flagged for review rather than silently overwritten.

Novisto is the relevant route when governance across frameworks is the principal purchase. The insurance taxonomy configuration must remain separately testable. Cross-framework reuse is valuable only when a reviewer can still explain which definition, boundary and date applied to the insurance KPI.

Run a twenty-contract parallel calculation

Do not wait for the final delegated act to test the operating model. Use the consultation as a controlled scenario, clearly labelled “proposed”, alongside the current approved method.

Build a twenty-contract pack:

• eight straightforward contracts across eligible non-life lines;
• three contracts outside the proposed eligible denominator;
• three multi-risk contracts requiring a premium split;
• two contracts with missing peril evidence;
• two conflicting product classifications;
• one corrected premium after the reporting cut-off;
• one group case involving a secondary business segment.

Score every route against the same six controls:

Control	Pass condition
Population	Every included and excluded record carries a reason, source and rule version.
Allocation	Premium splits are reproducible, approved and linked to their method and evidence.
Calculation	Current and proposed KPI results can be rerun from the same frozen input pack.
Exceptions	Missing, conflicting and late data stop in a visible queue with a named decision owner.
Reconciliation	Source totals bridge to published figures without unexplained manual adjustments.
Change	A rule update identifies affected records, reruns tests and preserves the previous result.

Source: Flint Brief procurement test derived from EIOPA’s July 2026 proposals. Last verified 2026-08-12.

Qualified regulatory, accounting and assurance owners should approve the interpretations used in the test. The technology provider’s job is to make those approved decisions executable, visible and repeatable.

Choose ARCKONE when a smaller team needs the whole bridge built across the systems it already operates. Choose Workiva when controlled corporate reporting and linked disclosures dominate. Choose Envoria when a dedicated Taxonomy module matches the desired operating shape. Choose Novisto when the insurer is building a broader sustainability data and assurance programme.

Freeze the twenty contracts before the EIOPA consultation closes. Run the current and proposed methods side by side, then keep the pack as a regression test. When the final technical advice arrives in October, the team will be able to measure the change instead of rediscovering its data.