July 24, 2025

New features

  1. FASB Income Tax Disclosure Update (ASU 2023-09)
    : This will enhance transparency and decision usefulness of income tax disclosures, the FASB issued an update to Topic 740, Income Taxes.
    1. Domicile Sub-Consolidation Management
      : Administrators can now designate domicile sub-consolidations through a new checkbox in Unit Sub-Consolidations settings.
    2. ETR Materiality Rollup Sets (Only applicable to Stacked CSC view)
      1. Introduction of ETR Materiality rollup set type for creating category-specific data groupings with new Standard Categories.
      2. Rollups created under this type of rollup set can be assigned to a specific Standard Category and their codes for Import/Export:
        1. Other Reconciling Items (ORI)
        2. Effect of Cross Border Tax Laws (ECB)
        3. Tax Credits (TC)
        4. Valuation Allowances (VA)
        5. Nontaxable or Nondeductible Items (NNI)
        6. Changes in Unrecognized Tax Benefits (UTB)
    3. Enhanced Reporting Capabilities for Effective Tax Rate CSC Breakout - Stacked CSC View
      1. Now only visible for ETR Materiality rollup set type.
      2. Domicile sub-consolidations will always be displayed first.
      3. Complete category visibility regardless of custom rollup assignments.
      4. Rollups that don’t meet materiality will be displayed under “Other” row.
    4. Foreign Jurisdiction Optimization
      1. Automatic consolidation of immaterial items under "Other Reconciling Items"
      2. Smart grouping of sub-consolidations that don't meet materiality thresholds
        1. Sub-consolidation displayed as a single line item if no rollups meet materiality, but the sum of rollups does.
        2. Sub-consolidation shown under “Other Jurisdictions” row if no rollups meet materiality and neither the sum of the rollups meet materiality.
  2. We have moved our reporting capabilities from PowerBI directly into ONESOURCE™ Tax Provision’s DataQuery Reporting tile. These enhancements give you more ways to access, analyze, and report on your tax provision data directly within ONESOURCE.
    Available Dashboards
    :
    1. YoY Analysis
      - Compare pre-tax income and effective tax rates year-over-year
    2. WW Tax Expense and ETR
      - View total tax provision and rates across your datasets
    3. Tax Expense & ETR by Jurisdiction
      - Break down current, deferred, and total tax by location
    4. State Dashboard
      - Analyze state tax rates, apportionment, and expenses
    5. Payables Account Rollforwards
      - Track ending balances for rollups
    6. Global Sign Off Status
      - Monitor sign-off progress across users and units
    User Guidelines
    :
    • Default time period:
      All historical data is available, but you can filter 3 years of data at a time
    • Table totals:
      Tables show totals for ALL records, not just filtered results
    • Filtering:
      You can filter data by country, dataset, currency type (local/reporting), year, and other criteria depending on the dashboard

Enhancements

In the Payable OData API, the Currency Translation Adjustment (CTA) and Ending Amount now appear as a ‘rollupname’ with its respective values in fields ‘amountlocal’ and ‘amountrptg’.

