Error codes ยท EBA technical checks (reception)
807: The reported data must follow the key-foreign key contraints defined in the DPM
Rejects the file also shown as EBA.807
Official text
The reported data must follow the key-foreign key contraints defined in the DPM
How it appears in feedback
[table],[row],[column],807,The reported data must follow the key-foreign key constraints defined in the DPM,[value]EBA.807: Contractual arrangement reference numbers must match (parent: [parent table] [parent column], child: [child table] [child column]), missing key-foreign: [value]EBA.807: Identification code must match (parent: B_05.01 c0010, child: B_05.01 c0110), missing key-foreign: [value]EBA.807: LEI of the parent should be also a record (parent: ..., child: ...), missing key-foreign: [value]Formula Error: eba_807_1 : B_XX.XX, c00XX is not in list {b_XX.XX, c00XX}. Rule check: The reported data must follow the key-foreign key constraints defined in the DPM. Reported value: XXXXXXXX. Template: B_XX.XX Row: XXXXXXXXX Column 00XX. (CBI portal wording)
What triggers it
Referential integrity: a value in a foreign-key column has no matching primary key. The most frequent rejection everywhere (AFM: 'the most common reject'). Two shapes: across tables (e.g. b_03.01 c0020 must exist in b_01.02 c0010; b_02.02 c0020 in b_06.01 c0040; b_02.03 c0010 in b_02.01 c0010; b_05.02 c0030 in b_05.01 c0010; b_04.01 c0020 in b_01.02 c0010) and self-reference (b_05.01 c0110 ultimate parent must itself be a row in b_05.01 c0010; b_02.01 c0030 master contract must be a row in b_02.01 c0010). Cascades: if a whole table failed to load (801, 805, 809, non-UTF-8), every FK into it fails.
A value points at a row that does not exist: a contract reference in B_03.01 that is not in B_02.01, a provider in B_07.01 that is not in B_05.01, a parent LEI in B_01.02 that is not itself a row of B_01.02. Also fired for every reference into a table that could not be loaded because of an 801 or 805 error.
Templates: B_02.01, B_02.02, B_02.03, B_03.01, B_04.01, B_05.01, B_05.02, B_07.01. Columns: b_03.01.c0020->b_01.02.c0010, b_02.02.c0020->b_06.01.c0040, b_02.03.c0010->b_02.01.c0010, b_05.02.c0030->b_05.01.c0010, b_04.01.c0020->b_01.02.c0010, b_05.01.c0110->b_05.01.c0010, b_02.01.c0030->b_02.01.c0010, b_07.01.c0010->b_02.01.c0010
How to fix it
Before packaging, check every FK listed in 'Data Model for DORA RoI' resolves; add the ultimate parent as its own b_05.01 row (or repeat the provider's own ID in c0110 when it has no parent); strip leading/trailing spaces from key values; fix 801/805/809 first because they produce spurious 807s.
Fix the referenced table first. Every arrangement in B_02.02, B_03.x, B_04.01, B_05.02 and B_07.01 must exist in B_02.01; every provider in B_02.02, B_03.02, B_05.02 and B_07.01 must exist in B_05.01; every entity LEI must exist in B_01.02; every function in B_02.02 must exist in B_06.01 for the same entity.
Sources
- EBA, Overview of technical checks, validation rules and business checks to be applied by the EBA for RoI reporting (updated 28 April 2025), xlsx (read 2026-10-31)
- ESAs/EBA, Observations from reporting of RoI to the ESAs - key common issues identified (16 Apr 2025, updated 16 May 2025), slides (read 2026-10-31)
- CSSF, Guidance for interpretation and resolution of ESA error messages related to the DORA register, v1.0, 15 May 2025 (read 2026-10-31)
- CSSF, Guidance for interpretation and resolution of CSSF error messages related to the submission of the DORA register, v1.0, 10 Feb 2026 (read 2026-10-31)
- Central Bank of Ireland, Guide to Submitting DORA Registers of Information on the Central Bank of Ireland Portal (PDF dated 23 Feb 2026, 93 pp.) (read 2026-10-31)
- AFM, Q&A-sessie DORA-informatieregister (March 2026 session; PDF, Dutch) (read 2026-10-31)