CMiC

¹Custom WBS segments are NOT supported at this time

²Project level cost codes must be added to the project from the Company level ERP Standard Cost Code List. New cost codes must be created in your ERP system, and cannot be created in Procore.

³Exports the ‘Estimated Cost at Completion' and ‘Forecast to Complete' values from a Procore budget to CMiC

⁴Export of payment records from Procore to CMiC is only supported for customers in the United States who license Procore Pay.

⁵Budgets containing line items with $0 values can be exported from Procore to CMiC .

⁶Import companies by type, including those without a specified company type from CMiC to Procore.

⁷PCCO with multiple linked PCOs can be exported as individual PCIs to CMiC. See Export a PCCO with Multiple PCOs as Individual PCIs to CMiC.

¹⁸PCCOs can be exported as OCOs to CMiC. See Export a PCCO as an OCO to CMiC.

Exporting a Procore project to CMiC creates a 'project' in CMiC, but not a 'job'. You must create a job manually in CMiC after exporting your Procore project through the integration.

¹Project level cost codes must be added to the project from the Company level ERP Standard Cost Code List. New cost codes must be created in your ERP system, and cannot be created in Procore.
²Cost codes added to a job in CMiC after the job is synced with Procore can be added to the project in Procore by clicking 'Refresh Cost Codes' in the Project level Admin tool's Work Breakdown Structure (WBS) cost code section. If multicompany is enabled, a specific company ID will be assigned to multicompany projects during the import and export of jobs in Procore.
³If multicompany is enabled, a specific company ID will be assigned to multicompany projects during the import and export of jobs in Procore.
⁴Once a project is synced as a multicompany project, all downstream transactions such as contracts, invoices, and more will automatically sync with the specific company.
⁵Cost codes and cost types are synced with Procore projects when importing jobs to Procore, exporting jobs from Procore, resending projects to CMiC, and exporting budgets to Procore.

When Companies in Procore are exported to CMiC, they will create a Business Partner and Vendor record. Additionally, when companies identified as a Customer in CMiC are imported to Procore, the integration will create a Company record in the Company Directory. Below is a table that displays the field mapping between these records.

¹ Export note: The ERP Vendor ID is entered manually by an accounting approver when a company is exported from Procore to CMiC. This is stored as the ERP Vendor ID (you can view it in the company-level ERP Integrations tool under Vendors or in the company-level Directory tool) and is then used on other vendor related exports (Commitments, Commitment CO’s).² If a Vendor has a masked Vendor Class or masked JcdtSrcCode in Boomi, it will not appear in the Ready to Import filter list.
³ Import note: This is stored as the ERP Vendor ID (you can view it in the company-level ERP Integrations tool under Vendors or in the company-level Directory tool).
⁴ Export note: When Companies in Procore are exported to CMiC they will create a Business Partner and Vendor record. Business partner records must be manually assigned as a Customer in CMiC.
⁵ Include the Employer Identification Number (EIN) of a vendor when importing their record to the Procore directory. Note: Procore currently supports CMiC Registration Codes in US EIN format only.

Original Budget Amounts/Pending Original Budget edits are exported to CMiC as a PCI Type. The PCI will export over with an "Approved" status and will need to be posted in CMiC.

¹To sync previously unused project level cost codes to CMiC, you must add a cost budget line item to the Budget in Procore using that code. Syncing is automatic following addtion of cost budget line items.

¹Amount populates the 'Budgeted Amount' by default, but can be set up to update ''Billing Amounts' as well. This requires assistance from ERP IIS. Contact support if interested in getting this to also populate the 'Billing Amounts' on a Budget Change export to CMiC.

Estimated Cost at Completion exports to CMIC as a PCI Type.

¹ To export Estimated Cost at Completion Total values you must first enable the feature. See How do I export cost forecast data from a Procore budget to ERP?

¹ When a commitment is created in Procore you must select a type, Purchase Order or Subcontract. This is used as the commitment type for CMiC.

² The ERP Vendor ID associated with the Contract Company is used on the import file for CMiC. You cannot export a commitment for a Contract Company that does not have an ERP Vendor ID.

⁴ Subcontracts that are using the Accounting Method of "Unit/Quantity Based" will have these on the Schedule Of Values.

To sync a CCO, the Commitment has to be synced to CMiC first. The CCO will export to the Subcontract/PO and will need to be posted once it successfully exports to CMiC. When entering the SOV for a Commitment Change Order in Procore, you have the option of selecting an existing line item or entering a new line item.

¹ This field is pulled from the Cost Type.

²Typically Quantity, Units and Unit Cost are only used on Purchase Orders.

³The field is titled Contract Amount when working in a Subcontract, and it is titled Subtotal when working in a Purchase Order.

¹The description for an invoice that will be created in CMiC can be entered into the Description field by an accounting approver on the Ready to Export screen in the ERP Integrations tool under Subcontractor Invoices. If no description is entered at the time of export the Description field will be blank on the invoice created in CMiC.

²This is filled automatically based on the Billing Date of the Invoice in Procore, but can be overridden at the time of export on the Ready to Export screen in the ERP Integrations tool under Subcontractor Invoices.

³The subcontractor invoice must exist in Procore to sync payments.

¹ PCCO with multiple linked PCOs is exported as separate PCIs to CMiC when the ‘Create Multiple PCIs’ setting is enabled in Procore. See Export a PCCO with Multiple PCOs as Individual PCIs to CMiC.

² PCCOs are exported as OCOs to CMiC when the ‘Create Owner Change Orders’ setting is enabled in Procore. See Export a PCCO as an OCO to CMiC.

Import from CMiC only. Cost information is retrieved from CMiC for each Cost Code/Type on Synced projects for use in 2 locations in Procore, the Budget and the Job Costs report. Job Cost information can be synced in either the ERP Integrations tool under the Job Costs sub-tab or within the Project Admin tool under Work Breakdown Structure, within Cost Codes there is a "Refresh Cost Codes" button.

¹This is a calculated column that displays the difference between the two database fields in CMiC.

Import from CMiC only. If the feature is enabled, all posted “Actual” cost transaction details from the Job Costing Transaction Record in CMiC are imported into the Direct Cost tool for each project. This provides transaction detail for the costs displayed in Procore, and if the budget view is configured properly, the values of those transactions can be viewed into the Direct Costs or JTD Cost columns for a budget line item.

¹Cross reference table created to map Journal Codes from the Transaction Record to proper Procore Transaction Type. Requires work with ERP IIS to help set up, please reach out to support if interested in getting this set up.

²Client can choose whether “Reference Date” or “Post Date” will be pulled into Procore from CMiC for the “Date” field in the Direct Cost Tool.

³Client can choose whether “Post Date” or “Invoice/Reference Date” will be pulled into Procore from CMiC for the “Received Date” field in the Direct Cost Tool.

⁴You can choose whether to include the “Reference Code” when importing the “Source Description” into Procore for the “Description” field of line items in the Direct Costs tool.