Roifile

Guides

The DORA register zip filename, part by part

The ESAs read the filename before they open the zip. Four reception checks and one DPM check depend on it, and the first sign of trouble in 2025 was files rejected within a minute for a name that looked right.

635400EWECOAKJOHRI84.IND_IE_DORA010100_DORA_2025-12-31_20260115093000000.zip
└──────── LEI ───────┘ └┘ └┘ └──────────┘ └──┘ └───────┘ └─────────────┘
                        │   │       │         │       │           17-digit creation timestamp yyyyMMddHHmmssSSS
                        │   │       │         │       reference date, the period end, yyyy-mm-dd
                        │   │       │         module name, always DORA
                        │   │       framework code and module version: DORA 1.1.0 is written DORA010100
                        │   country of the competent authority, two letters
                        consolidation scope: IND (the entity alone) or CON (a group register)

What is checked against it

102The name must match the pattern exactly: upper-case LEI, a dot, CON or IND, underscores, a hyphenated date, 17 digits, .zip.
105The folder inside the zip must carry the same name without .zip. Several portals (CBI, CSSF, AFM, MFSA, FI, Norway) enforce this harder than the ESAs.
109, 111The reference date must be a real date and not in the future. A file for 31 December 2026 cannot be sent on 20 December 2026.
714entityID in parameters.csv must be rs: plus the first part of the filename: rs:635400EWECOAKJOHRI84.IND for the example above.
320refPeriod in parameters.csv must equal the date in the filename.

Where the pattern is different

The packager writes the right name for each of these from a validated ESA package.

Other guides