Implementation guide

The following best practices are recommended to ensure a smooth and successful implementation:

  • Use the Sage Intacct Implementation Environment rather than the Product Environment during setup and testing. Confirm and thoroughly test all features before migrating Sage Intacct data to the Production Environment.

  • Review and clean up Sage Intacct resource lists, including standard cost codes, customer companies, vendor companies, vendor types, employees, cost types, classes, departments, and AR/AP payment terms to ensure that they’re properly aligned with Sage Construction Management before transferring them.

  • Start by importing foundational data into Sage Intacct: standard cost codes, customer companies, vendor companies, vendor types, and employees. Once verified, transfer this data from Sage Intacct to Sage Construction Management.

  • First create any new projects in Sage Construction Management including prime contracts, cost budgets, and SOV, and then transfer them to Sage Intacct. Continue managing legacy projects using the previous ERP system.

  • Verify all Posting Preferences in the Accounting Link before running posting tests with the wizard.

  • Test all record and transaction postings in the Implementation Environment before moving to Production in Sage Intacct.

  • Confirm that all features demonstrated by the Sales team are currently available. Discuss any limitations with your client and clarify whether there are features that are not currently supported.

Keep the following points in mind to ensure a successful and streamlined implementation:

  • Unlike Sage Construction Management, Sage Intacct’s architecture is built to support multiple entities in a single tenant. If these entities require Sage Construction Management, then there should be a separate Sage Construction Management tenant for each Sage Intacct entity. We do not recommend tracking multiple entities in a single Sage Construction Management tenant.

  • Sage Construction Management must enter Accrued Equipment Timecards Cost as a special purchasing Transaction Definition (TD) in Sage Intacct that posts to the General Ledger (GL) only. This prevents it from appearing in AP Aging. Use a separate Contra GL Account to offset Equipment Timecard revenue with actual equipment expenses. This process must be explained clearly to prospects before they subscribe to set proper expectations.

  • Ensure that there are no duplicate names, including those in parent/child relationships.

  • Remove special characters from names of cost codes, customers, and vendors (for example, !@#$%^&*+<>?).

  • Avoid leading zeros in cost codes (for example, Project Number 0125 in Sage Construction Management will appear as 125 in Sage Intacct).

  • Use MLESO for cost types and map custom Sage Intacct cost codes to one of the five cost types in Sage Construction Management: Material, Labor, Equipment, Subcontract, and Other.

  • Differentiate Sage Intacct customer and vendor entries by appending a C or V to the company name.

  • Consider using ALL CAPS for parent cost code descriptions in the Sage Intacct standard cost code catalog for clarity.

  • Create projects, prime contracts, cost budgets, and SOV in Sage Construction Management first, then transfer them to Sage Intacct. Continue managing legacy projects in their original ERP system.

  • To enable financial analytic reporting in Sage Construction Management, select Post to GL Budgets in Posting Preferences under Project Estimate – Integrate with GL or Project Contract – Integrate with GL.

  • The optimal selections for your specific client and its final configuration must be determined by the partner implementation team in Sage Construction Management.

  • The Sage Construction Management Accounting Link supports Sage Intacct Multi-Tax but is not compatible with Avalara or other third-party tax applications.

  • The Sage Construction Management Accounting Link for Sage Intacct is not currently configured to work with Bill.com, Ramp, or similar automation tools.

  • Misc Expense transactions in Sage Construction Management do not post to Sage Intacct’s Cash Management module. These transactions will not appear in Bank or Credit Card Reconciliations but will post correctly to the GL if both systems are properly configured.

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

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

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 the formatting, there will be expected issues when sending data, for example, Jobs, Commitments, etc., with the wrong format.

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

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 have not 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.

Except for subcontract change orders, this error might 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 in the Project Analytics in Sage Construction Management. You can then import the CSV file including the PM forecast at completion and contract 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.

There are multiple posting status types used in Sage Construction Management when integrating with Sage Intacct:

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

The Vendor Summary report displays payment information based on data synchronized between Sage Construction Management and Sage Intacct.

Payment amounts are updated through the following process:

  1. A transaction is created in Sage Construction Management, such as a subcontract invoice.

  2. The AccountingLink utility or browser solution posts the transaction to Sage Intacct.

  3. Sage Intacct processes payments for the bill or subcontract invoice.

  4. The AccountingLink retrieves payment details from Sage Intacct and updates the payment information in Sage Construction Management.

For example, for subcontract invoices:

  1. The subcontract invoice is created in Sage Construction Management.

  2. The AccountingLink posts the subcontract invoice to Sage Intacct.

    Sage Construction Management stores the associated accounting transaction ID to retrieve payment information later on.

  3. When a payment is made in Sage Intacct, the AccountingLink retrieves the payment information during the next synchronization.

  4. The payment amount is then updated in the Accounting Info section of the subcontract invoice record and becomes available for reporting and analytics.

Payment information is not updated in real time. The Retrieve Payment and Deposit Information from Sage Intacct function on the Post tab is responsible for updating payment amounts in Sage Construction Management. This synchronization can be run manually or scheduled to run automatically on a recurring basis.

If payment amounts do not appear in the Vendor Summary report, verify that:

  • The transaction was successfully posted from Sage Construction Management to Sage Intacct through the AccountingLink.

    Payment information is available only for transactions posted from Sage Construction Management to Sage Intacct through the AccountingLink. The posting process creates the relationship needed to match Sage Construction Management transactions with payment records in Sage Intacct. If a transaction is entered separately in both Sage Construction Management and Sage Intacct, no relationship is created between the records. In this situation, payment information entered in Sage Intacct cannot be linked to or displayed for the corresponding transaction in Sage Construction Management.

  • Payment has been processed in the accounting system.

  • The Retrieve Payment and Deposit Information from Sage Intacct function has completed successfully.

On this page

Posted July 22, 2026 © 2026 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.