TDS Biz appealed last year's AAT decision to the Federal Court and lost.

TDS Biz appealed last year's AAT decision to the Federal Court and lost.

In recent R&D Tax news, TDS Biz appealed last year's AAT decision to the Federal Court and lost.

This case concerns a company attempting to claim the cost of overseas moulds, fabrication, CAD and assembly within its R&D Tax Incentive claim without having first attained an Overseas Finding from AusIndustry. Expenditure on overseas R&D activities is excluded unless a positive Overseas Finding is obtained.

The interesting point though is the distinction between what is an overseas R&D activity, and what is the mere purchase of components to be used in R&D activities undertaken in Australia. The latter being considered as an eligible R&D expense.

In this case, the Commissioner and the Federal Court considered that the things being done offshore were significant and warranted an Overseas Finding.

Some interesting points though:

1. Off the shelf items were caught in the overseas activity argument. TDS Biz stated that: "Hefei Kelly supplied ‘off-the-shelf’ items, e.g. motor controller, etc. which were required for the construction/assembly of the prototypes in Australia to enable the continuation of the core R&D activities in Australia as specified in 1.1 Electro- mechanical design."

2. TDS Biz did not appear to have demonstrated how and when the offshore components would be used in Australia.

The impact of this case on the regulators' interpretation of an Overseas R&D activity as opposed to a cost linked to Australian R&D activities is something which we will be seeking to further clarify in consultation with them.

This case has further highlighted the importance of having a clear distinction between R&D costs associated with Australian R&D activities, and evidence of these, as opposed to what could be seen to constitute overseas R&D activities.

Updated software R&D guidance — a step in the right direction

Updated software R&D guidance — a step in the right direction

  • Prior administration of the R&D Tax Incentive frequently misapplied understandings from the physical sciences to the software space, resulting in regulatory uncertainty and imposing ambiguous obligations on software claimants.

  • Promising new draft guidance from AusIndustry shows an improved awareness of software development processes and documentation.

  • Determining that the state of the art was insufficient, and R&D was indeed necessary, remains a key regulator focus area. While proving due diligence in this area has been clarified somewhat, explicitly specifying an ‘on balance’ threshold would be better still.

  • Ambiguity in the legislation permits significant regulator discretion. Manifesting these positive changes will be a product of sustained education within the regulator organisations, of which this is a positive first step.

Following feedback that greater clarity is required for identifying R&D in the software development field, AusIndustry has released draft software industry guidance in the hope of achieving this. This updated guidance is still in draft and subject to consultation.

We welcome the attempts to provide clarity to claimants and re-instil confidence in the R&D Incentive program. Some of the areas that were more uncertain for software R&D claimants have been addressed. In general, these were present in areas where it was implied that a very academia-style project, or biotech/pharma documentation process with explicit records should be present. Some of the language and references that remain may still imply this.

Commercial software R&D typically occurs in a more iterative, agile manner, and whilst records are kept, these often require a degree of cross-referencing and more rigour being applied to capture key aspects (outcomes of research and enquiries being key).

The upfront focus on ‘unknown outcomes’ is great to see as this is critical. Although, this test would be an ‘on balance’ assessment in each case. For example, questions may still remain as to the degree of research and enquiries required to establish the outcome cannot be determined in advance. That is, does a claimant need to have consulted external experts, if it employs experts or competent professionals? Or does worldwide literature research suffice if the employees engaged are demonstrably competent professionals? Also, companies seldom detail why existing approaches/knowledge are inadequate, more so referencing the investigations that occurred. Do these suffice if it is demonstrable existing approaches/knowledge investigated were deficient?

The references to ‘less formal’ format of record-keeping being acceptable, and explanations of what constitutes ‘experimentation’ in software development involving known, repeatable series of steps or methods, are also welcome (albeit could be made even clearer). Previously, defining certain types of tests, or the broadly used term ‘bug fixing’, as rarely being part of a core R&D activity introduced confusion and uncertainty, so it was positive to see a more balanced acknowledgement of this.

Software development predominantly makes use of existing frameworks and methods, yet can still involve R&D. Acknowledging this, and also providing a list of software R&D areas which are emerging, and how this R&D occurs in a commercial scenario would be further welcome.

Ultimately, guidance can be interpreted in a very strict manner, or with a more pragmatic industry-specific lens. We feel that this is a step in the right direction as it shows a focus by AusIndustry to understand and support how software R&D occurs in a commercial environment. Reinforcing commercial confidence in the program’s predictable administration will require positive guidance to be reflected in the regulators’ day-to-day interpretations and judgements.

AusIndustry’s draft software R&D guidance, and the public consultation link can be found here.


AusIndustry changes R&D Incentive application

AusIndustry changes R&D Incentive application

For the 2021 income year, AusIndustry has changed from the existing PDF form for registering R&D activities, to an online customer portal. The portal is aimed at improving the customer experience, and the information captured (compliance) as a part of the process.

At this time, you can begin drafting an application form but you will be unable to submit until Monday 5 July, 2021.

How to activate your R&D Incentive application so we can lodge on your behalf

1.     an authorised officer* of the company must log into the R&DTI customer portal using myGovID

*an authorised officer can be anyone the company recognises as empowered to review and approve the application

i. enter the authorised officers’ email (linked to MyGov)

ii. download and open the myGovID application

iii. authenticate the login following the prompts

2.     complete the R&D Tax Incentive preregistration questions (typical example answers below)

i. are you an eligible R&D entity - yes

ii. have you self-assessed the activities that you are claiming are eligible under the legislation - yes

iii. if you are claiming overseas activities, do you have an Overseas Finding in place for those activities - N/A

iv. if your R&D expenditure is less than $20,000, did you use a Research Service Provider (RSP) to perform your R&D - N/A

v. have you kept records to show that your activities are eligible - yes

vi. are you applying to register within 10 months of your company’s income year end - yes

3.     login to the R&DTI customer portal and open the ‘Manage access’ page

4.     add a new authorisation to access the R&DTI portal on your behalf

i. enter RSF Consulting Pty Ltd’s ABN – 88604126052

ii. select “Tax professional” as the relationship

iii. enter the start and end dates of your financial year respectively

iv. finalise the authorisation and confirm with tim.florea@rsfconsulting.com

A detailed look at the impact of new Temporary Full Expensing provisions on R&D Claims

A detailed look at the impact of new Temporary Full Expensing provisions on R&D Claims

The Australian Tax Office (ATO) has recently altered the depreciation rules, affecting R&D tax claims for periods including 6 October 2020 7:30pm onward.

In claiming expenditure under the R&D Tax Incentive, eligible entities must assess their expenses to determine eligibility. While some expenditure is straightforward to identify, there are complexities associated with others. Depreciation or the cost of assets may only be included in an R&D tax claim when the underlying tax deduction is made within Division 401 (ITAA1997), which provides standardised rules for depreciating plant and equipment assets.

The Comparison

Previously, small businesses could accelerate the depreciation of certain assets under the Instant Asset Write-Off (IAWO), however this would preclude them being claimed under the R&D Tax Incentive. The recent addition of Temporary Full Expensing (TFE) permits the accelerated depreciation of certain assets while still allowing them to be claimed under R&D.

Instant Asset Write-Off

Date (asset first used or installed ready for use) Turnover below $10m Turnover above or equal to $10m Threshold (Individual asset must be less than this amount)
2 April 2019 to 11 March 2020 Small Business rules – sub-Division 328-D (no R&D claim available) Turnover less than $50m:

Div40 (s40-82) applies

Therefore R&D claim can be made for the proportionate R&D use.

$30,000
12 March 2020 to 30 June 2021 (Important* - See note below: effective change from 7 October 2020) Small Business rules – sub-Division 328-D (no R&D claim available) Turnover less than $500m:

Div40 (s40-82) applies

Therefore R&D claim can be made for the proportionate R&D use.

$150,000

Note: For assets, you start to hold, and first use (or have installed ready for use) for a taxable purpose from 7.30pm (AEDT) on 6 October 2020 to 30 June 2022, the instant asset write-off threshold does not apply. You can immediately deduct the business portion of the asset's cost under temporary full expensing.

