Solvency II Excel imports: catch the €60,000 column mistake

The spreadsheet is complete. Every record has an amount. Yet one source-column choice changes the total by €60,000.

The problem is easy to miss because both columns contain sensible numbers. Before reusing an import, a reporting team needs to confirm which number answers the reporting question—and inspect the proposed result before applying it.

Start with one row

Our synthetic source contains four positions dated 30 September 2026, in EUR, at scale 1. The source owner has already prepared the Solvency II amounts.

For the first position, selecting Book value proposes €980,000. The intended source for this example is €1,010,000 in Synthetic assets!E2. Nothing about the smaller number's format makes it invalid. Its business meaning is wrong for the agreed destination.

These are four fictional positions, not a complete assets return. Their labels identify source records; they do not establish valid security identifiers or full reporting contexts.

Read the reporting field before choosing the source

In EIOPA's 2.8.2 Hotfix annotated templates, S.06.02.01.01 / C0170 is Total Solvency II amount.

The reporting instruction gives the meaning: C0170 is the asset value on the Article 75 Solvency II valuation basis. For relevant assets, it uses par amount times the Solvency II percentage price, or quantity times the Solvency II unit price, with accrued interest included where applicable. Cash (CIC 71) and property (CIC category 9) use the asset's Solvency II value. That is why a clean price or a book-value column cannot simply substitute for the required total.

Confirm the amount's valuation basis and any required adjustments with its owner. A price per unit, a book value and a total value for a position can all be correct while answering different questions. Renaming a column does not resolve those differences.

For this exercise, Solvency II amount is an explicit input assumption: the source already contains the required total amount. SolvencyBridge does not infer that basis from the header. In a real filing, the reporting team must establish it from the source methodology and applicable instructions.

Sources: We checked the field label and code in EIOPA's annotated templates, cells R5–R6, on 2 October 2026. We checked the C0170 instruction and CIC definitions in Annex II (page 669) and Annex VI (pages 1592–1593) on 5 October 2026.

Make the source boundary visible

Select Synthetic assets!A1:F5: one header row and four records. Exclude the instruction sheet and the note below the table. Confirm the entity, reference date, currency and scale before mapping.

SolvencyBridge's workbook inventory lets a preparer inspect sheets and ranges before reviewing the proposed import. Preserve the original upload. Formula cells need particular care because the import does not run Excel's calculation engine. This example uses stored numeric values, so the result does not depend on an Excel recalculation. Import workflow, supported formats.

A source range also needs a reporting destination and a record identity. For a repeating assets table, review the applicable row keys and required context as well as the amount column.

Inspect the mistake before applying it

Select Book value in the draft mapping and inspect the proposed first amount. Then compare it with the agreed source at E2. The mismatch explains why the choice needs to change before the import reaches the filing.

Correct the mapping to Solvency II amount, then inspect all four records. Their source control total is €4,550,000, versus €4,490,000 for Book value. The €60,000 difference is the net result: it includes a −€30,000 difference on the second position. Looking only at the first row would miss that detail.

Reconcile the selected source records, then check the amount's meaning with its owner. A plausible numeric result can still come from the wrong source column.

Keep testing, review and application connected

In the mapping workflow, save the current choices and test the revision against the selected source. Submit the tested revision for reviewer assessment. Approval and activation are separate steps; an executable change after testing needs fresh evidence. Reusable mappings.

Before importing with the active mapping, inspect the preview again. Preview does not update the filing. Apply is a separate action. After applying a supported import, inspect the reported amount and its source lineage, including the worksheet, cell and mapping revision.

This is how SolvencyBridge helps turn a spreadsheet choice into reviewable work: the preparer can see the proposed result, the reviewer can inspect a tested revision, and the reported amount retains its source evidence. Mapping approval does not replace the filing's own review or the external submission process.

Reuse the mapping, then check the new source

Next cycle, check whether the provider changed the layout, the amount's meaning, or both. A moved column needs a layout check; a changed valuation basis needs a new business decision. Review the new preview even when the headings look familiar.

Download the four-row source workbook below to inspect this example. It contains the actual source values and selection instructions. Start with DEMO-A01, trace the amount to E2, and reconcile the other positions before accepting the mapping.

See the preparation and review workflow

The four-row example above shows why the EUR 60,000 source-column difference needs a reviewed mapping decision. The English reporting walkthrough follows a separate synthetic Slovak Q3 2026 filing through import preview, correction, independent review and approved EIOPA XBRL export. National XML, supervisory submission and authority acceptance are not demonstrated.

Request a guided evaluation. We first confirm supported scope and demonstrate the relevant workflow, then agree a free 14-day trial where appropriate, with an owner and a success criterion.