Create a filing cycle and confirm applicability

Who can perform the task

Administrators and preparers can create a filing cycle. Administrators own organization and entity configuration.

Before you begin

Confirm the reporting entity, authority profile, reporting year, annual or quarterly cycle, supervisory or public-disclosure purpose, reporting level, and approved template-applicability basis. The reporting entity must have reporting defaults and at least one authority profile.

The public Solvency II reporting deadlines page is a planning reference for routine calendar-year annual and quarterly reporting. It is not the filing deadline shown here: the filing setup derives that date from the selected entity, period, reporting level, and authority profile. Confirm the derived date against the applicable authority instruction, including any entity-specific decision, exemption, national form, event-driven obligation, non-calendar-year adjustment, or portal cut-off.

The public reference shows routine calendar-year dates and source freshness; the filing setup remains the source of the deadline for the filing you create.

Quick path

1. Open Filings and select Create filing.
2. Choose the organization, reporting entity, reporting period, and reporting authority profile.
3. Confirm the taxonomy, module, currency, and filing deadline.
4. Review the derived applicability decisions and resolve anything that needs confirmation.
5. Create the filing and verify its identity before importing or entering data.

Detailed guidance

1. On Filings, expand Create filing.
2. Choose the reporting entity and reporting authority.
3. Enter the reporting year and choose annual or quarterly reporting.
4. Choose supervisory or public disclosure and solo, group, or branch.
5. Review Derived filing setup. The product derives the exact period, deadline, required Solvency II taxonomy version, and module from the selected context. YE 2026 periods through 2026-12-31 remain on EIOPA 2.8.2-hotfix. Q1 2027 and later periods use EIOPA 2.10.0; do not move a 2026 filing onto the Review package early.
6. Stop if the derived taxonomy is not installed or the context is not valid. Do not substitute another taxonomy or module.
7. Search the module-compatible template catalog and select the initial required working set. Templates not selected here remain Needs confirmation; they are not silently marked non-applicable.
8. For a 2027 filing, review the National Review evidence notice. If its legal or authority evidence is incomplete, confirm the preparation-only boundary. The confirmation is tied to the profile, period, taxonomy, evidence checksum, actor, and time. It does not unblock export or submission.
9. Select Create filing and open it.
10. In the filing navigation, choose Manage templates. Search the combined catalog or filter it by EIOPA or the national authority, then add the templates needed for this filing. An added template becomes available for preparation immediately.
11. To remove a template from the filing, choose Remove, enter the reason, and confirm. Removal excludes the template from completion, validation, and export without deleting its entered values or history. Adding it again restores the same work. The filing must retain at least one required EIOPA template.
12. Use National reporting status only when an included national form is a nil or not-filed return. Forms that require explicit reported values do not offer that shortcut, and a populated form must be cleared before it can be changed to nil or not filed.
13. Expand the applicability details when a decision requires Required, Not required, or Needs confirmation together with its rationale and evidence.
14. In What happens next, follow the ordered action. Its Open control takes you to the exact applicability, template, validation, review, or export control that currently owns the next step.

Expected result

The filing header and portfolio show the intended entity, period, jurisdiction, status, and due date. The filing uses the derived taxonomy and module. Required templates appear in completion and validation; unresolved templates remain visible as blockers until explicitly decided.

For a preparation-only 2027 filing, the filing retains the exact confirmation snapshot. Export, authority packaging, and submission readiness remain blocked until the current national legal and authority evidence gates pass.

The derived setup makes period, deadline, taxonomy, and module visible before creation.

Template membership is managed in one place. Detailed applicability decisions remain explicit and evidence-backed inside the same drawer.

How to verify

Compare the filing identity and applicability summary with the approved instruction. Confirm the derived taxonomy version and module before importing data. Resolve all Needs confirmation decisions before review. Confirm the installed taxonomy package identity against the approved release record.

Common problems

• Configure the entity and authority profile first means the reporting defaults or authority profile are incomplete.
• If the derived setup is invalid, correct the entity, authority, year, cycle, purpose, or reporting level.
• If the needed taxonomy is not installed, stop and ask the operator to install the approved package.
• If a template is missing after creation, open Manage templates and search the combined catalog rather than importing into another table.
• Removing a template does not delete its saved values. Add it again to restore the prior work, or clear the values explicitly if they should no longer be retained.
• Confirm the National Review preparation boundary means the current profile has no fresh, checksum-bound legal or authority evidence sufficient for export readiness. Review /coverage, confirm only if draft preparation is intended, and do not treat the confirmation as transposition evidence.
• A blocked action states what is missing. Use Open rather than searching manually for the affected control.

Audit and data consequences

Template membership and applicability determine which forms are part of completion, validation, and export. Removal preserves values and attributable history so the choice can be reversed. A wrong decision can omit required information or include an inappropriate template. Preserve the basis for each decision.

Regulatory limitations

The product can guide and record applicability; it does not make the regulatory determination for your organization.

Directive (EU) 2025/2 and the related Review framework apply from 30 January 2027 at EU level. The product separately tracks Member State measures notified through EUR-Lex and EEA incorporation evidence. An official notification is not proof that transposition is complete or correct, and neither the tracker nor a preparation confirmation is legal advice, proof of compliance, regulator approval, or authority acceptance.