Things to Know

Background

Each of Procore's available ERP connectors perform the basic function of syncing data between the ERP system and Procore, usually in the same way as other connectors. However, each connector has a unique set of items it can sync, and the way those items are synced will vary based on how that ERP system and its corresponding integration are built to function.

CMiC, like all ERP integrations, has some key considerations, limitations, and things to know about how each Procore object is synced. Those considerations, limitations, and things to know are outlined in the table below according to tool or item being synced.

Things to know about the {{integrations_cmic}} Connector

Procore Item or Setting

Considerations, Limitations, and Requirements

configuration settings & sync schedule

  • This integration is not automatically synced (except for Job Costs). Everything can be synced on-demand (manually) using the "Refresh" button in the Integration.

  • Settings active for CMiC Integration: Default Project Template, Cost-Type for Converting bids, Accounting Approver Report (Other settings in Configurations do not apply).

  • Exports happen instantly upon approval by your organization’s Accounting User(s). Imports happen upon requests which can be made by your Project and Accounting Teams directly within Procore.
    Note: Within Procore, any exports to CMiC must be approved by your company's designated accounting approver(s).

COMPANY LEVEL work breakdown structure (wbs)

  • WBS/Cost Codes will be configured in CMiC and imported into Procore. Division codes (control codes) can be used on transactions (but this can be turned off on request).

  • Supported Cost Code Delimiters:

    • If your company has enabled the ERP Integrations tool for CMiC, Procore permits the following cost code delimiters from CMiC: hyphen/dash (-).

PROJECT LEVEL work breakdown structure (wbs)

  • Any project level cost codes that are not synced will automatically sync with your ERP when exporting your budget.

companies

  • Import Companies to Procore:

    • You can filter companies that are ready for import by company type using the Type filter under the Companies tab on the ERP Integrations page.
      Note: You can filter companies by type, even those without a company type, to be synced to Procore.

  • Additional Information:

    • Standard Cost Code/Type List* Each company in CMiC can maintain its own master cost code list; however, Procore uses a single list of cost codes for all companies.* You must be able to identify the specific company to which each cost code belongs within CMiC.* To prevent project sync issues, ensure that all master cost code lists for companies in CMiC have the same number of divisions or tiers.

    • If a cost code from another company is added to a Procore project, you will be unable to sync the project with CMiC. To resolve this issue, you must remove that cost code from the Procore project.

    • To minimize the risk of adding cost codes from the wrong company to a project, use project templates. For any additional queries, reach out to your Procore point of contact.

  • Recommendations:

    • Always use the steps below to make sure the vendor records created in CMiC are linked to the appropriate company match in Procore.

    • If you have a vendor record in CMiC that you will not be using in Procore, you must archive it.

  • Limitations:

    • After a vendor record from CMiC is linked to a company record in Procore, any 'Address' changes are not synced between the two systems. This is because the 'Address' in CMiC pertains to the vendor's billing address, which may be different from the mailing address that your project management team needs to use for job related correspondence

projects

Syncing:

  • Projects that are in-progress or created before connection of the integration cannot be synced. Professional Services for assistance with integrating in-progress/pre-existing project records are available for an additional fee.

  • Sync Cost Codes & Cost Types with Procore Projects

    • When importing a job from CMiC into Procore, all project cost codes from CMiC will automatically sync with the job in Procore.

    • When exporting a job from Procore to CMiC, all project cost codes from Procore will automatically sync with the job in CMiC.

    • If the Procore project has already been synced and a new cost code is added to the project, click Resend to ERP to ensure that the new project cost code is synced with CMiC.

    • Any project cost codes that are not synced will automatically sync with Procore when exporting your budget to Procore.

Multicompany:

  • If multicompany is enabled, a specific company ID will be assigned to multicompany projects in the following cases:

    • Import jobs to Procore: Procore will store the company ID from CMiC.

    • Export jobs to CMiC : You can specify the relevant company ID.

  • After a project has been synced as a multicompany project, all downstream transactions (contracts, invoices, and more) will sync with the specific company.

Recommendations:

  • When creating a project, only include the necessary project-level cost codes, rather than adding all of them automatically. Adding a large number of cost codes or cost type assignments can lead to extended sync durations.

  • When adding project-level cost codes, make sure to assign a cost type.

    • The cost type typically defaults from the company-level ERP tool. However, if there are no cost type assignments at the company level, you must manually assign the cost type within the project's Admin tool.

Additional Information:

  • When multicompany is enabled, ensure that the master cost code list has the same number of divisions or tiers across all companies in CMiC to prevent project sync issues. If discrepancies exist in the number of divisions or tiers, follow these steps with your Procore point of contact to successfully resend projects to ERP:

    1. Use the JC Structure tool located in Job Costing > Utilities > Recalculations > Correct JC Structure to update your cost codes in CMiC. This will ensure that all companies have the same tier levels of cost codes.

    2. Once you update the hierarchy of cost codes in CMiC, you can delete any invalid cost codes in the standard cost code list in Procore.

SUB JOBS

  • You cannot delete a Sub Job if there are cost codes tied to that Sub Job.

