Sage Construction Management integration with Sage 100 Contractor FAQs

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.

hh2 officially supports Windows Server 2016 or later for hosting the synchronization client. While Windows 10 is technically unsupported, it might still function. The key requirement is that the environment is Windows-based. However, hh2 cannot guarantee full functionality or support on Windows 10. If issues arise, they might not be resolved due to the unsupported nature of the OS. Installing the synchronization client on Windows 10 can be attempted, but it will be done at your own risk.

You might be able to install and run the synchronization client successfully. However, there's no guarantee of stability or compatibility. hh2 support might be limited or unavailable if issues occur. For long-term reliability and full support, migrating to a supported Windows Server OS is recommended.

hh2 acts as the integration layer between your local environment and Sage Construction Management. Specifically, hh2 provides the synchronization client used to transfer data between your system and Sage’s cloud-based Sage Construction Management platform. hh2 does not manage or control Sage Construction Management. hh2’s role is limited to enabling secure and reliable data synchronization.

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 one, 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 AP posting settings, those general ledger and job cost transactions will either be automatically posted 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

hh2 does not provide an object to assign a client to a Sage 100 Contractor 3-5 Jobs (Account Receivable) profile. After Sage Construction Management posts the prime contract to Sage 100 Contractor, you need to add the client manually to the newly created job in Sage 100 Contractor. The client in Sage 100 Contractor must exactly match the customer company specified on the prime contract in Sage Construction Management.

No, because retainage is managed differently in Sage Construction Management and Sage 100 Contractor. Sage Construction Management tracks subcontract invoice retainage by cost code and retainage is released in a separate invoice. In contrast, Sage 100 Contractor manages retainage by vendor invoice rather than by cost code. Retainage is released by entering the amount in the appropriate field within the subcontract invoice record.

Use the following process to handle released retainage:

1. Release retainage for a sub invoice in Sage Construction Management as usual.

   This creates a transaction in Sage Construction Management showing the released retainage.

2. Go to AccountingLink > Accounts Payable (AP) > View Sub Invoices - Not Posted, select the invoice with the retainage release, and select Mark Selected Sub Invoices as Posted.

   This prevents AccountingLink from sending the transaction to Sage 100 Contractor, avoiding duplication of the retainage release.

3. In Sage 100 Contractor, release the retainage in the subcontract invoice as usual.

   The released retainage is then added to the payable balance, making it available for payment.

No, because retainage is managed differently in Sage Construction Management and Sage 100 Contractor. Sage Construction Management tracks retainage for prime invoices by cost code and retainage is released in a separate invoice. In contrast, Sage 100 Contractor manages retainage at the invoice level. Each receivable invoice tracks the retainage amount separately, which can later be released using the appropriate field within the invoice record.

Use the following process to handle released retainage:

1. Release retainage for a prime invoice in Sage Construction Management as usual.

   This creates a transaction in Sage Construction Management showing the released retainage.

2. Go to AccountingLink > Accounts Receivable (AR) > View Prime Invoices - Not Posted, select the invoice with the retainage release, and select Mark Selected Prime Invoices as Posted.

   This prevents AccountingLink from sending the transaction to Sage 100 Contractor, avoiding duplication of the retainage release.

3. In Sage 100 Contractor, release the retainage in the receivable invoice as usual.

   Saving the invoice makes the released retainage amount immediately due and payable.

The following posting status types are used in Sage Construction Management when integrating with Sage 100 Contractor:

• Posted: The transaction has been successfully posted in Sage Construction Management and linked to a corresponding purchasing or accounts payable (AP) transaction in Sage 100 Contractor. This is the final status, confirming successful integration.

• Marked as Posted: The transaction was manually marked as posted within Sage Construction Management but is not linked to a Sage 100 Contractor transaction. This status helps prevent duplicate entries when a transaction is manually entered in both systems.

• Not Posted: Transactions eligible for posting that appear in the Posting Wizard but have not yet been processed.

• Partially Posted: Only part of the transaction has been posted. This status is common in cases involving multiple line items or partial approvals.

• In Queue: The transaction has entered the posting process via background operations but is not yet complete. This status indicates that asynchronous posting is underway.

• In Queue (In Progress): A more specific variant of In Queue, indicating that the background posting process is actively running.

• Posting Failed: The transaction encountered an error during the posting process. Details, including error messages or exceptions, can be found in the Posting Log on the Posting Tab.

• Discrepancies: The transaction was posted, but the totals between Sage Construction Management and Sage 100 Contractor do not match. This status indicates mismatches that require reconciliation.