This release is scheduled to go live beginning on the evening of May 15, 2020.

Company and Console

Configuration for Inter-Entity Transactions

A new configuration object for inter-entity transactions allows you to designate payable and receivable accounts for inter-entity transactions in a multi-entity shared company. There is only one inter-entity configuration object for a company, and the record number is always 1.

Two types of inter-entity configuration are available:

  • With basic configuration, you provide one default inter-entity receivable (IER) account and one default inter-entity payable (IEP) account for each entity.
  • With advanced configuration, you create a relationship between two entities and provide the IER and IEP accounts for each side of the relationship.

Your company will use one type of configuration or the other—they cannot be used together.

For more information:

Cash Management

Enhanced checking account reconciliation with online bank feeds

You can now reconcile your checking account using online bank feeds from Sage Cloud Services or by providing your own XML transaction records.

For more information:

The legacy reconciliation function (reconcile_bank) does not support online bank feeds.

Project and Resource Management

Timesheet Approvals

You can now approve and decline timesheets, either one at a time or all at once for a given timesheet.

Whenever a timesheet entry is submitted, a timesheet approval history object is created for tracking purposes.

For more information:

Accounts Payable

The new decline_appaymentrequest function lets you decline one or more payment requests.

Platform Services

Previous UI to retire on May 15, 2020

Sage Intacct is officially retiring the previous UI on May 15. This means that the option to switch back to it will no longer be available. Everyone will use the Action UI.

If you encounter any issues, contact your Sage Intacct representative or submit a support case.

Note: This change does not affect the Layout type available for users who want to personalize Platform and Customization Services—they can still choose Action UI or Previous layout (Action UI is recommended).

Improved scripting environment

To make writing code easier, we’re working with the CodeMirror® library to provide syntax highlighting and autocompletion when working on page scripts:

Platform syntax highlights

You can also name script components and give them descriptions.

In addition, you no longer have to add a comment line to your script to provide a name for debugging—you can configure your Platform Services preferences so a name is automatically generated. Any existing inline script identifiers are overwritten during runtime when you enable this option.

For more information, see the Page Script Walkthough.

Note: Platform Services must be enabled for the Action UI Layout type to access these features.

Web Services

Unique IDs in error messages

Error messages now include a unique ID that can be used to identify the error if you need to contact Support, for example:

[Support ID: OGK8U%7EXoSyYDERVL706Ok1X%40VBawAAADI]

Construction Early Adopter Program

With this release, functionality for Construction projects is available to new customers in our Early Adopter program. To see if you are eligible for this program, contact your account manager as described in the Sage Intacct product help. If you are an Early Adopter, refer to Configure Construction in the Sage Intacct product help before starting any work.

The Construction application allows you to represent your project’s full work breakdown structure (WBS). The WBS is traditionally defined as job/cost code/category, but Sage Intacct uses project/task/cost type to reflect this structure.

The Construction APIs let you:

  • Create standard cost types, such as labor, materials, and subcontracts, to use as templates when you create new cost types.
  • Create accumulation types to break down and categorize cost type information for reporting.
  • Create a catalog of standard tasks to use as templates when creating new tasks.
  • Create Order Entry and Purchasing transactions with information unique to the Construction industry.
  • Configure retainage amounts for AP bills and AR customer invoices.

New cost type dimension

The new cost type dimension lets you easily capture cost type data for tasks as you enter transactions for your project. Each project typically has several cost types, such as labor, materials, subcontracts, and so forth. You can create a catalog of standard cost types to use as templates for creating new cost types.

Each cost type you create must be associated with a task, which in turn must be associated with a project. A cost type record is uniquely identified by the combination of its standard cost type, project, and task values, or by its record number.

Because a cost type is a dimension, you can use it in API functions that support standard dimensions such as departments, locations, items, and so forth. For example, you can create an AP bill and provide a project, task, and cost type on the transaction.

For more information:

Observed percent completed for cost types

You can provide an estimation of how complete a cost type is as of a specific date. For more information, see the COSTTYPEKEY parameter here:

Accumulation types for reporting

Accumulation types let construction companies break down and categorize cost type information for reporting purposes. An accumulation type is typically specified at the level of the standard cost type, but it can also be provided when creating an individual cost type.

For more information:

Standard tasks

You can create a catalog of standard tasks to use as templates for new tasks. Standard tasks are independent of projects.

A standard task can link to multiple standard cost types. When you create a task based on a standard task like this, the corresponding cost types are created for your task.

For more information:

Transaction support for Construction

Purchasing transactions can now include information related to subcontracts, and Order Entry transactions can now include information related to change orders, change requests, and Construction contracts.

You can enable these new fields in Purchasing transaction definitions via the API. For Order Entry transaction definitions, use the Sage Intacct UI.

For more information:


Retainage is a portion of the agreed upon contract price deliberately withheld until the work is substantially complete. Amounts can be retained from AP bills or AR customer invoices, then released when ready.

To set the agreed upon retainage percentages, use the RETAINAGEPERCENTAGE parameter when:

Note: You can also use the API to enable retainage on Purchasing transaction definitions. For Order Enty transaction definitions, use the UI.

To release retainages, use the following:

Provide feedback