Reports
The report forms are generated from the official ESA JSON schemas (version 2025-03-26) for the initial notification, the intermediate report and the final report. Required fields are marked with an asterisk.
Pre-filling
- Settings fill the general information: entity name, LEI or code, type of entity, ultimate parent undertaking, primary and secondary contacts, report currency and the FI institution number in the report header.
- The incident fills the incident reference code, detection, classification, occurrence and resolution times, the description, the classification criteria and FI's reference code.
- The previous report fills the intermediate report (from the initial notification) and the final report (from the intermediate report).
- Import JSON loads a report you generated earlier into the form.
Your draft is saved automatically in this browser while you type. Values you have entered take precedence over pre-filled values.
Validation and download
Validate and Download JSON send the form to the server, which builds the report and validates it against the ESA JSON schema. The data is processed in memory and not stored. Errors are shown next to each field.
The following ESA consistency rules are applied automatically:
- The affected-entity LEI is left out when it is the same as the submitting entity.
- LEI and entity code are mutually exclusive.
- Impacted Member States are only included when geographical spread is a selected classification criterion, and the home Member State is removed from the list.
Date, time and duration formats
The formats follow Annex II to Commission Implementing Regulation (EU) 2025/302 (ITS on incident reporting), the ESA JSON schemas and FI's reporting templates.
| What | You enter | Exported as |
|---|---|---|
| Date and time (fields 2.2, 2.3, 3.2, 3.3, 4.7, 4.8 and 4.16) | Swedish time, 24-hour clock, YYYY-MM-DD hh:mm |
UTC in ISO 8601, YYYY-MM-DDThh:mm:ss.0Z |
| Duration and service downtime (fields 3.15 and 3.16) | Days, hours and minutes, DD:HH:MM |
DD:HH:MM, for example 01:04:30 |
| Reporting date (report header) | YYYY-MM-DD |
YYYY-MM-DD |
Swedish time is converted to UTC, including daylight saving time. For example, 2026-03-01 23:30 is exported as 2026-03-01T22:30:00.0Z. Durations are zero-padded, so 1:4:30 is exported as 01:04:30; hours must be 0-23 and minutes 0-59. A duration longer than 99 days uses three digits for the days.
Every form in the app shows dates as YYYY-MM-DD and times on the 24-hour clock, whatever your browser's language. Type the date or use the calendar button. 20260301 and 2026-3-1 are changed to 2026-03-01, and 0930 to 09:30.
When you import a JSON file, the UTC times are shown in Swedish time again.
Submitting to FI
Upload the JSON file in FI's reporting portal. Then open the incident and record the submission time and, after the initial notification, FI's reference code. The next deadline is calculated from the submission time.
Use the same incident reference code in all three reports.