image_1.pngCopyright©2024 Yonyou Group All rights reserved.Without the written permission of Yonyou Group, no part of this user manual may be copied, reproduced, translated, or reduced for any purpose. The content of this user manual may change without notice, please stay informed.Please note: The content of this user manual does not represent a commitment made by Yonyou Network.OverviewProduct OverviewContract performance is a key component of the contract management system, used to manage the entire process of contract execution, including business performance, financial performance, and transaction management after the contract is signed.Operation GuideContract Affairs ManagementOverviewContract management is a key component of contract performance, used to manage changes in the status of contracts such as activation, freezing, termination, contract modifications, and abnormal contracts.Contract ChangeProvide an entry for contract change management and maintenance, allowing management of contracts that are not submitted, in change, change not approved, and change completed.Process of Contract Modification:From the [My Contracts] service node, find the original contract to be changed (Contract Status = Effective) and click the button, or directly initiate the change from the [Contract Change] service node. The original contract data will be pushed to the change application form, reducing data entry.Fill out the change application: Contract change type (change transaction type), change method (currently only supports supplementary agreement), contract change category (contract change category for service maintenance change category files).Change the content of the contract modification, such as contract amount, subject matter, etc.Upload the contract text of the supplementary agreement (currently only supplementary agreements are supported for upload).Contract change saved, submitted, approved for change — finalized — electronic signature (or offline signature) — effective, completing the contract change.After the change takes effect, the data will be synchronized to the original contract.Relationship between Contract Change Submodule and Contract StatusNot Submitted: Draft, OpeningIn Change: Under Approval, Approved, In Signing, Signing Completed, ReturnedChange not approved: Approval terminated, scrappedChange completed: EffectiveFor different contract change scenarios, the content that can be changed varies (for example, for changes to the subject matter, only the subject matter information can be modified): create transaction types under the contract change object and create the corresponding UI templates.Contract Change Document, Key Fields and Descriptions (Refer to My Contract for Other Field Descriptions):Column NameColumn DescriptionChange TypeRefers to the contract change transaction type, the transaction type established under the contract change object, controls the contract change UI template (controls the current change, which fields are editable and which fields are not), and the approval process for changes.Change MethodCurrently only supports supplementary agreements.Change CategoryThe reason for the contract change, maintained in the custom file at the [Contract Change Category] entry.According to the query plan, retrieve the list of contract changes that meet the criteria.Contract Change List, split into multiple modules based on contract change status, supports quick filtering.Support for switching between list and card modes.Support sorting by importance, urgency, and confidentiality level.image_2.pngimage_3.pngThere are 2 entry points to initiate a contract change: (1) From the [My Contracts] service node, find the original contract to be changed (Contract Status = Effective), and click the button to start the change; (2) In the [Contract Change] service node, click the button to select the contract to be changed and initiate the change. After initiating the change, the original contract data will be pushed to the change application form, reducing data entry.image_4.pngClick to initiate the change, then open the contract change application page to proceed with the contract change:Fill out the change application: Contract change type (change transaction type), change method (currently only supports supplementary agreement), contract change category (contract change category service maintenance change category file)Change the content of the contract modification, such as contract amount, subject matter, etc.Upload the supplementary agreement change contract text, supporting pdf and word formats. If the contract text is in word format and has editing permissions, it can be edited and revised again.Risk checks can be performed on contract change texts: Check the contract change text for triggered sensitive words based on the sensitive word library settings.Submit the contract documents to the approval process.image_5.pngNote:1. Only contracts that are in effect and are original contracts not undergoing changes can initiate a modification;1.After initiating a change, which data can be pushed to the contract change application form, based on the configuration of document conversion rules, can be modified by the project according to the scenario;image_6.png2.Contract Change Type: This is a transaction type created under the contract change business object in the transaction type service node. This transaction type controls the contract change UI template (which fields are editable and which fields are not editable for the current change) and the approval process for the change.3.Contract Change Categories (Change Category Files for Service Maintenance of Contract Changes)After the contract change is submitted, it follows the relevant approval process configured under the contract change business object (or transaction type). Different contract types can have different initiation conditions for the change approval process.image_7.pngAfter the contract change approval is completed, the contract text can be finalized, and the signing contract can be generated.: Set the contract number for the supplementary agreement according to the contract coding rules, convert the contract change text to PDF, and apply the contract watermark specified in the watermark scheme to the PDF. How to generate the contract number in the contract text, refer to the relevant introduction in [My Contracts].image_8.pngThe numbering generation rule for supplementary agreements: Original contract number + coding rule configuration + auto-increment code. For example: The original contract number is A001. After the first supplementary agreement change takes effect, the supplementary agreement number will be A001S1. In the coding rule configuration, only S needs to be configured. The A001 and the auto-increment code after S are the system's default logic.image_9.pngFor scenarios where the signing method is electronic signature, after generating the contract for signing, you can initiate the signing and sign the electronic contract. The signing process is configured according to the signing process of the selected original contract. You need to configure the electronic signing process in Digital Modeling > Electronic Signature Configuration > Organizational Business > Contract Signing Configuration (for detailed information, please refer to the help documentation of the relevant nodes).Electronic signature scenario: After the contract is signed, the date of contract completion will be written back to the contract signing date in the document.For scenarios where the signing method is offline signing, after generating the contract for signing, download and print the contract, then stamp it offline. Subsequently, the offline signed contract needs to be scanned into a PDF format file, and the contract signing date must be filled in. After the information is sent back to the system, subsequent business can proceed. When returning the offline signed contract, it is required to fill in the signing date and provide the scanned copy of the offline signed contract.image_10.pngFor scenarios where the signing method is "not signed," once the contract for submission is generated, it is considered that the contract is completed.image_11.pngAfter the contract is signed, the operation to execute the contract change can be performed, indicating that the contract change is complete. The relevant data will be synchronized to the original contract based on the write-back rules of the document conversion rules.Notes4.Once a contract is initiated for change, it will be locked and cannot be terminated, completed, or frozen until the change is either completed or failed;image_12.png5.The contract change list is controlled by data permissions, currently supporting organization (contracting organization), department (contracting department), and contract type. Configuration is required under the contract change object, as shown in the example below:image_13.png6.The current service buttons are controlled by button permissions: Example - Button permission authorization: From the "Role Management" service node, find the corresponding role to edit, and select the corresponding service and button.Abnormal ContractsFunction DescriptionFor contract administrators, view contracts with abnormal termination (i.e., contracts with a status of terminated).Operation Instructionsimage_14.pngThis node provides an entry to view contracts that have been terminated (i.e., contracts with a status of terminated), offering only query and view functionalities.Notesimage_15.png7.The list of abnormal contracts is controlled by data permissions, currently supporting organization (contracting organization), department (contracting department), and contract type. Configuration needs to be done under the contract information object, as shown below:image_16.png8.The current service buttons are controlled by button permissions: Example - Button permission authorization: From the "Role Management" service node, find the corresponding role to edit, and select the corresponding service and button.
