2 min readBlockingEIOPA taxonomy 2.10.0Updated 11 November 2026

Balance sheet and non-life technical provisions: a total must equal the sum of its parts (S.02.01, S.17.01, EIOPA rule BV724)

A blocking check on the balance sheet (S.02.01) and non-life technical provisions (S.17.01) templates, in the annual solo (ARS) and annual branch (ARB) returns.

It applies to 2.8.2 returns too, the release for the 2026 returns, and Line4 Check runs it there as well.

The rule in plain words

The item "Technical provisions calculated as a whole (health NSLT)" in template Balance sheet (S.02.01) must be equal to technical provisions calculated as a whole without transitory measures plus the corresponding amount of transitory measures reported in template Non-life technical provisions (S.17.01)

The headline gives only the template and the kind of check, because the rule is too long to say in a headline. The plain words above say all of it.

EIOPA writes it out as separate checks, one for each table or return it covers. Line4 Check runs two of them (BV724-4 and BV724-8), and a failure names the one that failed.

What to do if your return fails it

  1. 01Open the tables below and find the cells the rule reads.
  2. 02Add up the parts in your return and compare the result with the total.
  3. 03If they differ, a part is missing, a value sits in the wrong cell, or the total is out of date.
  4. 04EIOPA allows a small rounding difference, worked out from the decimals each value is reported with.
  5. 05It runs only when your filing indicators mark S.02.01 and S.17.01 as reported.
  6. 06This is a blocking check. A return that fails it is normally rejected, so fix it before you submit.

The cells it reads

Balance sheet (S.02.01.01.01)

Row

  • R0570Technical provisions calculated as a whole

Column

  • C0010Solvency II value

Balance sheet (S.02.01.07.01)

Row

  • R0570Technical provisions calculated as a whole

Column

  • C0010Solvency II value

Non-life technical provisions (S.17.01.01.01)

Rows

  • R0010Technical provisions calculated as a whole
  • R0290TP as a whole

Columns

  • C0020Medical expense insurance
  • C0030Income protection insurance
  • C0040Workers' compensation insurance
  • C0140Non-proportional health reinsurance

A worked example

The first of its checks, with simple numbers.

Illustrative values
Technical provisions calculated as a whole, Medical expense insurance1,200
Technical provisions calculated as a whole, Income protection insurance800
Technical provisions calculated as a whole, Workers' compensation insurance450
Technical provisions calculated as a whole, Non-proportional health reinsurance300
TP as a whole, Medical expense insurance150
TP as a whole, Income protection insurance100
TP as a whole, Workers' compensation insurance60
TP as a whole, Non-proportional health reinsurance40
Together3,100
What the rule then expects

Technical provisions calculated as a whole, Solvency II value must then be 3,100.

3,100Passes
3,200Fails

A file that reports 3,100 passes. One that reports 3,200 fails, by 100.

The numbers are illustrative, reported to the unit, so the rounding tolerance does not change the result.

Which returns it applies to

Line4 Check runs it on annual solo (ARS) and annual branch (ARB) returns on EIOPA taxonomy 2.10.0. EIOPA applies it to annual branch (ARB) and annual solo (ARS) returns, as a blocking check.

EIOPA’s own words and formula

In EIOPA’s list of validations, word for word:

The item "Technical provisions calculated as a whole (health NSLT)" in template S.02.01 - Balance sheet must be equal to technical provisions calculated as a whole without transitory measures plus the corresponding amount of transitory measures reported in template S.17.01 - Non-life technical provisions.
Show the formulaShow

EIOPA's formula, for BV724-8. Cells are written as {t: table, r: row, c: column}.

{t: S.02.01.01.01, r: R0570, c: C0010} = {t: S.17.01.01.01, r: R0010, c: C0020} + {t: S.17.01.01.01, r: R0010, c: C0030} + {t: S.17.01.01.01, r: R0010, c: C0040} + {t: S.17.01.01.01, r: R0010, c: C0140} + {t: S.17.01.01.01, r: R0290, c: C0020} + {t: S.17.01.01.01, r: R0290, c: C0030} + {t: S.17.01.01.01, r: R0290, c: C0040} + {t: S.17.01.01.01, r: R0290, c: C0140}

BV724-4:

{t: S.02.01.07.01, r: R0570, c: C0010} = {t: S.17.01.01.01, r: R0010, c: C0020} + {t: S.17.01.01.01, r: R0010, c: C0030} + {t: S.17.01.01.01, r: R0010, c: C0040} + {t: S.17.01.01.01, r: R0010, c: C0140} + {t: S.17.01.01.01, r: R0290, c: C0020} + {t: S.17.01.01.01, r: R0290, c: C0030} + {t: S.17.01.01.01, r: R0290, c: C0040} + {t: S.17.01.01.01, r: R0290, c: C0140}

Every Solvency II rule on S.02.01

Checks like this one, run at the point of submission, are the first step to real-time supervision. Line4 builds SupTech software for financial regulators that runs checks like these as each return arrives.