Skip to main content
Procore Support (en-au)

Which cost code formats are supported by my ERP Integration?

  1. Last updated
  2. Save as PDF

Which cost code formats are supported by my ERP Integration?

Select Your Supported ERP:

Answer

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.

See Also

 

Answer

You must use standard

UndefinedNameError: reference to undefined name 'integrations_sageintacct' (click for details)
Callstack:
    at (faq/which-cost-code-formats-are-supported-by-procore-sage-intacct), /content/body/div/div/p[1]/span[1], line 1, column 1
    at wiki.page()
    at (faq/which-cost-code-formats-are-supported-by-erp), /content/body/div/div[3]/div/pre, line 2, column 10
 cost codes in order to sync them with the Procore + 
UndefinedNameError: reference to undefined name 'integrations_sageintacct' (click for details)
Callstack:
    at (faq/which-cost-code-formats-are-supported-by-procore-sage-intacct), /content/body/div/div/p[1]/span[2], line 1, column 1
    at wiki.page()
    at (faq/which-cost-code-formats-are-supported-by-erp), /content/body/div/div[3]/div/pre, line 2, column 10
 connector. Procore supports all cost code section rules from
UndefinedNameError: reference to undefined name 'integrations_sageintacct' (click for details)
Callstack:
    at (faq/which-cost-code-formats-are-supported-by-procore-sage-intacct), /content/body/div/div/p[1]/span[3], line 1, column 1
    at wiki.page()
    at (faq/which-cost-code-formats-are-supported-by-erp), /content/body/div/div[3]/div/pre, line 2, column 10
. For example, if you changed the format of your
UndefinedNameError: reference to undefined name 'integrations_sageintacct' (click for details)
Callstack:
    at (faq/which-cost-code-formats-are-supported-by-procore-sage-intacct), /content/body/div/div/p[1]/span[4], line 1, column 1
    at wiki.page()
    at (faq/which-cost-code-formats-are-supported-by-erp), /content/body/div/div[3]/div/pre, line 2, column 10
 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

UndefinedNameError: reference to undefined name 'integrations_sageintacct' (click for details)
Callstack:
    at (faq/which-cost-code-formats-are-supported-by-procore-sage-intacct), /content/body/div/div/p[2]/span[1], line 1, column 1
    at wiki.page()
    at (faq/which-cost-code-formats-are-supported-by-erp), /content/body/div/div[3]/div/pre, line 2, column 10
 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
UndefinedNameError: reference to undefined name 'integrations_sageintacct' (click for details)
Callstack:
    at (faq/which-cost-code-formats-are-supported-by-procore-sage-intacct), /content/body/div/div/p[2]/span[2], line 1, column 1
    at wiki.page()
    at (faq/which-cost-code-formats-are-supported-by-erp), /content/body/div/div[3]/div/pre, line 2, column 10
 and sync then into Procore. Currently, you cannot create project-specific or special cost codes in Procore and export them to
UndefinedNameError: reference to undefined name 'integrations_sageintacct' (click for details)
Callstack:
    at (faq/which-cost-code-formats-are-supported-by-procore-sage-intacct), /content/body/div/div/p[2]/span[3], line 1, column 1
    at wiki.page()
    at (faq/which-cost-code-formats-are-supported-by-erp), /content/body/div/div[3]/div/pre, line 2, column 10
. Since cost codes are always being synced from
UndefinedNameError: reference to undefined name 'integrations_sageintacct' (click for details)
Callstack:
    at (faq/which-cost-code-formats-are-supported-by-procore-sage-intacct), /content/body/div/div/p[2]/span[4], line 1, column 1
    at wiki.page()
    at (faq/which-cost-code-formats-are-supported-by-erp), /content/body/div/div[3]/div/pre, line 2, column 10
 to Procore, you can add new cost codes throughout the project, as needed.

See Also