This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
terminating_a_contract [2025/04/22 17:46] – tina.robles | terminating_a_contract [2025/04/22 18:25] (current) – tina.robles | ||
---|---|---|---|
Line 26: | Line 26: | ||
{{: | {{: | ||
- | A date is required for each of the terminate actions, but a user can choose to terminate Accruals only or Claims only. Sweep should only be used in combination with one of the other dates. | + | **Contract Termination Options |
- | * **Accruals Date**: | + | This outlines |
- | * **Claims Date**: No more claims are processed after this date. The contract state will update to Terminated on the date entered for Claims. | + | General Termination Guidelines: |
- | * **Sweep | + | * A specific date is required for each termination action. |
+ | | ||
+ | | ||
+ | | ||
+ | |||
+ | Termination Actions: | ||
+ | |||
+ | ______Accruals Termination__ | ||
+ | | ||
+ | * 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 | ||
+ | |||
+ | ______Claims Termination__ | ||
+ | * Effect: Claim processing ceases after the specified date. | ||
+ | * System Action: Updates | ||
+ | |||
+ | ______Sweep Action__ | ||
+ | * Effect: Zeroes out the balance | ||
+ | * System Actions: a. Transfers the current balance to a " | ||
+ | * Note: This action | ||
+ | |||
+ | **Best Practices**: | ||
+ | * When implementing the Sweep option, it is recommended to terminate both Accruals and Claims concurrently. | ||
+ | * Carefully consider the implications of each termination action on contract management and financial reporting. | ||
+ | |||
+ | 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 the implications of each action, users can effectively manage contract terminations while maintaining accurate financial records. | ||
+ | |||
{{: | {{: | ||
- | **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 | + | |
- | * When you add a termination | + | __Date Requirements__ |
- | * If you ALSO add today’s date as the termination date for claims at the same time you terminate for Accruals, then instead, | + | |
- | * Lumpsums on a contract | + | * The "Date" |
- | * Sweep date will not impact either of the above. | + | * All entered |
+ | |||
+ | __Contract Status Updates__ | ||
+ | |||
+ | * Only the Claims termination | ||
+ | * Accruals | ||
+ | |||
+ | __Accruals Termination__ | ||
+ | |||
+ | * Upon submission | ||
+ | |||
+ | __Simultaneous Accruals and Claims Termination__ | ||
+ | |||
+ | * When both Accruals | ||
+ | |||
+ | __Impact on Lump Sum Payments__ | ||
+ | |||
+ | * For contracts | ||
+ | |||
+ | __Sweep Date Considerations__ | ||
+ | |||
+ | * The Sweep date does not affect | ||
+ | |||
+ | 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: | ||
{{: | {{: | ||
Line 60: | Line 152: | ||
----- | ----- | ||
- | The Terminated Date display | + | The Terminated Date displays |
{{: | {{: |