Determination Anywhere 2026.01 release notes

Review this release note in conjunction with the Determination – Enterprise Cloud (EC) 2026.01 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).

Release highlights

Determination Anywhere 2026.01 release introduces support for Global Product Group (GPG) in tax content and a consolidated tax endpoint, along with several key enhancements designed to improve security, performance, and usability across the DA platform.

New features

Global Product Group (GPG) Support in DA (4312094 & 4312095)
Starting in 2026, Thomson Reuters IDT tax content will include support for GPG within tax content – covering product groups and related tax regulatory updates. Both EC and DA (Store and Cloud apps) now support the use of this new content alongside the existing product trees across the U.S. and other international jurisdictions.
For more details on GPG, refer to the HELP section in the application UI.
note
To enable GPG in tax content, ensure that DA is configured to receive tax content updates via the CaaS process, as outlined in the DA 2025.06 release notes.
Merged Tax API for Rest Web Service (4351809)
To streamline our tax determination architecture, we have consolidated the previously separate components used by the REST web service–based tax calculation engine. This update reduces system complexity by eliminating the need for multiple containers and unifying these capabilities into a single container, resulting in modest tax calculation performance improvements.
All existing REST tax calculation integrations remain fully compatible. There are no changes to the request payload or response JSON structure. This update applies to the calculate, commit, and reverse REST web service endpoints.
To begin using the merged tax endpoint, please coordinate with your PS team to ensure required DNS or URL updates are applied to your current REST tax calculation web service configuration.
note
These changes do not apply to the SOAP‑based tax calculation web service.
DA Transaction Sync – Retry Handling & Payload Control (4410572)
This enhancement significantly improves the reliability of data synchronization between DA Clients and the Mothership, particularly in environments with strict network constraints. Previously, when DA Clients communicated through proxy or gateway services enforcing rate limits and payload size restrictions, these limitations often caused failed transaction synchronizations.
Enhancements to address this include exponential backoff for retries, gradually increasing wait times between attempts, configurable maximum retry attempts to prevent endless retry loops, payload size controls with automatic splitting of large data packages. These improvements are applied automatically with the update. Administrators may optionally configure the new retry behavior parameters in the DA Overlay to optimize performance for their specific environment.
DA Client – PostgreSQL Upgrade (4297051)
To ensure optimal performance, security, and access to the latest features, the PostgreSQL database inherent within the DA app has been upgraded from version 15.x to 17.5.
This upgrade ensures your DA environment runs on the latest stable database technology, providing improved performance, enhanced security patches, and access to the newest PostgreSQL features.
Advanced Authentication – DA Client to Mothership on AWS (4311999)
For DA Mothership components running on AWS, authentication between DA Client components and the DA Mothership previously relied on Cognito-based authentication. However, basic authentication credentials are easily decoded and provide limited protection against unauthorized access.
To enhance security, APIGEE-based authentication has now been introduced, offering client-side token generation, rate limiting, and alignment with TR’s enterprise security standards.
Both AWS and OCI environments (OCI support introduced in DA 2025.04) running DA Mothership now support this advanced authentication mechanism.
Data Residency – S3 Object Tagging (4805592)
Data Residency enablement in DA generates Avro files in the customer’s object storage (specifically S3). In the DA 2025.06 release, metadata tagging for certain invoice data elements was introduced using the modern S3 Metadata API (see reference 4447641 in that release note). However, some customers experienced compatibility issues because their existing systems relied on the classic S3 Tags API, creating gaps in data processing workflows.
To address this, the Transaction Sync Client now supports attaching custom metadata using either the S3 Tags API or the Metadata API. A new configuration option,
s3MetadataAsTags
, allows switching between these methods, with S3 Tags as the default when data residency is enabled.
note
Further details about tagging can be found here. Be aware of tag restrictions, as non-compliance may impact transaction sync back to TR.
DA Client – Add Custom HTTP Headers to Token Generation Requests (4623579)
Previously, DA client components supported custom HTTP headers for Mothership endpoints but lacked this capability for token generation requests (Cognito and Apigee). This limitation prevented customers with strict proxy requirements from properly authenticating their proxy configurations.
With this update, the existing custom header mechanism now extends to include Cognito and Apigee token generation requests, ensuring that custom headers sourced from Kubernetes secrets are correctly applied across all token authentication flows.
Improved Configuration Data Reconciliation Process (4560217)
When errors occur during the full data sync process, a reconciliation workflow may be triggered to automatically clean up invalid data on the DA client. This ensures that configuration data remains consistent between Enterprise Cloud and DA, helping maintain accurate tax calculations based on customer‑defined settings. However, this reconciliation process previously took several hours to complete for customers with large data volumes, making it a time‑consuming step.
We have significantly optimized the performance of the reconciliation process, reducing execution time from hours to minutes. To ensure this enhancement is enabled in DA, confirm that the following setting is included in the Overlay file (it may already be present by default):
sdi.importstate.experimentalFeatureEnabled: true
Combined with the SDI performance improvements delivered in the DA 2025.06 release (4608354), customers can now complete the SDI process much faster, especially in environments where data volume was previously a bottleneck.
note
We plan to replace the current SDI process with an enhanced full data sync mechanism, which will eliminate the existing sync‑related errors altogether.
Enhanced Logging & Improved Error Messaging for Streaming Sync Process (4906599)
When the DA Client version does not match the DA Mothership version, the tax content streaming sync is automatically paused. This typically occurs after a new release is deployed to the Enterprise Cloud, while the customer’s DA Client has not yet been upgraded. Previously, the sync errors displayed during this version mismatch were not descriptive enough – especially for GPG content – making troubleshooting more difficult.
This update introduces clearer, more specific error messages to help users understand the root cause of version mismatch issues. The enhanced logging provides better visibility into why the sync was paused and assists in faster issue identification and resolution.
DA Dashboard UI – Role Based Access Control (4482714)
Previously, DA Dashboard sync configuration features lacked proper role-based access controls, which could allow users to perform actions beyond their authorized permissions. This created security concerns and confusion when users attempted operations they weren’t authorized to perform.
With this update, we’ve implemented comprehensive role-based access controls to ensure users can only access features appropriate to their assigned roles:
  • Dashboard Visibility – the DA dashboard is viewable by all user roles – Power User, Standard User, View-only User, DA Support User, and DA Tenant Administrator (first three are tenant-level roles).
  • Sync Configurations button – visible only for DA tenants where streaming-based configuration sync is enabled.
  • Review Changes Then Sync button – access is limited to users with DA Tenant Administrator or DA Support roles, and only when on-demand sync is enabled for their tenant.
  • Clear Error Messaging – added explicit error messages when users lack permissions or when features aren’t enabled for their tenant.