Special note for Small Business Entities (SBEs) – SBEs can still use the instant asset write off after 6 October, and there is no cap on the cost of assets. They can opt-out of the SBE regime for 2021 to access the Temporary Full Expensing regime instead; this will provide the same deduction under sub-Division 40BB under Division 328. Opting out of the SBE regime may have other consequences for the entity which should be considered.

Temporary Full Expensing

Date (asset first used or installed ready for use) Turnover below $50m Turnover above or equal to $5 billion Threshold (Individual asset must be less than this amount)
From 7.30pm 6 October 2020 to 30 June 2022 Sub-Division 40BB Second-hand assets can be included Therefore R&D claim can be made for the proportionate R&D use. Sub-Division 40BB Therefore R&D claim can be made for the proportionate R&D use. No limit on asset cost (other than cars)

Can claim under other depreciation rules if desired

If an asset qualifies for an immediate deduction under temporary full expensing in an income year, you can choose to claim a deduction using other depreciation rules. However, you must notify the ATO in an approved form that you have chosen not to apply temporary full expensing to the asset. The choice is unchangeable, and you must inform the ATO by the day you lodge your income tax return for the income year to which the choice relates.

WHAT TRAPS SHOULD I WATCH OUT FOR?

Balancing adjustment

The biggest one is balancing adjustments in later years. As the asset will have a zero residual value for tax, when sold, there will be a balancing adjustment required. If the asset has been claimed, in part or full, under Division 355 R&D, then an adjustment for R&D will also need to be made at that time.

Small Business Entities (less than $10m aggregated turnover)

Is the full cost of the asset being deducted under the Small Business Rules (Division 328) or Temporary Full Expensing (sub-Division 40BB) or possibly section 40-82? While the ordinary tax outcome is the same for each of these provisions only deductions determined within Division 40 (both 40-82 and 40BB) can be claimed within the R&D tax regime.

If a SBE opts out of the simplified depreciation rules, it may lose access to other benefits in FY21. This should be considered separately to determine which regime provides the most effective tax treatment. Note the lockout rules have been suspended for FY21 and FY22; so the SBE can return to the simplified depreciation rules immediately in FY23 if it opts out in FY21 and FY22.

Timing of Deduction

The TFE and IAWO are available in the year that the asset is used or installed ready for use. This may be different from when the cost of the asset is incurred or paid for. Remember that using an asset for R&D activities is a taxable use, and the asset can be deducted in the year.

For further detail, read on below where we cover the differences between, and relevance to the R&D Tax Incentive of, the following:

1.     Instant Asset Write Off (IAWO) - prior to 7:30pm 6 October 2020

2.     Temporary Full Expensing (TFE) - post 7:30pm 6 October 2020

1. Prior to 7.30pm 6 October 2020: What is the Instant Asset Write Off?

Under the IAWO, eligible businesses can claim an immediate deduction for the business portion of the cost of an asset in the year the asset is first used or installed ready for use. For companies that would otherwise have to depreciate the same asset over many years, this is a valuable tax benefit.

From 12 March through to 31 December 2020, an asset is eligible if its cost is less than $150,000 (up from $30,000) and eligibility has been expanded to cover businesses with an aggregated turnover of less than $500 million (up from $50 million). Under the current rules, businesses with an aggregated turnover:

·      below $10 million claims the IAWO through sub-Division 328-D; and

·      between $10 million to $500 million claim the IAWO through section 40-82.

How is this relevant to the R&D Tax Incentive?

Division 355 only allows you to claim a notional R&D deduction on a tangible depreciating asset that would be eligible for depreciation under Division 40.

If your aggregated turnover is less than $10 million, the IAWO is obtained through sub-Division 328-D (the simplified depreciation rules), not Division 40. Thus if you elect to apply sub-Division 328-D for an income year, you cannot claim a notional R&D deduction for the decline in value of any of those eligible assets under Division 355. This means you have a choice, and you can either claim:

·      the IAWO for the newly installed assets by electing to apply sub-Division 328-D to all eligible assets; or

·      the depreciation over the actual effective life of the asset under Division 40, and claim the R&D benefit as it arises each year (to the extent an asset is used for R&D during the year). However, if you elect to claim under Division 40, you must do so for all eligible assets, not just those used for R&D.

This means you should consider which treatment will provide the most benefit to your business, both in the immediate term and across the life of any eligible assets.

If your aggregated turnover is $10 million to $500 million, the IAWO provisions under s.40-82 automatically apply (i.e. you cannot choose not to apply them). Under section 40-82, your R&D use of the asset in the first year determines your notional R&D deduction for the entire cost of the asset. For instance, if in the year of installation, you:

·      use the asset for R&D, and then you can claim a notional R&D deduction under Division 355 for its proportionate R&D use;

·      do not use the asset for R&D, and then you can never obtain a notional deduction under Division 355 for any subsequent R&D use you might put the asset to. 

2. Post 7.30pm 6 October 2020: What is Temporary Full Expensing?

Businesses with an aggregated turnover of less than $5 billion can immediately deduct the business portion of the cost of eligible new depreciating assets. The qualified new assets must be first held, and first used or installed ready for use for a taxable purpose, between 7:30pm AEDT on 6 October 2020 and 30 June 2022.

For businesses with an aggregated turnover of less than $50 million, temporary full expensing also applies to the business portion of eligible second-hand depreciating assets.

Businesses can also immediately deduct the business portion of the cost of improvements to eligible depreciating assets (and assets acquired before 7.30pm AEDT on 6 October 2020 that would otherwise be eligible assets) if those costs are incurred between 7.30pm AEDT on 6 October 2020 and 30 June 2022.

If your income year ends on 30 June, deductions under temporary full expensing are only available in the 2020–21 and 2021–22 income years.

If an asset qualifies for an immediate deduction under temporary full expensing in an income year, you can choose to claim a deduction using other depreciation rules. However, you must notify the ATO in an approved form that you have chosen not to apply temporary full expensing to the asset. The choice is unchangeable, and you must inform us by the day you lodge your income tax return for the income year to which the choice relates.

How is this relevant to the R&D Tax Incentive?

Temporary Full Expensing is available under sub-Division 40BB and therefore, your R&D use of the asset in the first year determines your notional R&D deduction for the entire cost of the asset.

However, SBEs with an annual aggregated turnover of less than $10 million can choose to apply the simplified depreciation rules in sub-Division 328-D of the ITAA 1997.

Under the temporary full expensing rules, SBEs that apply the simplified depreciation rules will deduct:

·      the total cost of eligible depreciating assets that are first held, and first used or installed ready for use for a taxable purpose, between the Budget time and 30 June 2022;

·      the second element of cost of these assets and of existing eligible depreciating assets incurred during this period; and

·      the balance of their general small business pool.

SBEs can opt-out of the simplified depreciation rules and access TFE under sub-Division 40BB instead.  Any other impacts of the decision to opt-out of simplified depreciation rules should be considered.


Links

For more information, please refer to the below links:

Instant asset write-off for eligible businesses - ATO

Temporary full expensing - ATO

Temporary full expensing of depreciating assets - Tax Banter

Temporary full expensing opt-out Bill has passed Parliament - Tax Banter    

   

The above information is noted as a guide only and does not constitute tax advice.

Complexity in these areas is why we advise you speak to a professional to obtain the best guidance that would be relevant to your situation. 

Please get in touch with us here.

R&D Tax Incentive to support Australia’s economic recovery

R&D Tax Incentive to support Australia’s economic recovery

Some very positive R&D Tax Incentive news from tonight’s budget to support Australia’s economic recovery. 

By large it would seem the government has backed down to cutting funding to the R&D Tax Incentive program, instead opting to use it as a mechanism to spur economic growth and drive R&D investment.

Key points involve increasing the benefit:

