OTP to OCT integration application guide

About transitioning to NextGen

ONESOURCE Corporate Tax (OCT) is transitioning its content from the Classic version to the NextGen version. This transition includes updating the content template used for ONESOURCE Tax Provision (OTP) to OCT integration.
Assuming that users understand the OCT NextGen transition, this article focuses on the new procedures for OTP to OCT Phase 1.
note
Phase 1 involves transitioning users of OTP to OCT integration from Classic content to NextGen content.
In Phase 2, we introduced an Application Programming Interface (API) between ONESOURCE Tax Provision and Corporate Tax. This API will enable seamless data integration into Corporate Tax, eliminating the need for manual export and import of the Integration Report between the two applications.
Refer to
Import data from ONESOURCE Tax Provision (AU NextGen templates)
 in related links for instructions on how to import data.
While the overall integration process hasn’t changed significantly, we made updates to the import process and associated mapping and import files. We’ve updated these to align with the OCT NextGen templates, providing enhanced integration, additional flexibility, and improved automation within ONESOURCE Corporate Tax.
The primary goal of OTP to OCT integration is to produce the relevant Australian Tax Office (ATO) Forms for lodgment.

This article applies to:

  • Product: ONESOURCE Corporate Tax

Related Content