DA Version Control UI – Role Based Access Control (4482727)
Previously, the DA Version Control screen lacked proper access controls, creating risks of unauthorized changes and user confusion.
With this update, version data is visible to all users, while management actions are restricted to authorized roles:
  • Screen Visibility – is limited to tenants with the DA Store app instance enabled.
  • Version Data – is viewable by all user roles, but action buttons are restricted to authorized roles.
  • Status Information – displays appropriate status based on the tenant’s push mechanism (dynamic or version control.
  • Action Restrictions – Action buttons are available only to users with DA Support or DA Tenant Administrator roles when version control is enabled.
  • Clear Error Messaging – added clear error messages for unauthorized access attempts.

Fixes

The following topics outline previously identified issues that have been resolved in this release.
SDI Configuration Sync Issue (4441078)
An issue was identified during configuration data synchronization using SDI, where the process terminated with errors due to duplicate key violations in the database. This prevented proper import and synchronization of critical tax data, causing workflow disruptions.
The error occurred when processing records with identical external tokens, which violated the database’s unique constraint requirements. This issue has now been resolved, ensuring smooth synchronization and uninterrupted workflows.
Streaming Configuration Sync Issue (4764405)
An error occurred during configuration data synchronization using streaming due to missing references in the configuration dataset on the DA Client side. This resulted in corruption of the import state for the affected dataset.
The streaming process has been updated to automatically trigger a full SDI sync whenever missing references are detected, ensuring data integrity during future synchronizations.
High Security Vulnerability Remediation (4312100)
We’ve successfully addressed high-severity vulnerabilities identified during internal security scans across components related to data and transaction sync, telemetry and authentication, as well as decommissioned unused repositories related to standard content and config sync.
These targeted security enhancements significantly bolster the integrity of the DA platform and the protection of customer data. By proactively resolving these issues, we’ve mitigated potential risks, reinforced compliance with industry security standards, and strengthened the overall security posture of our tax determination environment.

Related Content