2025

December 2025 release notes

Feature Enhancements

  1. Ability to Delete Mappings
    Users can now delete a map when it is not in use, i.e., not associated with any entities/journals. This simplifies mapping maintenance, reduces clutter, and gives users better control over configuration without risking data integrity.
  2. Allow Users to Update Roll Forward (RF) Flag for Non-Standard Sheets
    Users can now view and modify their
    RF
    preference for non-standard sheets via a new menu
    Tools
    Sheet Settings
    Roll Forward (Excel Sheets).
    .
    • Displays all non-standard sheets with RF decision made at the time of insertion.
    • Allows toggling of it without the need for deleting and reinserting sheets.
    • Changes persist on calculation save and are tracked in calculation history.
  3. Support Manual Journals on Conditional Mapped Accounts
    Manual journal entries now flow into calculations for accounts mapped using conditional mapping:
    • Drill-down screen displays both imported and manual journal data.
    • Journal adjustments are visible in Imports > Trial Balance for transparency.
  4. Option to Download E-Filing Packages Directly from EFM
    Users can now download e-filing packages directly from EFM under Queued and History tabs.
    • Previously only supported via eFile > Exports in OCT application.
    • Supports quick access for review and approval workflows.
  5. Split "Allow Overriding of Import/brought forward Values" permission:
    The combined permission has been divided into separate permissions, allowing administrators to assign each one individually for more granular control. This applies to databases with the new permission module enabled.
    • Allow overriding import values
    • Allow overriding brought forward values
  6. Improved Line Item Access Through Updated User Permissions:
    Three new permissions have been implemented to manage line items, minimising the potential for unintentional changes to active line items and enhancing oversight of configuration management. This applies to databases with the new permission module enabled.
    • View Line Items - Users with this permission can view the Configuration > Line Items screen, but cannot make changes.
    • Manage Line Items Not in Use - This allows users to create new line items and edit or delete any line items that aren't currently being used.
    • Manage Any Line Items - Users with this access can create and edit all line items. However, they cannot delete line items that are in use, as this could affect mappings, drilldowns, and other settings.
  7. Enhanced OSR Integration for Journal Imports
    We've improved the integration with ONESOURCE Statutory Reporting (OSR) by introducing the ability to fetch journals from a specific client. This enhancement gives you greater control when importing data in environments with multiple clients, helping reduce errors and improve efficiency.
    • A Select Client dropdown has been added to the OCT import wizard for OSR imports.
    • By default, it selects your current client, but you can easily switch to another client as needed. This change is effective when OSR enables ONESOURCE Client Manager (OCM).
    This change is effective when OSR enables ONESOURCE Client Manager (OCM).
  8. Public API to Switch Sheet Type Between Computation and Working Paper:
    Introduced a new API endpoint that allows switching sheet types programmatically:
    • Supports changing a sheet from Computation to Working Paper and vice versa.
    • Changes are tracked in the calculation history on save.
    API: POST ~/datasets/sheet -types?workbookId=ID
  9. Public API to Verify Existence of a Sheet in a Calculation:
    Introduced a new API endpoint that allows checking if a sheet exists before insertion, reducing errors and improving automation workflows.
    API: POST ~/datasets/sheet-exists?workbookld=ID
  10. Public API to Update Cells in a Calculation:
    Introduced a new low-level API endpoint for updating one or more cells in a calculation programmatically to automate complex data migration scenarios, reducing manual effort and errors:
    • Allows updating specific cells in standard and non-standard sheets.
    • Supports updates to multiple cells across the sheets in one call.
    API: POST ~/datasets/bulk-cell-update
  11. Enhanced Transition to Skip Insertion of Existing Unique Sheets (UK):
    Transition routine now checks for existing unique sheets (sheets that can only be inserted once in a calculation) before inserting new ones, preventing duplication and transition errors.
  12. Improved Naming Convention for Review PDFs in E-Filing Packages (UK & Malaysia)
    To enhance traceability and make it easier to identify the correct version of exported files, we've updated the naming convention for review PDFs generated during the E-Filing package creation process.
    New file name structure includes:
    • Calculation Name
    • Print Report (e.g., Tax computation and Returns)
    • Print Mode (e.g., "Draft")
    • Timestamp for uniqueness in MMDDYYYYHHMMSS format.
    This update ensures better version control and simplifies file identification.
  13. Generate XML Payload Without Indentation in Submission Package (UK)
    Submission packages now include XML payloads exactly as transmitted to HMRC-without indentation or formatting. This change ensures compliance and consistency for firms that use their own e-filing solutions. This change:
    • Eliminates discrepancies between submitted and downloaded packages
    • Improves compatibility for firms filing directly with HMRC using in-house tools
    • Review packages remain formatted for easy readability in browsers and XML editors