BUDGET

  • Syncing:

    • You can export budgets containing original line items with $0 values from Procore to CMiC.

  • Prerequisites for Export from Procore:

    • You must assign a cost type to each project cost code to export your budget, regardless of whether the cost code is included in the budget.

  • Restrictions:

    • After exporting a budget from Procore to CMiC, the import function (i.e., from CMiC to Procore) will no longer be available for that job/budget.

    • The ability to unlock the Procore budget, resend data to CMiC, add budget line items, and create budget modifications will be disabled until:* The export from Procore to CMiC is complete and the exported entries have been manually posted to CMiC using its Job Cost function. See your CMiC Help system for instructions.

  • Limitations:

    • After using the Project Financials + CMiC Connector to export a budget from Procore to CMiC, the import function to Procore will no longer be available for that job/budget.

    • The following functions are disabled in Procore until all synced data is visible in CMiC as the Budgeted Cost Amount.* The ability to unlock a Procore budget.* The ability to resend data from Procore to CMiC.* The ability to create a budget line item.* The ability to create a budget modification.

BUDGET CHANGES & ESTIMATED COST AT COMPLETION

  • Each budget change line will be sent to CMiC as a PCI

  • Forecasting/Estimated Cost at completion is sent to CMiC as "Projected Cost/Final" amounts on the budget.

COMMITMENTS

  • Prerequisites:

    • The Commitments tool must be an active tab on the project.

  • Limitations:

    • To sync a commitment, all a Schedule of Values (SOV) line items must be tied to a cost codes and categories from your ERP-synced lists of Standard Cost Codes and Cost Types.

    • Commitments synced to CMiC will NOT contain details regarding tax codes.

    • All Commitments Exported to CMiC must be Posted.

COMMITMENT CHANGE ORDERS (CCO)

  • To add a Schedule of Values (SOV) line item to a CCO, it must be tied to an existing cost code and category.

  • If a line item on a CCO creates a new line item on the original contract, that new line item will not be reflected on the CMiC contract. However, the CCO's line item will still be sent to CMiC.

  • All CCO's Exported to CMiC must be Posted

subcontractor invoices

  • Minimum Invoice Requirements:

    • Before you can send an invoice from the Commitments tool to the ERP Integrations tool, the invoice must be in the Approved, Approved as Noted, or Pending Owner Approval status.

  • Additional Information:

    • Billing Date. This date in Procore is transferred to CMiC as the Date on a bill.

    • Invoices with a total amount of zero dollars cannot be sent to CMiC. These invoices will not be synced when exported.

    • Retainage Release invoices can be created and exported to CMiC with the integration.

PRIME CONTRACTs

  • Prime Contracts can be imported or created manually. Values will be imported from the Revenue budget, and to use the PCCO feature there must also be a contract in CMiC.

  • If you choose to update the Prime Contract in CMiC, you will need to manually sync and re-import your changes to Procore.

  • Within your ERP Integration settings, ERP Admins can enable the ability to designate your prime contract as either Unit-based or Amount-based before importing to Procore.

  • You will not be able to re-import a Prime Contract when:

    • The Prime Contract is in an unapproved state.

    • The Prime Contract does not belong to a synced job.

    • The Prime Contract has inadvertently been added to two projects in your company's Procore account.

PRIME CONTRACT CHANGE ORDERS (PCCO)

  • Requirements:

    • There must be a Contract set up for the Project/Job in CMiC.

    • The Date field on a PCCO is required.

    • The PCCO must be in the 'Approved' status.

    • For each associated line item that you add to the change order's Schedule of Values (SOV), you may designate a unique associated Prime Contract line item or the same associated Prime Contract line item for all change order line items.

    • Horizontal and vertical markups are allowed.

  • Syncing:

    • PCCOs are sent to CMiC as a PCI (your Integration Implementation point of contact can set the PCI type).

    • PCIs will be sent as un-posted and can either be posted or added to an OCO.

JOB-TO-DATE COSTS

  • Syncing:

    • Job costs are synced automatically on a custom schedule (default setting is every 4 hours).

    • Job Cost transaction details and PDFs are not currently included in Job cost imports. We recommend sharing additional reports with anyone that does not have access to CMiC.

  • CMiC Reference Code in Direct Cost Descriptions:

    • You can choose whether to include a reference code in the descriptions of line items for direct cost types, such as expenses, payroll, invoices, and subcontractor invoices. For example, if this feature is enabled, a job cost transaction imported from CMiC with a source description of "Carpet" and a reference code of "123" would appear in the Direct Costs tool with the direct cost description as “Carpet - 123".

FORECASTING/PROJECTIONS

  • Forecasting will write the Estimated Cost at Completion amount to Projected Cost/Projected Final in CMiC.

Custom Settings Available on Request

  • Custom Subcontract & Purchase Order Type

  • Currency Code Type

  • CM (PCI) type for PCCOs

  • CM (PCI) Type for Budget Changes

  • Enable/Disable Revenue-only PCCOs

  • Enable/Disable Selectable divisions/control codes

  • Enable/Disable Prime Contract Imports

  • Enable/disable vendor exports

  • enable/disable commitment exports

  • Custom Job Cost Sync Schedule

  • Custom Budget Line Item Sync Schedule