Archive for the 'Contract Law' Category

Third Party Rights – Scots Law Stuck in the 17th Century

The Problem

Imagine you are a bank with a complex group structure, i.e. multiple companies in your group. A core computer system has gone wrong and most of the group companies have suffered loss as a result. So you sue the supplier.

The supplier’s defence is that it only has a contract with one member of the group, and while that group member can recover its loss, the supplier isn’t liable for loss suffered by the other group companies.

This is a fairly valid legal argument.

Third Party Rights as a Solution

There are various ways to reduce this “group loss v. single group contracting entity” problem. One way is to give all the group companies the right to enforce the contract against the supplier, so each of them can “kick” the supplier. These are called third party rights, because they give legal rights to a person who didn’t “sign” the contract (in legal terms a third party).

Since 1999 this has been fairly easy to do in English Law Agreements as a result of the Contacts (Rights of Third Parties) Act 1998 . (I say “easy”, but with my CYA head on I should note that there are some drafting traps for the unwary).

It has been possible to create such third party rights under Scots Law for quite a bit longer than that using the legal right “ius quaesitum tertio”, or “IQT”.  You can tell its really old because it has a Latin name! 

Moving Contracts between Scotland and England

As a lawyer working in England in the mid nineties I sometimes “moved” contracts to Scots Law in order to create third party rights using IQT.

However, since the English Act came into force I find myself doing the opposite, i.e. moving contracts to English Law in order to use the English third party rights legislation. 

Why?

Well because the IQT is massively inflexible when compared to the position under the English Act. For example, once you create a third party right under an IQT it can be very difficult to amend it or kill it. In contrast that is possible under the English Act (if you draft the clause correctly).

Recently I had a contract that had to be Scots law, but also needed to create flexible third party rights. The solution was to expressly apply the English Act to the third party rights clause, but have the rest of the Agreement subject to Scots law.  Very ugly – So ugly in fact that it prompted me to blog about it.

Let’s Update Scots Law

So I think the Scottish Law Commission  should look into updating the law in Scotland in order to mirror (or better) the English Act.

Goodwill payments to customers can be a direct loss

IT suppliers should be concerned at a recent court case involving Accenture and Centrica. Accenture supplied a faulty billing system to Centrica.  This disrupted Centrica’s business and caused hassle to its customers. In order to keep its customers sweet, and although it had no contractual obligation to do so, Centrica gave its customers payments to compensate them for their hassle. Those payments added up to 8m!

Centrica tried to recover those customer goodwill payments from Accenture. Accenture resisted because it thought those losses were covered by a clause in the IT supply contract that said that Accenture would not be liable for indirect or consequential losses. 

Lawyers love a good bun fight over whether a loss is direct or indirect.   Believe it or not (and you probably will), the landmark case on the subject was decided back in 1854.   

There is a lot of complex law behind the judgement – but the headline is that the Court found that the goodwill payments were not “indirect or consequential losses”, and thus were not excluded by the clause. 

It’s not the end of the line for Accenture as the court was only looking at points of principle. It is still to decide whether Centrica can actually recover these payments on the facts of the case.

So if you are an IT supplier working in the utility or banking (or similar) sectors you may want to specifically exclude or cap liability for goodwill payments (also known as “ex gratia” payments) made by your client to its customers. 

Although the article was mostly written by Fiona Murdoch – one of our professional support lawyers.

New UCTA and IT Contract Case – Red Sky

This is an entry for the law geeks out there. 

I just read Kingsway Hall Hotel Ltd v. Red Sky IT.  What a terrible decision!  For those who want to read it the key paragraphs are from paragraph 230 onwards. 

The Judge decided that an exclusion of implied warranties in an IT contract was “unreasonable” and therefore could be struck out under the Unfair Contract Terms Act 1977 (commonly known as “UCTA”).  The rationale was that the express warranty given in place of the implied warranties was a “compliance with spec” warranty, but the purchaser had not seen the spec pre-contract and therefore had no warranty protection!

