Support Home > Integrations > Sage 300 CRE > About the Sage 300 CRE Connector

About the Sage 300 CRE Connector

Overview

You can now manage a construction project in Procore that's integrated with your Sage 300 CRE account. The current integration enables you to link a vendor in Sage with its matching entry in your Procore directory, and you can also import vendors from Sage into Procore, and export vendors from Procore to Sage. You can also approve and push commitments and commitment change orders that use Sage cost codes and categories, and push them directly from Procore to your Sage database.

Architectural Diagram

The following reference architecture diagram highlights the key components of Procore’s Sage 300 CRE integration.

 

Sage300 Connector_v2.jpg

Integration Map


PROCORE
Exports data from Procore to Sage  Imports data from Sage to Procore
SAGE 300 CRE
PROJECTS
COST CODES
COST TYPES
JOBS
COST CODES
CATEGORIES
SUB JOBS   EXTRAS
COMPANIES AP VENDORS
BUDGET ESTIMATE
COMMITMENTS
SUBCONTRACTS & PURCHASE ORDERS
COMMITMENT CHANGE ORDERS (CCOs)
  COMMITMENTS
SUBCONTRACTS & PURCHASE ORDERS
COMMITMENT CHANGE ORDERS (CCOs)
COSTS
COMMITTED COSTS (ACTUAL)
JTD COST
MTD COST
  COSTS
COMMITTED COSTS (INVOICED)
JTD COST
MTD COST

Key Benefits

  • "Best of Breed" solution for existing Sage 300 CRE customers; use Procore for cloud-based construction management and Sage 300 CRE for finance and account management.
  • 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.
  • More efficient communication between Accounting and Project Management teams.

Supported Versions

  • Sage v13.x
  • Sage v14.1
  • Sage v15.1
  • Sage v16.1

Supported Features

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 and Procore.
  • Create a company-specific list of Sage 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 cost codes and categories.
  • Push approved commitments (e.g. Subcontracts and Purchase Orders) and change orders from Procore to Sage.
  • 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 database.
  • Link a Sage vendor and ID with a matching company in your Procore account's directory.
  • Create a new vendor entry in Sage by importing a company entry from Procore.
  • Create a new project in Procore by importing a job from Sage.
  • Import a Sage estimate into a Procore budget.
  • Import a Sage Extra into Procore as a Sub Job.

Unsupported Features

The following features are not supported at the current time.

  • Non-sectioned cost codes (e.g., '1234567' where the first part of the cost code does not denote a division). Similarly, you must also have a standard cost code list.
  • Cost code structures using both a dot (.) and dash (-) delimiter scheme. (e.g., 01-20.05).
  • Non-use of categories. Categories must be enabled and a standard category list must be used.
  • Integrate an active Procore project (i.e., that was created prior to the Procore account being integrated with Sage).
  • Integrated Payment Applications and Draw Requests.
  • Push commitments from Sage 300 CRE to a Procore project.
  • Owner Change Orders.

Common Questions

  • 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 typically 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 Sync Client on the system running your Sage 300 CRE application (e.g., Sage 300 CRE Server). Once the initial configuration has been completed, the hh2 Sync Client runs in the background as a web service.
  • How is data safely transferred between Procore, hh2, and Sage 300 CRE?
    The hhCloud Service is a third-party, professional-grade Data Center that is maintained and monitored 24/7. An hh2 Sync Client is installed on your Sage 300 CRE system and it uses the HTTPS protocol to keep in constant contact with your Sage data stored in the hh2 data center. The hh2 Sync Client also keeps your Procore data 'synced' with the hh2 Data Center and Sage 300 CRE system. To be synced with Sage, 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 Sync Client typically involves the customer's IT department or company.

Demo

If you are interested in learning more about how you can integrate your Sage 300 CRE account with Procore, please Sign-up for a free demo.

You must to post a comment.
Last modified
09:00, 7 Mar 2017

Tags

Classifications

This page has no classifications.