·      For small companies, those with aggregated annual turnover of less than $20 million, the refundable R&D tax offset is being set at 18.5 percentage points above the claimant’s company tax rate (current is 16 percentage points at maximum), and the $4 million cap on annual cash refunds will not proceed.

·      For large companies, an R&D premium (based on R&D expenditure as a proportion of total expenses for the year) will be increased such that the benefit will be:

a.     8.5 percentage points above the claimant’s company tax rate for R&D expenditure between 0 percent and 2 percent R&D intensity

b.     16.5 percentage points above the claimant’s company tax rate for R&D expenditure above 2 percent R&D intensity

The government will defer the start date so that all changes to the program apply to income years starting on or after 1 July 2021, to provide businesses with greater certainty as they navigate the economic impacts of the COVID-19 pandemic.

Whilst we very much welcome the changes, program regulation may continue to pose uncertainty in areas such as companies keeping ‘adequate’ records.

More details to follow.

The standard software development lifecycle and R&D 'experiments'

The standard software development lifecycle and R&D 'experiments'

We have come across references stating that if “the standard software development lifecycle can be applied, an experiment is not required”. We believe this is a fundamentally flawed statement. Here is why:

The standard software development lifecycle involves six phases, namely:

  1. Requirement gathering and analysis.

  2. Design.

  3. Implementation/coding.

  4. Testing.

  5. Deployment.

  6. Maintenance.

An experiment is taken to involve a systematic progression of work that proceeds:

  1. from hypothesis

  2. experiment

  3. observation and evaluation, and

  4. leads to logical conclusions

The above is also commonly referred to as a scientific method, which is commonly applied in a range of industries.

Experimentation is the foundation of the scientific method, which is a systematic means of testing if something works or is true. Although some experiments take place in laboratories, it is possible to perform an experiment anywhere, at any time, even in software development.

Following a process, does not preclude an experiment having occurred, or being undertaken. In fact it reinforces a a systematic progression of work has been followed; not ad-hoc, unstructured ‘trial and error’. The standard software development lifecycle is a process, which enables experiments to be undertaken.

  • Whether or not an experiment has occurred is predicated on having a hypothesis which is:

“a particular technical or scientific idea and is commonly expressed as a relationship between variables (or technical features) which can be proven or disproven.”

The hypothesis is the idea being investigated through the systematic progression of work. The hypothesis will generally direct the design and conduct of the experiment, observation and evaluation.

Applying this to the standard software development lifecycle, the hypothesis typically occurs during phases 1. and 2 (which involve research and design).

A hypothesis in software development involves…

  • an experiment is defined by the Cambridge Dictionary as:

“a test done in order to learn something or to discover if something works or is true.”

Applying this to the standard software development lifecycle, testing typically occurs during phases 3., 4. and can even occur in 5 (which involve prototypes at various levels, and testing of these).

  • observation and evaluation is the phase where the results of the experiment/testing are assessed against the hypothesis to determine if it has been proven/disproven.

Applying this to the standard software development lifecycle, results of testing are analysed to assess if the accuracy and performance metrics associated with a hypothesis have been met. Again, this typically occurs during phases 3., 4. and can even occur in 5 of the standard software development lifecycle (which involve prototypes at various levels, and testing of these).

Ombudsman recommends sweeping changes to R&D Tax Incentive administration

Ombudsman recommends sweeping changes to R&D Tax Incentive administration

Detailed report just released by the Small Business Ombudsman recommending sweeping changes to R&D Tax Incentive administration.

This is a very promising and welcome development. I am hopeful that these recommendations will be fully adopted, instilling confidence back in the R&D Tax Incentive program as an effective and reliable incentive for business to access appropriately.

We are working closely with the regulators, the ombudsman and businesses to ensure that this objective is achieved.

Key themes:

  • where compliance examinations or audits are necessary, they should take place as close as possible to the first year of registration of a project

  • guidance material needs to be comprehensive, clearer and up-to-date and developed in consultation with small business

  • agency record keeping requirements be simplified and take into account commercial practicality for a small business

  • small business must be assisted to help identify and retain professional and responsible R&D consultants.

Link to: Summary

Link to: Full report

The Impact of Proposed R&D Tax Incentive Changes on Large R&D Entities

The Impact of Proposed R&D Tax Incentive Changes on Large R&D Entities

A QUICK RECAP:

The proposed changes to the R&D Tax Incentive (RDTI) will significantly impact large companies looking to make a claim, i.e. companies with > $20 million aggregated turnover. The key changes to note are the following:

·        Notional deductions capped at $150 million,

·        Large R&D entities are entitled to an R&D tax offset equal to their corporate tax rate plus a premium based on the level of their incremental R&D intensity for their R&D expenditure.

By large, the change reduces the benefit for most companies, and significantly complicates the process.

Below we detail the concepts of R&D Intensity and Intensity Premiums.

R&D INTENSITY:

The R&D intensity is the proportion of the R&D entity’s total expenses spent on R&D expenditure for the income year:
R&D Intensity = (Notional Deductions ÷ Total Expenditure)

Notional deductions relate to expenditure on R&D activities and depreciation on assets held for R&D  purposes.
Total expenditure relates to the entity’s total expenses reported in their company tax return. The expenses reported at item six of a company’s income tax return are the expense amounts taken from the company’s financial statements.

INTENSITY PREMIUMS:

As mentioned, large entities are entitled to an R&D tax offset made up of two components:

 R&D Tax Offset = Corporate tax rate + Intensity premium

These intensity premiums will be determined cumulatively by the entity’s R&D intensity rate as follows:

INTENSITY RANGE SQUARESPACE.PNG

WORKED EXAMPLE:

Company A has notional deductions of $5 million for the 2018-2019 income year. They also had $63 million worth of total expenses. Its aggregated turnover exceeds $50 million, meaning it is subject to the 30% company tax rate.

 Under the current R&D Tax Incentive scheme:

The tax offset would be calculated by simply multiplying notional deductions by the current 38.5% rate for large entities:

CURRENT SCHEME SQUARESPACE.PNG

The net benefit would be 8.5% of the R&D spend/notional deduction under the current scheme.

Under the proposed R&D Tax Incentive scheme:

Proposed scheme.PNG

Comparing the benefit:

PROPOSED SCHEME SQUARESPACE.PNG

THE MAIN POINT:

Introducing progressive rates to the RDTI based on R&D intensity, will effectively reduce Company A’s overall tax benefit by approximately $100k. Instead of getting a tax benefit of 8.5%, company A will now only receive a 6.48% tax benefit under the proposed scheme. Moreover, if Company A wanted to continue accessing a tax benefit of 8.5%, they would need to increase their R&D intensity to 13%. Lastly, even if Company A increased their R&D intensity to 100%, the maximum benefit they could access is 12% due to the sliding scale.

The majority of large companies will struggle to continue accessing the current 8.5% tax benefit, as most companies have an R&D intensity between 0-4%, Therefore they will only be eligible for the 4.5% tier 1 tax benefit moving forward. Given this, many large companies may consider that the RDTI is unviable if the proposed changes were to take take effect.

Deja vu: Summary of proposed cuts and timing to the R&D Tax Incentive

Deja vu: Summary of proposed cuts and timing to the R&D Tax Incentive

The proposed changes to the Research and Development Tax Incentive (RDTI) were tabled in Parliament on 5 December 2019. Debate on the Bill was adjourned and won’t resume until at least February next year. The Bill is largely unchanged from its previous incarnation.

Key points as follows:

  • Start date of 1 July 2019 – 5 plus months have already passed and it will be more before the Bill is enacted. R&D work done between July and now will attract the proposed lower rates of benefit.

  • Small company groups with less than $20 million turnover will receive the company tax rate plus 13.5% as a refundable tax offset. Currently, these companies receive the tax rate plus 16%.

  • Refundable offsets will be capped at $4 million. Amounts over $4 million can be carried forward and used to offset future income tax payments. Clinical trial activities will be excluded from this cap.

  • Non-refundable “premium” rates have been simplified to 3 categories. As the rates apply on a sliding scale, companies will need to spend 13% of their total expenses on R&D to achieve the current 8.5%. The headline rate of 12.5% cannot be achieved, even with 100% spend on R&D. This applies to company groups with turnover greater than $20 million.

  • Remove inconsistencies and inappropriate outcomes where grants, disposal of assets or sale of R&D outputs. These integrity measures have been combined to a single consistent method of adjustment.

  • Publishing the R&D expenditure for every company claiming the incentive.

  • Enabling Innovation Science Australia to issue determinations on R&D activities similar to the ATO’s Rulings program to provide enhanced guidance.

