As a
result, it is not uncommon for litigation to involve the quantification of financial
remedies across multiple political and monetary boundaries. How does one take
foreign exchange rates – and more specifically, fluctuations in foreign
exchange rates between the date of initial wrongdoing and the trial date – into
account? In the next two posts, I will consider the following five examples, through which I
hope to illustrate some basic concepts:
1. A
US-based company, Manifest Destiny Inc. (“MDI”)
has a contract to sell $1M (USD) of specialized goods to a Canadian firm. The
Canadian firm breaches the contract, and MDI is unable to make the sale (or to
mitigate its loss). The exchange rate at the time of breach was $1 USD = $1.25
CDN; it is now $1 USD = $1 CDN.
2. Gordon C. Canuck (“Mr. Canuck”), an executive working for
a Canadian subsidiary of a US-based public company is wrongfully terminated. As
a result, the stock options to which he would have been entitled as of July
2009 did not vest. He sues for wrongful dismissal, and is successful. His
damages are assessed as the difference between the exercise price ($1 USD per
share) of the options and the market value of the stock on July 2009 ($10 USD
per share). The trial occurs in 2011, and an award for damages is granted
shortly thereafter.
3. Nancy Nascar, (“Ms. Nascar”) a US resident, is injured
in a motor vehicle accident in Canada, and will never be able to work again.
She sues the motorist who collided with her, and seeks to recover her future
loss of income.
4. Maple Leaf
Technologies Inc. (“MLT”) infringes
a patent by manufacturing goods in Canada and selling them in the United
States. Most of the firm’s operations are in Canada. Under Canadian law, the
patent owner – a US based firm, Stripes and Stars Inc. (“SSI”) - may sue for either damages on its lost sales, or an
accounting of the defendant’s profits from the infringing sales.
5. Stick
and Puck Ltd. (“SPL”) a Canadian
firm that manufactures products in Canada and sells them in the United States,
suffers a fire in its factory. It sues the electrical contractor to recover its
lost profits. SPL does a steady volume of business in the US, and in order to
reduce its exposure to fluctuations in foreign exchange rates, it typically
enters into forward contracts to sell USD and purchase CDN.
You may be asking at
this point, why not simply quantify whatever the financial remedy is in the
foreign currency? If only it were that simple!The Currency Act, R.S.C., 1985, c. C-52, s. 12,
requires that any money referenced in a legal proceeding in Canada must be
stated in Canadian currency. It is on this basis that Canadian courts
have generally felt compelled to convert awards for financial loss into
Canadian dollars, even if the losses relate to a foreign currency.
There
was, for many years, an established rule that the exchange rate be set based on
the date of breach or wrongdoing. As summarized by the Manitoba Court of
Appeal:
89 At present, the Canadian
“breach date rule” is based on a series of Canadian cases which adopted a now
obsolete British rule.
90
In 1945, the Supreme Court of Canada, in Gatineau Power Co. v. Crown Life Insurance Co., 1945 CanLII 33 (SCC), [1945] S.C.R. 655, applied a date of conversion at breach date in an
action to recover a debt. They did so in brief reasons, referring to the
cases of The Custodian v. Blucher,
1927 CanLII 69 (SCC), [1927] S.C.R. 420 (a case dealing with unpaid dividends), and S.S. Celia v. S.S. Volturno, [1921] 2 A.C. 544 (H.L.).
91
Those two cases, in turn, relied upon principles enunciated by
previous English House of Lords cases. That principle was that in all
cases involving sums payable in a foreign currency, the applicable rate of
exchange was the rate in existence on the date of breach. See, for
example, Re United Railways of the
Havana and Regla Warehouses, Ltd., [1960] 2 All
E.R. 332 (H.L.).[1]
The
MBCA went on to describe how some Canadian jurisdictions have moved away from
this principle, writing into their statutes specific rules to the contrary. For
example, in Ontario, section 121 of the Courts
of Justice Act stipulates that a damages award calculated in a foreign
currency must be converted to Canadian dollars based on the exchange rate in
effect at the judgment date; section 121(3) of that Act provides the court with discretion to use an alternate exchange
rate when warranted. Other jurisdictions, even without explicit statutory
adjustments, have also departed from this "rule" (as indeed did the MBCA in the
case in question).
In this
post and the next, I will discuss a variety of situations in which the issue of foreign
currency conversion will arise. I will suggest that a simple set of principles
can be applied to cut through some of the confusion to arrive at monetary awards
that are economically fair and predictable.
1. Matching the Remedy to the Loss
The basic principle behind an award for damages is to return the injured party to the position he or she would have been in but for the wrongdoing. Let us apply this principle to the question of foreign exchange in each of the five examples listed above.
Turning
to our first example listed above, consider that MDI is a US company, and its lost sales
were in USD. The exchange rate at the date of breach is irrelevant to MDI; MDI
was never going to take the proceeds from the sale and invest them in Canadian
dollars. It would have taken the USD from the sale and used them to run its
US-based business. It has lost USD.
In
order to be made whole, MDI needs to receive an amount of Canadian dollars such
that it can take them to the bank today and convert them into $1M USD (the amount of its loss). The
relevant exchange rate is therefore the rate in effect on the award date, not
on the date of breach.
(By the
same logic, if there is a delay between the award date and the date of actual
payment, we would argue that it is the date of actual payment that is more
relevant.)[2]
[1] Kellogg Brown & Root Inc. v. Aerotech
Herman Nelson Inc. et al, 2004 MBCA 63, at para. 89. This decision
contains a useful summary of the legal background to this issue.
This comment has been removed by a blog administrator.
ReplyDelete