Recent Content
Dimension Member Names - Renaming and Deleting
Attached is a 10 tab Excel file that shows which member names can be renamed, deleted or not changed at all. It also indicates if the member name is used in CV's, BR's, Dashboard objects or in Data Management. It looks at the following dimensions: Scenario Entities Accounts Flow UD1, UD2, UD3, UD4, UD7 and UD80likes2CommentsSample Excel Formulas
Attached is a 4 tab Excel file that has many sample Excel formulas. It shows you how to reference the 18 dimensions in order to pull or push data as well as pull in metadata attributes. Areas of examples include: XFSetCell / XFGetCell / XFGetMemberProperty / XFGetRelationshipProperty / XFGetMemberInfo. This is an excellent file to help you get up and running quickly using Excel formulas.0likes1CommentForm Templates
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 147. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Form Template Groups & Profiles" Form Templates The Tax Provision Blueprint Form Templates are used for Tax Forms/Schedules and are used in the Workflow Profiles. Several Form Template Groups are used to break down the schedules into smaller groups so that several specific Form Template Profiles can be created and attached to the different types of workflows that are possible. All the Form Templates are of the Form Type “Dashboard”. Dashboards allow greater flexibility in how the schedules are rendered to the user.0likes2CommentsSample Workflow Upload Template
Attached is a one tab Excel file that has a sample Workflow Upload template. It is OneStream's "Workflow Hierarchy Builder" that has been updated with sample Tax Provision Blueprint metadata. If you have a lot of WF's to create, this may be a good solution to assist you with creating workflows. Please test a small sample in a Dev app to make sure you are filling in all the proper fields based on your specific application.0likes0CommentsDesign 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.0likes0CommentsWhat 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:0likes0CommentsWorkflow Profiles
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. Workflow Profiles XFW_TXP is the Root Workflow Profile for Tax Provision Blueprint. Workflows are set up by country. You can have several workflows within a country, however, entities assigned to a workflow MUST be in the same country. Only one Local Group Filer workflow profile can exist per country. Only one National Group Filer workflow profile can exist per country. Naming conventions are key to understanding what each workflow is supposed to represent. We have used suffixes on our workflows. 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: Profile Properties 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 thescenario 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: Base Level parent workflow: Workflow Name Cube View Profile Name Confirmation Profile Name Text 1 Text 2 Text 3 Base Level “Tax Schedules” workflow: Workflow Name Profile Active Input Forms Profile Name Cube View Profile Name Text 1 Text 2 Text 3 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. Workflow Text Field Notes Text 1 is only required when using group filing (either national or Local): GroupFiler can be either: National NatGroupFiler=Yes Local LocalGroupFiler=Yes Entity WF are specific workflow profiles to allow certain schedules for specific entities. There are 5 types of entity workflows: Nat_LocalGF see: XFW_TXP_US_107_Nat_LocalGF / XFW_TXP_US_117_Nat_LocalGF Used for countries that do not do National group filing but do Local group filing The entities in these workflows are filer entities (Text7: LocalFiler=Yes) The entities in these workflows can process the National and Local JD’s NatPrep_LocalGF see: XFW_TXP_CA_101_LocalGF / XFW_TXP_CA_102_LocalGF Used for countries that do National group filing and Local group filing The entities in these workflows are filer entities (Text7: LocalFiler=Yes and/or NatFiler=Yes) The entities in these workflows can only process the Local JD’s For the National JD only Schedules 05 and 06a are available and only the sections required for national preparation NatPrep see: XFW_TXP_CA_103_NatPrep / XFW_TXP_AE_101_NatPrep Used for countries that do National group filing Only Schedules 05 and 06a are available and only for the National JD NatPrep_Local see: XFW_TXP_LU_101_NoLocalGF / XFW_TXP_LU_102_NoLocalGF Used for countries that do National group filing The entities in these workflows can only process the Local JD’s For the National JD only Schedules 05 and 06a are available and only the sections required for national preparation <Blank> see: XFW_TXP_US_Eastern / XFW_TXP_DE_101 Used for countries that do not do either National and/or Local group filing Text 2 and Text 3 positions must be separated by a comma ( , ). No exceptions. You need to put in the dimension identifier (E#, U1#, U7#). This helps the admin to understand what dimension each text field represents. In BR’s, we remove the dimension identifier and the # where necessary. Do not Use Text 4. Leave open for non-Tax usage or for future Tax expansion. It is required to have an identifier on the workflow profile names (i.e., xxx_LocalGroupFiler, xxx_NatGroupFiler, xxx_Nat_LocalGF …). Confirmation rules looks to see if the profile name contains “LocalGroupFiler”, “NatGroupFiler”... Group Filing workflows will not have any entities associated too them. For Text 2, position one, you can specify one entity (i.e., E#TXP_US_107). The schedules will only display this entity in the POV combo box. So, if other entities are added to this workflow by mistake, they will not show up in the POV. The following are some sample screen shots of the different types of workflow profiles and the Text 1, 2 & 3 setup. XFW_TXP_Total 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. XFW_TXP_GLTaxAdmin 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: Copy Definitions: TXP_Actual scenario – Dashboards to facilitate copying of group filing definitions. Forecast scenarios – Dashboards to facilitate the initialization and data copy steps for source (actuals) data copy to forecast. Schedules: TXP_Actual scenario – Dashboards to process bulk tax rates, manage by period the Interim Reporting Run Rate, set the return year, and set Losses not Benefited entities. Forecast scenarios – Dashboards to set Losses not Benefited entities and National Benefit excluded local jurisdictions. 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: National group filing: No Local group filing: Yes XFW_TXP_US_LocalGroupFiler 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 associatedwith 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. XFW_TXP_US_107_Nat_LocalGF 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. XFW_TXP_US_108 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: National group filing: Yes Local group filing: Yes XFW_TXP_CA_NatGroupFiler 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. XFW_TXP_CA_101_LocalGF 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. XFW_TXP_CA_Eastern_NatPrep 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: National group filing: Yes Local: No local tax provisioning XFW_TXP_AE_101_NatPrep 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: National group filing: Yes Local group filing: No XFW_TXP_LU_101_NoLocalGF 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: National group filing: No Local group filing: No XFW_TXP_DE_101 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: National group filing: No Local: No local tax provisioning XFW_TXP_UK_101 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#”.0likes0CommentsDimension - Entities
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 49. 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" Entities XFW_TXP_Entitiesis the Tax Provision Blueprint sample Entity Dimension. It is provided with sample entities to show Reporting and Forms. A Legal or Tax reporting structure should be built in the XFW_TXP_Entities Dimension if the desired entity structure is not available in the Financial Model Entities Dimension. If the design decision is made to use the XFW_TXP_Entities, we recommend that this structure share base entity members (through a linked cube setup) with an existing finance structure that is used for consolidation. If distinct base entities must be created for tax, we recommend adding a _TXP suffix to each Entity Member (Houston_TXP). This makes writing Business Rules and Entity mapping easier and consistent across solutions. The sample entities that are included in XFW_TXP_Entities should be used as a reference for how to set up the Text properties for various situations, including National and Local Jurisdictions. Prior to data entry, all sample entities should be removed, except the TXP_GLTaxAdmin – Global Tax Admin entity. If the XFW_TXP_Entities Dimension is replaced as the assigned Entity Dimension for the XFW_TXP Cube, the TXP_GLTaxAdmin – Global Tax Admin entity must be removed from XFW_TXP_Entities and created in the Legal/Tax Hierarchy in the Entity Dimension that is being used. Do not change the Member Properties that are initially assigned to TXP_GLTaxAdmin – Global Tax Admin. The Tax Provision Blueprint application will not function properly without the TXP_GLTaxAdmin entity in the assigned Financial Model Entity Dimension under the Tax/Legal Hierarchy that is used. The TXP_GLTaxAdmin entity should be a sibling to the main Tax Entity hierarchy (TXP_Legal_CTX in Tax Provision Blueprint). The Tax Provision Blueprint application uses the Entity / Jurisdiction (UD1) grouping to help drive the results. UD1 is the Tax Jurisdiction that corresponds with the National (country) and Local Jurisdictions (where applicable) in which the legal entity will be taxed. There can only be one national jurisdiction associated with an entity. Each Entity Member (includes all entities added to XFW_TXP_Entities or the current entities in the substituted Financial Model Entity Dimension for Tax/Legal hierarchy) must add the following Entity Member Properties. Follow the guidelines in the Entity / UD1 Table below for sample setups. Entity Notes: General Alternate hierarchies can be used. All parent members must have the word Total in the description. This will help in the formatting of Cube Views. If intercompany (IC) is needed in the app., then flag the appropriate base level entities as “Is IC Entity=True”. UD1 Constraint Used on all entities (base and parents) – this drives the Finance Business Rule to execute. Limit’s what is a valid intersection. UD7 Constraint Used on all base level entities and up to country level parent entities. Limit’s what is a valid intersection. UD1 Default Used on all base level entities but not required on parent entities. Text 7 Used on any base entity that calculates both a National and a Local tax provision and calculates a National Benefit for the Local data (such as U.S. Federal Benefit of State): NatBenefit=Yes. Also used to tell the app if an entity is a Filer (only used for group filing – either National or Local): NatFiler=Yes and / or LocalFiler=Yes – base entity only. If a base entity requires more than one setting, use a comma to separate the two settings. NatBenefit=Yes,NatFiler=Yes,LocalFiler=Yes All other base entities – leave the property blank. All sub-country/country level parent entities – leave the property blank. At parent entities above the country level, use SETR=No to stop the parent entity from appearing on the Statutory Waterfall reports. Text 8 Required for all Tax entities (base and parent level). This is used to help determine the UD1 members. UD1 member that will vary by entity: base entity that calculates both a National and a Local tax provision; base entity that calculates only a National tax provision; parent entity. Here is a more detailed list of what each entity setting represents: UD1 Constraint: This limits the valid UD1 jurisdictions available for the entity. This ensures that invalid jurisdictions are not available for data entry (i.e., using a Germany JD on a US entity). For entities that have local jurisdictions, this member should be a parent (i.e., Entity: TXP_US_101 -> UD1 Constraint: TXP_US_Total). If there are no local jurisdictions for the entity, then the UD1 Constraint should be the National JD (i.e.: Entity: TXP_UK_101 -> UD1 Constraint: TXP_UK). For entity parents above the country level, use the member TXP_TotalNational. Note: If Finance is using or planning to use UD7 Constraints, UD1 Defaults, Text 7, or Text 8 fields, then it’s suggested to use the “Tax” / “ScenarioType7” / “ScenarioType8” Scenario Types and any other scenario types that are utilized in the tax cube. UD7 Constraint: This limits the valid UD7 group filing entities available for the entity. This ensures that invalid group filing entities are not available to enter data into (i.e.: using a Canadian group filer entity on a US entity). The UD7 Constraint should be the parent country member (Entity: TXP_CA_115 -> UD7 Constraint: TXP_Canada_Total). If an entity is not part of a group filing country (either National or Local), then use “None”. Parent entities above the country level should also be “Root”. UD1 Default: For base level entities and parent country entities, use the National jurisdiction (i.e. Entity: TXP_UK_Total -> UD1 Default: TXP_UK). For parent entities above the country level, use the “None” member. Parameters that use UD1 Default: UD1_Default_TXP Text 7: This field is used for four purposes listed below: NatBenefit=Yes Tells the system whether to execute the National Benefit from Local JD’s for that entity. See CV: Schedule LP 05_06a National Process excl Local JD_TXP. BR: TXP_BusinessRules: Schedule5_6NationalBenefitLocalCurrency Schedule8LocalRateReconciliationETR Schedule9ConsolidatedRateReconciliationETR LocalFiler=Yes This tells the app that this entity will be a Local Filer entity (for Group Filing Countries only). Parameters that use this: Entity_FilerType_TXP Entity_FilerType_MFEntity_TXP WF_TaxEntities_WFText2_P1_TXP NatFiler=Yes This tells the app that this entity will be a National Filer entity (for Group Filing Countries only). Parameters that use this: WF_TaxEntities_WFText2_P1_TXP SETR=No Used in the Home Page dashboard waterfall report. Removes parent entities above the country level from the entity combo box. Parameters that use this: Tax_Entities_SETR_TXP Text 8: This is used to populate the UD1 jurisdictions for the entity. It is used in parameters, business rules and directly in CV’s. Here is an example from a CV: U1#XFMemberProperty(DimType=Entity, Member=|!WF_TaxEntities_WFText2_P1_TXP!|, Property=Text8) Some of the parameters that use Text 8: UD1_JD_Nat_LV_TXP UD1_JD_Nat_TXP UD1_JD_Nat_DM10aAdmin_TXP UD1_JD_Local_TXP UD1_JD_Local_FC_TXP UD1_JD_Local_TaxEntities_TXP Business Rules that use Text 8: TXP_BusinessRules: variable “Jurisdiction” TXP_Copy_Data EntityText8 TXP_Copy_Data_FCST EntityText8 TXP_MemberList TXP_ParamHelper: GetEntityText8 Some of the CV’s that use Text 8: Sch_05c_Review_NatGF_No_Local_TXP Sch_05cFC_Review_NatGF_No_Local_TXP Sch_05c_Review_NatGF_Yes_Local_TXP Sch_05cFC_Review_NatGF_Yes_Local_TXP Sch_DM20a_Data Copy Provision_TXP Sch_DM20aFC_Data Copy Provision_TXP Sch_DM20aAdmin_Data Copy Provision_TXP Sch_DM20aAdminFC_Data Copy Provision_TXP Sch_LP05_06_National Process excl Local JD_TXP Sch_LP05_06_FC_National Process excl Local JD_TXP 10d Sch 05 Local Consol_TXP 10d FC Sch 05 Local Consol_TXP 20d Sch 06 Local Consol_TXP 20d FC Sch 06 Local Consol_TXP 25d Sch 07 Local Consol_TXP 25d FC Sch 07 Local Consol_TXP 80a_Stat_ETR_Analytics_TXP 80b_Stat_ETR_Waterfall_TXP There MUST be a Text 8 on ALL Tax entities (all base entities and all parent entities). There is a section in the main BR (TXP_BusinessRules) that looks to see if there is something in the entity Text 8 field. If there is nothing, none of the Tax Provision Blueprint rules will be executed for that entity. If there is no Text 8, the message displayed below will get written to the Error Log. No indication will be rendered to the user during a calculation or consolidation. So, it is important that the admin review the Error Log on a regular basis. This is especially true during the development of the app. Note: US entities TXP_US_LegalEntityA, TXP_US_101 and TXP_US_107 have their entity attributes set at the “Tax” Cube Type and the “Tax” Scenario Type as an example. All other test entity attributes are set at the “Default” Cube or Scenario Type. There are a few CV’s that use the XFMemberProperty to get the UD1 default or the Text 8. In order to make this dynamic to the Scenario Type and WF time period associated to the Scenario, a parameter has been created called “WFScenarioType_TXP”. The XFBR rule dynamically gets the scenario type associated with the scenario. When referencing the UD1Default (notice it is VaryByCubeType), we use: VaryByCubeType=[Tax], VaryByTime=[WFTime] When referencing the Text 7 or Text 8 (use the new parameter – notice it is VaryByScenarioType): VaryByScenarioType=[|!WFScenarioType_TXP!|], VaryByTime=[WFTime] The following CVs are impacted by these two options: XFW_Tax Forms Actual (TXP) folder: Sch_DM10a_Data Copy Provision_TXP Sch_DM20a_Data Copy Provision_TXP Sch_DM20aAdmin_Data Copy Provision_TXP Sch_DM20b_Data Copy Return_TXP Sch_DM30a_Data Copy Provision_TXP Sch_DM30b_Data Copy Return_TXP Sch_LP05_06_National Process excl Local JD_TXP XFW_Tax Forms FCST (TXP) folder: Sch_DM10aFC_Data Copy Provision_TXP Sch_DM20aFC_Data Copy Provision_TXP Sch_DM20aAdminFC_Data Copy Provision_TXP Sch_DM30aFC_Data Copy Provision_TXP Sch_LP05_06_FC_National Process excl Local JD_TXP XFW_Tax Reports Actual (TXP) folder: 80a_Stat_ETR_Analytics_TXP 80b_Stat_ETR_Waterfall_TXP XFW_Tax CV’s All Workflows Actual (TXP) folder: Sch_05b_Review UD2 Gross and Tax_TXP Sch_05c_Review_NatGF_No_Local_TXP Sch_05c_Review_NatGF_Yes_Local_TXP Sch_06b_NatGF_No_DefLocal Review_TXP Sch_06b_NatGF_Yes_DefLocal Review_TXP XFW_Tax CV’s All Workflows FCST (TXP) folder: Sch_05bFC_Review UD2 Gross and Tax_TXP Sch_05cFC_Review_NatGF_No_Local_TXP Sch_05cFC_Review_NatGF_Yes_Local_TXP Sch_06bFC_NatGF_No_DefLocal Review_TXP Sch_06bFC_NatGF_Yes_DefLocal Review_TXP The following parameters uses these options: UD1_JD_Nat_TXP UD1_JD_Nat_LV_TXP UD1_JD_Nat_DM10aAdmin_TXP UD1_JD_Local_TXP UD1_JD_Local_FC_TXP UD1_JD_Local_TaxEntities_TXP0likes0CommentsSample Reports - Overview
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 20. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Report Groups" See KB article: "Reports" Sample Reports - Overview We have several Report Groups and will show sample reports from group. Here are the links to all the Sample Reports that have been created in the Tax Provision Blueprint solution. Sample Reports - Tax Provision Blueprint Solution Sample Reports - Overview of Rates / RTP Years / Nat Process / LNB Sample Reports - Metadata Review Sample Reports - FX Currency Rates Sample Reports - Calc Status Sample Reports - Tax Provision Blueprint Overview Sample Reports - Group Filings Analysis Sample Reports - Trend Reports Sample Reports - Consolidating Reports Sample Reports - Tax Reviewer – Actual Reports (Actual Scenario Only) Sample Reports - Tax Reviewer - Forecast Reports Sample Reports - National Benefit Analysis0likes0Comments