Predictions for the R&D Tax Incentive over the next 5 years

Predictions for the R&D Tax Incentive over the next 5 years

By Tim Florea, Managing Director of RSF Consulting

With another year coming to a close, and further developments in the R&D Tax Incentive space, I thought it would be useful to pause and reflect.

What does the future of the R&D Tax Incentive in Australia look like? What is the case for it as a support mechanism?

The R&D Tax Incentive has been in place in Australia for over 7 years now, following its predecessor the R&D Tax Concession (instated in 1986). These programs followed very similar schemes in leading countries such as America, Canada, and the UK amongst many. Notably, Singapore and New Zealand have subsequently followed Australia’s scheme. 

My predictions over the next 5 years for the R&D Tax Incentive

  • A more balanced approach to reviews and audits undertaken by the regulators, following a rebalancing of the R&D Tax Incentive system which was somewhat needed to ensure its integrity and longevity.

  • New guidance from both AusIndustry (on record keeping and activities with consultation currently occurring) and the ATO (on eligible expenditure and records) by the end of next year.

  • A change in the rules/benefit over the next 2 to 3 years (perhaps sooner if it is simply reduced inline with the tax rate being reduced).

  • Record keeping will continue to be a key focus and point of contention for claimants and the regulators. Claims with some merit that are reviewed will escalate to audit and be denied where records are significantly deficient.

  • More sophisticated assessments of software R&D claims, and further Administrative Appeals Tribunal (AAT) and Federal Court cases hopefully providing greater clarity for all.

The case for government support in this area

The R&D Tax Incentive is the single largest and most beneficial source of support for companies undertaking cutting-edge work in science and technology in Australia.

Innovation and productivity are key drivers of economic growth.

As economic conditions continue to change, Australia's continued heavy reliance on exporting resources, and China's economy pose key risks.

A paradigm shift needs to occur where Australia is seen as, and is, a nation supporting and promoting technological and scientific innovations.

At the moment, Australia generally follows key trends in larger economies such as that of America, and lags in the worldwide innovation index to 22nd in the world*. This places Australia as the Asia-Pacific’s sixth most-innovative country – behind Singapore, South Korea, Hong Kong, China, and Japan.

Ongoing investment and support to companies undertaking innovative technology and scientific work in Australia should be a critical focus.

The key mechanism to support this is already in place (the R&D Tax Incentive); it just needs to be seen as a reliable source of funding that is in touch with the way technological innovation occurs across sectors, and how modern companies operate.

A lot remains to be done in this area and positive collaboration between government, regulators and companies is key.


*https://ia.acs.org.au/article/2019/australia-drops-in-wipo-innovation-rankings-.html

The Impact of State Level R&D Tax Credits on Entrepreneurship

The Impact of State Level R&D Tax Credits on Entrepreneurship

A QUICK RECAP:

A recent study conducted by the National Bureau of Economic Research (NBER) has concluded that states with increased R&D tax incentives better support entrepreneurial activity, innovation, and experience greater long term growth. The study examined how the introduction of state-level R&D tax credits in the U.S. affected the rate or composition of new firm formation, as well as the quality-adjusted quantity of entrepreneurship in the given state. The results found that while R&D tax credits provided minimal impact on these factors in the first few years following its introduction, the incentives actually provided an impressive 20% increase in both quantity and quality-adjusted quantity of entrepreneurship over a ten year period.

The study can be found and downloaded <here>

IMPLICATIONS OF THE STUDY:

The research paper introduces a dilemma for policymakers surrounding the subject of tax schemes and entrepreneurship. While the study has found that R&D tax schemes do in fact support the current entrepreneurial environment, it also acknowledges that the effects of these incentives are not realised immediately as it may take years before a company develops a product or service that is market-ready.

In any case, realising the benefits of the tax incentive later on is still better than stifling entrepreneurship and discouraging firms from innovating, which may have adverse long-term effects on the economy. In fact, the study found that U.S. states that chose to prioritize investment tax credits over R&D tax credits experienced little to no impact on the overall quantity and quality-adjusted quantity of new firms founded.

OUR TAKE:

The Australian government plays a crucial role in innovation policy and fostering an environment that is conducive for long-term growth. Despite this, there have been several proposals by government officials to slash the R&D budget due to growing concern over the legitimacy of R&D claims being made. Regulators argue that several claims, and hence incentive payouts, have been going to companies carrying out activities lacking the technical sophistication and advancement that constitute R&D. While true in some cases, this concern can be addressed through better regulation of claims to ensure that funding is properly allocated to the right companies.

The R&D tax scheme provides start-ups with much needed capital to extend their runway to commercial success, and is the single biggest program supporting Australian start-ups. While the current program isn’t perfect, dialogue between both the government and small-business communities may cultivate a better understanding of pressure points within this program, as well as the expectations between parties, to bring on necessary reform to address both sides.

The positive impact of R&D tax incentives on the Australian economy cannot be ignored. With adequate government support, the increase in the number and quality of start-ups as a result of the tax incentive, may foster healthy competition, provide more job opportunities, and most importantly, catalyse innovation that will drive Australia’s long-term economic growth.

A Summary of the Recent AAT Software Case and Key Observations

A Summary of the Recent AAT Software Case and Key Observations

A QUICK RECAP:

The recently decided AAT case involving H2O Exchange Pty Ltd has highlighted particular details which software companies must take notice of should they wish to register defensible R&D claims under the Income Tax Assessment Act 1997 (Cth) & Industry Research and Development Act 1986 (Cth).

H2O Exchange Pty Ltd (‘The Claimant’) is a software company that attempted to build a software platform for trading water rights within New South Wales, Victoria, and South Australia. Soon after, they applied for the R&D Tax Incentive to try and recoup a portion the expenses incurred to develop this platform. They registered identical R&D activities for the 2014 and 2015 income years which were found invalid due to the lack of substance and evidence in key areas of the legislation, namely the Unknown Outcomes and New Knowledge sections.

The full case can be found <here>.

KEY OBSERVATIONS FROM TIM FLOREA, RSF CONSULTING DIRECTOR:

1.      New Knowledge, Unknown Outcomes, and Core Activities were poorly described, making use of generic technical terms and lacking specific details in support

2.      The claimant reused most of the previous year’s project description, impairing the claim’s legitimacy

3.      Inability to have the contracted third party and lack of supporting evidence of testing to prove complex technical work undertaken substantially weakened the claimant’s defence

4.      The expert engaged on behalf of the claimant could not support key R&D areas as detailed records were not kept, despite some merit of the work undertaken

5.      The expert engaged by the regulator held a flawed position against the claimant, but was found successful due to the claimant’s inability to substantiate its activities

OUR TAKE:

The case highlights the regulators’ recent shift in focus from a mere understanding and compliance with the Tax Incentive’s structure towards detailed record keeping and substantiation of the scope of activities conducted. The regulators have now taken the view that it’s not R&D if there are no records, regardless of how advanced or complex the capabilities being developed are.

As the regulators continue to shift to an activity scope focus, the likelihood of R&D claims being reviewed will undoubtedly increase. In order to successfully defend these reviews, you must:

·        Adequately describe the key legislative criteria in the R&D Registration Form

·        Maintain detailed evidence linked to those areas

Reforming the R&amp;D Tax Incentive

Reforming the R&D Tax Incentive

THE NEED FOR MORE R&D INCENTIVES IN AUSTRALIA

If Australia wants to be seen and regarded as fostering innovation, then the government needs to act, and put the interests of startups first. Reforming Australia’s R&D Tax Incentive should be the cornerstone of this change.

