On March 16, 2018, Sage Intacct will disable the TLS 1.0/1.1 encryption protocols while continuing to support TLS 1.2 and higher for all customers.

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.2 and higher to access our cloud software.

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

How does Sage Intacct use TLS?

Transport Layer Security (TLS) is a protocol that provides security and privacy by encrypting data shared over a network. Sage Intacct uses TLS to secure both browser and Web Services (API) access to our application.

How will users/developers be impacted?

Once Sage Intacct disables support for TLS 1.0 and 1.1, any browser UI access or API call 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 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 under their control can use the following resources:


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

Provide feedback