Design Assumptions
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 12. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Dimension Member Names - Renaming and Deleting" See KB article: "Dimension Text Fields - Summary" Tax Provision Blueprint Design Assumptions Tax Provision Blueprint has made several assumptions in order for this blueprint to function properly in all sorts of client environments. Below is a list of the key assumptions. Cube: The app comes with a pre-defined cube called “XFW_TXP” We have used the Standard calendar that is defined monthly from Jan (M1) to Dec (M12). Your application may use a different calendar and most likely will follow what has been used in the Finance cube/app. For purposes of this document, the Seed year is 2019 and the first tax provision that is calculated is in 2020. Application Properties: Application Properties are not packaged with the Tax Provision Blueprint app as it could conflict and overwrite existing application properties. OneStream Dimensions: Scenarios: The app comes with a set of tax scenarios. Two actual scenarios are used called “TXP_Actual” (holds Actuals data) and “TXP_ActualRTP” (holds return to provision data). These scenarios use the scenario type of “Tax”. Several forecast scenarios have been created. These current year Forecast scenarios use the scenario type of “ScenarioType8”. Multi-year forecast scenarios are set up as “ScenarioType7”. This release has not been tested for multi-year forecasts and these scenarios are there for future development. Entities: The app comes with a set of test entities. It is expected that these entities will be removed and replaced with client specific entities. Base entities use - UD1 Constraint / UD7 Constraint / UD1 Default / Text 7 / Text 8 Parent entities use - UD1 Constraint / UD7 Constraint / Text 7 / Text 8 An admin entity called TXP_GLTaxAdmin is required. Accounts: The app comes with a set of tax accounts. Text 1 is used on base and parent members to identify “Discrete” accounts. Text 1 is also used on base members to identify “Losses Not Benefitted”. Alternate hierarchies are used with Aggregation weights. Flow: The app comes with a set of tax flow members. Text 1 is used on base and parent members to identify “Discrete” flows. Alternate hierarchies are used with Aggregation weights. UD1 (Jurisdictions): The app comes with a set of tax UD1 members. Text 1 is used on all base and parent UD1 members. Text 2 is used on some base level UD1 National members for countries doing National group filing. Alternate hierarchies are used with Aggregation weights. UD2 (Data Type): The app comes with a set of tax UD2 members. Alternate hierarchies are used with Aggregation weights. UD3 (Reporting/Accounting Type): The app comes with a set of tax UD3 members. UD4 (Tax Type): The app comes with a set of tax UD4 members. UD5 and UD6: The UD5 and UD6 dimensions are not used. The default is None. If you use UD5 and/or UD6 or the other dimensions differently than the Tax Provision Blueprint setup, significant updates and testing will be required in all the BR's, CV's, Parameters, Data Management sequences and Dashboards. UD7 (Group Filing entities): The app comes with a set of tax UD7 members. Base level and country parent level UD7 members must be the same as the base level and parent level entity members. Only required for countries doing Local and/or National group filing. Minimum required members are: TXP_TopTax / TXP_GFEntities / None when no group filing is used. UD8 (Dynamic Reporting): The app comes with a set of tax UD8 members. Cube Views: The app comes with several cube view groups and profiles. Schedules: Schedules (Form templates) are rendered through Dashboards. Several schedules have linked CV’s to get at additional detail (i.e.: the UD7 group filer entity detail). Business Rules: Most of the Tax Provision Blueprint business rules reside in the main Finance BR called “TXP_BusinessRules”. It is attached to the tax cube (XFW_TXP) as Business Rule 1. Dashboards: Dashboards are used extensively throughout the Tax Provision Blueprint app. All the tax schedules and reports are rendered through a dashboard. Workflows: The app comes with a set of workflow profiles. All entities assigned to a workflow must be in the same tax country (National jurisdiction). Workflow Text 1, 2 and 3 apply to all base level workflows (at the Tax Schedule/Forms workflow and the immediate parent workflow.) The “Adj” base level workflow is not active. This can be adjusted in your application. We have used a workflow suffix naming convention for the different types of workflow profile names. This makes it easier to understand what each type of workflow represents. Examples are: Xxx_LocalGroupFiler Xxx_NatGroupFiler Xxx_LocalGF Xxx_NatPrep Xxx_Nat_LocalGF Xxx_NoLocalGF Workflow Types: National Group Filing: Only one National Group Filer workflow is allowed per country. This workflow must end with “NatGroupFiler”. UD7 is used to hold the entities being filed by country. The base level UD7 members must be defined exactly how the entities are defined. No exceptions. Local Group Filing: Only one Local Group Filer workflow is allowed per country. This workflow must end with “LocalGroupFiler”. UD7 is used to hold the entities being filed by country. The base level UD7 members must be defined exactly how the entities are defined. No exceptions. Workflow Entity: Multiple workflow filers can be created in a country. Confirmation Rules: There are a few confirmation rules that are supplied with the app for both Actual and Forecast scenarios. They do not have to be used. They serve as a starting point Security: There is no security setup in the Tax Provision Blueprint app. We only use the two supplied groups called “Everyone” and “Administrators”. Other Important System Design Information National and/or Local group filing is either “On” or “Off” per country. It cannot be on for some entities/workflows and off for others. All dimension member parents should have the word “Total” somewhere in the description. This will assist with formatting the CV’s. We strongly recommend that you install the Tax Provision Blueprint app as is in a development environment. We have also supplied a supplemental Excel file that shows more detailed setup that is difficult to show and explain in Word. It is strongly recommended to review this file and reference it during your client specific setup. It can be downloaded from the Global Setting dashboard. There is also a supplemental Excel file that shows which dimension members can be deleted or renamed. It can be downloaded from the Global Setting dashboard.What Types of Tax Provisioning Can Be Done
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 17. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" What Types of Tax Provisioning can be Done? OneStream Tax Provision Blueprint computes national and local tax provisions for an unlimited number of countries and local jurisdictions. The computation of tax provision includes current and deferred tax expense computations and related balance sheet account roll forwards. The system provides forms and computations to capture the impact of tax return true up, the financial statement impact of losses, credits and other tax attributes, and any payments or other activity that impacts tax accounts. Forecast scenarios are included to calculate the full year forecasted tax provision for the current year’s required period. Discrete data and losses not benefited are accounted for in the computation of the Interim Reporting run rate. This rate is then used to compute the Actuals period Applied Interim Reporting ETR. We can compute national and/or local tax provisions by filing group (“Group Filing”) with the related ability to control entity/filing group relationships through easily managed dashboards. Group filing (GF) refers to the aggregated computation of tax provision for a group of entities, with the combined results of the computations recorded on one of the entities within the group. Group filing may be adopted for national and/or local tax provision computations. When group filing is adopted in OneStream Tax Provision Blueprint, the UD7 dimension is used to store income and book tax adjustment information for the entity/members of the group. The following types of tax provision ‘groupings’ can be computed in this release: National JD with no GF – create a National tax provision with no group filing. Each entity calculates their own National tax provision. National JD with GF – create a National tax provision using group filing. One or more entities calculates a tax provision on behalf of a group of entities for the National JD. Local JD with no GF – create a Local JD tax provision with no group filing. Each entity calculates its own local jurisdiction tax provision for the local jurisdictions for which it is responsible. Local JD with GF – create a Local tax provision using group filing. One or more entities calculates a tax provision on behalf of a group of entities by each local JD. Any combination of the above can be used for each country. When Group Filing is required, a country specific “LocalGroupFiler” and/or a “NatGroupFiler” workflow will be required. Only one of each can be used per country. When a country contains one entity that is a ‘GroupFiler’, the entire country (jurisdiction) is subject to national group filing treatment in OneStream. Similarly, when a country contains one or more local jurisdictions that require Group Filing, all local jurisdictions in that country are subject to local group filing treatment in OneStream. See below example where Entities 1 through 4 are filing as a group, while entities 5 through 7 would effectively be separate company filings, all defined on the same group filing definition form. The Tax Provision Blueprint enables computation of the following combinations of group filings:How to Import the Tax Provision Blueprint app in a Dev Environment (Step 1)
We strongly suggest that you first install the MarketPlace Tax Provision Blueprint in a Test environment / Test App as a stand alone app. From there, you can export the objects that you need into a recent copy of your Production app that is in your Dev environment. Why do we say this?The Tax Provision Blueprint installation includes test entities, related metadata, and workflows, all which will need to be removed. It is strongly recommended that this removal and the related addition of customer entities, metadata and workflows be performed in a development environment, and that the production migration be planned from this updated development environment. Here are the high level steps required to import & setup the Tax Provision Blueprint app into your Dev environment. This "Step 1" KB article will walk you through: Installing the MarketPlace app into a Test environment / Test app. This app will be your reference app with test entities and test workflow profiles. Export only the required objects from yourTest environment / Test app. Import the required objects into your Dev environment / Dev app. Configure the Tax Provision app in yourDev environment / Dev app. so that you have a working Tax Provision application. Note: Additional metadata updates and system configurations will still be required. Please see KB article "How to Setup the Tax Provision Blueprint app in a Dev Environment (Step 2)". (1) Download and Install the MarketPlace app in a TestEnvironment/App The app in this environment will be a complete install including test entities and test workflows. This will be your Tax Provision app to reference. Download the MarketPlace Tax Provision Blueprint app Create a test app Create the required FX Rate Types or load in the FX Rate Type file Load in the downloaded "xml" file Load in the SaveDataEventHandler BR (2) Export the Tax Objects from the Test Environment/App Only specific objects need to be exported then import into your Dev. app. Export Metadata - AllBusiness Rules, all Dimensions (except XFW_TXP_Entities, FIN_Entities_TXP), exclude Time Dimension Profiles & Cubes Export Cube Views - AllBusiness Rules, Groups & Profiles Export Form Templates - AllGroups & Profiles Export Data Management - All Groups Export Confirmation Rules - All Groups and Profiles Export Extensibility Rules - only the SaveDataEventHandler Export the Dashboards - All Business Rules, Workspaces, Profiles Export the new FX Rate Types - seven in total (3) Import The Tax Objects into your DevEnvironment/App This Dev app. should be a recent copy of your Production app. The following steps must be done in this order: Create the Tax Cube (XFW_TXP) -(to be configured later on) Load/Create the necessary FX Rate Types Import the Metadata file Import the Cube View file Import the Form Templates file Import the Data Management file Import the Confirmation Rule file (need the cube to be created) Import the Dashboard file If you already have a "SaveDataEventHandler" BR, copy in the Tax BR section. If there is no "SaveDataEventHandler" BR, then you can load in the file. (4) Configure Tax Provision in the DevEnvironment/App The Tax Provision Blueprint app comes with a very comprehensive "Instruction Guide" that we strongly encourage you to read. Create an Entity hierarchy for Tax or use an existing hierarchy (ie: Finance...). Configure the Entities. Add the "TXP_GLTaxAdmin" entity as a sibling of the Tax entity hierarchy. Make sure you update the proper properties. XFW_TXP Cube - Update the Cube Properties, the Cube Dimensions, the Cube References and Integration settings.See your Test environment / Test app for examples. Update the Application Properties, if necessary. Update the Global Setup Dashboard for the Entity dimension, the Tax Entity hierarchy and the security group access. Update the other settings if necessary. Update UD7 (Group Filing) XFW_TXP_UD7: Remove Blueprint entities. Remove countries you are not using. Add new countries and entities that are using Group Filing. Must be exactly as they appear in the Entity dimension. If you are not using Group Filing at all, remove all the Blueprint entities and countries. Remember to keep the minimum required members. Set a "Cube POV" for the XFW_TXP tax cube. There should be no "?" for any dimension member. Create "test" Workflow Profilesto validate the Schedules. See your Test environment / Test app for examples.Is Tax Provision Compatible with Version 8 (v8)?
The most currently release of Tax Provision Blueprint (PV7.3.0 SV100) is compatible with version 8 (v8). Tax Provision releases prior to PV7.3.0 SV100 (PV6.2.0 SV300): Release PV6.2.2 SV300 is not compatible with version 8 (v8). Based on our testing, prior releases would only need a minor tweak in your business rules (BR's) where you reference a "Literal Parameter". You would first need to upgrade your OneStream platform to version 8. From there, you will need to compile all your business rules (BR's). A list of error messages will be generated. For Tax Provision, you should get the following "Warning" message: CASE 1: As long as when you upgraded your OneStream platform to version 8, you let the Tax Provision Dashboard default to the following location: Workspace / Default / Maintenance Units / XFW Tax Provision (TXP) The fix is to replace all the "old" references to get a literal parameter as follows: The default workspace is just an empty Guid, so if you aren't using a custom workspace, Guid.Empty should work as the 3rd parameter while keeping everything else the same. CASE 2: If you are using a non-default workspace, the DashboardExtenderArgs has a property to get the workspace, for example using it like this: BRApi.Dashboards.Parameters.GetLiteralParameterValue(si, false, args.PrimaryDashboard.WorkspaceID, "[YOUR DASHBOARD PARAMETER NAME GOES HERE]") Example: I want to get the literal parameter that is stored in a "non" Default Workspace. Note: The BR syntax that we are using below is only available starting in version 7.4.0 The syntax would be as follows: And if I write the "TestWorkspace" to the error log, I get the correct literal parameter: There will be several of these cases throughout all the business rule (BR) files. Note: If you have made additional customized enhancements to a prior release of Tax Provision, there may be other changes that are required to be v8 compatible.What are the Necessary Activities to Start a New Tax Provision Year - "Actual"
Attached is a Word document that highlights the steps necessary to start a new tax provision year or a new tax provision for a period other than the first period in the year. Many of these steps will most likely be executed by the Admin. These are the following classifications of tasks: Global (applies to all entities) Executed only in the first period of the year. Executed once at the start of a tax provision period. Individual entity Executed only in the first period of the year. Executed once at the start of a tax provision period. This is a summary of the detailed information that you can find in the "Instruction Guide" that comes with the Tax Provision Blueprint application.Data Flow Flowchart - Actual and Forecast
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 277. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" Attached are 2 PDF files that shows the Actual and Forecast Data Flow Overview. They are high level flowcharts that shows the flow of data from schedule to schedule while splitting up the functions between Data Collection / Workpapers / Calculations and Reporting. Data Flow Overview We define Tax Provision Blueprint in four sections: Data Collection, Workpapers, Calculations and Reporting. A data point is entered once and then flows through the tax provision calculation as defined. The main data input is achieved through the Schedules (Forms) 01 – 06 as shown in the blue boxes below. Data Collection – Schedules 01 – 04 Workpapers / Calculations – Schedules 05 – 18 The data collected and calculated in Schedules 01 – 06 are then used to populate Schedule 07 – 18 (Tax Account Reconciliation, Statutory ETR, and Consolidated ETR, Interim Reporting ETR, Applied Interim Reporting ETR). These forms are view only, except for the ability to reclassify income statement or balance sheet data in the Tax Account Reconciliation.Summary of the Tax Provision Functionality by Version
Below are the versions of Tax Provision with it's associated functionality. There is an attached zip file that has all the Release Notes for each version. Note: Tax Provision Blueprint is not an upgradeable solution. PV430 SV100 - release date: Nov 30, 2018 (referred to as Dev01) Initial launch of Tax Provision. Feature Functionality National jurisdiction tax provision. PV511 SV100 - release date: Sep. 23, 2020 (referred to as Dev02) Feature Functionality The Tax Provision solution now supports the ability to compute Local Tax Provisions. UD1 now includes Local Jurisdictions. Business Rules now calculate both National and Local Jurisdictions. All Schedules have the ability to display either the National Jurisdiction or any one of the Local Jurisdictions. Added the ability for an entity to receive a National Tax Benefit from Local Jurisdiction(s). Where applicable, Schedules will suppress specific rows or columns that are not related to the selected Jurisdiction, allowing the same Schedule to be used for different purposes. See KB article: "Release Video - PV5.1.0 SV100" Additional Enhancements The Tax Provision Setup Instructions contain detailed information for all implementers and Administrators regarding the use of Schedules in both the Seed Year and the years after the Seed Year. There is now a Tax Provision Dashboard which includes a Home page. There is now a Settings page that is accessible from the Tax Provision Dashboard. The top line in each Schedule now shows the Calc Status. Schedule row and column descriptions now include data origination and destination.Also, specific data cells will display a colored box around them to indicate where data is expected. Analysis Cube Views were created and can be attached to a Workflow. The SaveDataEventHandler Business Rule now validates the years that a user enters into Schedules 2, 3, and 4. Error messages will pop up when trying to save or calculate incorrectly entered years. These messages contain corrective instructions. An Admin Cube View (available in OnePlace) is provided to help the Administrator pre-populate the Origin Year for Schedule 3. The Start Year is now referred to as the Seed Year. Form Templates are now created using Dashboards rather than Cube Views. The main Finance Business Rule (TXP_BusinessRules) has been re-organized and is better structured for understanding and maintenance. RTP - Return Year must be set and no longer defaults to the prior year. In Schedule 3, the data for UD2 member “CY > -19” no longer rolls off the schedule, but rather is added to the last year’s balance. PV620 SV100 - release date: Sep 24, 2021 (referred to as Dev03) Feature Functionality The Tax Provision solution now supports the ability to calculate a tax provision with or without Group Filings (GF): National and/or Local jurisdictions. Workflows are used extensively to facilitate the different tax provision setups for group filing or no group filing. The Entity dimension has 2 new Text 7 properties required for group filing: “NatFiler=Yes” and “LocalFiler=Yes”. The UD1 National JD has a Text 2 requirement for National GF: “NatGF=Yes”. The UD7 dimension is now being used to hold the group filing entities. New schedules have been created to allow the users to enter in Group Filing Definitions. The Finance BR “TXP_BusinessRules” has been updated for the UD7 dimension. See KB article: "Release Video - PV6.2.0 SV100" Additional Enhancements Additional UD8 members have been added for dynamic reporting. There are now ten Form Template Profiles to assist with the different types of workflows. The tenth one being the Admin profile. All schedules now have an attached PPT file.These files can be customizable to each application. Schedules no longer have an Instructions section below the POV / above the cube view. Instead, we now have a PPT help file with the instructions in it. This saves on the schedule’s real estate space. All schedules now include a vertical and horizontal moveable splitter bar. Five new copy schedules have been added – DM 10a, DM 10b1, DM 10b2, DM 30a and DM 30b. DM 10a is used to copy the National provision data to the National filer entity. Several new Data Management jobs have been created to assist with copying data and annotations. There are now Scenario formulas on both Actual scenarios that impact the first period of the following year when a calculate is done in period 12. These can be removed or changed based on your specific app. Four Forecast scenarios have been created for reference only. FX rates and Excel data files are included with sample data that can be loaded into the Tax Provision app. Schedules that start with a “DM” represents a Data Management job that copies data or cell text. Schedules that start with a “LP” represents Local Processing for local jurisdictions. PV620 SV200 - release date: Feb 28, 2022 (referred to as Dev04) Feature Functionality The Tax Provision solution now supports the ability to execute a bulk data copy: Allows National group filers to copy the national preparation data to the filer member. Allows copy from National to Local jurisdictions. The GLTaxAdmin workflow allows you to process all the different country bulk data copies from one workflow. A new Finance business rule was created called “TXP_CustomCalcs” which is used to calculate the new Time Stamp for the bulk data copy dashboards. Additional Enhancements Several reports now have a combo box selection to select the number of decimal places to display for percentages. The Tax Provision dashboard home page for reports is now divided into two panes – Report Groups and Reports. Several reports now have a check box to allow you to sort the entities in the combo box. Reports now let you select the time period (month) for the report and assumes the workflow year you are in. This means that the user does not have to be in a specific workflow period to run a report. PV620 SV300 - release date: Jul 10, 2023 (referred to as Dev05_Dscr) Feature Functionality The Tax Provision solution now supports Interim Reporting computations for the current year. Option to calculate a full year forecast for the current period. Ability to calculate the Interim Reporting Run Rate in the forecast scenario. Added classification of discrete items to facilitate Interim Reporting. Includes Losses Not Benefited computation. Consolidated Interim Reporting Run Rate is used to calculate and report the Applied Interim Reporting Effective Tax Rate. We have assumed that the workflow profiles are the same for Actual as well as for Forecast scenarios. Single year Forecast scenarios are set up to use the Scenario Type of “ScenarioType8”. Six new FX rate types have been added that are used on forecast scenarios. New sets of schedules have been created for Forecast scenarios. New Forecast Tax Reviewer reports have been created. We added the ability to do a bulk copy of last year’s CY tax rates & last year’s Deferred tax rates into the current year.This is only done in period 1. See KB article: "Tax Provisioning Blueprint Overview - PV6.2.0 SV300" See KB article: "Release Video - PV6.2.0 SV300" Additional Enhancements Added parent account TXP_TIBeforeLosswNatBen to allow the National Benefit Deduction to be included when creating a tax loss. We added a new Global Setting page option for a security group. All schedules and Reports now have a “Refresh Data” button in the toolbar. We added the “Sticky POV” concept on the schedules.This will hold your POV as you go from schedule to schedule. Reports will now automatically hold your POV (same as the Sticky POV concept). Schedule column headers now indicate if there are linked CV’s in that column. Additional Actual Tax Reviewer reports have been created. Multi-year Forecast scenarios are set up to use the Scenario Type of “ScenarioType7”, but we have not explored that avenue in this release. PV730 SV100 - release date: Jan 15, 2024 (referred to as Dev06) Feature Functionality Lots of new reports were created and updated. See KB article: "Tax Provisioning Blueprint Overview - PV7.3.0 SV100" Additional Enhancements Added the UD1 "Total Local" member to the toolbar combo boxes. Added monthly, quarterly & yearly confirmation rules for forecast scenarios. BR's - changed the reference for "RemoveZero" to "RemoveNoData" - specifically for forecast scenarios. FX calculations were updated to include local FX due to multiple translations. Documented which dimension members can be "renamed", "deleted" or not touched. The Waterfall graph (80a) no longer uses BR’s for the graph. There is now a new Advance Chart called “Waterfall” that has the same functionality as the BR.What are the Necessary Activities to Start a New Tax Provision Year - "Forecast"
Attached is a Word document that highlights the steps necessary to start a new tax provision year for a Forecast scenario. Many of these steps will most likely be executed by the Admin. In the actual scenario, the admin will need to select the forecast scenario where the Interim Run rate will come from and once the Interim Run Rate has been calculated enter the Interim Run Rate. For each forecast scenario where a tax provision is calculated, the administrator will most likely be responsible for initializing the scenario with data from actuals for a set number of periods and then facilitating data copies within the forecast periods. Within the XFW_TXP_GLTaxAdmin workflow, there are dashboards to do the following: Forecast scenario – Prep tasks Forecast scenario – Initialize & Data copy tasks Forecast scenario – Data copy tasks (forecast periods) TXP_Actual scenario – Initialize tasks This is a summary of the detailed information that you can find in the "Instruction Guide" that comes with the Tax Provision Blueprint application.Glossary
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 10. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" Tax Provision Blueprint uses terminology that may be different from what you are used to. We want to make sure that everyone has a basic understanding of the terms used in the app.