Below I explore with Detch Singh, Dhruv Singh and Tom Pisel the current startup environment:

https://www.governmentnews.com.au/type_contributors/australia-needs-more-incentives-for-rd/

R&amp;D record keeping during 'agile' software development

R&D record keeping during 'agile' software development

R&D record keeping in agile software development 

A practical guide:

As detailed in the last blog post and in response to the Tax Payer Alerts issued last year (see our summary here), RSF has developed a simple and practical guide to better assist companies with R&D record keeping.

Increased regulator activity from AusIndustry and the ATO means heavier scrutiny is being placed on R&D claims and reviews. In the interest of improving claim strength and facilitating quick responses to regulator reviews, it is necessary to retain simultaneous documents that substantiate both:

1.     The R&D activity occurring, and

2.     Employee effort attributed to it.

This guide aims to leverage existing IT project management processes where possible for easy record keeping.

Firstly, the requirements on Record-Keeping and R&D Planning as defined by AusIndustry can be found on the business gov website, with particular reference to Record-keeping requirements;

“The R&D Tax Incentive operates on a self-assessment basis. This means claimants are responsible for determining whether their activities and expenditure meet the eligibility criteria* of the program, and for maintaining records to support their registration or claim.”

*More information on which entities are eligible for the R&D Tax Incentive can be found on Page 7 in the AusIndustry Customer Information Guide.

During the progression of an R&D project, activity and efforts are captured across various modes, however, typically not in a format commonly recognised by the regulator. It makes sense to utilise existing systems for record keeping, whilst minimising the introduction of alternative measures.

IF IT AIN’T BROKE, DON’T FIX IT

Four commonly used methods are detailed below, along with how to leverage these for record keeping purposes. This creates substantiating documentation over the course of an R&D project.

1. AGILE AND STAND-UPS

It is not uncommon for companies to have regular stand-up meetings as a key part of their R&D project development methodology. During these short meetings, each developer identifies that they are working on, challenges they have encountered, and what happened to issues discussed in the previous stand-up. This allows team members to identify issues within the development. It is also a great opportunity to document work and challenges in real-time.

It is also useful after each 1 to 4-week Sprint of work to have a formal review to assess performance and plan any changes to future plans. For larger companies, the minutes of board meetings relating to the progress of R&D activities may also be recorded.

In a spreadsheet, the stand-up leader should record a line for each developer on a weekly basis, detailing what technical issues they are encountering and quickly classify them according to its feature area. Some of these areas should be previously claimed activities, if they are continuing into this year.

Copy formal reviews and/or board minutes, especially any discussion  of technical challenges that arise into your ongoing R&D  documentation folder.

2. VERSION CONTROL AND MANAGEMENT TOOLS

Two common applications of version control and project management tools are Git and JIRA. Git, including hosted services like GitHub, manages committing code to project repositories. A developer can export all of the commits made on a report by using the following code into terminal (for the relevant time period):

git shortlog -sne --since="01 Jul 2017" --before="30 Jun 2018"

The balance of commits against R&D repos and non-R&D repos can give a regulator an indication as to how much of a developer’s time can be claimed.

Likewise, JIRA - depending on the particular implementation - enables issues to be filtered by sprint, type or a custom classification key. It is also capable of recording who was assigned and how much time was taken to resolve the issue. Issues can be filtered for a selected time period and exported to Excel, which can be classified on the basis of the categorisation method chosen. Individual percentages and efforts can be derived from there.

If a classification does not currently exist that maps closely to the activities being worked on, it is advisable to add a new key or tag to issues that do. This allows very strong substantiation to be assembled quickly, with minimal disruption to existing workflows.

Which option is best depends on what you are able to classify against the R&D activities. If your GitHub repos aren’t granular enough, then classifying JIRA issues by sprint may be preferable.

This allows a time-apportionment to be calculated against each developer.

Copy documents detailing assignment up to date into your ongoing R&D documentation folder.

3. TESTING SUITE AND CONTINUOUS INTEGRATION TOOLS

Many software companies run testing environments that allow hypotheses to be articulated, implemented in code, and tested against pre-defined suitability criteria in a rapid fashion. This development paradigm enables companies to run hundreds of such experiments each day.

This allows companies to find and address bugs more quickly but is also great from a documentation perspective, with industry regulators reemphasising the importance of R&D being done within a formal experimental structure.

There are many different testing and CI tools, as well as tools to monitor server resources. Consider how your system may be able to compile a log of tests – both successful and failing builds over time – against Git commits or JIRA issues, especially if you already have a good R&D assignment in place. Ideally, we would then be able to show identified performance metrics such as page load improving over design iterations.

4. CONTRACTS AND CONSULTING

When writing contracts and invoices, adding a reference to the specific R&D activity it contributes to amounts to strong record keeping. This is because the ATO seeks specific references to “R&D. Note that while certain roles absolutely contribute to the research that defines technical requirements and direction of R&D activities, the regulator may frown upon association if they have been misreported in the accounts as “marketing” or “sales”. As such, it is important to ensure that the role description is accurate with regards to R&D activity contribution and appears consistent across contracts, invoices and the books.

On the other hand, when undertaking R&D while consulting for someone else, there are two areas where eligibility for the R&D Tax Incentive may be undermined:

1.     Remuneration for the work must be “at risk”

·       Meaning it is entirely contingent on being able to attain a specified outcome, where failure to achieve said outcome would result in a fee to not be paid out; and

2.     To claim the incentive for the development of any IP, you must have effective ownership of it

·       Meaning you have retained the right to commercialise it outside the niche implementation you were contracted for.

The above two points should be discussed with lawyers to best cover for future engagements.

The finance team should also consider the ideal classification of expenses generally as they occur. For example, instead of recording server costs under the one-line item, split off the servers supporting your R&D under “R&D Expenses”. Remember, in order to claim capital expenses under the R&D Tax Incentive, they must be nominally depreciated under Division 40, rather than the small business write-off.

Copy contracts and any research artefacts produced into your ongoing R&D documentation folder.

[disclaimer: the measures for record keeping above should be used as a guide only, with specific examples only used to illustrate direct application of the principles described. Further information on record-keeping can be found at AusIndustry source]

A summary of recent R&amp;D case law and takeaway points

A summary of recent R&D case law and takeaway points

Contents

 

1.

Rix’s Creek; Bloomfield

eligibility of R&D activities (various elements)

2.

DZXP, KRQD; QJJS

application by a MEC subsidiary

3.

Silver Mines

late applications

4.

JLSP

generating new knowledge through contracted research

5.

Docklands Science Park

substantiation

6.

Tier Toys Limited

substantiation

7.

Hadrian Fraval Nominees

substantiation

8.

Mt Owen Pty Ltd

eligibility of R&D activities (various elements)

 

 

 

Rix’s Creek Pty Ltd; Bloomfield Collieries Pty Ltd and Innovation Australia [2017]

 

Facts

®    Applicants applied to overturn a decision disallowing their claims for R&D activities.

®    Q: whether claimed activities counted as R&D activities (fell within s.73B of the Income Tax Assessment Act 1936) i.e.

o   whether systematic, investigative and experimental;

o   whether there was appreciable novelty;

o   whether innovative or involving high levels of technical risk;

o   whether activities carried on for purpose of new knowledge;

o   whether there was sufficient evidence.

 

Held

®    Claimed activities did not count as R&D activities.

 

1.     Understanding the legislation

 

Ø  ‘Systematic, investigative and experimental’ (defined following RACV Sales and Marketing)

o   Requirement of detailed documentary evidence as expected feature of activity that is systematic, investigative and experimental (following Docklands Science Park).

 

Ø  ‘Appreciable element of novelty’ (S.73B(2B)(a) ITAA; defined following Explanatory Memorandum 1996 [9.56])

o   Requirement that the element of novelty is a “fairly large constituent part of the activity”.

 

Ø  ‘Involving high levels of technical risk’ (s.73B(2B)(b) ITAA)

