September 19, 2025

We've expanded ONESOURCE™ Tax Provision’s DataQuery Reporting tile with 2 new dashboards to provide deeper insights into your tax data.

component-detail-state
: View detailed line-by-line information specifically from State Provision report.
ETR Waterfall:
Analyze various components that increase or decrease the effective tax rate for a selected period, dataset and unit, culminating in the total effective tax rate.

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.

We've introduced additional ONESOURCE™ Tax Provision OData APIs (Link: Thomson Reuters Developer Portal Home). These endpoints enable a user to access calculated report data for datasets and units based on specific user permissions within the default instance, enabling flexible data analysis. Below is the list of added endpoints:

effective-tax-rate

We added a new functionality to manage OData datasets. Administrators can now choose which datasets are exposed via OData. To enable datasets for OData:

Go to
Administration
Manage Datasets
Datasets
Export
.
Specify a name for the export file.
In the exported file, go to
#CD#
Datasets sheet.
In the ‘OData’ column enter
1
to enable or
0
to disable for each dataset.
Import the updated file via
Administration
Manage Datasets
Datasets
Import
.

Auto-Default of Adjustment Types When same is left Blank:

In Workpapers, the

Adjustment Type

field was changed from mandatory to optional in Function Wizard interface across 13 data entry areas. When left blank, the system automatically pulls amounts for both Current and Non-Current types for TD categories, and both P/L AND Equity types for PD categories.

Implement the Bridge Import performance in bridge API:

When a user imports data via the UI, the system checks if Enhanced Performance is enabled and routes the request accordingly. If enabled, user selections are stored in a new table structure for optimized processing.

Unable to search sub-tier of a sub-consolidation:

The

Reporting

screen's search function under Report Level didn't return sub-tiers of a sub-consolidation, only the sub-con itself. This prevented users from easily locating and running reports at the sub-tier level. The user will now be able to search sub-tier more effectively.

The

rollups

OData endpoint has been enhanced to display all available component rollup sets including the new ETR Materiality rollup set.

We've reorganized the columns in OData reports to improve usability and readability by aligning them with the logical calculation flow presented in the user interface

Updated Payable Account Rollforward DataQuery Reporting Dashboard

: Now displays Currency Translation Amount (CTA) and Ending Balance.

Saved Report not Visible

: For some customers, saved batch reports were missing from the UI repository display. Users could not recreate reports with the same names due to "Report exist with same name" errors, despite the reports not being visible, preventing both viewing existing reports and creating new ones with those names.

Editing temp diff from RTPGS screen clears out deferred amount

: When users edited temp diff entries from the Return To Provision GS screen in GAM, deferred amounts were incorrectly zeroed out for the edited line items. This prevented users from editing temp diffs via RTPGS without data loss.

Tax Provision report shows duplicate PTBI components from TB:

When users used the same PTBI component in both PTBI and Trial Balance data entry, the Tax Provision report incorrectly duplicated the component instead of displaying a single totaled amount. This occurred when USETBPTBI was set to 2, causing user confusion.

Read only user is able to update Data for few data entry screens:

Fixed an issue where Read-only users were able to add, edit, and delete records through API in the Detail tab of three data entry screens (Perm diff book tax basis, AT Temp Diff-Book/tax Basis, and Temp Diffs - Book/Tax Basis). This unauthorized access allowed read-only users to modify data that should have been restricted to admin and read-write users, potentially affecting other users' data.

Sign-Off transition API calls:

Fixed an issue where the signoff-transitions endpoint only returned units in "unprepared" state if they were rolled back from "prepared" instead of all unprepared units shown in the Sign-off Summary Report. This caused the OTP Dashboard to malfunction and display inaccurate data, preventing proper monitoring of tax provision processes.

Bridge import zeros out tags that weren’t selected during bridge import:

Fixed an issue when users performed bridge import on tag datasets, the process incorrectly zeroed out amounts for unselected tags instead of only affecting the selected tag. This caused data loss for other tags that weren't part of the import process, making bridge import unusable on tag datasets as it destroyed existing data for non-target tags.

Different subcons generated when creating batch reports:

Fixed an issue when users performed batch reports on selected subcons in GAM, the exported results displayed data for different subcons instead of the selected ones. This issue didn't affect OTP batch reports.

Page doesn't load if there are many GAAP-STAT Classes:

Fixed an issue when users imported 1000+ GAAP-STAT Classes into Manage Configurations, the screen failed to load and timed out after 30 minutes of spinning. This prevented users from accessing the Manage Configurations screen with large datasets.

Getting error while copying/rollover dataset in OFR enabled instance:

Fixed an issue when users performed dataset copy/rollover in OFR-enabled instances, an error message "Following problems occurred while saving" appeared despite successful data copying.

Bridge import from Developer portal API in Temp Diffs Tax basis not getting record for all class:

Fixed an issue where Bridge import from Developer portal API in Temp Diffs Tax basis failed to retrieve records for all classes, particularly for "post to selected class" across different class and subclass selections.

Data Source History Unknown Datasource – FilingUnit

: Fixed an issue where the Data Source History Screen showed 'Unknown' instead of "Manual Entry" when filing units were activated in the data entry screen. Resulting in users unable to view the entry source in the admin screen's Data Source History.

After bridge import, the record should be inserted on Temp Diff data entry screen

. We have fixed the bridge import process to ensure that Temp Diff records are inserted on the Temp Diff Data Entry screen. Previously, records were not inserted if the class was assigned any data entry rule and Post End Balance was enabled. With this update, Temp Diff records will now be correctly created regardless of these conditions, ensuring consistent data handling during bridge imports.

Bridge Import Incorrectly Aggregates Beginning Book/Tax Balances When "Post to End" is Disabled.

Fixed an issue in the Temporary Differences Book/Tax basis, where Book Beginning and Tax Beginning Balances were incorrectly changing after bridge import. The update resolves a calculation error that caused Temp Diff Tax Basis and Temp Diff Book/Tax Basis values to double when multiple profiles were selected with "Post to end balance" disabled. Additionally, calculated values now correctly populate only to the Activity column rather than spreading across Activity, Balance Sheet, and Deferred columns. This fixed ensures more accurate tax basis reporting and prevents unintended data duplication during multi-profile operations.

Bridge Import Temp Diff Book/Tax Basis.

We've resolved an issue where Temporary Differences Book/Tax Basis data failed to populate during bridge imports when the "post to end balance" option was disabled. Users can now successfully perform bridge imports for Temp Diff Book/Tax Basis data regardless of this setting. This fix ensures consistent data population behavior and eliminates the need for workarounds when importing temporary differences between book and tax basis calculations.

Component-detail-state OData Endpoint:

We're fixing an issue where certain values in Local and Reporting currency are incorrect.

We're fixing an issue in the

Payable Account Rollforward DataQuery Reporting dashboard

that caused the Currency Translation Amount (CTA) to be calculated for Local currency.

We're fixing an issue in the

TaxProvision OData API

where filtering on decimal fields returns an error instead of returning the expected records.