Skip to main content

Solutions

Law firms

Tax, audit & accounting firms

Corporations

Governments

Products

Legal

Trade & supply

Tax, audit & accounting

Corporate tax

Risk & fraud

Books

Recommended products

Questions? We are here to help.
Contact us

Purchase

Buy solutions

Buy books

Contact sales

Questions? We are here to help.

Resources

Insights

Events

Product training

Product communities

Developers

Determination - Enterprise Cloud

Determination 2026.02.02 patch release notes

UAT Patch for version 2026.02.02
UAT EMEA Patch Release Date: April 02, 2026
UAT AMER Patch Release Date: April 02, 2026
PROD EMEA Patch Release Date: April 06, 2026
PROD AMER Patch Release Date: April 06, 2026

What's fixed

Incorrect Rounding of VCT in Fusion Cloud Integration (5066636)
During tax determination in the Fusion Cloud integration, VCT document amounts split across multiple lines with multiple tax blocks were producing a variance between ONESOURCE and ERP totals due to penny-pitching not being applied correctly (for example, -4.94 in ONESOURCE vs. -4.98 in ERP). Two root causes were identified: the accrual method override was being ignored, defaulting to
PAY_VCT_NO_ACCRUAL
 regardless of what the request specified, and exempt lines (tax = $0) were causing vendor tax distribution to fall back to a basic equal distribution, failing to populate authority-level document amounts correctly. Both defects have been resolved; the accrual method now honors the value specified in the request with a fallback default only when none is provided, and exempt line handling has been enhanced to correctly distribute vendor tax across all authority levels, ensuring the full VCTV pipeline, including penny adjustment, executes as expected.
Alphanumeric Line Numbers with Multiple Charges or Related Line Amounts (5186087)
An issue was identified in the Tax API where calculation requests failed when using alphanumeric line numbers in combination with either multiple charges or a
RelatedLineAmounts
 block. This issue has been resolved, and the API now correctly processes tax calculation requests with alphanumeric line numbers regardless of the presence of multiple charges or
RelatedLineAmounts
 blocks.
Unique Line Number Not Returned in REST API Response (5225108)
An issue was reported where the
uniqueLineNumber
 attribute was not being returned in the REST API response payload for commit transactions, causing the
uniqueLineNumber
 field sent in the request to be omitted from the response. This issue has been fixed, and the
uniqueLineNumber
 attribute is now correctly returned in the response payload when provided in the request.

This article applies to:

  • Product: ONESOURCE Determination

Related Content