Skip to main content
Current release notes
Search
Search Tax Provision (ONESOURCE) Support Help and Support.

This article applies to:

  • Product: ONESOURCE Tax Provision

March 24, 2026

New features

  • Add Jurisdiction to Bridge Mapping and Bridge Import Logic:
     Bridge mapping enhancement supported jurisdiction-level rules instead of individual unit mappings. Previously, users mapped each unit separately; jurisdiction-based mapping automatically applied rules to all units within a country.
  • BRIDGE_PERF_ENHANCED
     system parameter was upgraded for all customers with the latest code to improve performance. Bridge import processing has been enhanced to handle large volumes of data. The import functionality now processes and imports data in a significantly shorter time, improving overall system efficiency.

Resolved issues

  • We resolved an issue where the total of certain temporary differences on the
    Deferred Balances State OData
     endpoint didn't equal the
    Ending Balance
     shown on the Deferred Balances FBOS report in ONESOURCE Tax Provision.
  • We resolved an issue where the
    Beginning Balance
     on the
    Deferred Balances State OData
     endpoint displayed incorrect values.
  • Deferred Book/Tax Detail | Header is missing in Batch reports for PDF format:
     When users generated the Deferred Book/Tax Details batch report in PDF format, the header was missing, though it appeared correctly in XLSX format. This issue caused slight user confusion when reviewing the report.
  • Workpaper tab throws error in accounting firm if the user account has more than 20 chars or @ in the account name:
     In a Workpaper-enabled accounting firm instance, users with account names longer than 20 characters or containing @ received an error when selecting the
    Workpaper
     tab. This prevented them from using Workpaper in OTP Accounting Firm instances.
  • Unable to import sublines with ‘&’ but able to add manually:
     Trial Balance sublines with
    ‘&’
     in the account code weren't imported from the categories file, although the same data saved correctly when entered manually at
    Administration
    Manage Trial Balances
    .
  • Unable to assign filing units for States:
     Users couldn't assign a filing unit to a state in
    Manage Units
    .
  • Override rates are not getting imported on a newly created dataset:
     When users imported a dataset into a new dataset, overridden unit tax rates were lost because later-imported parameter and rate sheets reset them to default values.
  • JE Report Datastore Number Audit Trail Report columns are misaligned:
     When users ran the
    View Numbers Data Source History
     report for
    JE Report Datastore
    , columns became misaligned starting with Report Unique ID, causing values to appear under the wrong headers.
  • Error Unhandled Database Error Code:
     Editing line items in the
    GAM Temp Diff
     or
    NOL
     screens failed when
    Advanced True Up Posting
     was enabled. The changes weren't saved, and an Unhandled Database Error appeared.
  • GLM Classic: Error 500 on Reporting Unit Rollup Creation - Webservice Failure to Pull ONESOURCE Tax Provision Units:
     GLM Classic fails to pull OTP units for Reporting Unit Rollup. Users receive Error 500 when creating a rollup after selecting ONESOURCE Tax Provision and year, instead of the expected OTP units display for mapping.
  • Book Trial Balance: Amount is posting as zero when a bridge import is performed with an R/W user:
    A Bridge Import defect caused amounts to post as zero in Data Entry. The job completion preview displayed correct non-zero calculated amounts, but Data Entry Book Trial Balance showed Amount posted as 0 instead of the expected values.
  • Bridge Import: Data is not populated when User selects single component for Book Trial balance/Tax Account:
    Bridge Import fails to update data when selecting individual components. For Tax Accounts only, preview shows data but units remain. For Book Trial Balance only, preview displays data but Data Entry screens show no rows for R/W and Custom users.
  • Data Entry Amounts Being Doubled Across Perm Diff (Book/Tax Basis), Temp Diff (Tax Basis) and Book Trial Balance Screen:
     API-triggered Bridge Import intermittently doubles values in Perm Diff (Book/Tax Basis), Temp Diff (Tax Basis), and Book Trial Balance. This occurs either when using API alone or when API import follows UI import without clearing data, causing values to stack instead of replacing.
  • Book Trial Balance: Amount is posting as zero when a bridge import is performed with an R/W user:
     A Bridge Import defect caused amounts to post as zero in
    Data Entry
    . The job completion preview displayed correct non-zero calculated amounts, but
    Data Entry Book Trial Balance
     showed
    Amount posted
     as 0 instead of the expected values.
  • Bridge Import: Data is not populated when User selects single component for Book Trial balance/Tax Account:
     Bridge Import fails to update data when selecting individual components. For Tax Accounts only, preview shows data but units remain. For Book Trial Balance only, preview displays data but
    Data Entry
     screens show no rows for R/W and Custom users.
  • Data Entry Amounts Being Doubled Across Perm Diff (Book/Tax Basis), Temp Diff (Tax Basis) and Book Trial Balance Screen:
     API-triggered Bridge Import intermittently doubles values in Perm Diff (Book/Tax Basis), Temp Diff (Tax Basis), and Book Trial Balance. This occurs either when using API alone or when API import follows UI import without clearing data, causing values to stack instead of replacing.

