Sage 300 CRE® : Connects Procore to Sage 300 Construction & Real Estate

Procore's Accounting Integrations connect Procore with your ERP or Accounting system, uniting the office and field teams with one source of financial project data.

Popular Tutorials (view all)

Top FAQ (view all)

Quick Links

Sage 300 CRE® course on the Procore Learning Portal
View this integration on Procore's App Marketplace

Sage, the Sage logo, Sage 300 CRE, Sage 300 Construction and Real Estate, and the Sage product are the registered trademarks or trademarks of Sage and/or its affiliates in the United States and/or other countries.

Set Up your Payroll Export for use with Sage

Sync Procore Projects with Sage Jobs

Import Vendors from Sage

Import a Prime Contract from Sage

Export Prime Contract Change Orders to Sage

Export a Procore Budget to Sage

Export a Procore Commitment to Sage

Export a Procore CCO to Sage

Export a Subcontractor Invoice to Sage

Export Budget Modifications to Sage

Export Companies to Sage

Export Sub Jobs to Sage

Export Timesheet Data from Procore into Sage

OUTDATED VIDEOS - Removed from Support Site and Certifications

Sage Marketing Video

Export Timesheet Data from Procore into Sage 300 CRE®

Sage 300 CRE®: Export a Subcontractor Invoice to Sage

Sage 300 CRE®: Export Budget Modifications to Sage

Sage 300 CRE®: Export Companies to Sage

Sage 300 CRE®: Export Sub Jobs to Sage

Sage 300 CRE®: Export a Commitment to Sage

Sage 300 CRE®: Export a Commitment Change Order to Sage

Sage 300 CRE®: Export a Budget to Sage

Sage 300 CRE®: Export Prime Contract Change Orders to Sage

Sage 300 CRE®: Import a Prime Contract from Sage

Sage 300 CRE®: Import Vendors from Sage

Sage 300 CRE®: Sync Procore Projects with Sage Jobs

Sage 300 CRE Employee Sync

Import Prime Contract - Sage 300 CRE

Sync Procore Projects with Sage Jobs

Export Budget Modifications to Sage

Export Commitments to Sage

Export Commitment Change Orders (CCOs) to Sage

Import Sub Jobs for Sage-Integrated Projects in Procore

Sync Procore Companies with Sage Vendors

Procore Construction Financials & Sage 300 CRE: Harvey Builders

The following workflow diagrams explain the order of operations when creating certain types of items in a Procore account that's integrated with Sage 300 CRE®.

Job Setup
Sub Job Setup
Budget Update
Create and Export Commitments
Create and Export CCOs
Create and Export PCCOs
Create and Sync Vendors
Set Up the Subcontractor Invoices Feature
Export Subcontractor Invoices from Procore

Job Setup

Sub Job Setup

Budget Update

Create and Export Commitments

Create and Export CCOs

Create and Export PCCOs

Create and Sync Vendors

Set Up the Subcontractor Invoices Feature

Export Subcontractor Invoices from Procore

Important

Several available actions in the ERP Integrations tool also require Accounting Approver permissions. An Accounting Approver is a user with either 'Standard' or 'Admin' level permissions to the ERP Integrations tool who has been granted the 'Can Push to Accounting' privilege.

Not all ERP connectors support every action described below. To learn more about your connector's supported functions, see Things to Know About your ERP Integration.

