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:


Contracts

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:


On December 15, 2017, Sage Intacct will disable support for TLS version 1.0 and below.

Why?

Sage Intacct takes the security of our customers very seriously. To enhance security and meet compliance requirements, we are mandating the use of TLS 1.1 (and later) encryption technologies to access our cloud software.

What is TLS?

Transport Layer Security (TLS) is a protocol that provides security and privacy by encrypting data shared over a network. TLS is typically used by web browsers and other applications that must securely exchange data. The current available versions of TLS are 1.0, 1.1 and 1.2. Currently TLS 1.1 and 1.2 are considered secure by various security standards organizations.

How does Sage Intacct use TLS?

Sage Intacct uses TLS to secure both browser (user interface) and Web Services (API) access to our application.

How will users/developers be impacted?

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

What do users/developers need to do?

Users

If you are logging into Sage Intacct with a web browser, ensure that your browser supports TLS 1.1 and above (most modern browsers do). You can use the following third-party resource to test your browser’s compatibility:

Developers

If you are a developer or partner using Web Services, you must ensure your application is configured to negotiate connections using TLS 1.1 or above. Depending on the programming language and OS, the requirements will vary. Below is some helpful info for a few popular languages and version. You should still test your code and not solely rely on this information.

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

Developers that want to test API clients under their control can use the following resources:

Support

Do you need help? Contact Sage Intacct Customer and Partner Support.


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

New AP Payment object

This release brings the new AP workbench, only available in Sage Intacct Action, the new user interface. Accompanying the workbench is the new AP Payment object, APPYMT. The API functions for APPYMT let you apply line level credits and discounts for payments, which you cannot do with the existing payment functions. Each credit or discount is stored in an APPYMTDETAIL object owned by the APPYMT object. You can update a payment to add or delete APPYMTDETAIL instances, and you can update the APPYMT object itself, such as by changing the state from draft to posted, changing the bank, and so forth. See the API reference and entity relationship diagram for more information.

The new APPYMT object corresponds with the new Accounts Payable > Pay bills functionality in the Sage Intacct UI, not to be confused with the existing Accounts Payable > Select Bills to Pay functionality.

General Ledger balances

The get_accountbalance and get_trialbalance API functions now support the dimension and reporting book filters already available when running account balance and trial balance reports from the user interface. The response data for these functions also includes the reporting book and currency as well.

Before these filters were available, integration partners had to use the readByQuery API function on the GLACCOUNTBALANCE object for getting comparable information. Because GLACCOUNTBALANCE is the lowest level detail in the system (limited to budgetable periods), such queries might produce hundreds of thousands of records, making it difficult to get basic balances. With the new filters, you can easily get a trial balance for your consolidation book, or look up that one project’s expense account balance on a certain date.

Make sure to check out the Account Balances and Trial Balances API reference pages.

Warehouse transfers

You can now move inventory from one warehouse to another in a single transaction with the Warehouse Transfer object, ICTRANSFER. Before this release, you had to manually create both a transfer-out transaction and a transfer-in using create_ictransaction. Check out the API reference for more information.

Audit trail

The getAuditTrail API function used to require that you set the record’s unique name in the objectKey field, which was problematic because record names take different approaches in objects across the system. You can now provide the record number in the recordNo field instead. Check out the API reference for more information.

Order Entry, Purchasing, and Inventory transactions

Previously, the update functions incorrectly allowed you to change the document number on Order Entry, Purchasing, and Inventory transactions. This is no longer allowed.

More support for attachments in Smart Events and Smart Rules

The SUPDOCID merge field that identifies attachments can now be used in Smart Events and Smart Rules on the following objects:

SDKs

Version 2 of the Sage Intacct SDK for PHP is now available. Make sure you check out the updated overview and guides that accompany this.


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

Postman collection for the Sage Intacct XML API

Do you like the Web Services test tool? If so, you will love Postman. If you aren’t familiar, Postman is a popular API test tool that lets you send HTTP requests to a server and review the responses. Sage Intacct is now providing a Postman collection that you can modify and use to make your XML API calls. You can import this collection into Postman, then easily configure Postman with environments for your Sage Intacct companies.

See Your First XML API Calls to get started.

Note: Google is ending support for Chrome packaged apps, such as the Sage Intacct test tool, which is a good reason to try out Postman now.


New SDK for .NET

A developer preview of the Sage Intacct SDK for .NET is now available. You can interact with the Web Services gateway using C# objects—you no longer need to work directly with the underlying XML API.

You can easily get started with the SDK, then follow up with the SDK Reference documentation.


More Smart Rules and Smart Events in Customization Services

Smart rules and smart events are now supported for roles and user groups in the Sage Intacct UI.


New contracts and revenue management API documentation

API documentation for contracts and revenue management is now available.


Web Services schema changes

Notable features related to schema changes are highlighted below.

If you want detailed information about every schema change, you can diff the schema files for the previous release and the current release after downloading them from the Sage Intacct releases page on GitHub.

Audit trail logs for standard objects

A new getAuditTrail function lets you list the audit trail logs for standard objects.

New read-only fields on order entry objects in Inventory Control

The following read-only fields are now available on Order Entry transactions:

Field Description
PRINTEDUSERID User ID for the user that executed the delivery.
DATEPRINTED Timestamp for the last time the document was delivered (printed or emailed).
PRINTEDBY Record number for the user that executed the delivery.

Exchange rate date and type for same currency transactions

In both AP and AR, the EXCH_RATE_DATE and EXCH_RATE_TYPE_ID fields on currency transactions for the same currency will now be nulled out (they are not relevant anyway).

Source Line Key

You can now specify the source line key of an existing Purchasing transaction from which to convert. Specifically, sourcelinekey was added to the potransitem used by the create_potransaction function.


If you are reading this, you are experiencing the new and improved Sage Intacct Developer website!

While the developer.intacct.com URL remains the same, the content and the experience are new. The site provides more tutorials, new user guides, enhanced API documentation, code samples, SDK documentation, and more!

For starters, check out some of the new content on the site:

Do you have anything to say about the new site? Feel free to give us your suggestions.