Here is some context.  Under UCTA the Court has the power to delete certain contract terms if they are “unreasonable”.   For a supplier this is a worry because the Court might delete your limit of liability clause leaving you with unlimited liability!  However, since 2001 (the Watford Case) the Courts have been reluctant to interfere with agreed contract terms unless there was a massive imbalance in bargaining position. This new case seems to go against that thinking.

In Red Sky case the Judge found the parties did not have equal bargaining position (a decision I find unsupported by the evidence).  In fact I don’t know what Red Sky did to annoy the Judge quite so much as the decision seems to me to be without any real basis in fact or law.

Also, the Judge spent a lot of time discussing whether an exclusion of implied warranties was reasonable, but did not  discuss the cap on liability or the exclusions of liability.  Bizarre!

The only practical lesson I can draw from the judgement is that if you (as a supplier) warrant that your software complies with its specification / manuals then you have to deliver those materials pre-contract. (Even that strikes me as wrong.)

I really hope Red Sky appeals this one.

Volcanoes, force majeure and business continuity

As a follow-up to Douglas’s post yesterday on Force majeure and Icelandic volcanoes, I thought I would add some additional comments.

I am aware of one incident involving a supplier claiming relief for a force majeure event. This followed a fire, which destroyed the supplier’s premises. Despite the supplier having an obligation to have in place a business continuity plan, the supplier claimed that the right of relief for the force majeure event (the fire) trumped its failure to have in place appropriate fire prevention systems, and therefore it was not liable to the losses incurred by the customer as a consequence of the fire. It is for this reason that it is crucial that you consider the interaction between a supplier’s obligations to have in place business continuity and disaster recovery procedures, and the relief that it is entitled to in the event of a force majeure event. This requires a careful review of the drafting of these clauses.

Following on from this, Douglas and I were discussing the potential impact of the erruption of the Eyjafjallajoekull volcano*. The prolonged closure of civil aviation space is likely to impact mainly upon the physical movement of goods, rather than people or information (data can be sent electronically, and people can video or tele-conference). For example, if your supplier has a service level obligation to replace a defective component within 48 hours, but is unable to meet that because it cannot get the replacement component flown over from the manufacturer in the USA, is that force majeure? Possibly yes.

It is for this reason that it is important that you properly scrutinise your supplier’s business continuity plans, and ensure that the supplier’s plan is sufficient and proportionate for the service you require (bearing in mind that if you don’t identify a deficiency until the plan is implemented, then there won’t be much you can do about it – at least in the short term).

For example, should you be requiring your suppliers to maintain a local (within driving distance) parts bin to guard against supply-chain problems? If your supplier otherwise proposes a just-in-time approach, and the supported system is business critical, then this may well be prudent to specify this.

*For those of you wondering how you pronounce “Eyjafjallajoekull”, the New York Times has a useful summary. My favourite tip is that is sounds like “Hey ya fergot la yoghurt”.

Force Majeure and Icelandic Volcanoes

The recent no fly zone across (most of) Europe because of the Icelandic volcano has made me think about force majeure clauses (sometimes known as “Act of God” clauses). 

A force majeure clause is a clause in a contract that excuses a contract breach where the “breaching party” cannot perform because of an event outside its reasonable control.  So for example, if I had an obligation to you to supply 10,000 widgets by 1 May 2010, but my factory was struck by lightning and burned to the ground in the middle of April, then the force majeure clause might protect me from your claim for contract breach.     

Is the no fly zone a force majeure event?  It might prevent an individual or an air-freight item getting somewhere in time, which might otherwise be a contract breach.  So possibly, yes. 

However, you have to check the drafting of the relevant clause carefully.  Also if the contract has no force majeure clause then there is no relief (the Courts do not imply them).

All that said in my 15 years of being an IT lawyer I have never seen a force majeure clause used in defence of a “you didn’t perform” claim.  My colleagues in litigation echo this, i.e. it’s not something they see used very often. 

