This release is scheduled to go live on the evening of February 9, 2018 Pacific Time.

Get information about user restrictions

A new, read-only object called USERRESTRICTION allows admins to access information about which users are restricted to given entities or departments.

For more information:

Smart Events and Smart Rules

In previous releases, the body length of Smart Event API actions was limited to 500 characters or less. This has been increased to 5000 characters.

In addition, new IN and NOTIN operators for Smart Event and Smart Rule conditions are available. For example, the following condition checks whether the currency for an AP Bill is specified in USD or INR:


For more, see the information about writing conditions in the Sage Intacct product help.


Version 2 of the Sage Intacct SDK for .NET is now available. The SDK now targets .NET Standard 1.6 in order to support both .NET Framework and .NET Core. Make sure you check out the updated overview and guides that accompany this.


Support for bill in advance

The API now supports bill-in-advance for contracts. You can set bill-in-advance options for specific customers, then optionally override those settings in your contracts. You can also set the options directly for each contract.

For more information, see the ADVBILLBY and ADVBILLBYTYPE parameters on:

Behavior change when posting multiple revenue and/or expense schedule entries

When posting multiple revenue or expense schedule entries, Sage Intacct will now skip any contract with scheduled entries that have errors, then post all other scheduled entries. Previously, when the system encountered an error during post, the process would terminate without posting any of the requested scheduled entries.

Force the Renewal of Contracts

You can now force the renewal of a contract that failed to renew at the scheduled time. For example, this can be useful if you uploaded multiple contracts as part of an integration and want to avoid manually renewing them in the Sage Intacct UI.

For more information:

On March 16, 2018, Sage Intacct will begin to disable support for older versions of the TLS protocol, which encrypts data that is communicated across networks. To enhance security and meet compliance requirements, we are requiring the use of TLS 1.2 and higher for all browser and Web Services (API) access to our cloud software.

Note: Previous communications stated that TLS 1.1 would be supported, but this is no longer correct.

How will users/developers be impacted?

Once Sage Intacct disables support for TLS 1.0 and 1.1, any browser or API access originating from a resource that does not support TLS 1.2 or higher will fail.

What do users/developers need to do?


Ensure that your browser supports TLS 1.2 or higher (most modern browsers do). You can use the following third-party resource to test your browser’s compatibility:


Ensure your application is configured to negotiate connections using TLS 1.2 or higher. Depending on the programming language and OS, the requirements will vary. Some helpful information is provided below, but you should not rely solely on this information and must fully test your code.

Language Info
PHP Ensure your PHP version supports cURL version 7.34.0 or higher
Java Java 8: No action required
Java 7: Explicitly enable support for TLS 1.2 and higher
Java 6: Explicitly enable support for TLS 1.2 and higher
Java 5 or earlier versions: Upgrade to Java 6 or higher and explicitly enable support for TLS 1.2
.NET .NET 4.6: No action required
Earlier versions: Research required changes

Developers who want to test API clients can use the following resources:


The changes required to address the TLS 1.0/1.1 disablement may require help from your IT resources or other resources familiar with your environment. If you are unsure of what is required and would like Sage Intacct to provide additional advice or guidance, we are happy to help. Contact Sage Intacct Customer and Partner Support or your Account Manager. We can put you in touch with Sage Intacct Professional Services who can assist with performing the necessary changes on a fee based engagement

Updates for the 2017-R4.1 release are available.

1099 options for Purchasing

You can now provide 1099 form and box options for vendor invoices at the line level.

For more information:

New updates for the 2017-R4 release are available.

Creating contract invoices

You can now use the API to create invoices for any contracts with billable transactions. You can use filters to preview a set of potential invoices, then execute an invoice run based on that preview.

Depending on how many invoices you have, you can choose to create them online or offline.

For more information:

Ship to contact on sales transaction line items

To accurately calculate sales tax, you might need to use the tax rate associated with the address where the customer will take possession of the products or services. You can now provide different contact names at the sales transaction line level to override the ship to contact name on the transaction itself.

For more information, see the shipto parameter on:

API documentation for legacy functions

This release provides additional documentation for legacy functions—the majority of these functions are now documented.

This release is scheduled to go live on the evening of November 10, 2017 Pacific Time.

Approvals for Purchasing

This release provides new functions to support approvals for purchasing. You can list all purchasing transactions that are ready for your approval, then approve or decline them as needed. You can also get the approval history for a given purchasing transaction.

For more information:


Posting contract expense and contract revenue schedules/entries

With this release, you can post all contract expense schedule entries or contract revenue schedule entries for a given customer (across contracts) or for a given contract. You can also post individual entries according to their record numbers.

For more information:

Hold and resume contract lines and expenses

You can now place contract lines and contract expenses on hold, then resume them when ready.

For more information:

Ship to contact on contract lines

To accurately calculate sales tax, you might need to use the tax rate associated with the address where the customer will take possession of the products or services. With this release, you can provide different contact names at the contract line level to override the ship to contact name on the contract itself.

For more information:

Warehouse transfer enhancements

You can now transfer inventory from a warehouse in one entity to a warehouse in a different entity with a different base currency.

For more information, see the EXCH_RATE_TYPE_ID, EXCH_RATE_DATE, and EXCHANGE_RATE parameters for the following:

Convert by line for Inventory Control and Order Entry transactions

You can now specify the source line of an existing transaction from which to convert. Specifically, sourcelinekey was added to: