The principles of the RDECX methodology are such that projects should still be documented and evidenced in line with ongoing HMRC requirements. The index provides a new and more objective lens for deciding whether a project is eligible. This additional level of assessment will assist in making the claim more robust. It allows companies to be more self-sufficient and is very likely to deliver greater efficiency in time and cost.
HMRC are not able to approve or endorse applications such as RDECX. The index has been discussed in detail with HMRC R&D specialists however, at launch, there will be a significant proportion of the HMRC R&D team who will not be familiar with the index. However, even with use of the index, projects should still be evaluated in line with ongoing HMRC requirements. HMRC will be provided with a universal log in to RDECX and so our expectation is that familiarity with the index will increase over time.
It is important that projects are evaluated and documented in line with HMRC guidelines. If the company is claiming up to three projects, it must include details for each one. If four or more projects are claimed, it should include all details of at least three to cover 50% or more of the total qualifying R&D costs. For those projects that are not documented in applying these guidelines, we would recommend that the index is nevertheless used to provide supportive evidence for inclusion.
The company could consider seeking an expert validation (see Expert Support) if they believe the project may be qualifying and it is worth investigating further. Please contact the RDECX team for more information.
This might indicate that the project is being considered too broadly where, looked at as a whole, there were significant elements of routine development. If broken down into two or more components some of these elements may be associated with a greater level of scientific or technological uncertainty. In which case, there would be merit in evaluating the components separately.
Absolutely not. Many projects will be eligible where there is no third party evidence. Please note that the evidence must be independent and give a strong indication that the project represents a scientific or technological advance. If the index is lower than 50% and there is no evidence the company could consider seeking an expert validation (see Expert Support). However, there is no guarantee that this will generate a positive outcome. Please contact the RDECX team for more information.
As a first step we would recommend, where appropriate, discussing the project with colleagues as this may provide a wider perspective around the scientific or technological baseline. The company could consider seeking an expert validation (see Expert Support). Please contact the RDECX team for more information.
If there are no alternatives in assessing cut off (beginning, end and excluded activities) or qualifying expenditure with greater accuracy, the company could consider claiming on reduced costs in order to provide greater certainty that the amount claimed could not be considered excessive. Going forward, we would recommend that new processes and controls are implemented to ensure improved accuracy in identifying qualifying activities and costs.
Our recommendation is to make full disclosure at the point of submission. FTI Consulting’s evaluation schedules and templates have been developed to address all the key criteria in a concise manner ensuring the level of disclosure is sufficient but not excessive.
To validate qualifying R&D in areas of uncertainty FTI Consulting have partnered with Patent Attorneys who are trained in interpreting innovation as applied to BEIS Guidelines for R&D. Not only do they bring in an objective 3rd party perspective, they are naturally disposed to identifying innovative qualities, where they exist, in order to support a project. There are different options of validation that can be used depending on the scale of the project. The output is consequently more certain and robust, putting forward a stronger case where the advance is less clear cut. However, there is no guarantee that this will generate a positive outcome. Please contact the RDECX team for more information.
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
PHPSESSID | session | This cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
lang | session | This cookie is used to store the language preferences of a user to serve up content in that stored language the next time user visit the website. |
Cookie | Duration | Description |
---|---|---|
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_gat_gtag_UA_147514514_1 | 1 minute | Set by Google to distinguish users. |
vuid | 2 years | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
Cookie | Duration | Description |
---|---|---|
bscookie | 2 years | This cookie is a browser ID cookie set by Linked share Buttons and ad tags. |
Cookie | Duration | Description |
---|---|---|
AnalyticsSyncHistory | 1 month | No description |
li_gc | 2 years | No description |
CP5XKN6QLDFWUC | session | This cookie is provided by the Calculated Fields form. This cookie is used by the online calculators on the website. Without the Calculated Fields cookie the instant quotation may not work. |
UserMatchHistory | 1 month | Linkedin - Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor's preferences. |