Notable Defects Remediated

  1. Screen Flicker During Data Entry
    Previous Behavior:
     The system sent updates to the screen in pieces (structure first, then cells in chunks). This caused the interface to briefly show incomplete states, leading to visible flickering as more data arrived.
    Current Behavior:
     Updates are now processed and delivered to the screen all at once. This results in a stable, smooth refresh with no flickering, creating a more seamless and reliable data entry experience.
  2. Date Formats Inconsistent on CMS Screen:
    Previous Behavior:
     On the CMS screen, the Period column displayed the dates in MM/DD/YYYY format, while Start and End Dates displayed in DD/MM/YYYY, causing confusion and misinterpretation of dates.
    Current Behavior:
     All dates on the CMS screen now consistently use same date format, improving clarity and reducing errors in date interpretation.
  3. User Preferences for Hide/Show Group Filter Not Persisted in CMS:
    Previous Behavior:
     When users customised the CMS view by hiding or showing the Group Panel and grouping columns, these preferences were lost upon navigating to other screens or logging out.
    Current Behavior:
     User preferences for Group Panel visibility and column grouping are now retained across sessions and screens, providing a consistent and personalised experience.
  4. Incorrect Application of User role Checks Under New Permission Module:
    Previous Behavior:
    User role checks were mistakenly applied to databases under the new permission module (V2), even though user roles were discontinued. This hid toolbar options like Add, Edit, Roll Forward, and workbook actions from users with valid permissions.
    Current Behavior:
    User role checks are now ignored for V2 databases. Toolbar options display correctly based on module, dataset, and entity permissions, restoring full functionality for authorized users.
  5. Intermittent Print Failures Due to Incorrect Print Titles (UK):
    Previous Behavior:
    When attempting to print, the print process intermittently failed (This was seen and reported on UK calculations). Users were unable to generate print PDFs and print titles (Print> Page Setup) on a few sheets changed unexpectedly during printing.
    Current Behavior:
     Printing now works reliably for all sheets, including those with large data sets. Print titles remain intact unless explicitly overridden by users, ensuring consistent and accurate print outputs.
  6. Invalid Values Update Dropdown Formulas Incorrectly on Import (UK):
    Previous Behavior:
     When importing data into dropdown cells, invalid values (not part of the dropdown list) replaced the formula key with incorrect entries like "See Analysis." This led to validation errors such as "All rows must have a valid option."
    Current Behavior:
     The system now preserves the original formula in dropdown cells. This prevents errors and maintains data integrity.
  7. Duplicate Sheets Inserted After Import Failure (UK and Malaysia):
    Previous Behavior:
     When an import failed (e.g., due to incorrect sheet names or partial success scenarios), the system inserted duplicate sheets automatically. This occurred in calculations created using UK Life and Malaysia templates, leading to clutter and incorrect calculations.
    Current Behavior:
     The system now prevents duplicate sheet creation during failed or partially successful imports. Only valid sheets remain, ensuring calculation accuracy and reducing cleanup effort.
  8. Review PDF Missing When Default Print Style Not Set (UK & Malaysia):
    Previous Behavior:
     If no default print style was set for a client, the Review PDF was not generated during e-filing, resulting in incomplete submission packages.
    Current Behavior:
    The system now automatically applies the "Modern" print style as a fallback when no default is configured, ensuring that Review PDFs are always generated.
  9. PDF Not Generated in Review Package if Notes & Queries Enabled (UK & Malaysia):
    Previous Behavior:
     When Notes and Closed Queries were enabled in the print style, the Review PDF was missing from the submission package after e-filing.
    Current Behavior:
     The Review PDF now generates correctly, even when Notes and Queries are enabled, ensuring complete and accurate submission packages.
  10. Unable to Download Corporate Interest Restriction (CIR) E-Flling Package via API (UK):
    Previous Behavior:
    Attempts to download CIR submission packages via API resulted in a 500 Internal Server Error, even though the package was available through the Exports page.
    Current Behavior:
     CIR packages can now be downloaded successfully via API, providing consistent access across all channels.
  11. Handle Exceptions During E-Filing Package Generation (UK):
    Previous Behavior:
     Exceptions during PDF/iXBRL generation caused silent failures and missing packages.
    Current Behavior:
     Detailed error messages are now included in the API responses for visibility.

