The rule in plain words
If entity uses MAP then template Impact of long-term guarantees measures and transitionals (S.22.01) has to be reported
EIOPA writes it out as separate checks, one for each table or return it covers. Line4 Check runs three of them (BV338-1 to BV338-3), and a failure names the one that failed.
What to do if your return fails it
- 01Open the tables below and find the cells the rule reads.
- 02The check applies only when its first part holds in your return. When it does, the second part must hold too: fix the second part, or correct the first.
- 03It runs only when your filing indicators mark S.01.01 and S.01.02 as reported.
- 04This is a blocking check. A return that fails it is normally rejected, so fix it before you submit.
The cells it reads
Content of the submission (S.01.01.01.01)
Row
- R0370S.22.01.01 - Impact of long-term guarantees measures and transitionals
Column
- C0010Reporting status
Content of the submission (S.01.01.04.01)
Row
- R0370S.22.01.04 - Impact of long-term guarantees measures and transitionals
Column
- C0010Reporting status
Content of the submission (S.01.01.07.01)
Row
- R0370S.22.01.01 - Impact of long-term guarantees measures and transitionals
Column
- C0010Reporting status
Basic information (S.01.02.01.01)
Row
- R0170Matching adjustment
Column
- C0010Report information
Basic information (S.01.02.04.01)
Row
- R0170Matching adjustment
Column
- C0010Report information
Basic information (S.01.02.07.01)
Row
- R0170Matching adjustment
Column
- C0010Report information
Which returns it applies to
Line4 Check runs it on annual solo (ARS), annual group (ARG) and annual branch (ARB) returns on EIOPA taxonomy 2.10.0. EIOPA applies it to annual solo (ARS), annual group (ARG) and annual branch (ARB) returns, as a blocking check.
EIOPA’s own words and formula
In EIOPA’s list of validations, word for word:
If entity uses MAP then template S.22.01 - Impact of long-term guarantees measures and transitionals has to be reported.
Show the formulaShowHide
EIOPA's formula, for BV338-1. Cells are written as {t: table, r: row, c: column}.
if ({t: S.01.02.01.01, r: R0170, c: C0010} = [s2c_PU:x51]) then {t: S.01.01.01.01, r: R0370, c: C0010} = [s2c_CN:x1] else true()BV338-2:
if ({t: S.01.02.04.01, r: R0170, c: C0010} = [s2c_PU:x51]) then {t: S.01.01.04.01, r: R0370, c: C0010} = [s2c_CN:x1] else true()BV338-3:
if ({t: S.01.02.07.01, r: R0170, c: C0010} = [s2c_PU:x51]) then {t: S.01.01.07.01, r: R0370, c: C0010} = [s2c_CN:x1] else true()Other rules on Content of the submission (S.01.01)
- Content of the submission and basic information: a conditional check (BV339)Blocking
- Content of the submission and basic information: a conditional check (BV336)Blocking
- Content of the submission and basic information: a conditional check (BV340)Blocking
- Content of the submission and basic information: a conditional check (BV335)Blocking
- Content of the submission and basic information: a conditional check (BV341)Blocking
- Content of the submission and basic information: a conditional check (BV334)Blocking
- Content of the submission and basic information: a conditional check (BV342)Blocking
- Content of the submission and basic information: a conditional check (BV333)
Every Solvency II rule on S.01.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.
