This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| terminating_a_contract [2022/01/03 14:10] – lisa.maloney | terminating_a_contract [2025/04/22 18:25] (current) – tina.robles | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| **__Terminating a Contract__** | **__Terminating a Contract__** | ||
| - | To terminate a contract, open the contract and select Terminate from the Actions section on the top right of the screen. | + | **Contract |
| - | {{:pasted:20160210-212247.png}} | + | Ability to terminate a contract within our system and specify the necessary user permissions |
| + | |||
| + | Procedure: | ||
| + | |||
| + | - Access the contract: Open the specific contract in the system. | ||
| + | - Locate the Actions menu: Navigate to the top right of the screen to find the Actions section. | ||
| + | - Initiate termination: | ||
| + | |||
| + | User Permissions: | ||
| + | |||
| + | * Hold Finalizer status | ||
| + | * Have Contract Approval rights assigned to their role | ||
| + | |||
| + | Note: Ensure that only authorized personnel with the appropriate permissions can perform contract terminations to maintain system integrity and comply with organizational policies. | ||
| + | |||
| + | |||
| + | |||
| + | {{:pasted:20240806-170448.png}} | ||
| ----- | ----- | ||
| After clicking Terminate, a Terminate popup will appear with 3 Terminate options and date associated with each: | After clicking Terminate, a Terminate popup will appear with 3 Terminate options and date associated with each: | ||
| - | {{:pasted:20220103-134942.png}} | + | {{:pasted:20240806-170524.png}} |
| - | A date is required for each of the terminate actions, but a user can choose to terminate Accruals only, Claims only, Sweep only, or a combination of any of the three dates. | + | **Contract Termination Options |
| - | * **Accruals | + | This outlines the various termination actions available within the contract management system, their implications, |
| - | * **Claims Date**: No more claims are processed | + | |
| - | * **Sweep Date**: After this date, the balance of the accrued | + | General Termination Guidelines: |
| + | |||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | |||
| + | Termination Actions: | ||
| + | |||
| + | ______Accruals Termination__ | ||
| + | * Effect: | ||
| + | * System Actions: a. Automatically updates the contract end date to match the entered date. b. Adjusts the end date of any lump sum payments to align with the entered date. | ||
| + | * Note: The contract state remains | ||
| + | |||
| + | ______Claims Termination__ | ||
| + | * Effect: Claim processing ceases | ||
| + | * System Action: Updates the contract state to "Terminated" | ||
| + | |||
| + | ______Sweep Action__ | ||
| + | * Effect: Zeroes out the balance of accrued | ||
| + | * System Actions: a. Transfers the current balance to a "swept amount" category. b. Reflects | ||
| + | * Note: This action does not alter the contract status. | ||
| + | |||
| + | **Best Practices**: | ||
| + | * When implementing the Sweep option, it is recommended to terminate both Accruals and Claims concurrently. | ||
| + | * Carefully consider | ||
| + | |||
| + | Example: In a scenario where a contract has a $4,000 balance, executing a Sweep action would result in: | ||
| + | * The $4,000 balance being reduced to $0. | ||
| + | * The $4,000 being recorded as the "swept amount" | ||
| + | |||
| + | By adhering to these guidelines and understanding | ||
| + | |||
| {{: | {{: | ||
| - | **Important Notes**: | + | **Contract Termination: |
| - | * The Date field is required on each of the actions. | + | |
| - | * The Date entered must be today' | + | This outlines key aspects of the contract termination process, including date requirements, |
| - | * Only the claim terminate | + | |
| + | __Date Requirements__ | ||
| + | |||
| + | * The "Date" | ||
| + | * All entered | ||
| + | |||
| + | __Contract Status Updates__ | ||
| + | |||
| + | * Only the Claims termination | ||
| + | * Accruals termination may result in an " | ||
| + | |||
| + | __Accruals Termination__ | ||
| + | |||
| + | * Upon submission of an Accruals termination date via the user interface: a. The contract header' | ||
| + | |||
| + | __Simultaneous Accruals and Claims Termination__ | ||
| + | |||
| + | * When both Accruals and Claims are terminated with the current date: a. The contract status changes to " | ||
| + | |||
| + | __Impact on Lump Sum Payments__ | ||
| + | |||
| + | * For contracts terminated for Accruals: Lump sum payments that begin before the termination date and end after it will have their event end date adjusted to match the termination date. | ||
| + | |||
| + | __Sweep Date Considerations__ | ||
| + | |||
| + | * The Sweep date does not affect the contract status or end date modifications described above. | ||
| + | |||
| + | By understanding these system behaviors and considerations, | ||
| + | Copy | ||
| ----- | ----- | ||
| - | If there is an active | + | **Contract Termination: |
| + | |||
| + | This outlines important considerations regarding | ||
| + | |||
| + | __Termination Prerequisites__ | ||
| + | |||
| + | * Active Contract with Existing Draft: a. An active contract | ||
| + | * Best Practice: Regularly review and manage draft contracts to ensure they do not impede necessary terminations of active contracts. | ||
| + | |||
| + | __Post-Termination Implications__ | ||
| + | |||
| + | * Claim Processing: a. Once a contract' | ||
| + | * Best Practice: Prior to terminating a contract, ensure all valid claims have been processed and consider notifying relevant stakeholders of the impending termination. | ||
| + | |||
| + | __System Safeguards__ | ||
| + | |||
| + | * The system' | ||
| - | Once a contract status is Terminated, no new claims can be created against that contract. | ||
| ----- | ----- | ||
| **__Un-Terminating a Contract__** | **__Un-Terminating a Contract__** | ||
| - | A Contract | + | **Contract Un-Termination Process** |
| + | |||
| + | This document outlines the procedure and implications of reversing | ||
| + | |||
| + | __Authorization Requirements__ | ||
| + | |||
| + | * Only users with appropriate system | ||
| + | * Access to this functionality is restricted to ensure proper contract management oversight. | ||
| + | |||
| + | __Un-Termination Procedure__ | ||
| + | |||
| + | * Initiation: Select | ||
| + | * System Response: The contract will automatically revert | ||
| + | |||
| + | __Impact on Contract Components__ | ||
| + | |||
| + | * For accruals, Upon un-termination, accrual calculations | ||
| + | |||
| + | * For claims, claims processing capability is restored if previously terminated. System allows new claim submissions according to contract parameters. | ||
| + | |||
| + | * For swept balances, | ||
| + | |||
| + | * System Behavior- The contract management system automatically: | ||
| - | {{:pasted:20220103-135906.png}} | + | {{:pasted:20240806-170728.png}} |
| If a contract is terminated, it can't be un-terminated if there is another contract out there with overlapping timeframe. | If a contract is terminated, it can't be un-terminated if there is another contract out there with overlapping timeframe. | ||
| ----- | ----- | ||
| - | The Terminated Date display | + | The Terminated Date displays |
| - | {{:pasted:20220103-140045.png}} | + | {{:pasted:20240806-170811.png}} |