--- title: Contracts: General Information description: Enter the core identification, risk, and financial details for each contractual arrangement — including the provider, reference, arrangement type, service classification, subcontracting permissions, and cost. --- [Skip to content](https://support.copla.com/contracts-general-information#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. [Completing the Register](https://support.copla.com/copla-registry?hsLang=en#completing-the-register) # Contracts: General Information ## Enter the core identification, risk, and financial details for each contractual arrangement — including the provider, reference, arrangement type, service classification, subcontracting permissions, and cost. #### Fields covered on this page: - [Register type](https://support.copla.com/contracts-general-information#Register-type) - [Provider](https://support.copla.com/contracts-general-information#Provider) - [Contract reference ID](https://support.copla.com/contracts-general-information#Contract-reference-ID) - [Is the contract signed?](https://support.copla.com/contracts-general-information#Is-the-contract-signed) - [Is service user different from reporting company?](https://support.copla.com/contracts-general-information#Is-service-user-different-from-reporting-company) - [Signing entity LEI](https://support.copla.com/contracts-general-information#Signing-entity-LEI) - [Is service user a branch?](https://support.copla.com/contracts-general-information#Is-service-user-a-branch) - [Branch name](https://support.copla.com/contracts-general-information#Branch-name) - [Contractual arrangement type](https://support.copla.com/contracts-general-information#Contractual-arrangement-type) - [Main contract reference ID](https://support.copla.com/contracts-general-information#Main-contract-reference-ID) - [Type of services](https://support.copla.com/contracts-general-information#Type-of-services) - [Cloud service model](https://support.copla.com/contracts-general-information#Cloud-service-model) - [Provider replaceability difficulty](https://support.copla.com/contracts-general-information#Provider-replaceability-difficulty) - [Is outsourcing of service parts allowed?](https://support.copla.com/contracts-general-information#Is-outsourcing-of-service-parts-allowed) - [Subcontractor names used for outsourced parts of this agreement](https://support.copla.com/contracts-general-information#Subcontractor-names-used-for-outsourced-parts) - [Processed data type](https://support.copla.com/contracts-general-information#Processed-data-type) - [Last risk assessment date](https://support.copla.com/contracts-general-information#Last-risk-assessment-date) - [Risk assessment summary](https://support.copla.com/contracts-general-information#Risk-assessment-summary) - [Financial reporting currency](https://support.copla.com/contracts-general-information#Financial-reporting-currency) - [Annual Contract expense amount](https://support.copla.com/contracts-general-information#Annual-Contract-expense-amount) --- ### `Register type` The type of register in which this contract record is maintained. #### What to enter **Select the register type that applies to this contract.** This must match the register type selected for the provider linked to this contract. *If you're having issues, see [Register setup, reporting metadata, and form state issues](https://support.copla.com/register-setup-reporting-metadata-and-form-state-issues?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Provider` The ICT third-party service provider responsible for this contractual arrangement. #### What to enter **Select the provider from the existing provider list.** If the provider does not yet exist in the register, save your progress, create the provider record first, then return to this contract. *If you're having issues, see [I cannot create a contract](https://support.copla.com/cannot-create-a-contract?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Contract reference ID` Your internal reference number or name for this contractual arrangement. #### What to enter **Enter the reference number or name your entity uses internally to identify this arrangement.** This value must be unique across the register and used consistently in every part of the register that references this contract. **NOTE:** - SLA numbers subordinated to a contractual arrangement are not valid contract references. - If you have one commercial relationship with multiple order forms, assess whether to report at the master agreement level or at the order form level, and apply that decision consistently. - The contract reference ID is a key value in the register. It cannot be left empty and must remain consistent across all records that reference this arrangement. *If you're having issues, see [My contract reference is being rejected](https://support.copla.com/my-contract-reference-is-being-rejected?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Is the contract signed?` Whether the reporting company has signed this contractual arrangement. #### What to enter **Select** `Yes` **if the contract has been formally signed.** Select `No` if it has not yet been signed. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Is service user different from reporting company?` Whether the entity that uses the ICT service under this contract is different from the entity that signed the contract. #### What to enter **Select** `Yes` **if a different entity within the group uses the service — for example, a subsidiary that receives the service under a contract signed by the parent.** Select `No` if the reporting company both signs the contract and uses the service. *If you're having issues, see [Service user, signing entity, and role confusion](https://support.copla.com/service-user-signing-entity-and-role-confusion?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Signing entity LEI` The LEI of the entity that signed this contractual arrangement. #### What to enter **Enter the 20-character LEI of the signing entity.** If the reporting company signed the contract, enter the reporting company's own LEI. *If you're having issues, see [Service user, signing entity, and role confusion](https://support.copla.com/service-user-signing-entity-and-role-confusion?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Is service user a branch?` Whether the entity using the ICT service under this contract is a branch of the reporting company. #### What to enter **Select** `Yes` **if the service is used by a specific branch.** Select `No` if the service is used by the head office or a non-branch entity. *If you're having issues, see [Service user, signing entity, and role confusion](https://support.copla.com/service-user-signing-entity-and-role-confusion?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Branch name` The specific branch of the reporting company where the relevant activity covered by this contract is managed. #### What to enter **Select the branch from the existing branch list.** This field is active only when the service user is identified as a branch. The branch must already exist as a branch record before it can be selected here. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Contractual arrangement type` The structural type of this contractual arrangement — standalone, overarching, or subsequent. #### What to enter **Select** `Standalone` **if this contract is concluded independently and managed separately from other arrangements with the same provider.** Select `Overarching` if this is a master or framework agreement that governs the terms for related subsequent arrangements. Select `Subsequent` if this contract is linked to and governed by an overarching arrangement. *If you're having issues, see [Contract reference and arrangement issues](https://support.copla.com/contract-reference-and-arrangement-issues?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Main contract reference ID` The reference number of the overarching arrangement that governs this subsequent arrangement. #### What to enter **Enter the contract reference ID of the overarching arrangement.** This must match the reference entered for that overarching arrangement exactly. This field applies only to subsequent arrangements — leave it empty for standalone and overarching arrangements. **NOTE:** - If there is no overarching arrangement, enter `Not Applicable` in this field. Do not leave it empty. *If you're having issues, see [Contract reference and arrangement issues](https://support.copla.com/contract-reference-and-arrangement-issues?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Type of services` The category of ICT service provided under this contractual arrangement. #### What to enter **Select the ICT service type that best describes the primary service delivered under this contract.** If one contract covers multiple service types, create a separate contract record for each category. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Cloud service model` The cloud delivery model used for this ICT service, where applicable. #### What to enter **Select the applicable cloud service model —** `SaaS`**,** `PaaS`**, or** `IaaS`**.** If the service is not a cloud service, select `Not applicable`. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Provider replaceability difficulty` The assessed ease or difficulty of replacing this ICT provider if the contractual arrangement were to end. #### What to enter **Select the option that reflects your entity's assessment.** Available options: `easily substitutable`, `medium complexity`, `highly complex`, or `not substitutable`. *If you're having issues, see [ICT service assessment issues](https://support.copla.com/ict-service-assessment-issues?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Is outsourcing of service parts allowed?` Whether this contractual arrangement permits the provider to subcontract important parts of the ICT service to another provider. #### What to enter **Select** `Yes` **if the contract allows subcontracting of important service parts.** Select `No` if it does not. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Subcontractor names used for outsourced parts of this agreement` The names of subcontractors that the provider uses to carry out important parts of the outsourced service for the reporting company. #### What to enter **Enter the names of any subcontractors.** If there are multiple subcontractors, separate each name with a space. This field captures the names for reference — the detailed supply chain entries are recorded in the `Specific Information` section of this contract. **NOTE:** - Leave this field empty if the provider does not use subcontractors for important parts of the service, or if subcontracting is not permitted under the contract. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Processed data type` The categories of data that the provider processes under this contractual arrangement. #### What to enter **Specify the types of data the provider processes.** For example, personal data, financial data, or operational data. This is a free-text field. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Last risk assessment date` The date on which the most recent risk assessment for this contractual arrangement was performed. #### What to enter **Enter the date in YYYY-MM-DD format.** If no risk assessment has been performed, enter `9999-12-31`. *If you're having issues, see [Criticality, RTO, RPO, and special value issues](https://support.copla.com/criticality-rto-rpo-and-special-value-issues?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Risk assessment summary` A summary of the main findings from the most recent risk assessment for this contractual arrangement. #### What to enter **Enter a plain-text summary of the key findings.** Focus on the outcomes most relevant to the arrangement's risk profile. **NOTE:** - Leave this field empty if no risk assessment has been performed. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Financial reporting currency` The currency used to express the annual cost for this contract. #### What to enter **Select the ISO 4217 alphabetic currency code that matches the currency used in your entity's financial statements.** This must be consistent with the currency used at the provider level and across the register. [Back to top](https://support.copla.com/contracts-general-information#top) --- --- ### `Annual Contract expense amount` The annual expense or estimated cost for this specific contractual arrangement for the past year. #### What to enter **Enter the monetary value in the reporting currency, in units.** This is the cost for this contract only — not the total for all contracts with the same provider. If the exact cost cannot be determined, enter the best available annual estimate. **NOTE:** - For overarching arrangements with subsequent arrangements, apply costs at whichever level they are actually incurred. - Do not duplicate costs across levels. - The sum of all arrangement levels must equal the total cost entered at the provider record level. *If you're having issues, see [Cost and cross-record consistency issues](https://support.copla.com/cost-and-cross-record-consistency-issues?hsLang=en) or [My provider costs and contract costs do not match](https://support.copla.com/my-provider-costs-and-contract-costs-do-not-match?hsLang=en).* [Back to top](https://support.copla.com/contracts-general-information#top) - [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