'Admin' on the project's Change Orders tool.
(Note: Typically, the project manager is responsible for sending an approved Commitment Change Order (CCO) to the ERP Integrations tool for acceptance by an accounting approver. See What is the accounting approver role?).
Minimum CCO Requirements:
Before you can send a CCO in the Change Orders tool to the ERP Integrations tool, the CCO must satisfy these requirements:
ID Number: Must be 12 characters or less.
Date Created: The date the CCO was created in Procore will be exported to Sage 100 Contractor® by default. This field cannot be edited. This corresponds to the 'Commitment Date' in Sage.
Title: Must be 30 characters or less.
Description: This value in this field is exported from Procore into the 'Scope' field in Sage 100 Contractor®. Sage imposes a one thousand (1000) character maximum on this field. Entries that exceed the maximum will be truncated in Sage. The entire description will be stored in Procore.
Schedule of Values (SOV). Must include at least one (1) line item with a Sage 100 Contractor® Cost Code. (Note: You can only add a line item to the commitment's SOV if its linked to an existing cost code and category.)
If desired, you can configure your default settings to use your Procore Change Order Number for an exported commitment's Sage ID field. If enabled, the Sage ID will auto-populate with the Procore Change Order Number. However, the value can still be edited. (Enabling this account-wide configuration setting requires 'Admin' level access on the ERP Integrations tool.)
Sage 100 Contractor® does not permit users to modify a contract line item on a CCO more than once.
If a contract line item on a CCO includes more than one (1) modification, Procore will automatically calculate the sum for all of that line item's modifications. After acceptance by an accounting approver, the amount of the items and send it to Sage as a single (aggregated) value.