Error code 807: reference to a key that doesn't exist

What the code means

A value in your register refers to a key that doesn't exist in the table it points to. The reported data must follow the key-foreign key constraints defined in the EBA's data model (EBA (opens in a new tab)).

According to the AFM, this is the most common reason for rejection. It includes references within the same table (AFM Q&A (opens in a new tab)).

Typical cause

An identification code is spelt differently in one table from the table it comes from, or is missing there altogether. The data model marks the referring fields; for most of them it doesn't name the target table outright (EBA Data Model (opens in a new tab)). The targets below follow from the field labels; apart from the B_02.02 reference number and B_02.01 field 0030, they are inferences.

Value in	Must appear in
Contractual arrangement reference number in B_02.02, B_02.03, B_03.01, B_03.02, B_03.03, B_04.01, B_05.02 and B_07.01 (field 0010)	B_02.01, field 0010
Overarching arrangement, B_02.01 field 0030	B_02.01, field 0010 (same table)
ICT third-party service provider code in B_02.02 (0030), B_03.02 (0020), B_05.02 (0030) and B_07.01 (0020)	B_05.01, field 0010
Entity LEI in B_02.02 (0020), B_03.01 (0020), B_04.01 (0020) and B_06.01 (0040)	B_01.02, field 0010
Function identifier, B_02.02 field 0050	B_06.01, field 0010
Ultimate parent undertaking, B_05.01 field 0110	B_05.01, field 0010 (same table)
Recipient of subcontracted ICT services, B_05.02 field 0060	B_05.01 or B_01.02, field 0010

Common situations:

• A contract or provider appears in a detail table but not in B_02.01 or B_05.01.
• A reference number was retyped with an extra space, a different dash or different capitals.
• An entity in B_02.02 or B_06.01 is missing from B_01.02. For individual reporting, B_01.02 holds at least the reporting entity itself (EBA FAQ, question 101 (opens in a new tab)).

How to fix it

Use exactly the same key value in every reference as in the source table (AFM Q&A (opens in a new tab)). In the Excel workbook:

1. Find the table, row, column and offending value in the message.
2. Look for the same value in the source table from the table above.
3. If the row is missing there, add it. If it is there with a different spelling, copy the value from the source table instead of retyping it.
4. If there is no overarching arrangement (B_02.01, field 0030), type "Not Applicable" (EBA FAQ, question 124 (opens in a new tab)).
5. If the provider is not part of a group, repeat the provider's own identification code in B_05.01 field 0110 (EBA FAQ, question 99 (opens in a new tab)).
6. Build the package again, with a new timestamp.

Does DORA Convert catch it before you file?

Largely. We check every reference in the table above, row by row, and name the value that isn't found and where it should have been. We also check the composite references from the EBA's official taxonomy.

The distinction:

Kind of reference	Result with us
Target explicit in the official sources, or a composite reference from the taxonomy	Error; the package is built only once it's fixed
Recipient in B_05.02 (0060), checked against both B_05.01 and B_01.02	Error; the package is built only once it's fixed
Target inferred from the field labels	Warning; the package can still be built

A reference warning is still a rejection: the AFM rejects the package with code 807. The warning says so; fix it before you file. We report leading or trailing spaces in a value separately, as a warning.

Related codes

• 805: a key column is empty.
• Code 806 (duplicate key values in one table): DPM checks.
• LEI checks against GLEIF, such as VR_23 for B_01.02 field 0060: LEI and EUID checks.