02-15-2024 02:20 PM - edited 02-16-2024 09:02 AM
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 149.
See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100"
See KB article: "Workflow Templates"
Tax Provision Blueprint includes several Workflow Profiles related to the included Tax Provision Blueprint Cube.
OneStream Workflows are a key benefit of building a tax provision process using Tax Provision Blueprint. The ability to create Workflows that tailor the users experience to their specific responsibilities and show the status of the completed Workflow task is a key differentiator of Tax Provision Blueprint. Workflow is expected to be customized to address individual customer requirements.
Review the supplied Excel supplemental file that has a very informative matrix about the workflow setup.
Please see KB article: "Workflow Profile setup - Actual & Forecast".
Here is a screenshot of the supplied workflows:
All settings should be applied to the “Tax” scenario type. If you are using current year Forecast scenarios, use the scenario type “ScenarioType8”. If you are using multi-year Forecast scenarios, use the scenario type “ScenarioType7”. They should be applied to both the base level parent workflow and at the base level Tax Schedules workflow.
The following areas in workflows have been used in Tax Provision Blueprint:
Tax Provision Blueprint makes use of the Substitution Text Settings Text 1, Text 2, and Text 3. These three text fields are used to drive the tax schedules POV, combo boxes parameters and business rules. Text 4 is left blank intentionally for possible non-Tax use or future Tax use.
The following are some sample screen shots of the different types of workflow profiles and the Text 1, 2 & 3 setup.
This is the top-level workflow and is used to consolidate all entities. You are free to rename this workflow. Only one of these workflows is required per application.
This is the admin workflow and is used to perform monthly setup work including data copies and allows access to multiple jurisdictions in one workflow. Only one of these workflows is required per application.
There are 9 base level workflows that are meant more for the Admin:
The next 7 country workflows enable an Admin user (1) enter tax rates, (2) set the RTP year (TXP_Actual
only), (3) copy the Provision or Return data (TXP_Actual only) and (4) copy source data to forecast
(forecast scenarios only). These 7 country specific workflows allow a user (i.e.: Admin or power user) to
perform the monthly setup work from one workflow rather than going to several different workflows.
Most of these same schedules are also available in each country’s workflow – so you can process the
data in either area.
Note: The Workflow Profiles for US (United States) in Tax Provision Blueprint are based on:
This workflow is used to set up the Local group filing definitions for the country (US in this example).
Only one of these workflows is required per country doing Local group filing. No entities are associated with this workflow. Only Local Jurisdiction data is entered for this workflow. Can Load Unrelated Entities = True. The words “GroupFiler” must be included in this profile name.
This workflow is used to do both Local Jurisdiction and National tax provisioning. You can have more than one of these types of workflows per country (US in this example). An entity is associated with this workflow.
This workflow is used for National tax provisioning only (No National Group Filing). You can have more than one of these types of workflows per country (US in this example). An entity is associated with this workflow. The second position on Text 2 is not used, but we still include “,E#”.
Note: The Workflow Profiles for CA (Canada) in Tax Provision Blueprint are based on:
This workflow is used to set up the National group filing definitions for the country (CA in this example). Only one of these workflows is required per country doing National group filing. No entities are associated with this workflow. Only the National Jurisdiction data is entered for this workflow. Can Load Unrelated Entities = True. The words “GroupFiler” must be included in this profile name.
This workflow is used to do Local Jurisdiction tax provisioning and National Jurisdiction preparation. You can have more than one of these types of workflows per country (CA in this example). An entity is associated with this workflow.
This workflow is used to enter data for schedule 05, 06a and 06a1 FC (FCST only) for National tax preparation. The country also has Local jurisdictions, but no Local jurisdiction provisioning is handled in this Workflow. You can have more than one of these types of workflows per country (CA in this example). An entity is associated with this workflow.
Note: The Workflow Profiles for AE (United Arab Emirates) in Tax Provision Blueprint are based on:
This workflow is used to enter data for schedule 05, 06a and 06a1 FC (FCST only) for National tax preparation. The country also has No Local jurisdictions. You can have more than one of these types of workflows per country (AE in this example). An entity is associated with this workflow.
Note: The Workflow Profiles for LU (Luxembourg) in Tax Provision Blueprint are based on:
This workflow is used to do Local Jurisdiction tax provisioning and National Jurisdiction preparation. You can have more than one of these types of workflows per country (LU – Luxembourg in this example). An entity is associated with this workflow. The second position on Text 2 is not used, but we still include “,E#”.
Note: The Workflow Profiles for DE (Germany) in Tax Provision Blueprint are based on:
This workflow is used to do both Local Jurisdiction and National tax provisioning but has no Group Filing requirements. You can have more than one of these types of workflows per country (DE – Germany in this example). An entity is associated with this workflow. The second position on Text 2 is not used, but we still include “,E#”.
Note: The Workflow Profiles for UK (United Kingdom) in Tax Provision Blueprint are based on:
This workflow is used for National tax provisioning only and has no Group Filing requirements. The country also has No Local jurisdictions. You can have more than one of these types of workflows per country (UK in this example). An entity is associated with this workflow. The second position on Text 2 is not used, but we still include “,E#”.