FAQ for the Sage Construction Management integration with Sage 100 Contractor

Each Sage 100 Contractor company will require its own Sage Construction Management instance. However, you’ll only need one Sage Construction Management tenant. If you’re using departments, you’ll need to specify manually the department for a job in Sage 100 Contractor after it’s posted from Sage Construction Management.

You can purchase the AccountingLink for Sage 100 Contractor at an additional cost.

The hh2 Sync Client has different configurable sync options that will determine how often the data is transferred between each system. It might take up to 5 minutes for the quickest option because updates have to go from Sage Construction Management to hh2 Sync Cloud Services to hh2 Sync Client to ERP or vice versa.

We do not have a way to query the custom formats in the legacy ERPs, so these formats will need to be matched manually in Sage Construction Management. If they do not match formatting, there will be expected issues when sending data with the wrong format, such as jobs, commitments, and so on.

No, we do not have a way to map the payment types, so payment terms must be set up manually in each system to match. Payment terms need to be manually set up on vendors and customers.

The only endpoint that can post the transaction is the new job cost commitment ones which we can turn on for your test environments and customers. Apart from that, user settings for posting controls are going to dictate the posting behavior.

The user will need to post AP Invoices created through the platform in Accounts Payable. That posting process will create unposted transactions in the job cost and general ledger. Depending on the posting settings in AP, those general ledger and job cost transactions will either automatically post or the user will need to post them manually in their respective modules.

Direct cost entries created via the platform will need to be manually posted in job cost.

Only the new API for commitments is there an ability to post the transactions remotely. The control associated with posting is typically batch numbers and most of the methods that we use to get the data into Sage does not provide a response where we can grab the batch numbers for data feeds. The only case where job cost transactions will be automatically posted is for committed cost transactions created as a result of creating commitments through the Commitment API. In all other cases, the user must post the job cost transactions. This includes the following types of transactions:

• Original Estimates

• Approved Estimate Changes

• Approved Scheduled Value Changes (OCOs)

• Direct Costs

• Misc Worksheet Entries

Named files are not supported. If you have named files enabled for a given type of transaction file, we can specify a single specific file name that we’ll sync data from. This applies to the following file types only:

• PR Master

• PR System

• PR Transaction

• JC Transaction