parameters.csv in a DORA report package
parameters.csv tells the processor who is reporting, for which date, in which currency and at what precision. It has a header and five rows, and it is the file most often edited by hand and broken by hand.
name,value
entityID,rs:635400EWECOAKJOHRI84.IND
refPeriod,2025-12-31
baseCurrency,iso4217:EUR
decimalsInteger,0
decimalsMonetary,0entityID | The prefix rs: (the reporting-subject scheme), the LEI in upper case, a dot, then IND or CON. It must match the start of the filename (714). Forgetting rs: is the FSMA's most common rejection; Norway, Sweden and Finland put a national number here instead of the LEI. |
refPeriod | The reference date, yyyy-mm-dd, equal to the date in the filename (320). The period end, not the submission date. |
baseCurrency | iso4217: plus the code. EUR almost everywhere; iso4217:NOK in Norway, iso4217:SEK or EUR in Sweden. Amount columns are then read in this currency. |
decimalsInteger | 0. |
decimalsMonetary | The precision amounts are stated to. 0 means exact units; -3 means to the nearest thousand (FSMA, NBB and FIN-FSA examples); Norway's example uses -4. A value too low for the figures you report produces a decimals warning. |
Things that break it
- A semicolon separator, a BOM, or a header other than
name,value(the MFSA readsName,value; the ESAs accept either case). - A lower-case LEI, or spaces after
rs:. - The file saved as parameters.csv.txt by a text editor, which fails 701 (control file missing).
- Extra parameters the processor does not know, which raise
xbrlce:unreferencedParameterin CSSF feedback.
The builder writes this file from the metadata you type; the packager rewrites it for regulators that use a national identifier.