Procore is the only comprehensive cloud-based construction project management platform with an out-of-the-box integration with Sage 300 CRE®.
Connect your accounting and project management within Procore and provide field teams untethered access to financial data. Eliminate double-entry and give project managers one-click access to accurate job costing information on the construction site. With a Sage 300 CRE® integration you can have confidence in your financial data to make the best in-the-field decisions while giving accounting peace of mind as they retain full control over data pushed into accounting.
With the Procore + Sage 300 CRE® integration, you can:
- Save time and labor by streamlining the approval process of time sensitive tasks such as commitments and change orders.
- Reduce human error by eliminating the need for manual, double-entry when transferring data from Procore to Sage 300 CRE®.
- More efficient communication between Accounting and Project Management teams.
The following diagram highlights the key components of the Procore + Sage 300 CRE® integration.
Feature Set Map
|Exports data from Procore to Sage 300 CRE®||Imports data from Sage 300 CRE® to Procore||
Sage 300 CRE®
|STANDARD COST CODES 1
STANDARD COST TYPES
|STANDARD COST CODES (JC)
|SUB JOBS||EXTRAS (JC)|
|COMPANIES||AP VENDORS (AP)|
|COMPANY INSURANCE||VENDOR INSURANCE (AP)2|
|BUDGETS 3||ESTIMATE (JC)|
|BUDGET CHANGES||APPROVED ESTIMATE CHANGES (JC)|
|COST FORECAST DATA||COST FORECAST DATA|
SUBCONTRACTS & PURCHASE ORDERS
SUBCONTRACTS & PURCHASE ORDERS
|COMMITMENT CHANGE ORDERS||COMMITMENT CHANGE ORDERS (JC)|
|PRIME CONTRACT||CONTRACTS (CN)/MISC.
|PRIME CONTRACT CHANGE ORDERS (PCCOs)||PRIME CONTRACT CHANGE ORDERS 7|
BILLED RATE TRANSACTIONS 5
BILLED RATE TRANSACTIONS
||JOB COSTS TRANSACTION DETAILS|
1 Custom WBS Segments are NOT supported.
2 To sync vendor insurance from Sage 300 CRE® to Procore, your Procore point of contact must enable a backend configuration setting during the implementation process.
3 Exports the 'Estimated Cost at Completion' and 'Forecast to Complete' values from a Procore budget to Sage 300 CRE®.
4 Includes Sage 300 CRE® tax groups. For more details, see How can I use tax codes on a Procore project? and Configure Tax Code Settings.
5 Requires transactions generated from Work-In-Progress (WIP) in the Sage Billing module.
6 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.
7 Includes miscellaneous worksheet transactions.
8 Not supported for Canada.
9 To set up exports, the hh2 sync client must be running version 467 or higher. See Set Up the Export Subcontractor Invoices Feature for Sage 300 CRE®.
The following versions of Sage 300 CRE® are supported:
- v20.1, v20.2, v20.3, v20.4, v20.5
- v18.1, v18.2, v18.3, v18.4
If your company plans to sync Prime Contract and Prime Contract Change Orders (PCCOs) between systems, your company must be using Sage 300 CRE® version 17.1.4 or newer.
Procore's current integration with Sage 300 CRE® includes the following features.
- 2-tier and 3-tier cost codes.
- Synchronization of Sage 300 CRE® cost codes, categories, and job costs between Sage 300 CRE® and Procore.
- Create a company-specific list of Sage 300 CRE® cost codes that can be applied to each new project.
- Create commitments and commitment change orders in Procore where each line item uses Sage 300 CRE® cost codes and categories.
- Push approved commitments (for example, purchase orders and subcontracts) and change orders from Procore to Sage 300 CRE®.
- Built-in approval workflows for commitments and commitment change orders where designated Accountants can approve/reject them in Procore; approved commitments are pushed directly from Procore to your Sage 300 CRE® database.
- Link a Sage 300 CRE® vendor and ID with a matching company in your Procore account's directory.
- Create a new vendor entry in Sage 300 CRE® by importing a company entry from Procore.
- Create a new company entry in Procore by import a vendor from Sage 300 CRE® and also import insurance information with the entry.
- Create a new project in Procore by importing a job from Sage 300 CRE®.
- Import a Sage 300 CRE® estimate into a Procore budget.
- Export a Procore Budget to Sage 300 CRE® as an estimate.
- Import a Sage 300 CRE® extra into Procore as a sub job.
- Export a Procore sub job to Sage 300 CRE® as an extra.
- Export the 'Estimated Cost at Completion' and 'Forecast to Complete' values from a Procore budget to Sage 300 CRE®.
- Import Sage 300 CRE® job cost transactions to a Procore budget to reflect values in the 'Direct Cost' column of budget line items.
- Import multiple prime contracts to one (1) Procore project.
The following features are not currently supported:
- 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.
- Non-sectioned cost codes (for example, '1234567' where the first part of the cost code does not denote a division). Similarly, you must also have a standard cost code list. See What are 'Standard Cost Types' in the Admin Tool's 'Cost Types' page?
- Cost code structures using both a dot (.) and dash (-) delimiter scheme. (for example, 01-20.05).
- Non-use of categories. Categories must be enabled and a standard category list must be used.
- Integrated owner invoices and related payments.
- Import commitments from Sage 300 CRE® to a Procore project.
- Import one (1) unique prime contract to more than one Procore project.
- How does Procore connect to Sage 300 CRE®?
When Procore's ERP Integrations tool is configured to work with Sage 300 CRE®, your company's Procore Administrator will work with your Procore point of contact to install the hh2 synchronization client on your Sage 300 CRE® server. The synchronization client is a lightweight, Windows desktop application that establishes a secure network connection between the hh2 Cloud Service (www.hh2.com), which keeps the data in Sage 300 CRE® and Procore in sync.
Typically, the hh2 synchronization client requires no special network firewall permissions, since the client only uses standard outbound TCP Port 80, and sometimes Port 443 connections, which are commonly used for standard web access. In addition, no inbound connections are required. Standard web technologies like Web Sockets is used to maintain a persistent connection.
- What is required of the IT Team?
The only requirement is to download and install the hh2 synchronization client on the system running your Sage 300 CRE® application (for example, Sage 300 CRE® Server). Once the initial configuration has been completed, the hh2 synchronization client runs in the background as a web service.
- How is data safely transferred between Procore, hh2, and Sage 300 CRE®?
The hh2 Cloud Service is a third-party, professional-grade Data Center that is maintained and monitored 24/7. An hh2 synchronization client is installed on your Sage 300 CRE® system and it uses the HTTPS protocol to keep in constant contact with your Sage 300 CRE® data stored in the hh2 data center. The hh2 synchronization client also keeps your Procore data 'synced' with the hh2 Data Center and system. To be synced with Sage 300 CRE®, the compatible data in Procore must first be sent to the ERP Integrations tool for acceptance by an accounting approver. After acceptance, your Procore data is exported to hh2 and then synced with Sage 300 CRE®.
- Who can authorize what?
Within Procore, any exports to Sage 300 CRE® must be approved by your company's designated accounting approver(s). Any changes to the hh2 synchronization client typically involves the customer's IT department or company.