One final thought on this.  Force majeure clauses are often considered to be contract “boiler plate”.  That is, relatively standard clauses towards the rear of the contract.  Sometimes contract reviewers have “switched off” by the time they get to the force majeure clause.  That can be dangerous because sneaky lawyers can hide nasty stuff in the force majeure clause.  In fact when acting for suppliers I have been known to slip some stuff in there myself. 

This is particularly relevant in the area of telecoms / internet services / hosted services / SaaS where I have seen some events included in the definitions of force majeure that I think the supplier should be on the hook for.  Something to watch out for.

See EMI(ly) Pay – thoughts on Pink Floyd v EMI

You may have read that Pink Floyd recently won a legal case against their record company EMI. The case was decided a few weeks ago, but I delayed reporting it for reasons I shall explain.

The facts were that the band claimed EMI was breaching a 1999 Master Licensing Agreement by “unbundling” Pink Floyd albums and making individual tracks available for download, despite an express contractual prohibition against selling “albums in any configuration other than the original configuration”.

Pink Floyd said that the aim of this contractual prohibition was to “preserve the artistic integrity of the albums” and therefore had to extend to digital sales. EMI submitted that the word “album” in the contract referred to a physical object and there was nothing in the contract to suggest that ”album” applied to on-line distribution. (A third viewpoint not raised in the High Court, but amusingly advanced by Jeremy Telman, Professor of Law at Valparaiso University, is that Pink Floyd albums were usually enjoyed in their entirety because listeners were never in any condition to get up off the couch and move the needle to individual tracks.)

In judgement Sir Andrew Morritt held that there was a presumption that the provisions of the contract were to extend to digital sales unless something in the nature of the product suggested otherwise. Accordingly EMI was not allowed to “unbundle” album songs for individual download. (Intriguingly part of the hearing, relating to a challenge over the level of royalties paid by the record company, took place in private – excluding the public and media – after EMI made an application citing commercial confidentiality. The relevant part of the judgement was also held to be confidential.)  EMI are expected to try to appeal the judgement, or at least aspects of it.

I held back on writing this post as I had a feeling the decision would be portrayed as some sort of artistic victory for the album format in the face of today’s download culture. And that’s exactly what has happened, with respected musicians such as Guy Garvey delivering gushing praise

I’m not sure I agree.

Does it not seem curious that a bunch of normally cash-obsessed rock musicians such as Pink Floyd (who let’s not forget are also arguing about royalty rates as part of their case) would seek to defend the “original configuration” of their recordings at the likely expense of sales? Could it be that, rather than defending the concept of the album (or indeed the “concept album”), they are actually seeking to improve their bargaining position with a view to agreeing on the sale of individual tracks at some point in the future?  “Do you think you can tell?”

Sony and the phantom 29th of February 2010 – why date compliance clauses are still relevant

It appears that Sony has been hit by a Y2K bug style programming error, which brought down its PlayStation Network online gaming platform. According to reports, the PSN thought that 2010 was a leap year, causing millions of PS3 consoles to crash and reset their internal clocks to 1 January 2000, and no doubt some red faces at Sony HQ. Oops!

As Douglas has previously mentioned, it’s still worth including a date compliance clause in your contract.

When suppliers see a Y2K style date compliance clause, they tend to act surprised, make a joke about 1999, and then tell you that it is unnnecessary and over the top. But, as this story goes to show, new software date processing errors do continue to happen from time to time, and when they do they can cause havoc.

Amusingly, there was no excuse for this error, as the PSN didn’t even come into being until 2006. Have we now reached a point where the programmers working on cutting edge projects are too young to remember Y2K?

Audi you like that?

And so to a recent case where a new car appeared be showing more “kaputt durch technik”, rather than the advertised Vorchsprung durch Technik.

The case considers the period of time within which a buyer will be deemed to have accepted goods for the purposes of the the Sale of Goods Act 1979 (SGA). Whilst the case considered the point for the purposes of a buyer’s right to reject goods under section 15B (which applies only in Scotland), the case is of general relevance to the effect of acceptance under the SGA – in particular, the rights and remedies of a buyer in respect of the supply of defective goods.

