Determination Anywhere 2026.06 third patch release notes

This patch is specific to Determination Anywhere and does not include corresponding Determination – Enterprise Cloud changes.

The following DA components have been updated in this patch release.

All other components retain the versions communicated in past release notes

Thomson Reuters recognizes that security vulnerabilities in software deployed within our own environments, or within our customer environments can pose significant risk. We conduct daily vulnerability scans of ONESOURCE Determination application code and dependencies. ONESOURCE Determination Anywhere container images are scanned daily to identify and remediate security vulnerabilities. While we strive to address zero-day vulnerabilities as rapidly as possible, remediation timelines follow the Thomson Reuters Information Security & Risk Management (ISRM) guidelines based on severity classifications identified by our scanning tool, Snyk – Critical (30 days), High (60 days), Medium & Low (best-effort basis in a future release). If vulnerabilities are found after software is released, Critical issues are fixed through urgent Production releases or in the next scheduled release cycle. We aim to uphold our commitment to providing secure solutions.

This third patch for Determination Anywhere (DA) 2026.06 addresses several issues identified following the major release.

The following topics outline identified issues that have been resolved in this release.

The upgrade process has been updated to automatically restart the tax calculation pods if database schema changes are present in Delta dB, ensuring their database connections are refreshed.

These changes help ensure upgrades complete smoothly, minimizing the risk of calculation failures or service interruptions and eliminating the need for manual intervention.

No customer action is required after the upgrade to this patch version.

With this release, DA resolves an issue that could cause the Transaction Sync Calc History client to stop shortly after startup following an upgrade to version 2026.06. The issue was caused by a missing Java library dependency, which prevented calculation history files from being uploaded to the DA Mothership endpoint.

The required dependency is now included and supporting HTTP client libraries have been updated and validated for compatibility. The Transaction Sync Calc History client now starts reliably and maintains synchronization of calculation history files without requiring manual restarts.

No customer action is required after the upgrade to this patch version.

With this release, DA resolves an issue where archive tables in the client database could remain empty after a specific Content Throttling version was selected in Enterprise Cloud UI and the configuration was synchronized to DA.

The synchronization process has been updated to correctly populate the archive tables and transfer the applicable historical tax content. This update enables Content Throttling to reliably use archived tax content for tax calculations on the client side.

No customer action is required after the upgrade to this patch version.

With this release, DA Store improves the reliability of tax content synchronization for store deployments operating at large scale. Previously, when multiple stores synchronized concurrently, some store sync pods could fail to download required cache files from the DA Hub.

The issue occurred when concurrent download processes removed files still required by other active downloads or when cache files were unnecessarily recreated and became temporarily unavailable. The synchronization process has been updated to protect active and completed downloads and to avoid recreating cache files when the underlying tax content has not changed. Error handling and logging have also been improved to support troubleshooting.

These changes provide more reliable and automated tax content synchronization across large-scale store deployments.

No customer action is required after the upgrade to this patch version.

The topics below describe known issues in this release.

In environments with multiple tax calculation (tax-calc) pods, some tax calculation requests may intermittently return a NO_ZONE_TREE_MATCH error (“No Matching Zone Tree was found”).

This issue is related to the clustered cache feature introduced in the 2026.04 release and affects customers with this feature enabled. Clustered cache invalidation may not be applied consistently across all tax-calc pods, causing a small number of pods to handle state/ZIP conflicts differently. As a result, the same tax calculation request may produce different results depending on the tax-calc pod processing the request.

This issue is planned to be resolved in a future release.