o   Requirement that “the uncertainty of obtaining the technical or scientific outcome can be removed only through that program of activities” (RACV).

 

Ø  ‘For the purpose of acquiring new knowledge [...]’ (defined following Mount Owen Pty Ltd)

o   Requirement that new knowledge should not be incidental; claimed activities must be carried on for at least a significant purpose of acquiring new knowledge.

 

Ø   ‘Directly related activities’ (s.73B(1)(B) ITAA)

o   Requirement of a direct and close relationship between related activity and carrying on of the core R&D activity.

 

2.     Why were the requirements not met?

 

Ø  ‘DMS Project’

o   Requirement of a direct and close or immediate relationship between the related activity and the carrying of core R&D activity.

§  Requirement not met: they only tinkered with the overall design outcome (their claimed core activity was relatively modest and claimed ancillary activities were excessive); there was insufficient evidence provided – no basic records provided e.g. on duration, comparisons, performance, vital data.

 

Ø  ‘Explosives Projects’

o   Requirement that the design, development and investigation of the concept was systematic, investigative and experimental.

§  Requirement not met: “a paucity of documentation”; no worked out plan for trial and testing; no detailed plan identifying risks and mitigative measures; no project budget; their “R&D Project Plans” were vague, generalised, undifferentiated, unchronological and unauthored.

o   Requirement of innovation or high levels of technical risk.

§  Requirement not met because a “fairly large constituent part of the activity” did not involve novelty.

§  Requirement not met because there was no “significantly greater chance or possibility of failure” compared to the usual case.

o   Requirement of purpose of new knowledge.

§  Requirement not met because it was admitted in cross examination that they were “not creating a new product”.

 

Ø  ‘Excavator Projects’

o   Requirement that the design, development and investigation of the concept was systematic, investigative and experimental.

§  Requirement not met for similar reasons as Explosives Projects i.e. inadequate recording and documentation; inappropriate methods used; uncontrollable variables.

o   Requirement of purpose of new knowledge.

§  Requirement not met because method was considered inappropriate - the claimed activities were incapable of producing meaningful results consistent with the stated hypothesis.

 

3.     Takeaway point

 

Ø  Detailed documentation and recordings are not statutory requirements (at least explicitly), but they may as well be (in connection see Docklands Science Park, Tier Toys and Hadrian Fraval Nominees).

 

 

DZXP, KRQD and QJJS and Innovation and Science Australia [2017]

 

Facts

®    Applicants were subsidiaries of a multiple entry consolidated (MEC) group and applied to overturn a decision disallowing their claims for R&D activities.

®    Q: whether the Tribunal would review their activities given their subsidiary status.

 

Held

®    Application dismissed for review.

 

1.     Why was the application dismissed?

 

Ø  If you are a subsidiary member of a MEC group, only your head entity can apply for the R&D tax incentive – the applicants were never eligible in the first place.

 

2.     Takeaway point

 

Ø  Take care in filling out the application forms.

 

 

Silver Mines [2016]

 

Facts

®    An applicant for the R&D Tax Incentive and Concession was refused on the basis that they did not register their applications within 10 months after the end of their income year.

®    Applicant requested review of that decision (they wanted an extension of time of 12 to 14 months to allow their R&D registrations).

®    Q: (i) whether late registration could ever be permissible and (ii) whether their late registration was permissible.

 

Held

®    Late registration could be permissible in limited circumstances.

®    The applicant’s late registration, however, was impermissible.

 

1.     In what circumstances is late registration permissible?

 

Ø  Late registration is only possible where the action, omission or event causing the applicant's delay is:

o   not the responsibility or fault of the applicant; and

o   not within the control of the applicant.

Ø  The more time an applicant asks for, the greater the requirements are of explanation, evidence and justification.

 

2.     Why did the applicant fail?

 

Ø  The applicant did not take timely and prudent steps to inform itself and progress its registration applications.

Ø  The circumstances causing delay were not outside the applicant’s control.

 

3.     Takeaway point

 

Ø  Don’t make a late application. The circumstances in which a late application might be accepted are exceptional, limited and based on discretion.

 

 

JLSP [2016]

 

Facts

®    The applicant was carrying out contracted research for a company X (all data/knowledge generated and rights therein belonged to X under the contract).

®    The applicant requested review of a decision which determined that their research activities under their contract were not eligible as core R&D activities.

o   The applicant was refused because it was held the applicant’s substantial purpose was not generating new knowledge but fulfilling its contractual obligations.

®    Q: whether a company carrying out research under a contract for another company could say it has a substantial purpose of generating new knowledge.

 

Held

®    The applicant’s request for review succeeded.

®    A company carrying out contracted research can still make a valid claim if it can substantiate that that the company itself holds a substantial purpose of generating new knowledge.

 

1.     How is ‘purpose’ interpreted (s.355-25 ITAA)?

 

Ø  The purpose of generating new knowledge does not have to be the purpose that outweighs all the others.

Ø  It has to more than an insubstantial purpose; substantial enough to enable the activity to be accurately characterised as conducted for that purpose.

Ø  The purpose of generating new knowledge may be a substantial purpose even if at the same time other substantial purposes also exist.

Ø  The fact that an alternative purpose for the activity may be identified as a substantial purpose does not automatically negate the purpose of generating new knowledge as a substantial purpose.

 

2.     Does it matter that the applicant itself will never have use of the new knowledge generated?

 

Ø  No.

 

3.     Takeaway point

 

Ø  It is enough that the core activity satisfies the definition of “core R&D activities” in s 355-25(1) of the ITAA (where ‘purpose’ is not interpreted too restrictively); the question of whether tax offsets are available or not is irrelevant in determining the matter.

 

 

Docklands Science Park [2015]

Facts

®    Applicant requested a review of a decision which found that its registered activities were not eligible R&D activities.

 

Held

®    Applicant failed.

 

1.     Why did the applicant fail?

 

Ø  In summary: “Common to all the activities claimed by Docklands Science Park, there is scant documentation which points to that entity having conducted any activities at all let alone proceeding to conduct core R&D activities in the manner required by s. 355-25(1) of ITAA”.

 

2.     Takeaway point

 

Ø  Detailed documentation, recording the process of each activity as it develops, is necessary to:

o   substantiate that the activity took place; and

o   establish that the activity meets the legislative eligibility requirements of the R&D Tax Incentive scheme.

 

 

Tier Toys Limited [2014]

 

Facts

®    Applicant requested a review of a finding that it was not entitled to the R&D tax offset.

®    Q: whether the applicant proved on the balance of probabilities that its claimed expenditure was “directly in respect of” eligible R&D activities for the purposes of s 73B(1) and (14) of the ITAA 1936.

 

Held

®    Applicant failed.

 

1.     Why did the applicant fail?

 

Ø  The relevant records were missing and were not available as evidence of their R&D expenditure.

Ø  The Tribunal referred to

o   Chapter C1-7 of the Australian Taxation Office's "Guide to the R&D Tax Concession" which says companies should maintain adequate contemporaneous records on claimed R&D activities and related incurred expenditure; and

o   s.262A of the ITAA which requires records to be kept "that record and explain all transactions and other acts” relevant to the ITAA.

 

2.      Takeaway point

 

Ø  Records must:

o   be detailed enough to distinguish between charges associated with eligible and ineligible R&D activities (through reasonable methods);

o   verify the nature, amount and relationship of the expenditure incurred on R&D activities;

o   show how expenditure was apportioned between eligible core and supporting R&D activities as opposed to other non-R&D activities; and

o   be generally kept for a minimum of five years.

 

 

Hadrian Fraval Nominees [2013]

 

Facts

®    Applicant requested review of a finding that it was not entitled to a R&D Tax Concession claim.

 

Held

®    Applicant failed.

 

1.     Why did the applicant fail?

 

Ø  Applicant could not substantiate the claimed expenditure.

Ø  It did not take reasonable care to account for the R&D expenditure it incurred in relation to materials, licence fees and consultancy services.

 

2.     Takeaway point

 

