Skip to main content

Legal

Tax & Accounting

Trade & Supply

Risk & Fraud

News & Media

Books

Developers

Administration

Frequently asked questions for platform entities

Do we need to maintain any sequence while planning for the migration?

The Thomson Reuters team will discuss the sequence of the ONESOURCE Income Tax and ONESOURCE Tax Provision entity migration.
During the first migration (in this example, Income Tax entities are migrated first), we will set all the attributes. The second migration will pick only the missing attributes, updating the empty fields with values (if any) during the 2nd migration (Tax Provision-related attributes).
If there's an existing value for an attribute but a new value is found during the second migration, we'll ignore the new value and retain the existing value.

What is the bare minimum data needed to add an entity?

It needs a unique entity code only.

Why am I always getting data for Name and Return Name (line 1)?

Once you add the Entity, the entity code is cloned in the
Name
 field, and the 1st 45 characters are cloned in the
Return Name
 (Line 1) field.

Can I enter more than 45 characters for Return Name (line 1) and Return Name (line 2)?

No, it has a limit of 45 characters only.

Can I save a blank value for Return Name (line 1)?

Yes, only if it’s not associated with ONESOURCE Income Tax.

What if I enter my user credentials while using the migration tool?

It will ignore them and showcase the default value
ONESOURCE_TR_SUPPORT
.

Can I update entity data using the migration tool?

No, the migration tool only inserts data for empty attributes. It doesn’t update any existing data.

Is it possible to have different entity names on the ONESOURCE Platform and in the product after migration?

Yes, consider the following scenario:
  • The entity was created on the platform in 2021 with the name Company 1, and 45 characters were copied to
    Return Name
     (line 1) as Company 1.
  • In 2022, the product migrated entities to the platform with a different name, Company 2 Group.
  • Since
    Return Name
     (line 1) on the platform already had the value Company 1, the migration tool ignored the update for
    Return Name
     (line 1) because the field already had a value stored.
  • As a result, for the same entity code, 2 different values exist:
    • Platform: Company 1
    • ONESOURCE Income Tax: Company 2

What date combination is ignored for ONESOURCE Income Tax?

ONESOURCE Income Tax ignores the fiscal dates (beginning: 01/01 and ending: 12/31).

Can we bring in entities from prior years (older than 5 years)?

Yes, as there is no validation on the number of years for ONESOURCE Income Tax and ONESOURCE Tax Provision only.

Will the Tax Provision
Categories Export
 still be the same (will the units come out even though they are set up on the Platform?)

Yes, ONESOURCE Tax Provision
Exports
 remain as-is and will show platform entities as well. 2 additional columns will be added (Platform Country and Platform Currency).

This article applies to:

  • Product: ONESOURCE Income Tax, ONESOURCE Platform
  • Sub Product: ONESOURCE Administration
Chat now

error-icon

Triva isn't available right now.

Check out the support page for our phone number and hours

error-close