Notable changes introduced

The 'Change Start and End Dates' feature has been temporarily disabled because of issues with incorrect tax year updates. It will be restored in an upcoming release.

December 2025 patch release notes

Improvements
1. Execute Import Jobs Serially
Description:
Previously, when multiple import jobs targeting the same calculation were initiated (via UI or API), they could run in parallel, intermittently leading to errors and data import failures.
What’s Improved:
 The system now ensures that multiple import jobs for the same calculation are executed in sequence rather than in parallel. This method ensures reliable and accurate job management.
note
In rare cases where multiple jobs are initiated at exactly the same time (to the seconds precision), there may still be occasional sequencing issues if for instance, an "append existing" job is processed before the main import job. This is due to the absence of a built-in dependency model for such scenarios. We are monitoring this and plan further improvements, but this patch release should resolve most previously reported issues.
Notable Defects Remediated
1. Import Jobs Failing for Normal and Conditional Account Maps
Previous Behavior:
 When import jobs were run with maps containing both normal and conditional accounts mapped to tax targets, the system sometimes failed to populate data correctly. This led to incomplete or inaccurate data imports, impacting downstream tax calculations.
Current Behavior:
 The issue has been addressed. Import jobs now successfully populate data even when both normal and conditional accounts are mapped to tax targets, ensuring accurate and complete data imports.
2. Excel File Name Conflicts When Saving Calculations
Previous Behavior:
When saving a calculation to Excel, the system sometimes generated files with names that conflicted with existing files for the same calculation. This led to intermittent failures, where opening the Excel files triggered repair processes in Excel and resulted in undesired output files or loss of data integrity.
Current Behavior:
This issue has been resolved. Now, whenever an Excel file is generated for a calculation, it is assigned a unique name that does not conflict with any previously created file names for that calculation. This ensures reliable file generation and eliminates the need for Excel repairs due to file name conflicts. While we believe the chances of this issue reoccurring have been reduced with this release, we continue to monitor for any further occurrences.
3. Incorrect Validation Errors Caused by Regex Failures (Australia)
Previous Behavior:
 Failures in regular expression matching resulted in incorrect validations during tax calculations. This led to validation errors and potentially inaccurate tax results.
Current Behavior:
 The issue has been fixed. Regular expression matching now works as intended, ensuring validations in tax calculations are performed accurately.
4. Review PDF Generated in Incorrect Mode During UK E-filing
Previous Behavior:
The PDF generated inside the Review package during UK E-filing was printed in Review mode. This meant the document included a “Review” ink stamp, and the filename did not indicate its final status.
Current Behavior:
The system now generates the PDF in Final mode inside the Review package. The “Review” ink stamp no longer appears, and the filename includes “_Final” before the extension.
5. Review PDF Missing Intermittently (UK)
Previous Behavior:
 During E-file package generation, the Review package sometimes missed the PDF file, resulting in incomplete packages and impacting compliance checks.
Current Behavior:
 The PDF file is now generated and included in the Review package, ensuring completeness and reliability for validation and compliance. While we believe the chances of this issue reoccurring have been reduced with this release, we continue to monitor for any further occurrences.

This article applies to:

  • Product: ONESOURCE Corporate Tax