Action	Standard	Admin	Notes
Accept or Reject Cost Codes for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject Owner Invoices for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject Subcontractor Invoices for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject a Budget for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject a CCO for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject a Commitment for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject a Company for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject a PCCO for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject a Project for Export to ERP Web		Also requires Accounting Approver permissions
Accept or Reject a Sub Job for Export to ERP Web		Also requires Accounting Approver permissions
Add a Procore Project to your ERP System Web
Add an ERP Company to the Procore Company Directory Web
Add an ERP Job to Procore Web
Archive an ERP Company in Procore Web
Assign Default Cost Types To ERP Standard Cost Codes Web
Configure Advanced Settings: ERP Integrations Web
Configure the Sync Schedule for your ERP Integration Web
Enable or Disable ERP Direct Exports Web
Import a Budget from ERP Web
Import a Prime Contract from an Integrated ERP System into Procore Web
Import an ERP Sub Job to a Procore Project Web
Link ERP Companies to Procore Companies Web
Refresh the Companies List for ERP Web
Refresh the Cost Codes on an ERP Integrated Project Web
Send, Retrieve, or Resend Items to ERP Integrations for Accounting Acceptance Web			These actions do NOT require permissions to the ERP Integrations tool. Sending items to ERP for accounting acceptance requires 'Admin' level permissions on the tool where the item is located.
Sync Job Cost Transactions from an Integrated ERP into Procore Web
Sync Paid Invoice Notifications from ERP into Procore Web
Unlink CCOs Synced with ERP Web
Unlink Commitments Synced with ERP Web
Unlink Owner Invoices Synced with ERP Web
Unlink PCCOs Synced with ERP Web
Unlink Subcontractor Invoices Synced with ERP Web
Unlink a Company Synced with ERP Web
View a List of Synced Sub Jobs Web	Requires additional tool permissions	Requires additional tool permissions	Also requires 'Admin' level permissions to the Company level Directory tool, or 'Standard' level permissions with the 'Create New Project' granular permission.
View an Accountant Report for ERP Web
View an ERP Job Costs Report Web		Requires additional tool permissions to view at the project level	'Admin' level permissions to the ERP Integrations tool allows users to view this report at the Company level. To view at the Project level, users also require: 'Read-only' level permission or above on the project's Reports tool. AND 'Admin' level permission on the project's Budgets tool. OR 'Admin' level permission on the project's Prime Contract tool.
View an ERP Unsyncable Direct Costs Report Web			Users do NOT require permissions to the ERP Integrations tool to view this report. They do require: 'Read-only' level permission and above on the project's Reports tool AND 'Admin' level permission on the project's Budgets tool OR 'Admin' level permission on the project's Prime Contract tool.
View the Archived Companies List for ERP Web	Also requires Accounting Approver permissions	Also requires Accounting Approver permissions

Below are the notable changes to the Procore + Sage 300 CRE® integration.

Recent Changes

ERP Enhancement to Budget Syncing Functionality (02/03/2025)

Procore has automated the export process for project cost codes, eliminating the need for manual refreshes before exporting financial objects. The new functionality now ensures that any new cost codes are automatically refreshed and exported, streamlining the workflow for users connected to ERP systems. This new functionality applies to ERP integrations that allow cost code/WBS code syncing and project exports. See Things to Know about the Project Financials + Sage 300 CRE® Connector to learn more.

Improved Invoice line summarization with Sage 300 CRE® (08/05/2024)

Procore's Sage 300 CRE® Connector now consolidates multiple invoice lines into a single line per commitment, reducing unnecessary detail and simplifying financial reporting. No action is necessary to see this feature. If you would like to have this functionality turned off, please contact your Procore point of contact.

Improved Commitment Process with Sage 300 CRE® (07/10/2024)

Commitments are now posted automatically during the transmission process for a more streamlined export experience. Previously, commitments had to be posted manually, which created many disruptions. This update requires Sage 300 CRE® 23.2 or greater. Contact your Procore point of contact to get started today.

streamlined invoice export data with Sage 300 CRE® (02/23/2023)

Previously, invoices exported to Sage 300 CRE® included line-item detail based on the commitment’s subcontractor schedule of values (SSOV). Invoice exports now consolidate SSOV detail into the commitment and commitment change order schedule of values lines. Contact your Procore point of contact to get started today.

Common Error Messages and Resolutions

If you receive an error message from your ERP integration, review the table to find out how to resolve the issue. If you need to contact support, this page provides information about what details the ERP Support team will need to gather from you to provide a resolution. Sending the necessary information with your request for help can speed up the time it takes to resolve your case.

