Determination Anywhere 2024.05 Release Notes

Release highlights

Release date: August 2024
ONESOURCE Determination version 2024.05 includes bug fixes and introduces the following features:
  • New DA Hub feature.
  • Support activities.

New Features

The topics below describe features added with this release.
DA Hub (1179234, 1233132, 1233133)
DA Hub is an additional, and optional, DA deployment component that acts a middleman between the DA “Mothership” located on the Thomson Reuters (TR) network, and the DA client's deployed on the customer’s network.
Security restrictions on the customer network that prevents direct connectivity with an external/3rd party (TR) network - which is exactly what the DA client needs to operate by pulling content, configuration, and other relevant data from the mothership – justifies the need to have the DA Hub to bridge those connectivity limits. The DA Hub can exist as the conduit to move data from the source (mothership) to the target (DA client) and in reverse (transactional and informational data from client to mothership).
The data elements that the DA Hub manages include:
Data from DA mothership to DA clients:
  • Configurations –
    Custom data managed by the company within Enterprise Cloud Determination.
  • Content –
    Standard tax content periodically released by our Tax Research team.
  • User –
    Relevant users must securely authenticate and authorize through the tax web services and other DA components.
Data from DA clients to DA mothership:
  • Transactions –
    The tax engine will calculate the tax responses, which will then be audited in the Enterprise Cloud Determination database and included in subsequent reporting.
  • Telemetry –
    Error logs and other relevant information captured to troubleshoot and/or monitor the performance of the DA client instances.
The DA Hub could be utilized to cater to the DA clients that are propagated in various geographical areas or specific to different customer business units. Even though 1 DA Hub may be enough to cater to multiple DA client instances, the customer (along with direction from our PS Managed Services team) can implement more than 1 DA Hub based on the various localities of DA clients that those need to liaise with.
DA Transaction Reversal Improvements (1272617)
DA started to support the Transaction Reversals in the previous release (2024.04, see 1173670 and description of reversal process). With that implementation, negative scenarios such as when an original transaction invoice was never received into the audit database while a reversal for it had come through, weren't addressed. In such a case, the reversal invoice would remain in a queue along with other normal invoices (which later get into audit), but then the size of the queue can get large resulting in successful processing of the normal invoices as well.
With this release, we've added a separate queue for the reversal invoices that failed to match with the original invoice in the audit database, so it doesn’t affect the processing of normal invoices. There is a separate service which will reprocess the failed invoices for a certain number of tries, after which will be stored in a separate folder and subsequently added to a failed invoices database table.
Enable Auto Scaling (for non-audits) (1233129)
We've introduced the capability for the DA environment to automatically scale up or down based on seasonal transaction volume demands, eliminating the need for manual intervention.
Please work with the PS Managed Services team to learn more about how this will be achieved for your DA instances.
This capability is currently supported only for those customers who don't audit their transactions – that is, the tax engine-calculated data doesn't come back to the Enterprise Cloud Determination side for storage and reporting – or have disabled the use of Persistent Volumes with DA that temporarily holds such transactional data before syncing it back to the DA mothership.

Fixes

The topics below describe previously known issues fixed with this release.
Configuration Sync of NULL Data to DA (1267578)
There was an issue in the SDI process, with one of the mechanisms used to sync the configuration data created on Enterprise Cloud Determination with DA client instances.
If the database was marked with a NULL entry, when a record is fully deleted from the UI, then the data export process to DA was ignoring it. With similar configurations, the tax result was as expected in Enterprise Cloud, but not in DA. We've corrected this issue so that such data scenarios are supported in future data export and import utilizing SDI.

Related Content