Skip to main content
Determination Anywhere
Search
Search Indirect Tax Support Help and Support.

This article applies to:

  • Product: ONESOURCE Determination,ONESOURCE Indirect Tax

Manage tax content and configuration with version control

Use the
Version control
 screen to manage and deploy tax content and configuration updates for your Determination Anywhere (DA) instances.
note
The version control supports DA Store application instances only.
To view the
Version controls
 screen, go to
Determination Anywhere
Version control
.
How version control works
The
Version control
 screen lets you control when DA applies tax content and configuration updates. The system delivers new versions to this screen with a
New
 status instead of applying them automatically.
You can:
  • Test before deploying:
     Select a version for testing and validate it in staging or test environments.
  • Control production updates:
    Activate
     a version when you're ready for production.
  • Maintain an audit trail:
     Review who performed actions and when versions were created, activated, or archived.
  • Roll back:
     Reactivate the last stable version if you find an issue with the current active version.
note
Users with the
DA Tenant Admin
 role can perform actions. Users with the
DA Support User
 role can view cache versions but can't perform actions.

Functionalities and processes

By default, DA dynamically syncs newly released tax content and configuration to instances. To control updates manually with the
Version control
 screen, the tenant will need to have the version control enabled by Thomson Reuters IDT DevOps.
note
For all new customers, the cache version defaults to
Active
. To switch to version control manually, open a support ticket with the Thomson Reuters IDT DevOps team.
The Version control screen shows the following views:
  • No new versions:
     shows a message explaining that new versions will appear here when available.
  • List of available versions:
     shows a grid with all versions (New, Testing, Active, Archived). You can sort and filter each column.
Test a new version
To select a new version for testing:
  1. Go to the version control screen and find a version with the
    New
     status.
  2. Select
    Mark for testing
    .
  3. Select
    Confirm
     on the confirmation message, “This version will become available to test on all instances.” This changes the status to
    Testing
    .
The version is now ready for your team to validate against your test instances.
Activate a tested version
  1. Go to the version control screen and find a version with the
    Testing
     status.
  2. Select
    Activate
    .
  3. Select
    Confirm
     on the confirmation message, “This version will become activated on all instances. We’ll automatically archive the last active version. This changes the version status to
    Active
     for all instances and automatically archives previously active versions.

Field descriptions

Version control
Screen elements
Description
Version
A unique identifier for the content and configuration package.
User ID
The user who performed the last action. New versions may show “System Generated” until someone makes changes.
Status
Current state:
  • New - new version but not yet tested
  • Testing - available for testing on non-production instances
  • Active - current version used on all instances
  • Archived - previously active version
Action
Available action for the version:
Mark for testing
,
Activate
, or
Reactivate
.
Created on
Date and time when the system first made the version available.
Marked for testing
Date and time when the status changed to
Testing
.
Activated on
Date and time when the version became active on all instances.
Archived on
Date and time when the system archived the version.
U.S. content version
Version number of the U.S. tax content package.
INTL content version
Version number of the international tax content package.
U.S. CaaS content version
Version number of the U.S. Content-as-a-Service package.
INTL CaaS content version
Version number of the International Content-as-a-Service package.
Example use case
Scenario: A user needs to apply for the November 2025 tax content updates.
  1. Discovery
    • The user signs in and goes to
      Determination Anywhere
      Version Control
      .
    • There's a new version 01JMXS3X9H...V10 with status
      New
      . The
      Created on date
       is 11/05/2024.
  2. Initiate testing
    • Select
      Mark for testing
       for version V10 and
      confirm
      . The status changes to
      Testing
      .
    • DA instances set up as Test tenants automatically pick up cache versions marked for Testing.
    • The user lets the IT team know that the new content is ready for validation in User Acceptance Testing (UAT).
  3. Validate in UAT
    • The IT team begins testing transactions in UAT using version V10.
    • They confirm the calculations are correct and integrations work, then approves to continue.
  4. Activate in production
    • The user returns to the
      Version Control
       screen and selects
      Activate
       on V10 with a status of
      Testing
      .
    • Select
      Confirm
       on the confirmation screen that states version V9 will be archived.
    • Once active, DA instances that are set as PROD consume the active version by default.
  5. Live in production
    • Version V10 is now active. All production transactions use the November tax content.
    • Version V9 shows the status is
      Archived
      .
    • The system populates the
      Activated on
       timestamp for V10 and the
      Archived on
       timestamp for V9, providing a clear audit trail.