Area of change | Details and limitations |
|---|---|
Support for the updated HMRC v1.993 online filing service, business rules, and validations | We updated ONESOURCE for the new v1.993 business rules and validations for online filing submissions, and offline validations. These will be applied to all FY 2015 and later submissions and offline validations made following this release. |
Support for the new CT600 (2025), CT600F (2025), and CT600L (2025) | We added support for the new CT600 form and CT600F and CT600L supplementary pages, relevant from the beginning of April 2025. This supports the disclosures and business rules for validations and submissions under v1.993 of the HMRC online service, however we continue to support the existing CT600 (2024) form together with the CT600F (2023) and CT600L (2022) supplementary pages where you are already using these. Both CT600 options will be available from the Tax calculation [A] and Information for the return [P] sheet menus where the CT600 (2024) has not already been developed into the file. To replace the existing form with the CT600 (2025), simply erase the existing form. All new computation template packs and existing files for FY 2024 have been updated to support the new forms, and a note is added to W_FIXES to confirm when an existing file has been updated. |
Changes in the CT600 (2025) | The main CT600 (2025) form changes are:
We updated the Information for the return [P] sheet to support the relevant options and flags above. All new computation template packs and existing files for FY 2024 have been updated as part of the support for the new CT600. |
Updated CT600F (2025) form added | The main changes to the form are the inclusion of the new managed rate for tonnage tax and various text changes. We updated the Tonnage tax computation sheet to support these changes, including a separate calculation of the “Daily profit - managed” where appropriate, and a separate table showing the relevant rates and limits for managed ships. All new trade and multi-trade template packs and unsubmitted files for FY 2024 have been updated, and a note is added to W_FIXES to confirm when an existing file has been updated. As made clear in the note on W_FIXES, the new “Managed only” option and calculations will only be available from newly inserted rows on the Tonnage tax sheet where this already existed in the file. |
Updated CT600L (2025) form added | The changes to the form are mainly text changes to incorporate the new enhanced R&D-intensive support (ERIS) and merged RDEC schemes. |
New CT600P preparation | The new CT600P for creative industries was withdrawn by HMRC shortly before this release. However, we added and amended links from the Creative industry expenditure credit and Creative industries relief sheets to support the new boxes on the CT600 in respect of the creative expenditure credit and creative enhanced expenditure regimes:
We made the following changes to the Creative industry expenditure credit sheet to support the CT600P when it is released by HMRC (currently scheduled for April 2026):
We likewise made changes to the Creative industry relief sheet to support the CT600P:
|
Area of change | Details and limitations |
|---|---|
Creative industries - new qualifying low-budget productions 53% rate | You can now claim the AVEC (low-budget film) tax credit of 53% on qualifying creative expenditure from 1 April 2024. On the Creative industry expenditure credit sheet, choose "AVEC (low-budget film)" as the type of expenditure credit being claimed. The relevant credit rate has been included in the “Tax rates and expenditure percentages” section. |
EOGPL changes from 1 November 2024 | We updated the Energy (oil and gas) profits levy sheet to reflect the following changes effective 1 November 2024:
|
Hire cap restriction offset - CT600 requirements | Following HMRC confirmation, we updated the Losses and allowances sheet, Calculation of tax liability sheet, and relevant CT600 boxes to ensure that boxes 275 and 285 of the CT600 are completed correctly when amounts are offset against current period non-ring fence profits from either current period or brought forward hire cap restriction. |
CT600L box L75 – HMRC error and temporary workaround | The new merged RDEC rules introduced by Finance Act 2024 were incorporated into ONESOURCE Corporate Tax in our Q2 2024 release. At the time of the release, we were aware of an issue which we raised in the release notes as follows: We have identified an issue with the CT600L for periods beginning on or after 1 April 2024 where the tax credit cap exception applies. Our understanding is that box L75 Total relevant expenditure on R&D workers’ PAYE and National Insurance contributions should be zero when the tax credit cap exception applies, and box L80 Step 3 restriction carried forward to next AP should also be zero as there is no restriction to carry forward. However, this scenario will trigger validation error 9746 which states that box L80 must be the maximum of box L70 less box L75 and zero. We have written to HMRC for guidance and await their response. We received a response from HMRC on 27 March 2025 which acknowledges an error and sets out a temporary workaround until the problem can be resolved in the 2026 version of the CT600L. Unfortunately, due to this late notice, we were not able to include HMRC’s workaround for this release and the correction will be made in our next release. In the meantime, should you be affected by this scenario, please contact the Support team who will assist you in making the necessary changes to your computation. HMRC’s updated guidance and full notes on the workaround can be found here. The key points are as follows: "If you are claiming an exemption, please ensure that the amount entered in Box L75 equals the amount entered in Box L70, so the amount of Step 3 restriction carried forward to the next accounting period in Box L80 is zero. You must also add a note in your computations or in a PDF attachment with your CT return, that you are claiming an exemption under section 112E CTA 2009. We will update the service in April 2026 to fix this issue." |