The pursuer had purchased, as a “third car”, a £41,000 Audi A4 from Edinburgh Audi. Following a year of occasional use, a number of minor and then major problems occurred, the latter of which caused the car to suddenly run in “safety” mode (restricted to no more than 30 mph). When this happened for a second time, the pursuer took the car back to the dealer (now 15 months after delivery), where it remained for several months whilst the dealer tried to repair it. After a number of failed attempts to repair it, the pursuer sought to reject the car and seek repayment of the purchase price, failing which payment of damages.

The court held that the car was not of satisfactory quality (and therefore in breach of the SGA) as it had been fitted with a defective electronics component. However, the court also held that the pursuer had lost his right to reject the car. Under the SGA, if the buyer retains the goods for “a reasonable period of time” without intimating to the seller that he has rejected them then they wil be deemed to have been accepted.

There are a number of points to take from this case, which are relevant when considering whether a buyer still has a right to reject defective goods:

  • the right to reject is a short term remedy only, and the “reasonable period” for the purposes of deemed acceptance will be construed accordingly
  • this applies even where there is a defect that does not emerge until some time after delivery, as the the buyer still has a remedy in damages
  • however, any period during which the seller attempts to repair the goods is discounted for the purposes of calculating the “reasonable period”
  • in this case, after 15 months it was too late for the pursuer to reject the car
  • buyers wishing to preserve their right to reject goods should therefore not notify the seller as soon as they become aware of any defects or problems
  • notwithstanding this case, consumers may still have remedies (to rescind contracts or require replacement of goods) under the European law derived rights contained in later sections of the SGA

Sky v. EDS – Follow Up – Interim Damages Award

As a follow up to the blog on Sky v. EDS a few days ago I read that the judge has given Sky interim damages of £200m. Ouch!

Typically an interim award is quite a bit less than the final award. Ouch!

EDS has 14 days to cough up. Ouch!

Of course EDS is seeking leave to appeal the judgement.

That’s a fair punt.

It will spend, say, £2m of legal fees in attempt to avoid or reduce an award that is a minimum of £200m. 

Sky V. EDS – Misrepresentation Claims Side-Step Classic Breach Of Contract Defences

A mere 18 months after the case finished the judgement in Sky.v EDS has been published.  To be fair to the judge it is a massive 450 page judgement.

The case arose out of a failed IT implementation by EDS (now part of HP) for BSkyB (it was a Siebel CRM implementation for you techies out there).  Sky was claiming losses in the region of £700m, EDS was hiding behind a £30m limit of liability clause.

The case was mostly about misrepresentations (untrue statements) made by the EDS’ sales team in sales meetings prior to contract.  I am not saying this is typical behaviour but I was going to call this article “Salesman tells Fibs to Get Sale Shocker!”.

Here are the key points from my perspective

1.  The limit of liability did not protect EDS against liability for fraudulent misreps (what most people would call a “lie”, and what the judge called deceit). This is not new law.

2.  EDS were also liable (up to the £30m cap) for negligent misrepresentations.

What’s the difference between a fraudulent misrep and a negligent misrep? If you know the statement is wrong its fraudulent, if you don’t actually know the statement is wrong, but your should have known it was wrong, then its negligent.

Normally there is an “entire agreement” clause that would prevent liability for pre contract negligent misreps. However, in this case the clause was not well enough drafted.  (Expect lots of lawyers to be worriedly reviewing “their” entire agreement clauses to make sure they work. I say that with a degree of smugness because my standard clause does work). 

3. EDS claimed that the reason the project failed was because of Sky not doing its part in the project (a standard defence, and often true).  However, while the “it’s the client fault” defence can work against breach of contract claims, it doesn’t work against misrep claims (whether based on fraudulent misrep or negligent misrep).

All in all not a good day for EDS. Unsurprisingly I read that EDS is planning to appeal.

What is the outcome? Some commentators are saying that IT suppliers will not tender for big projects. I can’t see that happening. However, they may exercise more control over sales teams. Perhaps lawyers will now be compulsory at all sales meetings. Good news for lawyers!

Next Page »