--- title: My function identifier is invalid description: 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. --- [Skip to content](https://support.copla.com/my-function-identifier-is-invalid#main-content) English Show submenu for translations [![main-black-pinkglasses](https://support.copla.com/hubfs/main-black-pinkglasses.svg)](https://support.copla.com/?hsLang=en) Open main navigation Close main navigation - English Show submenu for translations - [Contact us](mailto:support@copla.com) [Contact us](mailto:support@copla.com) How can we help you? - There are no suggestions because the search field is empty. 1. [Copla Help Center](https://support.copla.com/?hsLang=en) 2. [Copla Registry](https://support.copla.com/copla-registry?hsLang=en) 3. [Troubleshooting](https://support.copla.com/copla-registry?hsLang=en#troubleshooting) # 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 - [Function and function identifier issues](https://support.copla.com/function-and-function-identifier-issues?hsLang=en) - [Core Guardian](https://support.copla.com/core-guardian?hsLang=en#main-content) - [General Instructions](https://support.copla.com/core-guardian?hsLang=en#general-instructions) - [Additional Information](https://support.copla.com/core-guardian?hsLang=en#additional-information) - [Demo Platform](https://support.copla.com/core-guardian?hsLang=en#demo-platform) - [Integration Setups](https://support.copla.com/core-guardian?hsLang=en#integration-setups) - [Copla Registry](https://support.copla.com/copla-registry?hsLang=en#main-content) - [Getting started](https://support.copla.com/copla-registry?hsLang=en#getting-started) - [Completing the Register](https://support.copla.com/copla-registry?hsLang=en#completing-the-register) - [Troubleshooting](https://support.copla.com/copla-registry?hsLang=en#troubleshooting) - [FAQ](https://support.copla.com/copla-registry?hsLang=en#faq) - [VendrIQ](https://support.copla.com/vendriq?hsLang=en#main-content) - [Trial](https://support.copla.com/vendriq?hsLang=en#trial) - [Overview](https://support.copla.com/vendriq?hsLang=en#overview) [![main-black-pinkglasses](https://support.copla.com/hubfs/main-black-pinkglasses.svg "main-black-pinkglasses")](http://copla.com) [support@copla.com](mailto:support@copla.com) [mailto:support@copla.com](mailto:support@copla.com) Copyright © 2026, Copla