Generate and verify an approved filing export

Who can perform the task

Administrators, preparers, and reviewers can generate the common approved export when the control is available. Jurisdiction-specific artifact controls can apply narrower readiness requirements.

Before you begin

The filing must be approved and locked. Confirm entity, period, taxonomy, jurisdiction, applicability, validation results, and authority-specific readiness. Know which artifact type the downstream process expects.

Quick path

1. Confirm that the filing is approved and locked against further edits.
2. Open Export readiness and resolve every named blocker.
3. Generate the required export from the approved snapshot.
4. Download the artifact and verify its entity, period, taxonomy, format, and checksum.
5. Retain the export evidence separately from later submission, receipt, and authority-acceptance evidence.

Detailed guidance

1. Expand Approval and export readiness. It stays collapsed so a long list of filing-specific blockers does not push the export and import controls down the page.
2. Review applicability readiness, local validation status and coverage, workflow status, approval snapshot, and profile-specific authority evidence. Stage explanations, blockers, warnings, evidence-review items, and their next actions follow your active interface language.
3. For every blocker, read what is missing and open the linked decision, finding, approval, or evidence control. Do not bypass a blocker.
4. Confirm the filing is approved and locked and that the approval snapshot is still current.
5. Expand Exports.
6. Read the artifact description and limitations displayed for the selected taxonomy and profile.
7. Select Validate and export approved filing.
8. Wait for success and download the new artifact.
9. Store it under controlled access without renaming away essential identity.

Expected result

An immutable artifact record appears with filename, creation time, snapshot sequence, size, and retained identity. Official supported releases may generate EIOPA or national XBRL; fixture taxonomies generate an auditable reference ZIP.

The generated artifact is identified as a reference ZIP for the synthetic fixture.

How to verify

Match the filename, checksum, and artifact record to the entity, period, taxonomy, profile, and approved snapshot. Confirm the export readiness summary was passing for that snapshot. The translated evidence summary keeps entity names, reporting dates, taxonomy versions, user identifiers, counts, snapshot numbers, and SHA-256 checksums unchanged so you can compare them directly with the source record. Exact validation findings also remain unchanged. Inspect the package contents using an approved safe process.

Common problems

• If export is unavailable, open the readiness summary and follow the named blocker to its source.
• A validation result can become stale after a value, applicability, mapping, or evidence change. Wait for or rerun validation.
• An export from an older approved snapshot remains historical evidence; it is not the current filing artifact after reopening or correction.
• A national Excel export is refused if a reported decimal cannot cross the workbook's JavaScript-number boundary without losing digits. Correct the source value or use the authority-supported exact format; the exporter does not round or truncate it silently.
• A reference ZIP is not a regulator submission package.

Audit and data consequences

Export changes status to exported and preserves an artifact for the approved snapshot. If an administrator later reopens the filing, the existing artifact remains evidence of the older snapshot and must not be presented as current.

Regulatory limitations

Successful generation proves only that the product created the stated artifact. It does not prove upload, receipt, validation by a portal, or acceptance.