TOOL/SOLUTION	ERROR MESSAGE	CAUSE	SOLUTION	Information ERP Support will require to provide assistance
CHANGE ORDER Packages
	A change order with code XXX already exists on this contract.	The change order number entered in the ERP tool is already in use on this contract in Sage 300 CRE®.	Check this contract in Sage 300 CRE® to verify the next available change order number for use. Retry the export with the next available number.	If the item is not in Sage 300 CRE®: Take a screenshot of the contract in Sage and contact ERP Support for further info. Note: If contacting ERP support using the form in the above link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	Job has been closed.	The job is in a 'Closed' status in Sage 300 CRE®.	Reopen the job in Sage 300 CRE®. Then, retry the export.	If the issue persists, contact ERP Support and provide a screenshot of the Sage 300 CRE® Job in an Open status. Note: If contacting ERP support using the form in the above link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	A commitment change order already exists with the specified id.	Commitment change order IDs need to be globally unique. The commitment change order ID entered in the ERP tool already exists Sage 300 CRE®.	Check if the commitment change order appears in Sage 300 CRE® with expected transaction information. If all of the commitment change order data has made it to Sage 300 CRE®, but shows as failed in Procore, the commitment change order needs to be linked by ERP Support.	Contact ERP Support and provide a screenshot of the commitment change order. Note: If contacting ERP support using the form in the above link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	A contract item already exists on this contract with the specified code.	This can happen if the line item is not marked as synced in Procore, if you modify contract items in {{integrations_sage300cre}, or if the prime contract change order is reset.	Contact ERP Support to confirm steps to resolution.	Note: If contacting ERP support using the form in the support link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	Commitment has been archived.	The issue may be either the parent contract has been archived in Sage 300 CRE® or there is an issue with one of the commitment schedule of value items on the parent commitment itself not being synced properly with Sage 300 CRE®.	Contact ERP Support to confirm steps to resolution.	Take a screenshot of the line items on commitment XXXXX in 'Job Cost >Tasks > Commitments. Note: If contacting ERP support using the form in the support link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	A commitment with code [XX-XXXXX-XX] already exits.	This error may occur due to the following: a commitment was deleted and re-created, a failed previous attempt at exporting, or a different commitment exists with the same code.	Contact ERP Support to confirm steps to resolution.
CONTRACTS
	A commitment with code [XX-XXXXX-XX] already exists.	This error may occur due to the following: the commitment was deleted and re-created, a failed previous attempt at exporting, or a different commitment with the same code exists.	Contact ERP Support to confirm steps to resolution.	Note: If contacting ERP support using the form in the support link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	Vendor is inactive/has been archived.	The vendor on the failing contract has been set to 'Inactive' in Sage 300 CRE®.	Uncheck the 'Inactive' option on this vendor in Sage 300 CRE® and verify that the vendor is still synced with Procore.	If it is no longer synced, contact ERP Support to have the vendors re-linked so the contract will export. Note: If contacting ERP support using the form in the support link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	Changing the code is not allowed.	This error indicates the item has been attempted multiple times and the previous export attempts need to be cleared.	Contact ERP Support to confirm steps to resolution.	Note: If contacting ERP support using the form in the support link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	No entities could be found of type [Category] with given where clause.	The category being used on the commitment item is no longer on the job in Sage 300 CRE®. This error is related to cost code and/or category items which have been deleted and/or re-added from Sage 300 CRE®.	Contact ERP Support to confirm steps to resolution.	Note: If contacting ERP support using the form in the support link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	A commitment already exists with the specified id.	Commitments will fail to export from Procore to Sage 300 CRE® if an existing commitment with the same code already exists in the hh² database. This can occur if a commitment was created directly in Sage 300 CRE®, even if it was later deleted.	Please review this FAQ for the steps to resolve this issue.
INVOICEs
	There are errors in the document's codings. Errors: Document already exists for specified vendor and code [XX-XXXXXX-XX].	There is already an invoice in Sage 300 CRE® with the same code for the vendor.	Confirm that you are using a unique invoice ID. If you are using a unique invoice ID, contact ERP Support for assistance with rectifying any data discrepancies between the systems.	Note: If contacting ERP support using the form in the support link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	Ap Invoice Api import failed with error message: GL period closed. Entry not allowed. (MM\DD\YYYY).	Invoices will not post to a closed GL period in Sage 300 CRE®.	Re-open the GL period and contact ERP Support to reset the failed export attempt.	Note: If contacting ERP support using the form in the support link, reply to your case confirmation email with any relevant files, attachments, or screenshots.
	The document's codings are incomplete: The document has no distributions.	In most cases, this error is because of the result of a zero-dollar invoice. This frequently happens when the Work Completed and New Materials Stored fields zero each other out. Once the lines reach a net zero, the integration doesn't send any lines over for $0. In this case Procore thinks that it doesn't have anything to export.	Please correct the zero-dollar invoice.
	Ap Invoice Api import failed with error message: Commitment XXXXXXX - amount invoiced exceeds approved amount plus tolerance.	This error occurs due to a Sage 300 CRE® setting and is not due to any settings within Procore or the integration itself. This means that the item has gone over the amount allowed by Sage 300 CRE® or the item is attempting to be overbilled and thus rejected.	Please check the tolerance setup in Sage 300 CRE® and adjust accordingly. Review the Sage 300 CRE® Knowledgebase support site for further assistance.
	Ap Invoice Api import failed with error message: [XXXXX] is an invalid expense account.	Sage 300 CRE® requires an expense account in the distribution. Since there's no expense account/[GL Account], Sage 300 CRE® is rejecting the invoice. This error is typically caused by a feature in Sage 300 CRE® called 'control accounts' that is turned on.	Review the Sage 300 CRE® Knowledgebase support site for further assistance.
ERP CONNECTION
	Entity with this ID not found.	This error is due to a data issue within the integration.	Contact ERP Support for assistance.
	Can't be blank.	This error is due to a data issue within the integration.	Contact ERP Support for assistance.
	We're sorry, an error occurred when attempting to sync your Jobs. Please contact your customer support rep for assistance.	This error is due to a data issue within the integration.	Contact ERP Support for assistance.
	Unknown Error => You have surpassed the max number of requests for an hour. Please wait until your limit resets.	You have run into API rate limits.	Contact ERP Support for assistance.
PROJECTs
	A job with that code already exists.	A job with the same code already exists in Sage 300 CRE®.	You will need to contact ERP Support and confirm that the duplicate job no longer exists in both Sage 300 CRE® JC and PJ. Afterwards, ERP Support can reconcile the data, and you can then reject and re-export the job from Procore.
	[Name] is too long, maximum length is 30 characters.	The name you entered has more than 30 characters.	Enter a name that is less than 30 characters.
	[AddressCity] is too long, maximum length is 15 characters.	The address/city you entered has more than 15 characters.	Enter an address/city that is less than 15 characters.
	[AddressZip] is too long, maximum length is 10 characters.	The address/zipcode you entered has more than 10 characters.	Enter an address/zip that is less than 10 characters.
	A job already exists with the specified id.	Job IDs have to be globally unique.	Please verify that the job ID being used is unique.

Set Up your Payroll Export for use with Sage

Sync Procore Projects with Sage Jobs

Import Vendors from Sage

Import a Prime Contract from Sage

Export Prime Contract Change Orders to Sage

Export a Procore Budget to Sage

Export a Procore Commitment to Sage

Export a Procore CCO to Sage

Export a Subcontractor Invoice to Sage

Export Budget Modifications to Sage

Export Companies to Sage

Export Sub Jobs to Sage

Export Timesheet Data from Procore into Sage

OUTDATED VIDEOS - Removed from Support Site and Certifications

Sage Marketing Video

Export Timesheet Data from Procore into Sage 300 CRE®

Sage 300 CRE®: Export a Subcontractor Invoice to Sage

Sage 300 CRE®: Export Budget Modifications to Sage

Sage 300 CRE®: Export Companies to Sage

Sage 300 CRE®: Export Sub Jobs to Sage

Sage 300 CRE®: Export a Commitment to Sage

Sage 300 CRE®: Export a Commitment Change Order to Sage

Sage 300 CRE®: Export a Budget to Sage

Sage 300 CRE®: Export Prime Contract Change Orders to Sage

Sage 300 CRE®: Import a Prime Contract from Sage

Sage 300 CRE®: Import Vendors from Sage

Sage 300 CRE®: Sync Procore Projects with Sage Jobs

Sage 300 CRE Employee Sync

Import Prime Contract - Sage 300 CRE

Sync Procore Projects with Sage Jobs

Export Budget Modifications to Sage

Export Commitments to Sage

Export Commitment Change Orders (CCOs) to Sage

Import Sub Jobs for Sage-Integrated Projects in Procore

Sync Procore Companies with Sage Vendors

Procore Construction Financials & Sage 300 CRE: Harvey Builders

Job Setup

Sub Job Setup

Budget Update

Create and Export Commitments

Create and Export CCOs

Create and Export PCCOs

Create and Sync Vendors

Set Up the Subcontractor Invoices Feature

Export Subcontractor Invoices from Procore

Important

Important

Recent Changes

ERP Enhancement to Budget Syncing Functionality (02/03/2025)

Improved Invoice line summarization with Sage 300 CRE® (08/05/2024)

Improved Commitment Process with Sage 300 CRE® (07/10/2024)

streamlined invoice export data with Sage 300 CRE® (02/23/2023)

Common Error Messages and Resolutions

CHANGE ORDER Packages

CONTRACTS

INVOICEs

ERP CONNECTION

PROJECTs