Export a CCO to Sage 300 CRE

Objective

To export a Commitment Change Order (CCO) in a Procore project to your integrated ERP system.

This process consists of the tasks, which are typically performed by two different users:

A project manager completes these tasks:
- Create a Commitment Change Order (CCO)
- Send the CCO to an accounting approver for export to your integrated ERP system
An accounting approver (see What is the accounting approver role?) reviews the CCO that was sent to the ERP Integrations tool for acceptance. Then, the accounting approver either accepts or rejects it. The system then does the following:
- Accepted CCOs are exported to the integrated ERP system.
- Rejected CCOs are NOT exported to the integrated ERP system. Instead, they are returned to an editable state in the project's Commitments tool so they can be corrected and re-sent to the ERP Integrations tool acceptance by the accounting approver.

Required User Permissions:
- 'Standard' or 'Admin' level permission on the ERP Integrations tool.
  AND
- The person's account must be granted the 'Can Push to Accounting' privilege in the Company Directory. To request to enable this privilege, submit a request to your Procore point of contact. This must be enabled for you by Procore.
Prerequisites:
- The ERP Integrations tool must be enabled on the company account. The tool must also be configured to work with the Sage 300 CRE. See Sage 300 CRE Connector: Setup Guide.
Limitations:
- To add a Schedule of Values (SOV) line item to a CCO, it must be tied to an existing cost code and category.
- Sage 300 CRE has a limitation where a contract line item cannot be modified more than once on any CCO. Therefore, if you have a CCO that contains more than one modification for the same commitment line item, Procore will automatically sum the amount of the items and send it to Sage 300 CRE as a single (aggregated) value.

There are three steps you need to take to export a CCO from Procore to Sage 300 CRE: