Determination Anywhere 2025.05 release notes
Read this release note alongside the Determination release notes, which give updates to the core tax engine, which includes logic modifications and regulatory adjustments. These updates extend to the tax engine within Determination Anywhere.
note
We have changed the terminology beginning with this release. References to the PS Managed Services team for DA implementation support will now be replaced with Edge Technology Services (ETS).
Release highlights
With the release of Determination Anywhere version 2025.05, we’ve introduced several key enhancements such as an enhanced dashboard, and a user-controlled mechanism that has been implemented for managing content and configuration updates. Updates specific to the DA Store app are clearly labeled, while all other changes apply to both the DA and DA Store apps unless explicitly stated otherwise.
New features
Determination Anywhere Dashboard (1340157)
We’re excited to introduce a redesigned Determination Anywhere (DA) Dashboard in version 2025.05, offering a more comprehensive and user-friendly interface for monitoring and managing DA instances. This enhancement delivers improved visibility into a DA client instance, such as sync updates, pod details, Hub information, etc.
The enhanced dashboard can be viewed on . All customer tenants with DA licensed or enabled will automatically see their DA details reflected in the new dashboard.
note
The previous DA dashboard used to be at . This has been removed from
Help
.
Further information about the Dashboard is outlined in the Determination Anywhere section of Help ().
DA Store App – UI for Version Controlled Tax Content and Config Sync (1714513)
In the previous release of DA Store app, we introduced backend controls for managing the versions of content and configuration synced to it (refer 1375879). In this release, we’ve expanded that capability by providing a user interface (UI) for version control.
The new Version Control screen, accessible from the Determination Anywhere menu, allows administrators to view all available content and configuration versions, mark versions for testing prior to activation for production use, and reactivate an archived version if needed. User access will be limited based on appropriate Roles.
note
By default, content and configuration changes will continue to sync automatically to the DA Client based on the configured schedule. To use the version control feature, it must be explicitly enabled for the tenant. Please work with the ETS team to enable this feature.
Further information about the UI is outlined in the Determination Anywhere section of Help ().
Java Update to Version 21 (1733714)
To maintain compliance with current standards and proactively mitigate potential security vulnerabilities, we are upgrading the Java component used across multiple areas of the DA application to v21. This update enables DA to leverage enhanced performance, security features, and long-term support offered by Java 21.
DA Client Sync – Enable Proxy to TR Mothership (1649181)
This feature enables DA client(s) to connect to Thomson Reuters Mothership through corporate proxy servers – ideal for customers operating in restricted network environments. Customers can now configure custom HTTP headers required for proxy authentication, ensuring DA Client components can communicate with external services when direct internet access is restricted.
New options in the installer overlay allow specification of custom API headers as key-value pairs, while sensitive header information is securely stored using Kubernetes secrets, DA Client components are updated to support adding custom headers to all outbound requests. This support is implemented across multiple components including Transaction Sync Client, Tenant Data Sync Client, and Telemetry Client.
Customers who need to connect through a proxy server should work with their TR ETS team to configure the appropriate custom HTTP headers in the installer overlay. These headers must be specified as key-value pairs based on your organization’s proxy authentication requirements.
DA Overlay Extension - Additional Volume Mounts (1720680)
This feature enhances the flexibility of DA deployments by allowing customers to mount additional volumes, config maps, and secrets to containers.
Previously, specialized configurations – such as self-signed Docker registries or custom monitoring tools – required manual edits that were lost during system updates.
Organizations with unique security setups, infrastructure needs, or monitoring solutions can now maintain their custom configurations reliably and persistently. By eliminating the need for manual reconfiguration, this feature improves system reliability and streamlines ongoing maintenance.To configure the appropriate overlay parameters for your environment, please consult your ETS team member.
Database Connection Management Enhancement (1731983)
We’ve implemented a critical update to DA that resolves issues related to database connection exhaustion in environments with multiple PgPool replicas.
In previous versions, over time, idle connections were not being properly released, leading to connectivity issues that could affect critical services like Tax Determination Sync Service (TDSS) and potentially result in entity state corruption requiring data reconciliation.
There is now a new process that regularly clears unused database connections to maintain optimal performance. This improvement prevents connection exhaustion and ensures stable connectivity across services. Database resources are now more efficiently managed, especially in environments with high transaction volumes or multiple replicas.
Fixes
The topics here describe previously known issues fixed with this release.
DA Data Sync Issues – Switch between SDI & Streaming (1795563)
We’ve resolved a critical issue in DA related to the data synchronization process, specifically during transitions from SDI to the streaming synchronization methods.
Previously, some change events were being skipped when the system switched between synchronization modes. This could result in inconsistent tax data across systems and potentially impact tax determination accuracy.
These improvements significantly enhance data integrity, ensuring that tax determinations are based on complete and accurate information. We have enhanced the data streaming mechanism to ensure seamless transitions between SDI and standard sync methods. Change event tracking has been strengthened to guarantee complete data capture across all synchronization scenarios.
TransEditor Sync Issue with Streaming (1806652)
An issue was identified where changes made in TransEditor (TE) within the cloud environment were not reflected in DA, resulting in inaccurate tax calculations. The root cause was traced to an incorrect sequence of change log entries, which the system relies on to detect, capture, and sync changes.
A fix has been implemented to ensure that all change events are logged in the correct order, preventing skipped entries and enabling accurate synchronization with DA.
Note: There are known issues with the streaming configuration sync process when data is saved via the Enterprise Cloud UI. One such issue is documented near
Known Issues
. We plan to address all outstanding items in the next major DA release.HTTP 502 Error Resolution (1742816)
We’ve resolved an issue that caused HTTP 502 errors during system maintenance and updates. These errors occurred when the load balancer attempted to route traffic to tax calculation service pods in AWS environments that were in the process of shutting down or starting up, resulting in temporary service disruptions.
To address this, we implemented improved pod lifecycle management to ensure clean service termination, enhanced coordination between the load balancer and application pods during rolling updates, and optimized readiness and liveness probe configurations to prevent premature traffic routing.
This will significantly improve system stability during maintenance windows. Customers can expect fewer service interruptions and error messages during routine platform updates.
API Rate Limit Configuration for Data Sync (1780753)
This standardizes the implementation process for DA APIGEE endpoints to prevent Configuration Sync and Transaction Sync failures caused by insufficient API rate limits or rate throttling and access issues.
Implementation teams must adhere to the documented setup process outlined in the Determination Anywhere section of Help () when configuring Apigee endpoints. This includes accurate user creation, appropriate role assignment, and rate limit configuration aligned with environment-specific recommendations.
Security patch update in OCI Load Balancer (1468430)
We’ve implemented a security enhancement to address vulnerability in our OCI load balancers, where non-secure listeners were detected. As these load balancers manage all incoming traffic to DA services, securing them is essential to maintaining overall system integrity.
Key improvements include enforcing secure SSL/TLS protocol versions across all OCI load balancers, configuring valid SSL certificates for all load balancer listeners, and eliminating non-secure communication channels to strengthen the security posture.
With this update, all traffic to and from Determination Anywhere is now fully encrypted, ensuring secure communication and enhanced protection for customer data.
Known issues
PostgreSQL Security Vulnerability Remediation (1778980)
We have identified security vulnerability in the PostgreSQL database used by DA. To address this, we will upgrade PostgreSQL from version 16.2 to 17.5. This update will enhance system integrity and reinforce protections for the database.The new version will be released outside of this standard release cycle. Once it’s available, we’ll notify the ETS team. Please coordinate with your ETS team to complete the upgrade.
DA Config Sync Streaming Issue – Filters (1797266)
This issue has already been documented in the DA 2025.04 hot fix release notes.
A known issue has been identified affecting the maintenance of filters within the following configurations – TransEditor, ERP Code Mapping, Conditional Mapping, Allocations, Rules, and Rule Qualifiers.
When multiple condition changes – such as adding, reordering, deleting, or modifying – are performed in combination and then saved, the synced data in DA may not reflect the correct order as displayed in the Determination UI. This discrepancy can impact tax result accuracy.
This issue is scheduled to be resolved in the next major release of DA. Until the fix is released, the best practice when making filter condition changes via the Determination UI is to save after each individual action. For example, if you intend to add a new condition, delete an existing condition, and reorder the new condition to the top, then follow these steps:
- add the new condition -> click Save.
- delete the desired condition -> click Save
- reorder the conditions -> click Save
Related Content
-
Determination Anywhere
Format:
Article,
1 min read
-
Determination Anywhere 2025.04.05 hot fix release notes
Format:
Article,
3 min read
-
Configure apigee endpoints
Format:
Article