2026

June 2026 release notes

Feature Enhancements

Index (Table of Contents) Entries Deduplicated for Multi-Print Sheets
When printing returns that include multi-print sheets (sheets designed to repeat for multiple entries such as partners or beneficiaries), the Table of Contents (Index) now shows only a single entry per sheet, rather than generating a separate entry for each instance. This makes printed outputs cleaner and easier to navigate, particularly for returns with a high number of repeating entries.
iXBRL Review: Cross-References Now Rendered as Clickable Hyperlinks (UK)
When reviewing iXBRL returns, cross-references to other sheets (e.g., 'A9') are now rendered as clickable hyperlinks within the iXBRL document. Users can navigate directly to the referenced sheet or section, making it easier to validate figures and trace data during review.

Notable Defects Remediated

Workbook Changes Not Saved Despite 'Save Successful' Notification
  • Previous Behaviour
    : In certain circumstances, the 'Save Successful' notification was displayed before the workbook data had been committed to the database. If an exception occurred during the save process after the notification appeared, changes were silently lost and the calculation remained in an inconsistent open state. Subsequently, printing would not reflect the latest changes, and users were prompted to save again despite having already done so.
  • Current Behaviour
    : The 'Save Successful' notification is now only displayed after data has been fully committed to the database. If a save operation fails for any reason, a 'Save Failed' notification is shown. Post-save, the calculation is in a consistent state, print output reflects the latest saved data, and no spurious save prompts are shown during refresh or print.
Print Operation Causes Calculation to Become Unresponsive
  • Previous Behaviour
    : In certain scenarios, initiating a print operation caused the process to enter a stalled state, resulting in the print never completing. Attempting to reopen the calculation after this point resulted in an indefinite loading screen, effectively blocking access to the calculation.
  • Current Behaviour
    : The underlying issue causing the print process to stall has been resolved. Print operations complete correctly, and calculations can be opened normally immediately after a print action.
Automatic Data Updates Applied Before User Action, Risking Data Loss
  • Previous Behaviour
    : Consolidation data updates were being applied to calculations automatically — before the user clicked the 'Data Update Available' prompt — which could overwrite unsaved changes in the calculation without warning.
  • Current Behaviour
    : Data updates are no longer applied automatically. Updates are only applied when the user explicitly acts on the notification, ensuring any unsaved changes in the calculation are not overwritten without the user's knowledge.
'Duplicate Key' Error When Opening / Saving a Calculation
  • Previous Behaviour
    : Opening or saving a calculation occasionally produced an 'An item with the same key has already been added' error. This was caused by certain calculations having more than one sheet with the same sheet reference — a state that should not occur but was present in some affected calculations.
  • Current Behaviour
    : While the root cause of how duplicate sheet references arise has not yet been fully addressed, a change has been made to allow affected calculations to open and save successfully. Where duplicate sheet references are detected, the system automatically assigns a disambiguating suffix to the duplicates (for example, a sheet reference D8 appearing twice would result in D8 and D8_DUP, or D8_DUP and D8_DUP1 for further duplicates). Users are notified of this with the following message: "Some duplicate sheet references were updated (e.g., D13_DUP) to prevent open/save issues. Please review and rename them if required, and save the calculation to retain these changes." Users are encouraged to review and rename any such sheets as appropriate and save the calculation to retain the changes.
Pushdown Override Option Causes Unknown Exception in Rollforward Calculation
  • Previous Behaviour:
     In Australian tax calculations, selecting the pushdown override option on a rollforward calculation resulted in an unknown exception, and the override value could not be applied. •
  • Current Behaviour:
     The pushdown override option in rollforward calculations now works as expected. Users can select and apply pushdown override values without encountering an error.
Values Do Not Flow Correctly After Unlinking and Relinking Prior Period
  • Previous Behaviour:
     When a user unlinked and then relinked the prior period calculation, values did not flow correctly to their respective descriptions. Data was misaligned relative to the expected layout, leading to incorrect figures being shown.
  • Current Behaviour:
     Prior period data now flows correctly to the appropriate descriptions after an unlink and relink operation. Values are correctly matched to their respective rows following prior period changes.
WORKPAPERS GET Function Not Returning Data for Australian Reports
  • Previous Behaviour:
     The WORKPAPERS GET function was failing to fetch data for certain Australian reports that return large volumes of data — specifically the Trial Balance (TB) and Tax Effect Accounting (TEA) reports. These reports were taking over 60 seconds to retrieve, causing a gateway timeout and resulting in empty or incomplete outputs in Workpapers, even though the same data loaded correctly in the OCT UI.
  • Current Behaviour:
     The WORKPAPERS GET function now correctly retrieves and displays data for Australian reports, including the Trial Balance and Tax Effect Accounting reports, within the required time limits.
Pushdown Updates Not Applied Until Child Entity Calculation Is Manually Opened
  • Previous Behaviour:
     Pushdown updates from parent entities were not being applied to child entity calculations unless the child calculation was manually opened by a user. This meant group and subgroup calculations could reflect stale data until the user intervened.
  • Current Behaviour:
     Pushdown updates now flow automatically to child entity calculations without requiring them to be manually opened. Group and subgroup calculations reflect the latest data from all underlying entities as expected.
AU E-Filer Form View: Missing IDS Section H and Incorrect Year Display for Losses Carried Forward
  • Previous Behaviour:
     The e-filing Form View was missing the IDS Section H (Debt Deduction Creation Rules) content, and the year displayed for Losses Carried Forward did not match the corresponding values in the XML and PDF outputs.
  • Current Behaviour:
     Section H now appears correctly in the Form View, and the year displayed for Losses Carried Forward is consistent with the XML and PDF outputs.
API Returns Duplicate Entity Error for Entities Shared Across Clients
  • Previous Behaviour:
     The public API incorrectly raised a duplicate entity error when an entity name already existed under a different client. This prevented valid API operations in environments where the same entity name is legitimately used across multiple clients.
  • Current Behaviour:
     The duplicate entity validation now correctly checks for uniqueness within the scope of the relevant client. Entity names shared across different clients no longer trigger a false duplicate error.
Line Item (CLI) Descriptions Displaying as Blank
  • Previous Behaviour:
     In some cases, custom line item (CLI) descriptions could appear blank in client templates or calculations. This issue has been observed across different scenarios and could not always be consistently reproduced.
  • Current Behaviour:
     Updates in this release address specific scenarios identified during investigation related to how line item relationships are created, updated, or refreshed, where CLI descriptions could appear blank. In addition, enhanced diagnostic logging has been introduced to improve visibility into these processes and support further analysis. Note: These changes target known scenarios identified to date. As this issue may have multiple contributing causes, it may not be fully resolved in all cases. The enhanced logging introduced in this release will support further analysis and help accelerate resolution of any additional occurrences.

Known Issues

For the most up-to-date list of known issues, refer to Alerts and Notices.

This article applies to:

  • Product: ONESOURCE Corporate Tax