FAQ for the Sage Construction Management integration with Sage 300 Construction and Real Estate

Each Sage 300 Construction and Real Estate 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 300 Construction and Real Estate 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.

 

hh2 officially supports Windows Server 2016 or later for hosting the synchronization client. While Windows 10 is technically unsupported, it may 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 may 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 may be able to install and run the synchronization client successfully. However, there is no guarantee of stability or compatibility. hh2 support may be limited or unavailable if issues occur.

For long-term reliability and full support, migrating to a supported Windows Server OS is strongly 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 SCM platform. hh2 does not manage or control Sage Construction Management. hh2’s role is limited to enabling secure and reliable data synchronization.

 

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 CM. If they don’t match formatting, there will be expected issues when sending data with the wrong format (Jobs, Commitments, etc.)

 

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.

 

Are there any issues with the hh2 APIs if a Replicator is used for Sage 300 Construction and Real Estate?

There shouldn't be any issues. If you have under resourced hardware or potentially large data sets, having both data syncs running simultaneously may put more load on your hardware and result in a change in performance. Deltas are used to minimize this. For large datasets, a Replicator can be used to pull an offline data cache for reporting.

 

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.

 

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

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

     

    Can I export Labor Timecards from Sage Construction Management and import them in Sage 300 Construction and Real Estate?

    Yes, you can export Labor Timecards in .TXT format using the Time & Expenses module in Sage Construction Management.

    See Export Labor Timecards from Sage Construction Management and Import Them in Sage 300 Construction and Real Estate for more details.

     

    Can I link a 300 Construction and Real Estate prime contract to Sage Construction Management?

    Yes, you can manually link a prime contract and import contract items using the Prime Contract information page links, after selecting a prime contract through the Project module.

    See Manually link a prime contract and import contract items.

    You can manage change orders in Sage 300 Construction and Real Estate either using the Job Cost module or the Project Management (PJ) module. This is set through the Use PJ for Change Management checkbox on the Job record in the Project Management module. When creating change orders, data is sent to the correct destination in Sage Construction Management automatically. When the Project Management module is used for change management, the change order data is stored and displayed in the Project Management module and won't appear in the change order in Job Cost.

    It is not recommended to set prime contracts and SOV line items using the available integration options since the use of hh2 has introduced complexities that make managing the posted records complicated.

    Sage Construction Management creates the project / job record only in Sage 300 Construction and Real Estate and then creates the estimate / cost budget and posts it to Sage 300 Construction and Real Estate. The contract and line items are set up in Sage 300 Construction and Real Estate and then pulled back to Sage Construction Management. Contract and prime invoice line items need to be managed manually. Prime invoices are posted as contract invoices in Sage 300 Construction and Real Estate by line item detail.

    To avoid discrepancies that may be caused by manually managing prime and contract invoices, we recommend setting the Sage 300 Construction and Real Estate jobs to default to the QuickBill Invoice settings. Sage Construction Management creates the project / job in Sage 300 Construction and Real Estate. Sage 300 Construction and Real Estate presets the billing method.

    A few settings need to be manually added. Prime invoices post in Sage 300 Construction and Real Estate as QuickBill invoices with a basic entry and totals only.

    Set the default billing method to QuickBill in Sage 300 Construction and Real Estate

    1. Go to Job Cost.

    2. Select File > Company Settings > JC Settings > Billing....

    3. Select Use Quick Bill > OK to make sure all new jobs will default to QuickBill unless manually overridden.

    4. When creating a new job, verify that the billing method defaults to QuickBill. Select Setup > Jobs... > Billing Info. Make sure that the Use Quick Bill radio button is selected at the Billing Method section.

    If you are using the hh2 API or another integration to Sage Construction Management, note that the APIs do not currently support populating the billing method and billing level fields directly. These values are pulled from the default values set in JC settings.
    If a job is created with an incorrect billing method, it must manually updated in Job Cost.

    There are various posting status types used in Sage Construction Management when integrating with Sage 300 Construction and Real Estate:

    • Posted: The transaction has been successfully posted in Sage Construction Management and linked to a corresponding purchasing or accounts payable (AP) transaction in Sage 300 Construction and Real Estate. 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 300 Construction and Real Estate 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 300 Construction and Real Estate do not match. This status flags mismatches that require reconciliation.

  • JC Transaction

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

 

Yes, you can export Labor Timecards in .TXT format using the Time & Expenses module in Sage Construction Management.

See Export Labor Timecards from Sage Construction Management and Import Them in Sage 300 Construction and Real Estate for more details.

Yes, you can manually link a prime contract and import contract items using the Prime Contract information page links, after selecting a prime contract through the Project module.

See Manually link a prime contract and import contract items.

You can manage change orders in Sage 300 Construction and Real Estate either using the Job Cost module or the Project Management (PJ) module. This is set through the Use PJ for Change Management checkbox on the Job record in the Project Management module. When creating change orders, data is sent to the correct destination in Sage Construction Management automatically. When the Project Management module is used for change management, the change order data is stored and displayed in the Project Management module and won't appear in the change order in Job Cost.

It is not recommended to set prime contracts and SOV line items using the available integration options since the use of hh2 has introduced complexities that make managing the posted records complicated.

Sage Construction Management creates the project / job record only in Sage 300 Construction and Real Estate and then creates the estimate / cost budget and posts it to Sage 300 Construction and Real Estate. The contract and line items are set up in Sage 300 Construction and Real Estate and then pulled back to Sage Construction Management. Contract and prime invoice line items need to be managed manually. Prime invoices are posted as contract invoices in Sage 300 Construction and Real Estate by line item detail.

To avoid discrepancies that may be caused by manually managing prime and contract invoices, we recommend setting the Sage 300 Construction and Real Estate jobs to default to the QuickBill Invoice settings. Sage Construction Management creates the project / job in Sage 300 Construction and Real Estate. Sage 300 Construction and Real Estate presets the billing method.

A few settings need to be manually added. Prime invoices post in Sage 300 Construction and Real Estate as QuickBill invoices with a basic entry and totals only.

Set the default billing method to QuickBill in Sage 300 Construction and Real Estate

  1. Go to Job Cost.

  2. Select File > Company Settings > JC Settings > Billing....

  3. Select Use Quick Bill > OK to make sure all new jobs will default to QuickBill unless manually overridden.

  4. When creating a new job, verify that the billing method defaults to QuickBill. Select Setup > Jobs... > Billing Info. Make sure that the Use Quick Bill radio button is selected at the Billing Method section.

If you are using the hh2 API or another integration to Sage Construction Management, note that the APIs do not currently support populating the billing method and billing level fields directly. These values are pulled from the default values set in JC settings.
If a job is created with an incorrect billing method, it must manually updated in Job Cost.

There are various posting status types used in Sage Construction Management when integrating with Sage 300 Construction and Real Estate:

  • Posted: The transaction has been successfully posted in Sage Construction Management and linked to a corresponding purchasing or accounts payable (AP) transaction in Sage 300 Construction and Real Estate. 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 300 Construction and Real Estate 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 300 Construction and Real Estate do not match. This status flags mismatches that require reconciliation.

On this page

Posted December 01, 2025 © 2025 The Sage Group plc or its affiliates ("Sage") or its licensors. All trademarks mentioned are the property of their respective owners. Use of non-Sage trademarks is not an endorsement of any person or product.