Sage Intacct®

¹ 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. Custom WBS Segments are NOT supported.

² Export of payment records from Procore to Sage Intacct® is only supported for customers in the United States who license Procore Pay.

³ Import of payment records from Procore to Sage Intacct® is only supported for customers in the United States.

⁴ Budgets containing line items with $0 values can be exported from Procore to Sage Intacct®.

⁵ Import companies by type, including those without a specified company type from Sage Intacct® to Procore.

⁶ Import direct cost transactions for payroll and expense up to the end of the current month.

When a Project is exported from Procore to Sage Intacct®, an import file is created for the Job Cost module. This import file is then run on the Sage Intacct® server automatically to create the Job record in Sage Intacct®. This import file contains 3 types of records.

¹ Export note: The Sage Job ID is entered manually by an accounting approver when a project is exported from Procore to Sage Intacct®. This may or may not, depending on what the accounting approver has entered, match the Job Number found in Procore under the project-level Admin tool. This is stored as the Sage Job ID (you can view it in the company-level ERP Integrations tool under the Synced section of Jobs) and is then used on other project-related exports such as Budgets, commitments, etc. Import note: If the job is imported from Sage Intacct®, the job ID will automatically populate in the project number field.

² Both Standard and Project-specific cost codes, which can be created in Sage Intacct®, are synced up to the Project Cost Code list in Procore. Project-specific codes are displayed in blue. Custom WBS Segments are NOT supported.

¹ Both Standard and Project-specific cost codes (which can be created in Sage Intacct® manually under Setup in Cost Codes) are synced up to the Project Cost Code list in Procore. Project-specific codes are displayed in blue.

² 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.

¹ Export note: The ERP Vendor ID is entered manually by an accounting approver when a company is exported from Procore to Sage Intacct®. 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, CCOs).

A Budget is exported from Procore to Sage Intacct® as the Workflow type Original.

When a Budget Modification is exported from Procore to Sage Intacct® as the Workflow type Revision.

¹ When a commitment is created in Procore, you must select a type: Purchase Order or Subcontract. This is used as the purchasing transaction for Sage Intacct®.

² The Contract Company must be ERP synced.

³ The Item ID is populated from the Sage Intacct® Cost Type’s default item.

⁴ Default Retainage (Header) populates the Sage Intacct® Retainage Percentage on the line entry.

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 gets 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.

¹ Project Contract Line ID will only display if all Project Contract IDs are the same.

² If the option to create a new line item on the prime contract was selected during the entry of the PCO in Procore, the accounting approver will be prompted to assign the new Contract item ID number at the time of export. The following special characters are not accepted by Sage Intacct®: ~`!@#$%^&*()-+={[}]|:;"'<,>? The following special characters are accepted by Sage Intacct®: _ . /

Import from Sage Intacct® only. Cost information is retrieved from Sage Intacct® for each Cost Code/Type on Synced projects for use in 2 locations in Procore, the Budget and the Job Costs report.

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

Line items on subcontractor invoices are automatically marked as 'Billable' in Sage Intacct® upon export if the invoice is linked to a customer in Sage Intacct®.

¹ The Invoice Number from the Subcontractor Invoice entered in Procore will prefill into the ERP ID field on the Ready to Export screen in the ERP Integrations tool under Subcontractor Invoices; however, the accounting approver can modify this before the Invoice is exported from Procore to Sage Intacct®. The value that was entered in the ERP ID field at the time of export is stored as the Sage Intacct® ID (you can view it in the Synced section in the ERP Integrations tool under Subcontractor Invoices).

² The description for an invoice that will be created in Sage Intacct® 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 Sage Intacct®.

³ 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.

Commitment Payments Issued imported from Sage Intacct® only for synced subcontractor invoices. To sync a payment from Sage Intacct® to Procore, you must record a Document Number for the payment in Sage Intacct®. Payments without a Document Number will not sync. Not available in Canada or APAC at this time.

¹ Payments in Sage Intacct® must be in an 'Approved' status before they can be imported into Procore.