Determination Anywhere 2025.06 release notes
Release highlights
note
Review this release note in conjunction with the Determination – Enterprise Cloud (EC) 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).
Determination Anywhere (DA) version 2025.06 introduces support for Content-as-a-Service (CaaS), enhancing TR’s ability to deliver content through accelerated release cycles. This update also resolves previously reported application defects, reinforcing our commitment to performance and reliability.
New features
The following topics outline the new features introduced in this release.
Content-as-a-Service (CaaS) Support in DA (1744175)
With the release of DA version 2025.06, tax content delivery transitions from the legacy Blue Customer Center (BCC) to the modern Content-as-a-Service (CaaS) model. This strategic shift supports the phased retirement of BCC while enabling seamless content delivery to DA clients and unlocking future tax content innovations that were not feasible under the legacy system.
note
The transition to CaaS occurs automatically with the DA 2025.06 update. To ensure uninterrupted access to new tax content, customers must have the Tenant Data Sync Streaming (TDSS) component enabled. Without TDSS, clients may no longer receive content updates once BCC is decommissioned.
Coordinate with your PS ETS team to confirm TDSS is active in your DA instance and safeguard against any disruption in tax content delivery.
Data Residency Avro file – Check Sum & Custom meta data tags (4447641)
Avro files stored in Cloud Object Storage (S3) now support industry-standard checksums to ensure data integrity. The following checksum algorithms are currently supported – crc32, crc32c, crc64nvme, sha1, sha256. This functionality is configurable via
s3CheckSumAlgorithm
overlay setting under dataresidency
in the transactionSyncInvoices.yaml
file.Additionally, metadata tagging is supported for the following invoice elements in the generated Avro file – H
ost_System, Calling_System_Number, External_Company_ID, Company_Role, Invoice_Number, Invoice_Date, Unique_Invoice_Number (combination of External_Company_ID||Invoice_Number||Company_Role), Merchant_ID,
and Is_Reversed
. One or more of these tags can be configured using the s3Metadata
overlay setting under dataresidency
in the same yaml file.Remove redundant URLs in Helm Charts (4350209)
The hub-cloud-sync helm charts contained redundant URL configuration fields that were initially needed when different authentication methods were used for different operations, but are no longer required with unified apigee-auth. We have removed redundant URL configuration fields –
apigeeURLPrefix
and mothershipURLPrefix
– and eliminated the dependency on the devportal
flag.Customers will experience simplified configuration management with fewer required fields and reduced potential for configuration errors when deploying or updating DA clients.
note
Review and update your helm chart values if you've been explicitly setting the now-removed fields.
DA Client to Mothership authentication – expiration time limit (4352038)
The deta-app-c-lite-sync application had a hardcoded JWT expiration time of 30 minutes, which exceeded the maximum allowed time for production environments (10 minutes), causing authentication failures. We have now made
jwt.expiresIn
configurable through overlay files.Customers can now successfully authenticate to the mothership in production environments without experiencing timeout errors, while maintaining appropriate security timeouts.
note
For production environments, ensure jwt.expiresIn is set to '10m' in your configuration overlay; for non-production environments this can be set to 30 minutes.
Fixes
The following topics outline previously identified issues that have been resolved in this release.
Configuration Sync Issues with Streaming (1794053)
This version resolves a known issue in previous DA versions (1797266) that caused inconsistencies in tax calculation results between the DA and EC tax engine platforms. The discrepancies stemmed from configuration synchronization issues related to the streaming feature, which led to unpredictable tax outcomes across DA instances within the same tenant.
With this fix, customers can confidently make configuration changes, knowing that tax engine results in DA are now consistent and reliable. We recommend validating changes with the streaming functionality enabled and reporting any anomalies to TR. Our team is committed to resolving high-priority issues promptly to ensure continued accuracy and compliance.
High Security Vulnerability Remediation (1798895)
We’ve successfully addressed high-severity vulnerabilities identified during our internal security scans, specifically within the telemetry component (
a208262_deta-app-c-telemetry
) and the hub cloud synchronization component (a208262_deta-app-c-hub-cloud-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.
PostgreSQL Security Vulnerability Remediation (1778980)
We have resolved a known security vulnerability in the PostgreSQL database used by DA by upgrading from version 16.2 to 17.5. This was mentioned in the previous version release notes.
This update strengthens system integrity and enhances database protection.
Data Residency – Line level data missing in Avro (4373402)
When data residency is enabled in DA, the Avro file generated in Object Storage (S3) initially lacked invoice line-level details. This issue stemmed from the conversion process between the private schema and the public schema format used in S3.
The conversion logic has since been corrected, ensuring that all invoice lines and their associated details are now accurately included in the Avro files stored in S3.
Configuration Sync Issues with Streaming using SOAP Web Services (4328029)
Legacy SOAP web services previously offered by TR had configuration constraints that interfered with data synchronization to DA when streaming was enabled. This issue surfaced during the certificate exemption process, where Customer data generated via these services led to discrepancies in DA.
The SOAP services have since been updated to support streaming-based configuration sync, ensuring reliable data management within DA.
DA Store – Invoice failing due to SQL constraint exception (1794892)
Invoice processing failures – caused by SQL constraint exceptions in the transaction data synced to the TR Mothership – were traced to improperly formatted or invalid payloads. These issues led to connection closures, preventing successful invoice recording into the audit database.
While payload data element verification is enabled by default for DA Cloud in the merged TaxAPI tax calculation web service, it is disabled for DA Store to optimize tax engine performance. As a result, invalid payloads were able to pass through, triggering these exceptions.
DA Store customers who require payload validation can enable it by setting the overlay parameter
taxapi.payload.validation=true
. Please note that enabling this may impact tax engine performance, but it provides an added layer of validation to prevent malformed payloads from being processed.Transaction impact during service restart (1794892)
An issue has been resolved that caused HTTP 502 errors during rolling updates in AWS EKS environments. These errors occurred when the Application Load Balancer routed traffic to pods that were either terminating or not yet ready, resulting in service disruptions despite the use of
terminationGracePeriod
and readiness/liveness probes. Customers will experience more reliable database upgrades with fewer failures requiring manual intervention. The system now intelligently detects and resolves in-progress operations, reducing installation failures and improving overall system stability during upgrades.
Delta dB upgrade failure (1839233)
This enhancement resolves an issue that caused installation failures when upgrading the delta DB chart while another operation was already in progress. Previously, errors such as “UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress” required manual intervention and led to delays during system updates.
The system now intelligently detects and manages concurrent operations, resulting in more reliable database upgrades, fewer manual recoveries, and improved overall stability during deployments.
Tax-API container error (4432107)
Users were encountering permission denied errors when the
tax-api container
attempted to create a secrets properties file, causing application startup failures. We have now fixed permission issues for this container and ensured proper directory access for secrets file creation.This fix improves reliability of tax-api container startup in customer cluster environments, reducing deployment failures and ensuring consistent service availability.
Related Content
-
Determination Anywhere
Format:
Article,
1 min read