SuiteTax and SOAP Web Services

SuiteTax and SOAP Web Services Banner

Table of Contents

NetSuite Updates – SuiteTax and SOAP Web Services.

Recent mPower blogs have focused on new capabilities being introduced in NetSuite including the strategy around AI and pathway to leverage AI with NetSuite Next, the generation of NetSuite (Please see our October Newsletter for additional information). There are also some items being deprecated by NetSuite we wanted to make you aware of, so you have plenty of time to address in your NetSuite instance. The two features being deprecated are Legacy Tax and removal of SOAP web services.

SUITETAX

NetSuite will be transitioning from Legacy Tax to SuiteTax as the primary tax solution in SuiteSuccess editions, starting with North America (NOAM).  The rationale for NetSuite is that it will help keep pace with evolving industry standards, reduce maintenance, and provide a single, modern solution as part of NetSuite Next.

All NOAM SuiteSuccess editions have been tested with SuiteTax and are ready for deployment, offering improved performance, enhanced security, and scalability.  For any new implementation, it is currently planned to have SuiteTax be the default configuration by the end of 2025. Currently, there have been no announcements related to transitioning existing customers from Legacy Tax to SuiteTax. However, more detailed information related to existing Legacy Tax customers should be provided during the 2026.1 and 2026.2 NetSuite Releases.

SOAP REST SERVICES INFORMATION

NetSuite has scheduled the gradual removal of SOAP web services as part of ongoing efforts to provide modern integration channels. Additional information behind the decision includes:

  • SOAP does not support the latest business features and new records have not been made available to SOAP for a couple of years.
  • SOAP does not support modern architecture standards like the most up-to-date architecture, SuiteAnalytics Workbooks and SuiteScript 2.x Analytics APIs.
    SOAP still uses token-based authentication, which is not consistent with other Oracle products and does not meet modern security standards.

While SOAP Rest Services will be gradually removed, the technology intended to replace SOAP is SuiteTalk REST web services.

  • Most functional use cases implemented using SOAP can already be implemented using REST web services.
  • Investment in REST API has been made to achieve functional parity with SOAP, and there are plans to fill any remaining gaps in upcoming releases.
  • For specific scenarios where REST web services cannot be used, it is possible to use SuiteScript RESTlets.

Currently, the planned changes to SOAP Rest Services by release include:

2026.1

  • No new SOAP endpoint is planned for the 2026.1 release. The 2025.2 SOAP endpoint is the last planned SOAP endpoint and any later SOAP endpoints would be released only as necessary to meet business, technical, or other significant requirements.
  • All newly built integrations should use REST web services with OAuth 2.0 for authentication.
    2027.1
  • All newly built integrations must use REST web services with OAuth 2.0.
  • Token-based authentication in REST will still be supported, but it will be highly recommended to use OAuth 2.0 instead.

2027.2

  • Only the 2025.2 SOAP endpoint will be supported. All earlier endpoints will no longer be supported.
  • SOAP will continue to be available, but potential bugs in SOAP will be fixed only in the 2025.2 endpoint.

2028.2

  • SOAP will no longer be available for any integrations with NetSuite.
  • Existing SOAP integrations with NetSuite will stop working.

If you’re using SOAP-based integrations, consider the following:

  • For any custom integration applications that you have developed using SOAP, you should start planning the migration of your solution to REST as soon as possible.
  • Get familiar with SuiteTalk REST web services and OAuth 2.0 authentication.
  • Do not wait for 100% parity of REST with SOAP. Consider using SuiteScript RESTlets when an object or method is not available in REST web services.
  • If have a partner that uses SOAP application to integrate with NetSuite, consult with them to provide you with a REST-based application instead.
  • If you use an Oracle NetSuite integration application, a REST-based application will be provided in time by NetSuite.

If you have questions about SuiteTax or SOAP Rest Services, contact your mPower contact to receive further information or assistance in planning for the upcoming NetSuite improvements. NetSuite will have more announcements and updates as it prepares for the next generation of NetSuite, NetSuite Next. If you would like more information, reach out to your Meridian Business contact or email Meridian at mpower@meridianbusiness.com.