About Entities and Entity Rollup
Entities
Entities in ONESOURCE Administration gives a single place to manage entities across all ONESOURCE applications. These entities are essential for the main functions of the applications and are used differently in each one.
With Entities in Administration you can create, make changes, view, and turn off entities that are used across multiple ONESOURCE products like Calendar, DataFlow, Data Hub, Income Tax, and Tax Provision, all in 1 central location.
Contact your Customer Success Manager to get started with this feature, then the product team will shift your existing entities over to the ONESOURCE Platform.
Entity rollup
Entity Rollup in ONESOURCE Administration gives a hierarchical view of the entities. You can connect different entities to form a parent-child relationship (for example, level 1, then level 2, and so forth).
With Entity Rollup, you can create and make changes in 1 central location, see changes reflected across products like Data Hub, publish changes from a single location, and track and monitor all entity rollups in 1 place.
note
- You can't update an entity rollup after publishing the changes. To make further updates, first unpublish the rollup and then proceed with the changes.
- The system supports a maximum of 3 levels of associations (for example Entity 1, Entity 2, and Entity 3).
Migration process
Everything that’s already in your products will move over to
Entities
in Administration, as long as it passes our checks and balances. - All units and fields currently populated in the product will transfer toEntitiesif they pass validation.
- There are some validations that the migration process will consider during the migration.
- The migration won't impact any existing data in the application.
- A migration report will be available.
- Contact the support team in case of any mismatch between the application integrating with Entities.noteRefer to each article about the specific ONESOURCE application for more information.
Prepare for migration
- Contact your Customer Success Manager or Account Manager to enableEntitiesfor your default instance. The Thomson Reuters technical team will run the migration job.
- Make sure to give the account name and ID. For example, ABC and A1B (3-digit account id).
After migration
- The Administrator must have product permissions for Entities inAdministration,Company Info, thenUsersin ONESOURCE Administration.
- You can view your Entities inAdministration,Company Info, thenEntities.
- The entity can't be deleted once it's created in Entities and associated with an ONESOURCE product.
Related Content
-
Company Info menu
Format:
Article,
1 min read
