Determination Anywhere 2026.04 third patch release notes
Please review this release note in conjunction with the Determination Enterprise Cloud 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).
Please also refer to the statement in the main release note regarding how security vulnerabilities in the DA client‑side application are addressed.
Release highlights
This patch fixes an issue identified on the DA Mothership side.
Fixes
The following topics outline issues identified that have been resolved in this release.
Streaming Sync Issue with Bulk Import (5656235)
An issue introduced in DA 2026.04 affected environments configured to use both Streaming Sync and Bulk Import for data synchronization. Under these conditions, records received from Enterprise Cloud through the streaming process could attempt to assign new IDs on the DA client side, rather than preserving the original IDs.
This issue only affected environments where Bulk Import was enabled as the full data synchronization method alongside Streaming Sync. Environments using SDI as the backup full-sync process were not impacted.
The streaming synchronization process has been updated to correctly preserve record IDs. Although the issue could occur during streaming synchronization, data integrity was maintained because the Bulk Import process automatically initiated when a discrepancy was detected, ensuring that original IDs remained unchanged on the client side.
DA Store – 500 Errors in Tax Calculations (5640176)
An issue was identified in the DA Store application that could result in HTTP 500 or Null Pointer Exception (NPE) errors during tax calculations. DA Store deployments contain tax content specific to the geographic region served by the physical store. In certain cases, tax content for a state included rule relationships that referenced content from another state. For example, MO - STATE SALES/USE TAX contained a Rule Qualifier within Rule Code 8888 that referenced IL - STATE SALES/USE TAX content.
When the referenced out-of-state content was not available in the deployed DA Store instance, the tax engine could encounter an error while evaluating tax jurisdictions, causing the tax calculation request to fail with a 500 error.
This issue has been corrected to ensure that tax calculations are processed successfully when cross-state rule references are encountered, eliminating the 500 and NPE errors previously observed.