FAQ for the Sage Construction Management integration with Sage Intacct

How many Sage Intacct data folders can one instance of Sage Construction Management connect to with the AccountingLink?

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.

 

How can I get the AccountingLink for Sage Intacct?

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

 

Are any installations required for the AccountingLink for Sage Intacct?

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.

 

How long does it take for data to become available for any manual data pulling?

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.

 

How will formats in Sage Construction Management be forced to match the required formats in Sage Intacct?

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.

 

Is there any integration mapping between the Sage Construction Management payment terms and the payment terms in Sage Intacct?

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.

 

When sending over costs through the APIs, will I need to post those within each module and then also post again 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.

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.

 

Is there any hh2 API that will handle posting Job Costs automatically?

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

 

How will the hh2 integration work when using transaction files?

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

Note: For all other types, we do not provide any name configuration.

 

Why doesn’t the Sage Construction Management Scope of Work (SOW) post to Sage Intacct?

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.