Select Your Supported ERP:
You must use standard Sage 300 CRE® cost codes in order to sync them with the Procore + Sage 300 CRE® connector. Procore supports all cost code section rules from Sage 300 CRE®. For example, if you changed the format of your Sage 300 CRE® cost codes (e.g. 12-3456-789). However, Procore does not support non-sectioned cost codes (e.g. 1234567) where the first part of the code does not reference a specific division.
Project-specific cost codes can be entered in Sage 300 CRE® and will appear in Procore during the next data sync. For projects using project specific codes in the Original Estimate, you must first set up the jobs in Sage 300 CRE® and sync then into Procore. Currently, you cannot create project-specific or special cost codes in Procore and export them to Sage 300 CRE®. Since cost codes are always being synced from Sage 300 CRE® to Procore, you can add new cost codes throughout the project, as needed.
You must use standard Sage Intacct® cost codes in order to sync them with the Procore + Sage Intacct® connector. Procore supports all cost code section rules from Sage Intacct®. For example, if you changed the format of your Sage Intacct® cost codes (e.g. 12-3456-789). However, Procore does not support non-sectioned cost codes (e.g. 1234567) where the first part of the code does not reference a specific division.
Project-specific cost codes can be entered in Sage Intacct® and will appear in Procore during the next data sync. For projects using project specific codes in the Original Estimate, you must first set up the jobs in Sage Intacct® and sync then into Procore. Currently, you cannot create project-specific or special cost codes in Procore and export them to Sage Intacct®. Since cost codes are always being synced from Sage Intacct® to Procore, you can add new cost codes throughout the project, as needed.