FAQ for the Sage Construction Management integration with Sage Intacct

Each Sage Intacct data folder will require their own Sage Construction Management instance. If one data folder is used with multiple GL prefixes, you will only need one Sage Construction Management tenant.

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

Yes, our integration is leveraging the APIs built by hh2. The hh2 Sync Client will need to be installed and configured before the AccountingLink will work.

The hh2 Sync Client has different configurable sync options that will determine how often the data is transferred between each system. It may 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 don’t 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 don’t match formatting, there will be expected issues when sending data, e.g., Jobs, Commitments, etc., with the wrong format.

No, we do not have a way to map the payment types now so payment terms should be set up manually to match in each system. Payment terms need to be manually setup 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.

AP Invoices created through the platform will need to be posted by the user in Accounts Payable. That posting process will create unposted transactions in Job Cost and General Ledger. Depending on posting settings in AP, those General Ledger and Job Cost transactions will either automatically post or the user will need to manually post them in their respective modules.

Direct Cost entries created via the platform will need to be manually posted in Job Cost.

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.

Only the new API for Commitments is there an ability to remotely post the transactions. The control associated with posting would typically be batch numbers and most of the methods 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 would be Committed Cost transactions created as a result of creating Commitments through the Commitment API. In all other cases, Job Cost Transactions must be posted by the user. This would include 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 would sync data from. This applies to the following file types only:

• PR Master

• PR System

• PR Transaction

• JC Transaction

Currently, the Scope of Work (SOW) created in Sage Construction Management does not post to Sage Intacct for the following items:

• Subcontracts

• Subcontract Change Orders (SCO)

• Prime Contracts

• Change Proposal Request (CPR)

• Prime Contract Change Orders (Prime CO)

This is because the Scope of Work (SOW) in Sage Construction Management supports unlimited length and Rich Text formatting, which allows for detailed and formatted descriptions. In contrast, the Scope of Work (SOW) in Sage Intacct has strict limitations on both length and formatting. It does not support Rich Text and cannot import such content through the API.

Until Sage Intacct supports these capabilities, detailed Scope information will be managed and maintained within Sage Construction Management.

However, header information and detailed line items by Job Cost Code for Prime Contracts, CPRs, Change Orders, Subcontracts, and SCOs will still post from Sage Construction Management to Sage Intacct.

A subcontract change order error occurs when a negative subcontract invoice line item is being sent to Sage Intacct but the following options haven’t been set in Sage Intacct:

• The reverse conversion is not turned on in Purchasing configuration.

• The reverse conversion permissions have not been assigned to the user trying to post a negative invoice line using reverse conversion.

• The reverse conversion is not enabled on the negative invoice line and the subcontract line value is positive.

To enable reverse conversion in Sage Intacct:

1. Go to Sage Intacct and select Purchasing > Setup > Configuration.

2. In the Construction section, select the Enable conversion reversal for non-inventory items checkbox.

To assign reverse conversion permissions to the Sage Intacct user:

1. Go to Sage Intacct and select Admin > Company.

2. Select Top Level > Admin.

3. In the Users, roles, and groups section, select Roles.

4. Select Purchasing > Purchasing Permissions and select the Reverse conversions checkbox.

To set the reverse conversion flag to true on the invoice:

1. Open the Subcontract Invoice record in Sage Intacct.

2. Select the Reverse conversion checkbox.

Note: Except for subcontract change orders, this error may occur when posting other procurement transactions.

Yes, you can export details regarding WIP PM forecast cost at completion and PM forecast contract value in .CSV format Project Analytics in Sage Construction Management. You can then import the .CSV file including the PM forecast at completion and contract value values in Sage Intacct.

See Export report details regarding WIP PM forecast cost at completion and PM forecast contract value from Sage Construction Management and import them in Sage Intacct for instructions.