STRUCT-DATE-FORMAT - Dates must use the yyyy-mm-dd format (B_01.01, B_01.02, B_02.02, B_06.01, B_07.01)

Official control text (EBA, verbatim)

Date type metric must be reported with format 'yyyy-mm-dd'

Source: EBA technical check 330 (sheet "DPM Technical Checks", category "DPM Technical Checks" in the official overview of the RoI technical checks). The RoI Builder runs it as structural check STRUCT-DATE-FORMAT.

What this rule checks

The check covers every date-typed column. Measured in eba-4.0-errata5, these are 8 columns: c0060 (Date of the reporting) in B_01.01; c0070 (Date of last update), c0080 (Date of integration in the Register of information) and c0090 (Date of deletion in the Register of information) in B_01.02; c0070 (Start date of the contractual arrangement) and c0080 (End date of the contractual arrangement) in B_02.02; c0070 (Date of the last assessment of criticality or importance) in B_06.01; c0070 (Date of the last audit on the ICT third-party service provider) in B_07.01. Selection is metadata-driven via the column data type.

Every non-empty cell of these columns must be a canonical ISO 8601 calendar date in the yyyy-mm-dd format - a real date, not just a matching pattern. An empty cell is null and is not a format violation; whether a date may be empty is governed by other layers (W2 row-completeness rules, severity warning).

Layer boundary: a malformed date is always a structural finding, never a W2 case - the W2 date rules (e.g. v8816_m) assume dates that are already syntactically valid and only compare them.

This is a structural check (STRUCT layer, severity: blocking). If it fails, the package is technically rejected on receipt (feedbackMain = REJECTED). The structural layer is the only layer that blocks a filing.

Most common causes

• A regional date format from Excel: 31/12/2024, 31.12.2024 or 12/31/2024 instead of 2024-12-31.
• A text fragment next to the date in the same cell (e.g. a note like "approx. 2024").
• A date that does not exist in the calendar, e.g. 2024-02-30, produced by hand-editing.

How to fix it, step by step

1. Open the flagged template and find the row - the finding gives the row number, the key values and the offending value.
2. Rewrite the flagged cell as yyyy-mm-dd (four-digit year, two-digit month, two-digit day), e.g. 2024-12-31.
3. If the cell mixed a date with a comment, keep only the date - the register has no room for free-text notes in date columns.
4. Run the validation again and confirm the finding is gone.

Example: fails vs passes

Fails - a regional format; the finding points at column c0070 of this B_01.02 row:

c0010 (LEI of the entity)	c0070 (Date of last update)
549300Q5EH2NP82EPE32	31/12/2024

Passes - the canonical format:

c0010 (LEI of the entity)	c0070 (Date of last update)
549300Q5EH2NP82EPE32	2024-12-31

Also fails (edge case) - 2024-02-30: the pattern looks right, but it is not a real calendar date.

Related rules

• v8816_m - a W2 date rule (end date later than start date on B_02.02); it assumes dates that are already syntactically valid - the format itself is checked here.
• v8865_m - a W2 row-completeness example on a date column: whether c0090 of B_01.02 must be filled is a warning-level question; the format of a filled value is structural.
• STRUCT-BOOLEAN-FORMAT, STRUCT-INTEGER-FORMAT, STRUCT-DECIMAL-FORMAT - the same per-cell type-format family on other column types.