Riley v. Hewlett-Packard Co.

36 F. App'x 194
CourtCourt of Appeals for the Sixth Circuit
DecidedJune 6, 2002
DocketNo. 00-2488
StatusPublished
Cited by3 cases

This text of 36 F. App'x 194 (Riley v. Hewlett-Packard Co.) is published on Counsel Stack Legal Research, covering Court of Appeals for the Sixth Circuit primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Riley v. Hewlett-Packard Co., 36 F. App'x 194 (6th Cir. 2002).

Opinion

PER CURIAM.

Riley appeals the grant of summary judgment to Hewlett-Packard (HP) in this contract dispute. The district court granted HP summary judgment on the basis that the accounts receivable at the center of the dispute were assigned in violation of an anti-assignment clause in a subcontracting agreement between Clover Technologies, Inc. (Clover) and HP. The anti-assignment clause is clear and valid. We therefore affirm the judgment of the district court.

I

In 1996, HP executed a master subcontractor agreement with Clover. The agreement required Clover to provide labor, materials, and technical assistance for projects that HP might decide to subcontract out to Clover. The agreement contained an anti-assignment clause that stated:

Unless otherwise agreed in writing by HP, Subcontractor shall not assign its [195]*195rights or delegate its responsibilities under this Agreement. Any purported assignment or delegation by Subcontractor, including the attempted subcontracting of all or any portion of the work to provided [sic] under this Agreement, shall be null and void.

During the course of the contract, Clover and HP quarreled over whether or not HP was required to pay for certain work done by Clover. HP argued that the work was beyond the scope of the HP-Clover agreement; Clover, of course, disagreed.

During this dispute, Clover was sold by Riley (who owned 97% of Clover’s stock) and Leonard Kruszewski (who owned 3%) to Ameritech. The payment for the company was made in two steps. The purchase price for Clover was $74,750,000, less a “holdback amount” of $17,500,000 that represented, among other things, the uncollected accounts receivable assigned to Ameritech as part of the purchase.

At the end of 15 months, those accounts receivable that remained uncollected were to be returned to the George P. Riley Business Trust and Kruszewski, in full satisfaction of the holdback amount, along with cash in payment for those accounts receivable that had been collected. The HP accounts receivable were returned (along with nearly $2 million in other uncollected accounts) as part of that process, because they were still disputed by HP and thei’efore remained uncollected.

On April 25, 2000, Riley filed suit against HP on behalf of himself and the Riley Trust. HP filed a motion for summary judgment based on the anti-assignment clause. The district court agreed with HP that the anti-assignment clause was clear and valid, and dismissed Riley’s action. Riley timely appealed.

II

We review a district court’s grant of summary judgment de novo. Napier v. Madison County, 238 F.3d 739 (6th Cir. 2001). Summary judgment is appropriate when no genuine issue of material fact remains between the parties. Fed. R.Civ.P. 56(c). All inferences must be drawn in favor of the non-moving party. Napier, 238 F.3d at 741-42.

The accounts receivable were assigned; the anti-assignment clause has clearly been violated. The remaining issue is whether there is any impediment to the enforcement of the anti-assignment clause. Riley raises four objections to the enforcement of the anti-assignment clause. First, he states that the clause is ambiguous and should therefore be invalidated based on certain interpretive rules against anti-assignment clauses. Second, he argues that Uniform Commercial Code § 9-318 as adopted by Michigan invalidates anti-assignment clauses. Third, he argues that, on the equities, the anti-assignment clause ought to be voided by the court. Fourth, he argues that Clover was no longer bound by the provisions of the contract because it had already performed. None of these arguments are convincing.

A. The Anti-Assignment Clause: General Contract Principles and Interpretive Rules

There is a general policy favoring the free alienability of contract rights to payment. The essential intuition seems to be that changing the payee does not impose serious consequences on the payor. See, e.g., Fox-Greenwald Sheet Metal Co. v. Markowitz Bros., 452 F.2d 1346 (D.C.Cir. 1971). Since free alienability creates other significant benefits, it is generally favored by interpretive rules. Ibid. Therefore, the Second Restatement of Contracts has adopted an interpretive rale: in cases of [196]*196ambiguity, anti-assignment clauses are construed to mean that duties, not rights to payment, are non-assignable. Specifically: “Unless the circumstances indicate the contrary, a contract term prohibiting assignment of ‘the contract’ bars only the delegation to an assignee of the performance by the assignor of a duty or condition.” Restatement of Contracts (Second) § 322(1) (1981).

The Restatement also notes that a “contract term prohibiting assignment of rights under the contract, unless a different intention is manifested, ... is for the benefit of the obligor, and does not prevent the assignee from acquiring rights against the assignor or the obligor from discharging his duty as if there were no such prohibition.” Restatement of Contracts (Second) § 322(2)(c) (1981).

These rules of interpretation do not override express statements of the will of the parties. If the contract shows an intent by the parties to limit both delegations of duties and assignment of rights, and specifically states who is bound by the assignment prohibition, then the interpretive default rules are inapplicable. Fox-Greenwald Sheet Metal Co. v. Markowitz Bros., 452 F.2d 1346 (D.C.Cir.1971). Similarly, where there is no ambiguity, the default rule of the Second Restatement is not used. See, e.g., Texas Farmers Ins. Co. v. Gerdes, 880 S.W.2d 215, 219 (Tex. App.1994).

The anti-assignment clause at issue here prohibits the subcontractor from either assigning rights or delegating responsibilities. Assignment of “the contract” is not mentioned. There is no ambiguity, and the intent of the parties is clear. The anti-assignment provision is therefore enforceable.

B. UCC Article 9 Does Not Invalidate the Anti-Assignment Clause

Riley incorrectly argues that UCC § 9-318(4), as adopted by Michigan in Mich. Comp. Laws § 440.9318(4), invalidates the anti-assignment clause. The section reads:

[a] term in any contract between an account debtor and an assignor is ineffective if it prohibits assignment of an account or prohibits creation of a security interest in a general intangible for money due or to become due or requires the account debtor’s consent to such assignment or security interest.

Mich. Comp. Laws § 440.9318(4) (1994).1 Michigan courts have not provided instruction on the scope of the section.

Article 9 governs secured transactions.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

MSPA Claims 1, LLC v. Tenet Florida, Inc.
918 F.3d 1312 (Eleventh Circuit, 2019)
Harding v. Viking Internatl. Resources Co., Inc.
2013 Ohio 5236 (Ohio Court of Appeals, 2013)

Cite This Page — Counsel Stack

Bluebook (online)
36 F. App'x 194, Counsel Stack Legal Research, https://law.counselstack.com/opinion/riley-v-hewlett-packard-co-ca6-2002.