Also, I think that's where the AA process mentioned by WiB could be very useful.
- Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
- Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
Inside IR35 and R&D
Collapse
X
-
-
Originally posted by jamesbrown View PostAlso, I think that's where the AA process mentioned by WiB could be very useful.
Question from me. In WiB's case the client is classing their work as R&D and down the chain WiB can claim RDEC. What if a contractor believes he is delivering a piece of work that meets the criteria but the client isn't going down that path. Can the contractor still go ahead or does the overall piece the client is delivering have to declared as R&D?'CUK forum personality of 2011 - Winner - Yes really!!!!Comment
-
Yes, it's resolving an uncertainty.
Discussions with Advanced Assurance were very helpful because I could give specific examples, and that really helps you get a feel for it. Maybe this will help a little.
I'll give one example I discussed with AA. It was a type of financial modeling that, as far as we know, had never been accomplished. I designed it, my staff coded it, client staff ran some numbers and crunched them, I looked at results to suggest adjustments to the model, etc. Most of this was R&D, because you simply don't have a model without any of it. We didn't know that we could get a model that actually gave reasonable predictions, and we didn't know we could make it fast enough to be usable. So there was obviously uncertainty. Interface coding on this project was not R&D, but sufficient data work to inform the model for testing purposes, and the coding of the actual modeling, was R&D.
The model (we did succeed) then needed further data over an extended time period, to be fully operational. That further data work was not eligible -- the uncertainty was gone from the project by that point. I was then asked in a few months later for a mini-project to tweak the model to account for certain market conditions we hadn't considered originally. Technically, it could have been included in the first cut and if it had I'd have probably included it in the RDEC claim, since we didn't know on the first cut that it would succeed. But it was my view that there really wasn't any uncertainty any longer, and that lots of people could have designed the tweak. So we didn't claim RDEC for that job.
Hope that helps a little bit. NLUK's link mostly seems to address IT advances. My RDEC jobs have been mostly advances in financial modeling.Comment
-
Originally posted by northernladuk View PostIndeed. It would appear to be the silver bullet.
Question from me. In WiB's case the client is classing their work as R&D and down the chain WiB can claim RDEC. What if a contractor believes he is delivering a piece of work that meets the criteria but the client isn't going down that path. Can the contractor still go ahead or does the overall piece the client is delivering have to declared as R&D?
So R&D can pop up for 1-2 hours or more in the middle of a much larger project that isn't R&D, or you can have a large project that is all or mostly R&D.
If the client isn't telling you how to code, it is possible that you could hit an R&D situation of which they know nothing, in the middle of a project which they aren't classifying as R&D at all. But I would guess most programmers are not going to be doing RDEC work unless it is as part of a larger RDEC project -- like the people who coded the model I mentioned above. Technically, it doesn't matter whether the client makes a claim or not if you are actually doing RDEC. Practically, if the client doesn't view the project as R&D you better have a pretty good argument, if you are ever challenged.
For those of us with foreign clients, I believe RDEC can apply to projects for them as well, but I've not asked that.Comment
-
Originally posted by WordIsBond View PostI'll give one example I discussed with AA. It was a type of financial modeling that, as far as we know, had never been accomplished. I designed it, my staff coded it, client staff ran some numbers and crunched them, I looked at results to suggest adjustments to the model, etc. Most of this was R&D, because you simply don't have a model without any of it. We didn't know that we could get a model that actually gave reasonable predictions, and we didn't know we could make it fast enough to be usable. So there was obviously uncertainty. Interface coding on this project was not R&D, but sufficient data work to inform the model for testing purposes, and the coding of the actual modeling, was R&D.
I'm assuming it's somewhere in the space of (1)-(3). Just trying to gauge what an "uncertainty" looks like here, because pretty much everything in modelling involves resolving an uncertainty, and uncertainty may be an explicit part of the modelling (), without being particularly novel. I'm guessing it has to be something that someone working in the area could broadly point to and say, "oh, that's new", whether that is due to the model structure or the way the parameters are estimated computationally or whatever.Comment
-
Originally posted by WordIsBond View PostI was told if you ever reach the point where you stop and say, "How can we do this?", and the answer is not readily available and not found by reading experts, you may have entered into R&D territory. Once you have an idea to solve it and you are trying it, you are still in R&D territory. That may include not only coding but also testing, including constructing a test / test data. But once you are past that point you aren't in R&D territory anymore.
So R&D can pop up for 1-2 hours or more in the middle of a much larger project that isn't R&D, or you can have a large project that is all or mostly R&D.
If the client isn't telling you how to code, it is possible that you could hit an R&D situation of which they know nothing, in the middle of a project which they aren't classifying as R&D at all. But I would guess most programmers are not going to be doing RDEC work unless it is as part of a larger RDEC project -- like the people who coded the model I mentioned above. Technically, it doesn't matter whether the client makes a claim or not if you are actually doing RDEC. Practically, if the client doesn't view the project as R&D you better have a pretty good argument, if you are ever challenged.
For those of us with foreign clients, I believe RDEC can apply to projects for them as well, but I've not asked that.
It would be quicker to ask what isn't R&D in the coding world. No new product has been produced, no scientific advancement, no resolution of scientific or technological uncertainty etc.
EDIT : So. I found a really useful link, but I guess you've already seen it.
CIRD81960 - Corporate Intangibles Research and Development Manual - HMRC internal manual - GOV.UK
That seems to sit much more in line with what I am thinking and it goes a long way to explaining in detail what 'uncertainty' is and puts some more context around 'How do we do this'. Neither of which stand up very well according to that doc and it totally covers all my examples.
I wish I'd found that link before the past discussions on R&D as it would have quickly cleared up all of them.Last edited by northernladuk; 24 July 2019, 13:32.'CUK forum personality of 2011 - Winner - Yes really!!!!Comment
-
Originally posted by jamesbrown View PostInteresting. So, to get a feel for this, without giving too much away, are we talking about: 1) a new model structure; 2) a novel application of an existing model structure to a new area; 3) an application of an existing model structure in a way that overcame some novel computational challenges; 4) an application of an existing model structure to a new application/dataset in a similar way to other applications.
Originally posted by jamesbrown View PostI'm guessing it has to be something that someone working in the area could broadly point to and say, "oh, that's new", whether that is due to the model structure or the way the parameters are estimated computationally or whatever.
If you go AA you can discuss projects very specifically with them for, I think, two years, as to whether they qualify as R&D. That makes it very easy and because you'll have discussed exact projects on which you are working you'll quickly get a feel for how other projects would fit, or not.Comment
-
Originally posted by northernladuk View PostThe business needs something so the project has to ask 'How do we do this'. The solutions options document is then produced. That's not R&D. I know the situation you mean about R&D popping up for a few hours in a project but this just isn't R&D in my mind. You may have to create something using existing methodologies or code and it's definitely a solution to a problem, but R&D?Comment
- Home
- News & Features
- First Timers
- IR35 / S660 / BN66
- Employee Benefit Trusts
- Agency Workers Regulations
- MSC Legislation
- Limited Companies
- Dividends
- Umbrella Company
- VAT / Flat Rate VAT
- Job News & Guides
- Money News & Guides
- Guide to Contracts
- Successful Contracting
- Contracting Overseas
- Contractor Calculators
- MVL
- Contractor Expenses
Advertisers
Contractor Services
CUK News
- Streamline Your Retirement with iSIPP: A Solution for Contractor Pensions Sep 1 09:13
- Making the most of pension lump sums: overview for contractors Sep 1 08:36
- Umbrella company tribunal cases are opening up; are your wages subject to unlawful deductions, too? Aug 31 08:38
- Contractors, relabelling 'labour' as 'services' to appear 'fully contracted out' won't dupe IR35 inspectors Aug 31 08:30
- How often does HMRC check tax returns? Aug 30 08:27
- Work-life balance as an IT contractor: 5 top tips from a tech recruiter Aug 30 08:20
- Autumn Statement 2023 tipped to prioritise mental health, in a boost for UK workplaces Aug 29 08:33
- Final reminder for contractors to respond to the umbrella consultation (closing today) Aug 29 08:09
- Top 5 most in demand cyber security contract roles Aug 25 08:38
- Changes to the right to request flexible working are incoming, but how will contractors be affected? Aug 24 08:25
Comment