Corporate law Brisbane

Use of IRUs in a telecommunications capacity

HomePrivate: BlogLegal insightsUse of IRUs in a telecommunications capacity

by

reviewed by

Malcolm Burrows

Reading Time:

4–6 minutes

Indefeasible rights of use agreements (IRUs) are commonly used in telecommunications agreements for the supply of cable system capacity services.  IRUs have specific tax treatment under section 995.1 of the Income Tax Assessment Act 1997 (Cth) and are treated as capital expenditure for suppliers and customers.  Tax considerations play a central role in structuring IRUs. Below, we set out the key areas an IRU must cover to be tax compliant.

The structure of IRUs

Typical capacity agreements are structured as service agreements, whereas an IRU must be structured in the right way to be tax and accounting treated as an IRU.

The term of an IRU is usually around 15 years, during which time the supplier grants the customer exclusive access to capacity over a fibre system.  Unlike a standard capacity service agreement, typically the customer must pay the price upfront in order for the customer to have the rights to the system for the effective life of the asset and to gain the benefit of tax capital depreciation allowances which are not usually available with service agreements.

To assist in the treatment of the agreement as an IRU, the grant of access must be indefeasible and give the customer economic ownership rights over the network assets similar to those of the supplier.

What is indefeasibility?

The term indefeasible is used in property law and requires that the network asset is:

  • Identifiable: For the network asset to be identifiable, it must be within a specific fibre core, or over specific fibre strands within a certain core, or over a specific route or routes.
  • Fixed: The capacity must also be fixed.
  • Exclusive: The capacity or infrastructure must be for the exclusive use of the customer.

To be characterized as indefeasible, an IRU agreement usually:

  • does not include a right to terminate by either party; and
  • does not entitle the customer to refunds of any upfront payments.

Ownership rights over the network assets similar to those of the supplier

To capture economic ownership, an IRU usually contains the following:

  • Supplier has no obligation to provide maintenance.
  • No compensation for defective service without separate warranty provisions.
  • Customer must pay its share of the costs of uninstalling the network asset if it reaches end of life.
  • Customer is entitled to share in the proceeds of disposal of the network asset.
  • Customer is entitled to proceeds which arise from claims made against third parties in relation to the network asset.
  • Generally, no right to terminate the IRU, even where the supplier fails to make capacity available, though many IRUs do include termination rights.

Operations and maintenance services

Under standard capacity supply agreements, network maintenance, service levels and service credits are provided for the benefit of the customer.

Under an IRU, because the customer has the risk and benefit of ownership of the network asset, the customer technically has to maintain that system, however a work around can be created whereby the supplier provides maintenance and network upgrade services under an outsourcing arrangement which can be built into the IRU or form part of a separate agreement between the parties.

How fixed is the capacity?

Indefeasibility in an IRU means that fibre strands or routes need to be specified in the IRU. In commercial reality, though, it may not be possible to set this in stone.

Therefore, the IRU must include the capacity requirements that are not expected to change as well as make provision for scaling.

The business needs of a customer might require capacity on different routes at various times.  This can be covered by stating the fixed capacity requirements in the aggregate and the potential routes over which that capacity may be needed.  To activate a route, the operations and maintenance agreement can provide rights of the customer to trigger certain routes.

Another tricky scenario is where the network has not been built and indefeasibility is not fully present.  To cover this, specified point to point capacity can be specified with certain routes and strands being subject to a separate design process under a design and network build agreement.

Termination rights

In normal capacity service agreements, the customer has a right to terminate if the supplier fails to provide the capacity services and may include a refund of upfront payments.

To provide termination relief for the parties in these circumstances, the customer can be granted a put option that can be exercised by the customer where the supplier fails to provide the capacity which obligates the supplier to buy back the customer’s interest, resulting in a net refund.

Conversely, the supplier can be granted a call option that can be exercised by the Supplier in the event that the customer breaches the agreement, such as failure to pay, which then obligates the customer to sell its interest back for an amount that would be equal to the amounts outstanding.

Takeaways

IRUs are complicated and require a careful collaboration of legal, tax and commercial considerations, often necessitating the guidance of a legal professional who specialises in technology law.

Links and further references

Legislation

Income Tax Assessment Act 1997 (Cth)

Further information about IRUs

If you need advice on IRUs, contact us for a confidential and obligation-free discussion:


Related insights about IRUs

  • Software as a service (SaaS) contracts

    Software as a service (SaaS) contracts

    Drafting a SaaS (Software-as-a-Service) contract requires careful legal consideration. This article covers the business model, Australian Consumer Law (ACL), jurisdiction and choice of law, third party access, data, user-generated content, intellectual property (IP) ownership and major clauses. Learn how to ensure an effective SaaS contract is in place.

    Read more …

  • Software licences classified as “goods” under the ACL

    Software licences classified as “goods” under the ACL

    This Federal Court case highlights the risks of supplying goods and services to Australian consumers. Companies should be aware of their legal obligations and seek advice to ensure their contractual terms comply with Australian Consumer Law. Find out more about the case and its implications.

    Read more …

  • Are software developers responsible for defects in their software?

    Are software developers responsible for defects in their software?

    Software developers in Australia may face legal liability in negligence and under the Australian Consumer Law. This article examines what is required for negligence in the context of relevant case law.

    Read more …

  • Legal challenges arising from data loss

    Legal challenges arising from data loss

    Organisations must protect confidential data from external and internal threats. Learn steps to secure data, potential data breach implications, and how a data breach notification bill may require affected entities to notify consumers.

    Read more …

  • Data Breach Bill 2016 – key data security considerations

    Data Breach Bill 2016 – key data security considerations

    The Privacy Amendment (Notifiable Data Breaches) Bill 2016 has been passed, making notification of data breaches mandatory from 23 February 2018. Find out how this could affect you and what measures you can take to protect your data.

    Read more …

  • What are Software Development Agreements?

    What are Software Development Agreements?

    Having a Software Development Agreement (SDA) is essential for any successful software development project. Learn more about the key clauses involved and how to avoid potential issues.

    Read more …

  • Legal risks in the in-app purchase model

    Legal risks in the in-app purchase model

    Software developers and publishers are offering users the chance to make In-App Purchases within their software, but there are legal risks involved. Learn how to protect yourself and your business by understanding the requirements of distribution platforms and Australian consumer law.

    Read more …

  • App developers – take care with Apple Developer License

    App developers – take care with Apple Developer License

    Creating apps for Apple devices requires adherence to Apple’s Developer Agreement, Program Licence Agreement, and App Store Review Guidelines. Learn about your rights and obligations when it comes to agreeing to Apple’s terms and conditions, and the consequences of ignoring them.

    Read more …

  • Data security – the increasing burden

    Data security – the increasing burden

    The consequences for an Australian business victim for a breach of cyber security are forecast to exponentially increase. In February 2015 the Parliamentary Joint Committee on Intelligence and Security (Committee) recommended the introduction of mandatory data breach notification scheme (Scheme) by the end of 2015.[1] Whilst the details of the incoming Scheme are currently scant,…

    Read more …


Posted

in

,
Send this to a friend