--- title: Contract date, renewal, and termination issues description: "Grouped troubleshooting page for active-register contract date issues: start date, renewal, early termination scope, termination-reason triggers, and buyer/vendor notice-period fields." --- [Skip to content](https://support.copla.com/contract-date-renewal-and-termination-issues#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) # Contract date, renewal, and termination issues ## Grouped troubleshooting page for active-register contract date issues: start date, renewal, early termination scope, termination-reason triggers, and buyer/vendor notice-period fields. #### What this issue group covers These issues usually happen when the contract dates in the record do not match the contract you are trying to report. The most common problems are using the wrong start date, carrying forward the wrong end date after renewal, or making an active contract look ended. This page is for troubleshooting records that still belong in the active register. If the contract has already expired or been terminated, the first check is whether it should still be in scope at all. #### Related - [My contract end date is being flagged](https://support.copla.com/my-contract-end-date-is-being-flagged?hsLang=en) #### Issues covered on this page - [I am not sure which date to enter](https://support.copla.com/contract-date-renewal-and-termination-issues#which-date-to-enter) - [I do not know what end date to enter](https://support.copla.com/contract-date-renewal-and-termination-issues#what-end-date-to-enter) - [I do not know which date to use](https://support.copla.com/contract-date-renewal-and-termination-issues#which-date-to-use) - [The termination reason field became mandatory](https://support.copla.com/contract-date-renewal-and-termination-issues#termination-mandatory) - [The notice period fields became mandatory](https://support.copla.com/contract-date-renewal-and-termination-issues#notice-mandatory) --- ### I am not sure which date to enter #### What this usually means This usually means you are choosing between several dates in the paperwork, but the record needs the contract’s actual start date. For this field, that is the date the contract entered into force. #### What to check and how to fix it **Check the `Contract start date` field.** If you are filling that field, use the date the contract actually became effective. **Check whether you used the signature date, approval date, or execution date instead.** If that date is different from the entry-into-force date, replace it with the date the contract started. **Check whether you used the signature date, approval date, or execution date instead.** If that date is different from the entry-into-force date, replace it with the date the contract started. **Check the format before moving on.** If the date is correct but not in ISO format, enter it as `yyyy-mm-dd`. [Back to top](https://support.copla.com/contract-date-renewal-and-termination-issues#top) --- ### I do not know what end date to enter #### What this usually means This usually means the contract does not simply run to its original fixed end date. Where the contract renews, the end-date field needs to reflect the renewal date that now applies. #### What to check and how to fix it **Check whether the contract renews automatically or has a defined renewal mechanism.** If it does not, use the end date stated in the current contract term. **Check the renewal date now governing the contract.** If the contract has rolled forward under a renewal term, enter that date in `Contract end date`. **Check whether the contract is indefinite rather than renewable.** If it is indefinite, use `9999-12-31`. **Check that you are not keeping an old first-term expiry date after the contract has renewed.** If that earlier date no longer applies, replace it with the renewal date now in force. #### Related issues - [My contract end date is being flagged](https://support.copla.com/my-contract-end-date-is-being-flagged?hsLang=en) [Back to top](https://support.copla.com/contract-date-renewal-and-termination-issues#top) --- ### I do not know which date to use #### What this usually means This usually means the contract did not run to its original planned end date, and you need to separate two cases: a contract that is still active but has a future termination date, and a contract that has already ended and no longer belongs in the active register. #### What to check and how to fix it **Check whether the contract has already ended.** If it has already expired or been terminated, do not treat this as a date-entry fix inside the active register; remove it from the active-register reporting scope. **Check whether notice has been given but the contract is still in force until a future date.** If the contract is still active, enter the actual effective end date that still governs the live contract in `Contract end date`. **Check whether you used the notice date, internal approval date, or decision date instead of the effective end date.** If you did, replace it with the date the contract is actually due to end. **Check whether the contract renewed or moved to an indefinite term instead of ending.** If that is what happened, update `Contract end date` to the renewed end date or use `9999-12-31` for an indefinite contract. #### Related issues - [My contract end date is being flagged](https://support.copla.com/my-contract-end-date-is-being-flagged?hsLang=en) [Back to top](https://support.copla.com/contract-date-renewal-and-termination-issues#top) --- ### The termination reason field became mandatory #### What this usually means This usually means the record is now reading like an ended contract, usually because the date logic points to a past end date. For an active-register workflow, the normal fix is to correct scope or date logic, not to complete termination data for ended contracts. #### What to check and how to fix it **Check whether the contract is still active.** If it has already expired or been terminated, remove it from the active-register reporting scope instead of trying to fix it on this page. **Check the value in `Contract end date`.** If you entered a past date by mistake, replace it with the end date that applies to the live contract. **Check whether the contract has renewed or is indefinite.** If it has renewed, update `Contract end date` to the current renewal date. If it is indefinite, use `9999-12-31`. **Check whether you entered a notice date or internal decision date instead of the actual contract end date.** If so, correct `Contract end date` so the record no longer reads like an ended contract. [Back to top](https://support.copla.com/contract-date-renewal-and-termination-issues#top) --- ### The notice period fields became mandatory #### What this usually means This usually means the ICT service is being treated as supporting a critical or important function. In that case, both business-as-usual notice-period fields are required. #### What to check and how to fix it **Check the linked function record and its criticality or importance assessment.** If the service should not be linked to a critical or important function, correct that assessment or linkage before returning to the notice-period fields. **Check `Notice period for termination of contract (buyer side)`.** If the contract gives the financial entity a business-as-usual termination notice period, enter that value in calendar days. **Check `Notice period for termination of contract (vendor side)`.** If the provider has a different business-as-usual termination notice period, enter that separate value rather than copying the buyer-side value. **Check that both values are entered in calendar days.** If the contract states weeks or months, convert them before saving. **Check that you are using the ordinary business-as-usual notice periods.** If you used a for-cause termination timeline, incident timeline, or offboarding target instead, replace it with the normal contractual notice period. [Back to top](https://support.copla.com/contract-date-renewal-and-termination-issues#top) --- #### What to do next Once the live contract dates and any dependent fields match the active contract record, continue with the entry. If the remaining problem is still a rejected end date, use [My contract end date is being flagged](https://support.copla.com/my-contract-end-date-is-being-flagged?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