Error code 701: required files missing

What the code means

The reports/ folder of your package lacks report.json, parameters.csv or FilingIndicators.csv, or one of those files is empty. The EBA requires all three, and not empty (EBA (opens in a new tab)).

The three files sit next to the CSV files holding your register (B_01.01, B_01.02 and so on). The EBA needs them to process the package (AFM Q&A (opens in a new tab)):

File	Content
report.json	Points to the DORA module entry point of the EBA taxonomy.
parameters.csv	Header name,value, with among others entityID, refPeriod and baseCurrency (EBA Filing Rules (opens in a new tab)).
FilingIndicators.csv	All 15 templates, each with the value true.

Typical cause

• Only the tables packed: the package holds the 15 table files but not the three extra files.
• Different file name: a file is named differently from the EBA's sample. The EBA then treats it as an extra file, and the required file as missing (AFM Q&A (opens in a new tab)).
• Wrong place: the files are not in reports/ but, for example, in the top folder.
• Empty file: one of the three files exists but is empty.

How to fix it

There is nothing to fix in the Excel workbook: the package was built incomplete. Build it again with all three files in reports/, spelt exactly as in the EBA's sample packages (opens in a new tab). The AFM filing guide shows the full layout.

Does DORA Convert catch it before you file?

Yes. DORA Convert writes META-INF/reportPackage.json, report.json, parameters.csv and FilingIndicators.csv into every package. Before you can download, we check that all four are present, in the right place and not empty. We check the content of parameters.csv and report.json too. If a check fails, we don't offer the package.

Related codes

• 720: extra or misnamed files in the package.
• 714: entityID in parameters.csv is missing or doesn't match the file name.
• 702 and 808: the content of FilingIndicators.csv.
• Code 505 (report.json doesn't point to the module entry point): DPM checks.