Posts Tagged Software Directive
I reported earlier on complex enforcement issues concerning SAS Institute v World Programming. In  EWCA Civ 599 SAS Institute Inc v World Programming Ltd Flaux J gives an overview of the various proceedings at 4:
The dispute between the parties has a long history. It includes an action brought by SAS against WPL in this country in which SAS’s claims were dismissed; a decision by WPL, following an unsuccessful challenge on forum non conveniens grounds, to submit to the jurisdiction of the North Carolina court and to fight the action there on the merits; a judgment in favour of SAS from the North Carolina court for some US $79 million; an attempt by SAS to enforce the North Carolina judgment in this jurisdiction which failed on the grounds that enforcement here would be (a) an abuse of process, (b) contrary to public policy and (c) prohibited by section 5 of the Protection of Trading Interests Act 1980 (“the PTIA”); and a judgment from the English court in favour of WPL for over US $5.4 million, which SAS has chosen to ignore.’
A good case to use therefore at the start of a conflicts course to show students the spaghetti bowl of litigation that may occur in civil litigation. There are in essence English liability proceedings, decided in the end following referral to the CJEU (Case C-406/10); North Carolina liability proceedings, in which WPL submitted to jurisdiction after an earlier win on forum non grounds was reversed on appeal and the NC courts came to the same conclusions as the English ones despite a finding they were not (clearly) under an obligation to apply EU law; next, an SAS enforcement attempt in England which failed (with permission to appeal refused): my earlier post reviews it; next, enforcement proceedings of the NC judgment in California. That CAL procedure includes an assignment order and WPL sought an anti-suit injunction to restrain SAS from seeking assignment orders as regards “customers, licensees, bank accounts, financial information, receivables and dealings in England”: it was not given the injunction for there was at the time no CAL assignment order pending which could be covered by anti-suit. Currently, it seems, there is, and it is an anti-suit against these new assignment orders which is the object of the current proceedings.
At 59 ff follows a discussion of the situs of a debt; at 64 ff the same for jurisdiction re enforcement judgments, holding at 72
Applying these internationally recognised principles to the present case, the North Carolina and California courts have personal jurisdiction over WPL but do not have subject matter jurisdiction over debts owed to WPL which are situated in England. That is so notwithstanding that the losses for which the North Carolina court has given judgment were incurred by SAS in the United States. Nevertheless the effect of the proposed Assignment Order would be to require WPL to assign debts situated in England to SAS which would at least purport to discharge its customers from any obligation owed to WPL, while the effect of the proposed Turnover Order would be to require WPL to give instructions to its banks in England which would discharge the debts situated in England currently owed by the banks to WPL. In substance, therefore, the proposed orders are exorbitant in that they affect property situated in this country over which the California court does not have subject matter jurisdiction, thereby infringing the sovereignty of the United Kingdom.
Which is later confirmed at 83. Consequently the earlier order is overturned: at 89: ‘it follows also that the judge’s conclusion that the Assignment and Turnover Orders were not “markedly exorbitant” was based upon a mistaken premise.’
The anti-suit and anti-enforcement applications are dealt with in particular with reference to comity, and largely granted with some collateral notices of intention by SAS not to seek a particular kind of enforcement.
Someone somewhere must have made partner on this litigation.
SAS Institute v World Programming. Ordre Public, res judicata, fraus and (European) statute conspire against enforcement.
SAS Institute Inc v World Programming Limited  EWHC 3452 (Comm) is a rare example of refusal by an English court of enforcement of a US judgment. 20 Essex Street have excellent analysis here and I am happy generally to refer.
The outcome of English Proceedings was that WPL defeated SAS’ claims regarding software licence and copyright infringements, with an important role played by the European software Directive as applied by the CJEU in Case C-406/10 upon preliminary reference in the very case.
Meanwhile SAS had commenced concurrent proceedings in the US. WPL initially objected to the US Proceedings on forum non conveniens and other jurisdictional grounds. These objections were later withdrawn and WPL submitted to the jurisdiction of the US District Court and participated in the process before it. Judgment was awarded against it. SAS curtailed its claim of enforcement to as to increase chances of success: it only seeks to enforce the US Judgment in England insofar as it is for compensatory damages based on WPL’s fraud (an issue which was litigated in the US but not in the UK); it does not seek to enforce the breach of contract claim or that part of the US Judgment which awarded multiple damages.
At 35-36 Cockerill J summarises the law: ‘There are three strands of potential preclusion: cause of action estoppel (not live here) issue estoppel and Henderson v Henderson abuse of process. As Lord Sumption observed in Virgin Atlantic Airways Ltd v Zodiac Seats UK Ltd  UKSC 46,  AC 160 at p.180H at :
“…the policy underlying all of the…[res judicata] principles…” is “…the more general procedural rule against abusive proceedings…”.
The different doctrines therefore have different requirements, but they shoot at the same target – that of ensuring that nobody should be vexed twice in respect of one and the same cause: “nemo debet bis vexari pro una et eadem causa“: as it was put by Lord Diplock in Vervaeke v Smith  AC 145 at p.160A-B, G. A more modern version was given by Lord Bingham in Johnson v Gore Wood  2 AC 1 at p.31A-B in the context of the Henderson doctrine:
“Henderson v Henderson abuse of process, as now understood, although separate and distinct from cause of action estoppel and issue estoppel, has much in common with them. The underlying public interest is the same: that there should be finality in litigation and that a party should not be twice vexed in the same matter. This public interest is reinforced by the current emphasis on efficiency and economy in the conduct of litigation, in the interests of the parties and the public as a whole.” ‘
Issue estoppel per Dicey (referred to by Cockerill J) at paragraph 14-156 means that a “foreign judgment will not be recognised if it is inconsistent with a previous decision of a competent English court in proceedings between the same parties“. Akin therefore in residual English private international law (EU law is not engaged, the judgment having been issued ex-EU) to Brussels I Recast’s Article 45(1)c ‘s rule.
The fundamental point is that issue estoppel bars relitigation not of all issues, but only of issues determined as an essential part of the cause of action (at 40). The Henderson principle is concerned with protecting the integrity of the cause of action and issue estoppel defences and preventing them from being deliberately or inadvertently circumvented by a party which did not advance an argument in England which would otherwise have created such an estoppel (at 47).
This is the core of the abuse investigation and this formulated one can see why it is a difficult test to apply.
At 55: ‘There are two issues: was the Fraud claim “parasitic” on the breach of contract claim and the related question of whether the Fraud claim was a separate, distinct and independent cause of action. Both of these really go to the question of whether there is sufficient identity of issue.’ At 73 Cockerill J concludes that there was such abuse: ‘Ultimately, I have come to the conclusion that the existence of the terms of the contract was a fundamental building block for the Fraud Claim and that without it that claim – as it was formulated in the US – could not have been run. The essence of the case in the US Proceedings related to alleged fraudulent representations concerning its “present intention to comply with those terms”. It was fundamental to the claim that WPL “had no intention of abiding by those terms“. It was inherent in that case that those terms did exist; and yet the courts of this country had already held that those terms did not exist.’
Obiter, at 156 ff, Cockerill J adds that enforcement would also have been refused for reasons of the public policy embodied in the Software Directive. Authority in the arbitration context was referred to to pro inspiratio, including CJEU authority C-168/05 Mostaza Claro and C-126/97 Eco Swiss (at 163). At 179: ‘The fundamental problem for SAS is that the Directive plainly envisages the rendering null and void of provisions such as those on which SAS wants to rely, indeed that is explicitly the policy enunciated in the case-law and yet SAS’s fraud case is dependent upon those terms’ existence. The effect of the Directive is, as I have indicated above, to make SAS’s fraud claim (as formulated) impossible to express. It is therefore unrealistic to analyse the matter as the Directive “authorising frauds“.’ And at 184: ‘It is clear that the Software Directive gives expression to two important public policy objectives of preventing the monopolisation of ideas and promoting competition and consumer welfare.’
A very lengthy judgment which merits full reading.