01c1Admin CY Tax Rates
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 318. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "01c2Admin Deferred Tax Rates" 01c1Admin CY Tax Rates This Admin schedule is used to copy either the “Prior Year Closing Deferred Tax Rates” or the “Prior Year Closing CY Rates” into period “1” (Jan. for the Tax Provision Blueprint app) for the CY Tax rates. We have made this schedule to only appear in the first time period of the workflow year. This schedule can be used as a starting point to bulk populate the CY Tax Rates. Manual adjustments can then be entered. The Copy rule populates the “O#Import” member. If you need a different amount after the copy, enter in the new YTD (total) amount and the difference will go to “O#Forms”. This schedule displays the “O#BeforeAdj” member. Once the copy is done, the last three columns will show if there are any variances. Right after a copy is performed, there should be no variances. If you then manually adjust a tax rate, then a variance will display. The Consolidated ETR Rate is displayed for informational purposes and is “Read” only in this schedule. The “Clear” button will clear the CY tax rates (at O#Import) that were previously “Copied” into. Any manual data input will still be left in the system. So, care should be taken when clearing and re-copying data. If you don’t see an expected entity / jurisdiction / group filer combination, then right click in a row header cell with an orange triangle and select “Insert Suppressed Member”.Data Integration
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 185. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" Data Integration - Overview There are several options for data integration between the core Financial Model and the Tax Provision Blueprint Cube data. The integration design for each implementation will vary, but could include: Data Management Export Sequences plus related Transformation Rules. Data Management Copy Sequences Use of Business Rules to copy/clear data within the Tax Cube, for example, copy from National to a Local Jurisdiction, which is included with Tax Provision Blueprint (see the next section below). File upload or direct Connectors for data loading of tax schedule data. Other data integration techniques. Data Management - Copy National jurisdiction to National or Local jurisdictions Several Data Copy options are included: Actual scenarios (Scenario Type - Tax): Copy National to National Group Filer Provision data – DM 10aAdmin Copy National (Group Filing: Yes or No) to Local (No Group Filing) Provision data – DM 20aAdmin Copy National (Group Filing: Yes or No) to Local (No Group Filing) Provision data – DM 20a Copy National (No Group Filing) to Local (No Group Filing) Return data – DM 20bAdmin Copy National (No Group Filing) to Local (No Group Filing) Return data – DM 20b Copy National Group Filer to Local (no Group Filing) Return data – DM 20b2Admin Copy National Group Filer to Local (no Group Filing) Return data – DM 20b2 Copy National (Group Filing: Yes or No) by Local (Group Filing) Provision data – DM 30aAdmin Copy National (Group Filing: Yes or No) by Local (Group Filing) Provision data – DM 30a Copy National (No Group Filing) by Local (Group Filing) Return data – DM 30bAdmin Copy National (No Group Filing) by Local (Group Filing) Return data – DM 30b Copy National Group Filer to Local Group Filer Return data – DM 30b1Admin Copy National Group Filer to Local Group Filer Return data – DM 30b1 Forecast scenarios (Scenario Type - ScenarioType8): Copy National to National Group Filer Provision data – DM 10aAdmin FC Copy National (Group Filing: Yes or No) to Local (No Group Filing) Provision data – DM 20aAdmin FC Copy National (Group Filing: Yes or No) to Local (No Group Filing) Provision data – DM 20a FC Copy National (Group Filing: Yes or No) by Local (Group Filing) Provision data – DM 30aAdmin FC Copy National (Group Filing: Yes or No) by Local (Group Filing) Provision data – DM 30a FC Set the Opening Scenario - DM 40 Admin FC Copy Actual Data into a Forecast scenario – DM 45 Admin FC Copy Actual Data into a Forecast scenario – DM 45 FC Data Management - Copy Tax Rates Actual scenarios (Scenario Type - Tax): Copy Prior Year M12 CY Tax Rates into Period M1 - 01c1Admin CY Tax Rates Copy Prior Year M12 Deferred Tax Rates into Period M1 - 01c2Admin Deferred Tax Rates These two dashboard allows the admin to copy prior year's ending tax rates into period M1 of the current year. Then the tax rates flow forward until the end of the year or until a user changes them in a period. These two dashboards are only available in the first time period and only on the XFW_TXP_GLTaxAdmin workflow. These dashboards are optional and are not required too be used. Data Management - Copy Group Filing Definitions (Cell Text / Annotations) Actual scenarios (Scenario Type - Tax): Copy Definitions - Actual Nat GF - DM 01a Copy Definitions - Actual local GF - DM 02a Copy Definitions - ActualRTP Nat GF - DM 11a Copy Definitions - ActualRTP Local GF - DM 12a These dashboards allow the admin to copy the group filing definitions from a prior period into the current period. The copy can be used as a starting point and then the admin can modify the copy for any changes. These dashboards are optional and are not required too be used. There are several supplied Dashboards (10aAdmin, 10aAdmin FC, 20a, 20a FC, 20aAdmin, 20aAdmin FC, 20b, 20bAdmin, 20b2, 20b2Admin, 30a, 30a FC, 30aAdmin, 30aAdmin FC, 30b, 30bAdmin, 30b1, 30b1Admin, DM45Admin FC, DM45 FC) that can be used to copy/clear data. When a data copy dashboard has the word “Admin” in its name, it means that there is the functionality to do “bulk” data copy or clear. Here are some sample Actual scenario workflow schedules: There are several Data Management jobs attached to the icons in each data copy dashboard that then call Business Rules to execute the clear or copy functions.DM 20b2 – Return Data: National Group Filer to Local (no Group Filing)
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 200. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Data Integration" Dashboard DM 20b2 – Return Data: National Group Filer to Local (no Group Filing) Select a WF entity and a Local Jurisdiction that you want the National Provision data to be copied into. This schedule can only copy or clear one POV at a time. The bottom section of the toolbar may have a “timestamp” with the last time a “bulk” copy or clear was executed. This can only be done via Sch DM20b2Admin. After a copy is completed, a 1 is entered to account TXP_Data_Copy_20b2. A Cube View is supplied in the dashboard to show the user which Entity, National Jurisdiction, Group Filer entity (UD7) has been copied to which Entity, Local Jurisdiction, None (UD7). You must select the RTP Year that you want to process. The JD RTP year/month is pulled from Schedule 02 Set the Return Year. The RTP year drives the copy / clear business rules. The JD RTP period is for informational purposes only. As each Local Jurisdiction can have a different RTP year/month, the cube view only shows the current jurisdiction. The last three columns help explain the variance for data that has been entered in local only permanent or temporary difference accounts.DM 20b2 Admin – Return Data: National Group Filer to Local (no Group Filing)
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 199. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Data Integration" Dashboard DM 20b2 Admin – Return Data: National Group Filer to Local (no Group Filing) Select a WF entity and a Local Jurisdiction that you want the National Provision data to be copied into. If the “All Entities” check box is selected, then all the entities in the combo box, all the local JDs and all the UD7 members associated to each entity will be copied or cleared for the selected RTP Year. It does not matter what is in the POV; the check box supersedes the POV. We refer to this as a “bulk” copy or clear. If the “All Entities” check box is not selected, then only the POV selected in the combo boxes will be copied or cleared. The bottom section of the toolbar will update with a “timestamp” with the last time a “bulk” copy or clear was executed. The timestamp will not be updated if the “All Entities” check box is not selected. After a copy is completed, a 1 is entered to account TXP_Data_Copy_20b2 A Cube View is supplied in the dashboard to show the user which Entity, National Jurisdiction, Group Filer entity (UD7) has been copied to which Entity, Local Jurisdiction, None (UD7). You must select the RTP Year that you want to process. The JD RTP year/month is pulled from Schedule 2 Set the Return Year The RTP year drives the copy / clear business rules. The JD RTP period is for informational purposes only. As each Local Jurisdiction can have a different RTP year/month, the cube view only shows the current jurisdiction. The last three columns help explain the variance for data that has been entered in local only permanent or temporary difference accounts.DM 20a – Provision Data: National (Group Filing: Yes or No) to Local (No GF)
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 195. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Data Integration" Dashboard DM 20a – Provision Data: National (Group Filing: Yes or No) to Local (No GF) Select a WF entity and a Local Jurisdiction that you want the National Provision data to be copied into. This schedule can only copy or clear one POV at a time. The bottom section of the toolbar may have a “timestamp” with the last time a “bulk” copy or clear was executed. This can only be done via Sch DM20aAdmin. After a copy is completed, a 1 is entered to account TXP_Data_Copy_20a. A Cube View is supplied in the dashboard to show the user which Local Jurisdictions have copied data. There are three rows to help explain the variance for data that has been entered in local only permanent or temporary difference accounts. We have created a flow member called “TXP_ConfirmBal_001” that holds the copied flow members. This parent member is strictly used to expand or collapse a row in the CV. The aggregated value is meaningless but shows you where there is data.DM 30b1 Admin – Return Data: National Group Filer to Local Group Filer
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 198. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Data Integration" Dashboard DM 30b1 Admin – Return Data: National Group Filer to Local Group Filer Select a WF entity, a Local Jurisdiction, and a Group Filer entity (UD7) that you want the National Return data to be copied into. If the “All Entities” check box is selected, then all the (filer) entities in the combo box, all the local JDs and all the UD7 members associated to each entity will be copied or cleared for the selected RTP Year. It does not matter what is in the POV; the check box supersedes the POV. We refer to this as a “bulk” copy or clear. If the “All Entities” check box is not selected, then only the POV selected in the combo boxes will be copied or cleared. The bottom section of the toolbar will update with a “timestamp” with the last time a “bulk” copy or clear was executed. The timestamp will not be updated if the “All Entities” check box is not selected. After a copy is completed, a 1 is entered to account TXP_Data_Copy_30b1. A Cube View is supplied in the dashboard to show the user which Entity, National Jurisdiction, Group Filer entity (UD7) has been copied to which Entity, Local Jurisdiction, Group Filer entity (UD7). You must select the RTP Year that you want to process. The JD RTP year/month is pulled from Schedule 02 Set the Return Year. The RTP year drives the copy / clear business rules. The JD RTP period is for informational purposes only. As each Local Jurisdiction can have a different RTP year/month, the cube view only shows the current jurisdiction. The last three columns help explain the variance for data that has been entered in local only permanent or temporary difference accounts.DM 30a Admin – Provision Data: National (Group Filing: Yes or No) by Local (Group Filing)
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 202. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Data Integration" Dashboard DM 30a Admin – Provision Data: National (Group Filing: Yes or No) by Local (Group Filing) Select a WF entity, a Local Jurisdiction, and a Group Filer entity (UD7) that you want the Local Provision data to be copied into. If the “All Entities” check box is selected, then all the (filer) entities in the combo box, all the local JDs and all the UD7 members associated to each entity will be copied or cleared. It does not matter what is in the POV; the check box supersedes the POV. We refer to this as a “bulk” copy or clear. If the “All Entities” check box is not selected, then only the POV selected in the combo boxes will be copied or cleared. The bottom section of the toolbar will update with a “timestamp” with the last time a “bulk” copy or clear was executed. The timestamp will not be updated if the “All Entities” check box is not selected. After a copy is completed, a 1 is entered to account TXP_Data_Copy_30a. A Cube View is supplied in the dashboard to show the user which Entity and National Jurisdiction has been copied to which Entity, Local Jurisdiction, Group Filer entity (UD7). The last three columns help explain the variance for data that has been entered in local only permanent or temporary difference accounts. We have created a flow member called “TXP_ConfirmBal_001” that holds the copied flow members. This parent member is strictly used to expand or collapse a row in the CV. The aggregated value is meaningless but shows you where there is data.01c2Admin Deferred Tax Rates
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 319. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "01c1Admin CY Tax Rates" 01c2Admin Deferred Tax Rates This Admin schedule is used to copy the “Prior Year Closing Deferred Tax Rates” into period “1” (Jan. for the Tax Provision Blueprint app) for the Deferred Tax Rates. This schedule can be used as a starting point to bulk populate the Deferred Tax Rates. Manual adjustments can then be entered. The Copy rule populates the “O#Import” member. If you need a different amount after the copy, enter in the new YTD (total) amount and the difference will go to “O#Forms”. This schedule displays the “O#BeforeAdj” member. Once the copy is done, the last three columns will show if there are any variances. Right after a copy is performed, there should be no variances. If you then manually adjust a tax rate, then a variance will display. The Consolidated ETR Rate is displayed for informational purposes and is “Read” only in this schedule. The “Clear” button will clear the Deferred tax rates (at O#Import) that were previously “Copied” into. Any manual data input will still be left in the system. So, care should be taken when clearing and re-copying data. If you don’t see an expected entity / jurisdiction / group filer combination, then right click in a row header cell with an orange triangle and select “Insert Suppressed Member”.DM 30b1 – Return Data: National Group Filer to Local Group Filer
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 198. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Data Integration" Dashboard DM 30b1 – Return Data: National Group Filer to Local Group Filer Select a WF entity, a Local Jurisdiction, and a Group Filer entity (UD7) that you want the National Return data to be copied into. This schedule can only copy or clear one POV at a time. The bottom section of the toolbar will update with a “timestamp” with the last time a “bulk” copy or clear was executed. The timestamp will not be updated if the “All Entities” check box is not selected. After a copy is completed, a 1 is entered to account TXP_Data_Copy_30b1. A Cube View is supplied in the dashboard to show the user which Entity, National Jurisdiction, Group Filer entity (UD7) has been copied to which Entity, Local Jurisdiction, Group Filer entity (UD7). You must select the RTP Year that you want to process. The JD RTP year/month is pulled from Schedule 02 Set the Return Year. The RTP year drives the copy / clear business rules. The JD RTP period is for informational purposes only. As each Local Jurisdiction can have a different RTP year/month, the cube view only shows the current jurisdiction. The last three columns help explain the varianceDM 20a Admin – Provision Data: National (Group Filing: Yes or No) to Local (No GF)
The following has been taken from the Tax Provision Blueprint "Instruction Guide" starting at page 194. See KB article: "Tax Provision Blueprint Instruction Guide - PV7.3.0 SV100" See KB article: "Data Integration" Dashboard DM 20a Admin – Provision Data: National (Group Filing: Yes or No) to Local (No GF) Select a WF entity and a Local Jurisdiction that you want the National Provision data to be copied into. This is the only copy schedule where you can also select “All JD’s”. If the “All Entities” check box is selected, then all the entities in the combo box will be copied or cleared. It does not matter what is in the entity POV; the check box supersedes the entity POV. We refer to this as a “bulk” copy or clear. If the “All JD’s” check box is selected, then all the JD’s in the combo box will be copied or cleared. It does not matter what is in the JD POV; the check box supersedes the JD POV. We refer to this as a “bulk” copy or clear. If the “All Entities” check box is not selected, then only the POV selected in the entity combo box will be copied or cleared. If the “All JD’s” check box is not selected, then only the POV selected in the JD combo box will be copied or cleared. You can mix and match these two check boxes. To have all entities and all JD’s copied or cleared, then both check boxes need to be selected. The bottom section of the toolbar will update with a “timestamp” with the last time a “bulk” copy or clear was executed. The timestamp will not be updated if the “All Entities” check box is not selected. The “All JD’s” is not considered for the timestamp. After a copy is completed, a 1 is entered to account TXP_Data_Copy_20a. A Cube View is supplied in the dashboard to show the user which Local Jurisdictions have copied data. We have created a flow member called “TXP_ConfirmBal_001” that holds the copied flow members. This parent member is strictly used to expand or collapse a row in the CV. The aggregated value is meaningless but shows you where there is data. Right click on any data cell and select “Drill Down”. Then expand the flow dimension to see the breakdown of the three accounts.