Ø  Companies must maintain adequate records to substantiate the R&D activities claimed and the incurring of expenditure in relation to those activities.

 

 

Mt Owen Pty Ltd [2013]

 

Facts

®    Applicant requested review of a finding that some of its activities were not R&D activities as defined in s.73B(1) of the ITAA.

 

Held

®    None of the applicant’s claims were accepted as being R&D activities.

 

1.     What were the main issues with the applicant’s claim?

 

Ø  Routine tests and common activities conducted in a complex environment are not, on their own, R&D activities – there must be evidence of a new or different approach to resolving issues.

Ø  There must be credible evidence of the purpose of conducting the activities and the existence of a hypothesis.

Ø  Where existing technologies are being combined in a new way, they must be used in an inter-related manner that generates some uncertainty in their combined effect.

Ø  Geology, safety, operational, production, economic and other commercial risks do not demonstrate technical risk – the technical risk must be from the substance of the experiment itself, and not the wider risks of the company's operations.

Ø  A specific hypothesis must form the basis for specific experimental activities (not vague & overarching).

Ø  Aggregation/disaggregation of activities – the applicant must:

o   identify and describe what was done in the activities; and

o   explain how activities collectively satisfy the definition if some or all of the activities don't individually.

 

2.     Takeaway point(s)

 

Ø  We have to identify:

o   What the activities involve;

o   A systematic progression of work with a genuine, specific hypothesis which was subsequently investigated in an experiment;

o   A new or different technical or scientific idea or proposition; and

o   Whether the generation of new knowledge is at least a significant purpose of the claimed core activity.

2018 Budget and changes to the R&amp;D Tax Incentive

2018 Budget and changes to the R&D Tax Incentive

CHANGES TO THE R&d TAX INCENTIVE

HERE IS A BRIEF LIST HIGHLIGHTING THE CHANGES TO THE R&d TAX INCENTIVE:

  • Changes will apply from 1 July 2018, pending passage through the senate

  • Lowering the rate of support for most startups to 41% (from 43.5%)

  • Introducing an intensity threshold for larger companies over $20M, rewarding R&D intensive activity with a higher benefit of up to 12.5% marginal

  • Greater scrutiny and monitoring activity

RSF Consulting's position:

In 2015, the Turnbull government announced the National Innovation and Science Agenda, or NISA. Our startup and tech community welcomed this renewed focus on Australia’s most dynamic sectors, and while the benefits of a few initiatives are yet to materialise, revisions to employee share schemes and government data access were long overdue. 

The 2018 budget departs from these priorities, and Australian startups in their growth stages will find little to celebrate. Small businesses not heavily involved in R&D may benefit from the renewal of the instant asset write-off, but startups will still be wiser to depreciate any assets used in R&D to make them eligible under the R&D Tax Incentive (R&DTI).

The R&DTI is critical to the success of many Australian startups, allowing them to access their tax losses via a refundable cash transfer, extending their runway and allowing them to conduct the experimentation required to succeed. The changes in the 2018 budget prioritise more established research and development companies, adjusting the tax credit downwardly for businesses with aggregated turnover less than $20M, and upwardly for businesses above that meet a certain threshold of claim intensity.

This intensity qualifier allows these larger businesses access to higher tax saving rates only if a sufficient proportion of their expenses are research and development. The effect will be to reduce transfers to large businesses doing incidental R&D, such as Telstra, and to prioritise support for large businesses for whom R&D is their primary concern. 

For small business (<20M aggregated turnover) the refundable offset rate will be reduced from 43.5% to 41%, and decrease commensurate to future company tax cuts. An annual cap of $4M on each cash refund will also be applied.

For large business (>20M aggregated turnover) the permanent tax benefit (difference between the tax rate and offset rate, which is not refundable for large companies) of 8.5% will be replaced by a marginal rate that starts at 4% and increases with R&D intensity up to 12.5%. Large businesses with an R&D intensity of greater than 13% will see a net benefit.

Consistent with the increase in regulator activity over the last few years, the budget reinforced a focus on program integrity. While increased scrutiny is appropriate, it is important for it to be cognisant of any additional overhead it may incur, and for it to be in touch with common R&D processes, particularly in the software sector. In this area, the regulator still lacks a breadth of knowledge over how software technology and development processes may differ from other engineering or scientific fields, making reviews an unnecessary burden.

In 2015, the Turnbull government recognised how critical innovators are to Australia’s economic future. While the R&DTI remains a key source of support for new ventures, the 2018 budget failed to live up to these ideals.

It's only R&amp;D if you keep detailed records

It's only R&D if you keep detailed records

dETAILED RECORD-KEEPING

As foreshadowed by the Tax Payer Alerts issued early last year (see blog post), the last 12 months has seen an intensive focus by both of the regulators (AusIndustry and the ATO) on R&D Incentive claims.

THE KEY FOCUS IS ON:

  • 'whole of project' claims which may include activities that are not eligible,

  • substantiation at a very granular level (i.e. activity breakdown supported by directly referenceable timesheets or task management systems), and

  • the merit of the R&D activities (level of 'complexity' and 'novelty' requiring experimentation).

An 'activity' needs to be linked to experimentation (development, test iterations) to address a unique technical problem that cannot be proven by reference to existing information.

The scope of the R&D activity is linked to the research and enablement of the experiment/s and the development/test iterations to the point the technical problem is resolved.

A very high percentage of R&D expenses to total company operations implies an aggressive 'whole of project' rather than R&D activity based claim. This may trigger a review with a high burden of proof.

The quality of the information in the AusIndustry Registration Form (rationale as to the new scientific knowledge sought by each core R&D activity, number of experiments, specific details of results and observations) is initially desk reviewed and if flags are present, this may also trigger a review.

In our experience

THE ATO IS INCREASINGLY DETAILED:

  • is very focused on substantiation of:

    • staff/contractor time and other costs

    • details of experiments focused on results, observations, evaluations and conclusions

  • starts by requesting detailed information of the experiments and results, company financials, funding sources, R&D costs, link to the R&D activities, and evidence to substantiate this

    • for example, if a developer is 100% involved in R&D activities, the expectation is that his activity could be cross referenced to a daily/hourly level. In a similar fashion involvement by a CEO is a key risk area for most claimants.

Once information is submitted, the request is either cleared with no further action, or a meeting ensues to bridge gaps in information before proceeding to a detailed audit (which may span years).

The meeting is very detailed and involves lines of questioning as to the company background, nature and location of the R&D activities, and gaps in evidence to support the claim.

EXPECT TO BE ABLE TO EVIDENCE TIME ON R&D TO AN HOURLY LEVEL

AUSINDUSTRY:

  • is increasingly applying a superficial review to information in the AusIndustry Registration Form

  • ignoring sound rationale and terminology in software development/computer science,

SEEKING A VERY ACADEMIC/SCIENTIFIC FORMAT BASED ON A DISCRETE FALSIFIABLE HYPOTHESIS, RESULTS, OBSERVATIONS, AND CONCLUSIONS

  • in a similar fashion to the ATO, starts by requesting a detailed written response to substantiate the R&D activities and evidence to support this

  • if concerns/questions remain, a site visit to meet key technical staff and better understand the nature of the R&D activities

  • may engage a industry specialist to provide an opinion in the late stages of a review/audit

With the R&D Incentive refunding 43.5% of expenses, and reviews/adjustments being retrospective, a company could face a considerable liability from any dismissed claims or adjustments. For example, not understanding the complex definition of 'aggregated turnover' being under $20m may result in a company that has received $600k in refunds over 2 years needing to pay this back plus interest and potential penalties.

Another key issue (especially for software companies) is that assessors often do not have a technical background and may struggle to understand the nature of the R&D activities in any information provided.

MANY COMPANIES CONTINUE TO IGNORE THE BURDEN OF PROOF REQUIRED, AND DO NOT UNDERSTAND WHAT DOES AND DOES NOT QUALIFY.

In our next blog post we will discuss a pragmatic approach to documenting details of R&D activities and associated effort.

