Determination Anywhere 2026.03 release notes
Please review this release note in conjunction with the Determination – Enterprise Cloud (EC) 2026.03 release notes, which outline key updates to the core application. These include enhancements to the tax engine logic, regulatory compliance improvements, UI feature upgrades, and may also highlight defect resolutions and known issues – all of which directly impact the tax engine's functionality within Determination Anywhere (DA).
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.
Release highlights
Determination Anywhere (DA) 2026.03 release introduces an enhanced configuration sync process, along with several key enhancements designed to improve security, performance, and usability across the DA platform.
New features
Bulk Import – Enhanced Bulk Configuration Sync Process (4613812)
DA uses two synchronization mechanisms to move configuration data from Enterprise Cloud to DA client environments. A streaming sync process handles incremental changes as they occur, while a bulk sync process is used to transfer the full configuration dataset – including certificates – typically when streaming is unavailable. Historically, the bulk sync relied on the SDI process, which is slower and has introduced data consistency challenges due to its underlying behavior.
This feature enhancement significantly accelerates configuration synchronization for DA, boosting sync performance by roughly 95%, shortening processing time from hours to just minutes, and offering a more dependable and scalable approach. It’s called “Bulk Import” and can be configured to replace the SDI process. It will also work in parallel with the streaming process, same as SDI was set up.
Bulk Import simplifies config synchronization by using configuration database IDs consistent between the Mothership and the client environment. This results in a "canonical" (exactly matched) replica, effectively removing an entire category of data-related problems. As such, there are some changes the customers need to make to their setup before the process can be used for operations. Please work with your ETS representative to get this setup completed so that the data sync process becomes faster but more importantly reliable.
OCI MENA Region Enablement (4976368)
ONESOURCE Enterprise Cloud Determination is now available on Oracle Cloud Infrastructure (OCI) in the Middle East and North Africa (MENA) region. Customers in this region now have access to the same capabilities previously available on AWS in AMER and EMEA, as well as OCI in AMER.
This expansion helps customers meet local data residency requirements by keeping data hosted within the MENA region on Enterprise Cloud. Customers can continue to connect to Determination Anywhere (DA) client deployments across supported platforms, as previously available, while benefiting from a localized DA Mothership for regional connectivity with their DA tax engine deployments.
Logging Optimizations to Improve Transaction Performance (5223387)
This release improves transaction performance by reducing unnecessary background logging during tax calculations. Selected log statements previously written at the INFO level have been moved to DEBUG, minimizing logging overhead.
As a result, customers can expect faster transaction processing, more efficient resource utilization – particularly in high‑volume environments – and cleaner, less verbose logs, making troubleshooting easier and more effective.
DA Det Calc Startup Optimization (5039372)
Previously, tax calculation pod initialization took approximately four minutes per pod, impacting rolling restarts, environment startup timelines, and overall deployment efficiency.
In this release, the tax calculation service startup process has been optimized and streamlined, reducing typical startup time by approximately 80%, to well under one minute. This improvement enables environments to come online faster, shortens maintenance windows, and reduces downtime risk during scaling or recovery operations
To enable this enhancement, customers must set the property
spring.main.parallel-initialization=true
at deployment time in either application.properties
or determination_application_overrides.properties
.DA App Installer & Overlay Enhancements (5035769)
In this release, the DA installer and overlay framework have been enhanced to provide greater flexibility for customer‑specific configurations. Key improvements include:
- Removal of hardcoded values (such as runAsUser and fsGroup) from the installer, enabling configuration through overlays.
- Added OpenShift compatibility by supporting dynamic UID assignment while maintaining functionality across all supported cloud platforms.
- Decoupled image pull secret refresh from auto‑update functionality, preventing credential expiration during maintenance windows.
- Extended overlay support to include custom service types, StatefulSet naming, and Infinispan cache configuration.
Added support for pulling charts and images from customer‑managed artifact repositories, with flexible authentication options.
DA Data Residency – Avro File Enhancement (5229016)
The Data Residency feature in DA generates Avro files and stores them in the customer’s cloud object storage for use in customer‑managed reporting solutions. Previously, the Avro files generated were incomplete, with some data fields missing values or showing inconsistencies when compared to tax calculation results.
This release addresses those gaps to ensure that all transaction details – including amounts, tax breakdowns, addresses, and compliance information – are fully populated and accurately aligned with the tax calculation response. As a result, customers receive reliable and complete data for reporting, analytics, and compliance purposes without requiring additional data transformation.
This enhancement is supported by accompanying documentation that maps Avro data fields to their equivalents in the tax engine XML response (produced by the SOAP tax calculation service) as well as the corresponding database table columns in the legacy Determination application, particularly helpful for customers transitioning from our legacy reporting solution. The documentation is available upon request.
Future updates to the documentation will include mappings for JSON response fields produced by the REST tax calculation service.
DA Data Residency and Transaction Sync Improvements (5209179)
In environments where dual transaction sync mode is enabled – supporting both data residency and audit – some invoices processed by the tax calculation engine were not consistently transmitted to the customer’s cloud object storage. This behavior could also then result in missing transaction records within Thomson Reuters reporting.
This release introduces enhanced logging to better monitor and detect such missing transactions. In addition, an optional capability has been added to allow invoice audit AVRO files to be named using the source_sync_id (UUID) instead of the default ULID, when the tax calculation profile
export-destination-filename-gen-uuid
is enabled. If this profile is not enabled, ULID‑based file naming remains unchanged and fully supported. When enabling UUID‑based naming, customers must also update the transaction sync client (invoice/audit invoice container) with the following configuration
transactionSync.fileManager.pattern
: “(?:[0-7]{1}[a-hj-km-np-tv-zA-HJ-KM-NP-TV-Z0-9]{25}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})\\.avro”. For DA Hub it would be transactionSync.fileManager.invoice.pattern
:"(?:[0-7]{1}[a-hj-km-np-tv-zA-HJ-KM-NP-TV-Z0-9]{25}|[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12})\\.avro".DA Store – Support Config Sync Service as a K8s Cron job (5118526)
We introduced an
optional
scheduled run mode for the config sync service on the DA Store app so it can run on a defined timetable instead of running continuously. This is enabled through a configuration setting (default behavior remains unchanged), and in scheduled mode the service completes one sync run and then stops with a clear success/failure outcome. This approach can reduce always‑on resource usage while keeping data updates predictable and easier to operate. In scheduled mode, only the Lite Sync component runs; telemetry and transaction‑sync components are not included (a future enhancement will add a best‑effort telemetry push after sync). No action is needed unless you choose to enable the scheduled run mode suing below mentioned property
sync.lite.executionMode property (deployment default, cronjob optional).
In this release, the tax calculation service startup process has been optimized and streamlined, reducing typical startup time by approximately 80%, to well under one minute. This improvement enables environments to come online faster, shortens maintenance windows, and reduces downtime risk during scaling or recovery operations
To enable this enhancement, customers must set the property
spring.main.parallel-initialization=true
at deployment time in either application.properties
or determination_application_overrides.properties
.DA Store – Support for Init Containers (5254994)
Introduced support for custom initialization containers that run before the primary sync and calculation containers. This enables integrations with custom APIs and other pre‑startup processing requirements.
- Added support forextraInitContainersto enable custom pre‑start logic
- ImplementedsharedInitVolumesto allow data sharing between initialization and main containers
Please work with your ETS representative to configure this feature based on your specific requirements.
Determination Anywhere Hub – UI (4311621)
DA Hub is an optional component that can be deployed within customer‑managed infrastructure. It is intended for customers with strict security requirements that restrict direct network connectivity between DA client instances and the Thomson Reuters–hosted DA Mothership.
For customers who do not transmit DA client telemetry data back to the TR Mothership, the existing DA Dashboard in Enterprise Cloud is not available. When DA Hub is deployed, the same dashboard functionality is now available locally within the customer environment.
Please work with your ETS representative to manage access to the DA Hub dashboard.
Fixes
Security Vulnerability Remediation (4696493)
This update addresses critical and high‑severity security vulnerabilities identified in the DA client‑side application, further strengthening the overall security posture of the platform.
Key remediation actions include:
- CVE-2026-22732 – Critical vulnerability in Spring Security Web that could allow sensitive information to be cached in HTTP response headers
- CVE-2024-22259 – Critical cache-related vulnerability in Spring Security Web that could expose sensitive information
- CVE-2026-22733, CVE-2026-22731, CVE-2023-20873 – Authentication bypass vulnerabilities in Spring Boot Actuator components
- CVE-2026-22737, CVE-2024-38739 – Directory traversal vulnerabilities in Spring WebMVC and WebFlux
- CVE-2026-24400 – XML External Entity (XXE) injection vulnerability in AssertJ Core testing library
- CVE-2026-1605 – Resource allocation vulnerability in Jetty Server that could result in resource exhaustion
- CVE-2025-55163 – Resource allocation vulnerability in Netty HTTP/2 codec
- CVE-2025-58057 – Data amplification vulnerability in Netty HTTP and HTTP/2 codecs
- CVE-2025-58056, CVE-2026-33870 – HTTP request smuggling vulnerabilities in Netty HTTP codec
- CVE-2026-33871 – Resource exhaustion vulnerability in Netty HTTP/2 codec
- CVE-2026-24308 – Sensitive information exposure in Zookeeper logs
- CVE-2026-24281 – Improper certificate validation in Zookeeper
- CVE-2025-41242 – Relative path traversal vulnerability in Spring Beans
- CVE-2025-41249 – Incorrect authorization vulnerability in Spring Core
- CVE-2025-48989 – Improper resource shutdown in Tomcat embedded core
- CVE-2025-55752 – Relative path traversal vulnerability in Tomcat embedded core
- CVE-2026-24734 – Incorrect authorization vulnerability in Tomcat embedded core
- CVE-2025-8671 – Denial of service vulnerability in Apache HttpComponents Core5
Telemetry Client DB PGPool Connection Reset Errors (5254465)
This release addresses intermittent “connection reset” errors in the telemetry service caused by database connections remaining open longer than expected, occasionally resulting in service disruptions.
The telemetry service has been updated to use the platform’s standard database connection management, ensuring idle connections are refreshed safely and do not become stale. This enhancement improves overall system stability and reduces the likelihood of similar connection‑related issues going forward.
Telemetry Client error with Apigee client secret authentication (4955992)
When using Apigee OAuth with client secret, some DA client applications (e.g., telemetry) could fail to start unless additional placeholder (“dummy”) settings were provided as a workaround.
This release updates the client authentication setup so those extra values are no longer required for client‑secret mode, reducing configuration complexity and improving startup reliability. No customer action is needed beyond upgrading to this release.
Related Content
-
Determination Anywhere
Format:
Article