From the Excel register to xBRL-CSV
Most registers live in a workbook, usually the EBA's annotated table layout. The ESAs confirmed in December 2024 that they would provide no converter, so the step from workbook to package is yours. These are the rules the conversion must apply.
- One sheet per template. B_01.01 to B_07.01 and B_99.01, each becoming
b_xx.xx.csv. Extra sheets (instructions, lists) are ignored. - Header row of column codes.
c0010,c0020,…. The ITS column names and the0010numbering are what the workbook shows; the csv wants the codes. Columns may be in any order; extra columns are dropped. - Codes, not labels.
eba_GA:IEnot Ireland;eba_CT:x300not Payment institution;eba_BT:x28not Yes. Every list is on the template pages. A label where a code is expected is 503. - Dates as yyyy-mm-dd. Excel will show 31/12/2025 and store a serial number; both fail 330.
9999-12-31is the convention for open-ended arrangements and not-yet-deleted entities. - Amounts as plain numbers. No currency symbols, no thousands separators, decimal point not comma; percentages as fractions where a template asks for a decimal.
- Keys filled, consistent and trimmed. Contract references, LEIs and function identifiers are compared exactly across templates: a trailing space in B_02.02 and none in B_03.01 is 807; an empty key cell is 805; the same key twice is 806.
- Booleans.
true/falsein B_03.01 c0030 and similar technical columns; the DNB Excel route wanted lower-case true. - Save as UTF-8 csv, then package as described in the package guide.
The builder does steps 1 to 8 from the workbook or a zip of csv files and validates the result. Austria's FMA, the CNMV and the DGSFP take their own Excel templates instead of a package; BaFin, DNB and Norway accept either.