Reception checks: file name, ZIP and encoding

The reception checks are the EBA's first step. They look at the ZIP file as a whole: its name, format and text encoding. If one fails, the EBA rejects the package before the content of your register is checked (EBA explainer (opens in a new tab)). In the EBA's sample responses, such a rejection is labelled REJECTED (EBA (opens in a new tab)).

The file name

Most reception checks concern the file name. It follows a fixed pattern, with the LEI, report type, country, module code, reference date and a timestamp (EBA Filing Rules (opens in a new tab)). The AFM gives the exact form for Dutch filings (AFM (opens in a new tab)); the AFM filing guide works through an example.

• The name uses only letters, digits, hyphens, underscores and dots.
• The reference date is a valid date in the form yyyy-mm-dd and is not in the future.
• Every submission has a unique name; when refiling, change the timestamp.
• Every file is UTF-8 encoded (EBA Filing Rules (opens in a new tab)).

Code 103, an invalid ZIP file, has its own page.

Does DORA Convert catch these checks?

Most of them. DORA Convert builds the file name from your workbook: the LEI and reference date from B_01.01, and a new timestamp on every build. Before you can download, we check the built package on the same points as the EBA: extension, size, ZIP structure, characters and structure of the name, module code, reference date and UTF-8.

Two checks depend on information only the EBA holds, so we can't run them beforehand:

• 107: the country in the file name must match the route by which the package arrives.
• 110: the file name must be unique against earlier submissions. A new timestamp on every build makes that all but certain, but we can't see earlier submissions.

Below is every reception check with its official description.