Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

My function identifier is invalid

Explains why a function identifier is invalid, how to check format and uniqueness, and how to fix broken links between B_06.01 functions and B_02.02 contract rows.

What this usually means

This usually means the value in Function Identifier does not follow the required pattern, or the same identifier is being used for the wrong combination of legal entity, licensed activity, and function.

A function identifier is not just a label you can reuse freely. In the register, it is the key for one specific combination of:

  • the financial entity LEI

  • the licensed activity

  • the function name

That same identifier can then be referenced in Contract specific information rows for contracts and ICT services linked to that function.

Why this happens

  1. The identifier does not use the required pattern of F followed by a natural number, such as F1 or F2.

  2. The same identifier is reused for two different combinations of LEI, licensed activity, and function name.

  3. A function was split or renamed, but the old identifier was kept on rows that no longer match it.

  4. Separate Functions rows were created for what is actually the same function combination, causing inconsistent identifiers.

  5. Contract specific information rows still point to an outdated or mismatched function identifier after changes in Functions.

What to check and how to fix it

Check the value in Function Identifier.

If it does not follow the required pattern of a capital F followed by a natural number, replace it with a valid value such as F1, F2, or the next correct number in your sequence.

Check the full function combination in LEI of the financial entity, Licenced activity, and Function name.

If the identifier is attached to more than one different combination, split those records and assign a different function identifier to each valid combination.

Check whether the same combination appears more than once in Functions under different identifiers.

If it does, keep one correct row for that combination and use one identifier consistently instead of maintaining parallel identifiers for the same function.

Check whether the licensed activity is correct. If the same function name exists under different licensed activities, each activity needs its own function identifier.

If the function is not linked to a registered or licensed activity, report it as support functions rather than forcing it into the wrong activity.

Check every Contract specific information row that uses that function.

If a contract row points to an old, invalid, or mismatched function identifier, update it so it matches the correct identifier defined in Functions.

Check whether you created a new function identifier only because the same function appears in more than one contract row or ICT service row.

If the LEI, licensed activity, and function name are still the same, reuse the same function identifier across those linked rows instead of creating another one.

What happens next

Once the function identifier is corrected in Functions and all linked Contract specific information rows use the same valid value, the function should be consistently linked across the register. Use the corrected values in your next save, validation, or export step.

Related issues