Known issues

  • Bridge Import fails at Unit level when Unit name contains angle brackets (< >) resulting in "Completed with Errors" and no preview/data insertion:
     Bridge Mapping Import at the Unit level fails when the Unit name contains angle brackets (<>). The job completes with errors, generates no preview output, shows 0 rows affected in logs, and does not insert data into data entry screens. Users must use Consolidated-level imports as a workaround, which may not align with operational needs and can complicate reconciliation processes.
  • Bridge import wipes out previous bridge import data:
     Consolidated-level bridge imports zero out existing bridge data for units not included in the import file, affecting Temp Diff while PTBI and Perm Diff remain unaffected. Users must include all unit data in the import file or use unit/subcon level imports to prevent data loss.
  • Bridge Import: Empty-file upload fails to clear existing amounts in the Data Entry screen:
     Bridge Import jobs fail silently when an empty/blank .txt file is uploaded for all components or individual components, providing no error logs or diagnostic output on the UI. In rare cases, selecting only PTBI and Perm Diff - Tax Basis with an empty file allows the job to complete successfully but makes no changes to Data Entry screens.
  • Bridge Mapping screen – Component Code changes revert on first save attempt:
     Bridge Mappings Component Code requires 2 save attempts to persist the selected value, creating risk of incorrect configurations and unnecessary rework.
  • Bridge Mappings save succeeds but new rows don't appear in grid:
     When users add a new Bridge Mapping row in Administration-Bridge Mappings, populate required fields, and select
    Save
    , the system displays a success message, but the newly added row disappears from the grid after the loading spinner completes, sometimes showing "No items found."
  • Bridge Mappings: Column filter dropdown shows blank option for values containing angle brackets with alphabetic characters across multiple columns:
     Bridge Mappings filter dropdowns display blank/empty options instead of actual values when field entries contain angle brackets (<>) in columns such as Jurisdiction, Unit, Flex1, Flex2, or Ledger Account Code.
  • Bridge Mappings: Jurisdiction field - "Changes saved" message is misleading for >60 chars:
     When a Jurisdiction value exceeding 60 characters is entered in Bridge Mappings (for example, Perm Diffs – Tax Basis component type) and saved, the system displays a validation popup message, and the entered value requires review.
  • Perm Diff - Book/Tax Basis: Incorrect amount aggregation and row duplication for multiple mappings with same component code:
     When the BRIDGE_PERF_ENHANCED parameter is enabled (set to 1), the Bridge Import process for Perm Diffs - Book/Tax Basis incorrectly consolidates multiple mappings with the same Component Code but different Types into a single data entry row with aggregated amounts, rather than creating separate rows for each Type as expected and as occurs when BRIDGE_PERF_ENHANCED is disabled (set to 0).