Search
Search Indirect Tax Support Help and Support.

Determination 2026.04 patch release notes

UAT EMEA/MENA Release Date: August 12, 2026
UAT AMER Release Date: August 13, 2026
PROD EMEA/MENA Release Date: August 17, 2026
PROD AMER Release Date: August 18, 2026

What’s fixed

Exempt cascading rules no longer discarded when no rate is present (5630998)
Exempt cascading rules that carry no associated rate are now applied as configured, so affected county and city authorities are correctly exempted rather than taxed. Previously these rules were skipped and higher-order non-exempt rules applied in their place, overstating total tax. Non-exempt rules that genuinely lack matching rates continue to be handled as before.
Error logs no longer printed for related line amount requests (5624118)
Determination no longer generates excessive "No Matching Authority" error log entries for transactions containing related line amounts, such as discount or coupon lines. Previously, these entries were logged even when the discount line address and the related line address matched exactly, adding unnecessary noise to transaction logs. Removing them produces cleaner logs and improves processing performance.
500 error resolved for Missouri transactions (5640176)
Determination now completes tax calculations successfully for all Missouri addresses, returning accurate results. Previously, these requests returned an HTTP 500 internal server error, preventing tax calculation results from being returned for transactions with Missouri addresses.
Global Product Group (GPG): Rules with a license condition now trigger correctly (5662466)
Determination now correctly evaluates the LICENSE rule qualifier on Global Product Group rules, resolving an issue where global rules configured with a LICENSE condition were not triggered. The associated authority is now triggered, and the rule is applied as configured.
Null pointer exception resolved for invalid or expired unit of measure (5638185)
Determination now processes XML invoice requests without error when a unit of measure is misconfigured or expired. Previously, the unset document fee amount caused a null pointer exception; the amount now defaults to zero and the request completes successfully.

Related Content