Error codes ยท Packaging checklists
PKG-NOT-APPLICABLE-CODES: Difference between a legitimate 'not applicable' code in an enumerated key and a placeholder string
Rejects the file
Official text
Key fields cannot be empty; where a primary key value genuinely cannot be provided report 'Not Applicable' (FAQ 26) using the DPM code, e.g. eba_GA:qx2007 for B_02.02 c0130/c0150/c0160; for providers without LEI use the real alternative identifier (FAQ 39/40), which is flagged as a DQ warning only. Placeholders such as 9999999DUMMY99999999 or 'not applicable' as a NAME are now flagged by E001-E005 (2026).
What triggers it
Difference between a legitimate 'not applicable' code in an enumerated key and a placeholder string in a free-text or identifier field.
How to fix it
Use codes, never invented strings; leave optional parent fields blank.
Sources
- ESAs, DORA RoI reporting FAQ (updated 28 March 2025) (read 2026-10-31)
- CSSF, Guidance for interpretation and resolution of ESA error messages related to the DORA register, v1.0, 15 May 2025 (read 2026-10-31)
- Commissariat aux Assurances (LU), Note d'information 26/3, 15 Apr 2026, Annex: ESA additional validation checks E001-E023 (read 2026-10-31)