Frascati Manual and R&amp;D in the software development field

Frascati Manual and R&D in the software development field

the frascati manual

What is the Frascati Manual and why is it relevant to R&D Tax Incentive claims?

In June 1963, the Organisation for Economic Co-operation and Development (OECD) met with national experts on research and development (R&D) statistics at the Villa Falcioneri in Frascati, Italy. The result was the first official version of the Proposed Standard Practice for Surveys of Research and Development, better known as the Frascati Manual.

Over five revisions later, the Frascati Manual is widely recognised as a cornerstone of internationally accepted definitions of R&D and classifications of its component activities. The Manual contributes to intergovernmental discussions on “best practices” for science and technology policies, and its pertinence to the Australian policy framework was reaffirmed in last year's Review of the R&D Tax Incentive (4 April 2016) authored by Mr Bill Ferris AC, Chair, Innovation Australia, Dr Alan Finkel AO, Chief Scientist and Mr John Fraser, Secretary to the Treasury. In the Review, the panel found that:

"...the definition of [eligible R&D] mirrors the principles in the OECD Frascati Manual which is regarded internationally as setting the benchmark for identifying R&D activities."

Below we set out excerpts taken from the Manual, which may help to elucidate the position of when software development qualifies as R&D. 

  • ROUTINE SOFTWARE DEVELOPMENT

77. Software-related activities of a routine nature are not considered to be R&D. Such activities include work on system-specific or programme-specific advances which were publicly available prior to the commencement of the work. Technical problems that have been overcome in previous projects on the same operating systems and computer architecture are also excluded. Routine computer maintenance is not included in R&D (see Section 2.4.1 for a more detailed discussion of borderline problems between software development and R&D).

  • SECTION 2.4.1 IDENTIFYING R&D IN SOFTWARE DEVELOPMENT

135. For a software development project to be classified as R&D, its completion must be dependent on a scientific and/or technological advance, and the aim of the project must be the systematic resolution of a scientific and/or technological uncertainty.

136. In addition to the software that is part of an overall R&D project, the R&D associated with software as an end product should also be classified as R&D.

137. The nature of software development is such as to make identifying its R&D component, if any, difficult. Software development is an integral part of many projects which in themselves have no element of R&D. The software development component of such projects, however, may be classified as R&D if it leads to an advance in the area of computer software. Such advances are generally incremental rather than revolutionary. Therefore, an upgrade, addition or change to an existing programme or system may be classified as R&D if it embodies scientific and/or technological advances that result in an increase in the stock of knowledge. Use of software for a new application or purpose, however, does not by itself constitute an advance.

2. BASIC DEFINITIONS AND CONVENTIONS

138. A scientific and/or technological advance in software may be achieved even if a project is not completed, because a failure can increase knowledge of the technology of computer software by showing, for example, that a particular approach will not succeed.

139. Advances in other fields resulting from a software project do not determine whether an advance in computer software has occurred.

140. The following examples illustrate the concept of R&D in software.

Should be included in R&D:

– R&D producing new theorems and algorithms in the field of theoretical computer science.

– Development of information technology at the level of operating systems, programming languages, data management, communications software and software development tools.

– Development of Internet technology.

– Research into methods of designing, developing, deploying or maintaining software.

– Software development that produces advances in generic approaches for capturing, transmitting, storing, retrieving, manipulating or displaying information.

– Experimental development aimed at filling technology knowledge gaps as necessary to develop a software programme or system.

– R&D on software tools or technologies in specialised areas of computing (image processing, geographic data presentation, character recognition, artificial intelligence and other areas).

141. Software-related activities of a routine nature which do not involve scientific and/or technological advances or resolution of technological uncertainties are not to be included in R&D. Examples are:

– Business application software and information system development using known methods and existing software tools.

– Support for existing systems.

– Converting and/or translating computer languages.

– Adding user functionality to application programmes.

– Debugging of systems.

– Adaptation of existing software.

– Preparation of user documentation.

142. In the systems software area, individual projects may not be considered as R&D but their aggregation into a larger project may qualify for inclusion. For example, changes in file structure and user interfaces in a fourth-generation language processor may be made necessary by the introduction of relational technology. The individual changes may not be considered R&D if viewed in their own right, but the entire modification project may result in the resolution of scientific and/or technological uncertainty and thus be classified as R&D.

  • Examples illustrating differences between basic, applied and experimental research

256. Examples from software development:

– Search for alternative methods of computation, such as quantum computation and quantum information theory, is basic research.

– Investigation into the application of information processing in new fields or in new ways (e.g. developing a new programming language, new operating systems, programme generators, etc.) and investigation into the application of information processing to develop tools such as geographical information and expert systems are applied research.

– Development of new applications software, substantial improvements to operating systems and application programmes, etc., are experimental development.

Table 3.2. Fields of science and technology

  • What science field software development belongs to

1. NATURAL SCIENCES

1.1. Mathematics and computer sciences [mathematics and other allied fields: computer sciences and other allied subjects (software development only; hardware development should be classified in the engineering fields)]

KEY TAKEAWAYS

Many companies do not understand what qualifies as R&D in the field of software development. The above provides some guidance which may help to clarify certain aspects. Beyond this, AusIndustry and the ATO have published a number of guidance documents drawing upon this.

The key for companies making a software development R&D claim is to identify eligible core R&D activities that outline a specific scientific or technical advance sought as a hypothesis. Secondly, ensuring the scope of those activities is clearly rationalised to avoid claiming for activities without a sufficient nexus. This may involve claiming support R&D activities with a sufficient nexus to enabling/supporting the experimentation, or excluding certain activities.

Talk to us today about your software development projects for a free assessment of R&D opportunities.

Our take on the recent ATO Taxpayer Alerts

Our take on the recent ATO Taxpayer Alerts

What has happened recently

The ATO has released four Taxpayer Alerts (TAs) concerning the R&D Tax Incentive program, highlighting the nature of incorrect R&D claims observed by the ATO and AusIndustry (joint program regulators).

The total annual program cost of the R&D Incentive is much higher than expected (~$4.7b). This, combined with companies/advisors not claiming appropriately or trivialising the scheme, has forced the regulator to apply even greater scrutiny.

TAs are linked for your reference as follows: 

What this means:

The TAs highlight the regulator targeting aggressive R&D arrangements, broadly described 'whole of project' claims, and claimants/advisors that trivialise what qualifies as R&D. Misconceptions such as activities qualifying based on business risk, and that all software development qualifies as R&D, have been quite common. 

The concepts covered are not new. They represent the legislative rules which have been in place since 2012. 

The concepts covered align to how RSF view, prepare and have successfully defended all R&D claims reviewed over the recent 12 months.

Any responsible and experienced R&D specialist advisor should be aware of these rules and have experience in dealing with regulator audits.

It is highly likely that over the next 12 months, greater review and audit activity will ensue as greater focus is being placed on R&D claims.

This typically is in the form of an initial request for further information, clarifying aspects of the R&D claim, or a site visit. Over the last 12 months we have been involved in 5 such reviews, all of which have been cleared. Over the last decade, RSF Director, Tim Florea has been involved in over 50 reviews/audits, all successfully defended with positive outcomes. 

Both the ATO and AusIndustry undertake regular reviews of claims to ensure compliance, and this should not be a cause of concern.

What we are doing about it:

  • Applying a greater focus on clearly defined R&D activity descriptions, and advising clients on rules and substantiating documentation required on a real time basis.

  • Liaising with the regulator to clarify areas of ambiguity.

  • Providing direct feedback and input as a part of the State Reference Group panel on policy and relevant issues.

We are confident in the integrity of the R&D claims we assist to prepare, and have critically challenged and rejected preparing claims with marginal merit.

Overall we welcome greater scrutiny applied in this area as it will help preserve the R&D Incentive program for the long term to support companies innovating in technology and science, aligned to the National Innovation and Science Agenda.

If you wish to discuss any of the above further, please contact our Director Tim Florea on 0432 401 222, or email tim.florea@rsfconsulting.com.