Resolved issues

  1. Manage Rollups | Saving is inconsistent while selecting Rollup dropdown:
    In the Administration->Manage Rollups section, users experienced inconsistent behavior when attempting to modify rollup selections from the dropdown menu. Specifically, when a component was already associated with a rollup and users tried to change it to "Unassigned," the system failed to save this change on the first attempt. The change was only successfully saved when users first toggled to another rollup option before selecting "Unassigned." The system should have properly saved any selection made in the rollup dropdown menu when the save button was clicked, including direct changes from an assigned rollup to "Unassigned" status. Due to which administrators could not directly unassign components from rollups in a single step. Instead, they were forced to perform an unintuitive multi-step process, toggling between different rollup options before finally achieving the desired unassigned state. This issue has been fixed
  2. Number audit trail | #UDO# Unit Dataset Options format issue for export:
    When users exported the Numbers Audit trail for Unit Dataset Options component types, the data in each cell appeared with unwanted formatting characters. Specifically, each cell's data was enclosed with =" " characters, which were visible in the exported file. These extraneous characters made the exported data difficult to read and interpret. The presence of these formatting characters created confusion for users when reviewing Unit Data Options sheets. The additional characters cluttered the exported data and potentially led to misinterpretation of the information being displayed. This issue has been fixed.
  3. Workpaper | Unit list & Range formulas not pulling unit details when a subcon name & code is different:
    An issue was identified in the workpapers functionality when attempting to retrieve data for sub consolidation using Unit List and Range formulas. The system failed to retrieve data when there was a discrepancy between the sub consolidation’s name and code in the user interface. When users attempted to use formulas to pull a list of all units under a subcontractor, the data retrieval process failed specifically in cases where the sub-consolidation’s name and code were different in the UI. This inconsistency prevented the formulas from functioning as expected. The system should have been able to pull data for sub consolidation regardless of any differences between their names and codes. The formulas should have functioned properly by recognizing the sub consolidation entity despite these naming discrepancies.
  4. GAM | Editing temp diff from RTPGS screen clears out deferred amount:
    When users edited an entry from temporary differences in the Return To Provision Global Schedule (RTPGS) screen within GAM, the system incorrectly cleared the deferred amounts for the edited line item that had an RTPGS class. After editing, these deferred amount fields displayed zero values, even though they should have maintained their original values. Editing a temporary difference entry from the RTPGS screen in GAM should have affected only the specifically edited fields while preserving the deferred amounts column values. The system should have maintained data integrity across all related fields unless explicitly changed by the user. This issue prevented users from effectively using the RTPGS screen in GAM for temporary difference edits.
  5. Data Entry | After App Temp Diff | Limitation on using filter on unit code:
    In the After App Temp Diff data entry screen, when users attempted to filter datasets containing 100+ units and 1000+ data records by unit code, the filter function displayed only a partial list of available units. Some units with existing data records in the system failed to appear in the filter dropdown options, despite having associated data within the After App Temp Diff screen. All units that had data records in the After App Temp Diff screen should have appeared as options in the Unit Code filter dropdown. The filter functionality should have provided a comprehensive list of all available units to enable complete data access.
  6. Review & Edit | Data Entry | NOL Temp Diffs - Tax Basis | Unable to Manually Enter Data on Screen for Interim Dataset:
    Under the Review & Edit tab for NOL Temp Diffs - Tax Basis, users were unable to manually enter data in the Activity, Deferred, and Balance columns. Despite having class options configured to allow editing of these fields, the input areas appeared grayed out and non-editable in the user interface. This prevented direct data manipulation within these critical columns. Clients were prevented from making manual adjustments to NOL Temp Diffs data through the standard user interface. This limitation disrupted normal workflows for tax basis calculations and required users to employ alternative, less efficient methods for data entry.
  7. Reporting Legacy | Excel Breakout option in State Provision summary report doesn't work:
    When users attempted to generate a Provision Summary report under Reporting (Legacy)->State Support with the Excel breakout (States) option selected, the system failed to produce the report. Instead, it displayed an "Error during Excel generation" popup message. This issue specifically occurred when the Enhanced View option was set to 'No' in the State Level settings under Manage Configurations. Due to which users were unable to view the State Support Provision summary legacy report in the Excel breakout (States) format when Enhanced View was disabled. Clicking on the Excel breakout (States) option should have generated the expected report without any errors, regardless of the Enhanced View setting in the Manage Configurations section.
  8. OTP API | Bridge Import | Import failed if file contain legacy unit code:
    When users attempted to use the Bridge Import API with files containing legacy unit codes instead of actual unit codes, the system failed to correctly map the units. This mapping failure prevented the proper import of data through the Bridge Import API when legacy unit codes were present in the import files. The failure of the unit code mapping functionality in the Bridge Import API prevented data from being imported when legacy unit codes were used. The Bridge Import API should have properly mapped legacy unit codes to their corresponding actual unit codes during the import process, similar to how the OTP UI handled this mapping successfully. The system should have recognized legacy codes and automatically translated them to the current unit code system.
  9. True-Up posting creates Ret-to-Prov items:
    Fixed issue when True-Up posting procedure was also creating Ret-to-Prov items in Data Entry screens.

Known issues

  1. We are currently resolving an issue on the OData APIs:
    component-detail & component-detail-state
    , where the filing unit field displays Unit ID instead of Unit Code. Further, the Reporting and Local currency amounts appear in separate rows instead of a single line.
  2. We are currently resolving an issue where the "
    Country – is not blank
    " filter on the YoY Analysis dashboard continues to display records with empty country fields. The filter is not properly excluding blank country values as expected.