Concept
Claims Reduce the Amount Owed
Assignee subject to account debtor's terms, claims, and defenses
Claims Reduce the Amount Owed
Subsection (a) of § 9-404 decides which of the account debtor's defenses and claims reach the assignee; subsection (b) decides what a claim can accomplish once it gets there. Subject to subsection (c) and except as subsection (d) provides, the claim of an account debtor against an assignor may be asserted against an assignee under subsection (a) “only to reduce the amount the account debtor owes.”1 The assignee collects from the account debtor, the person who owes the obligation,2 and a claim operates on that collection alone. It works as a shield, not a sword: the account debtor may subtract the claim from the balance but may not demand anything from the assignee beyond it.
The two outcomes in the print shop's case mark the whole rule. A claim smaller than the balance shrinks the payment; a claim larger than the balance erases it but produces no refund. The excess belongs in a different lawsuit against a different defendant, the supplier. The line stays in the same place when a defect injures the buyer: the buyer sets the damages off against the unpaid price but cannot assert the claim against the financer for the remainder.
Two ideas support the line. The first concerns what the assignee is. It joins the transaction after the fact, and the law treats an assignee's arrival as different in kind from that of a third-party beneficiary, whom the original parties meant to benefit when they made the contract.3 Section 9-402 adds that the mere existence of a security interest imposes no contract or tort liability on the secured party for the debtor's acts or omissions.4 The second idea concerns exposure. Reduction fixes the assignee's worst case: a claim can wipe out the balance and no more. Damages for a defective machine or a botched job can exceed the price of the goods or services, and a rule allowing affirmative recovery would leave the assignee with no ceiling.
Subsection (b) acts only on claims that have already cleared subsection (a). A claim in recoupment arising from the transaction that gave rise to the assigned contract clears paragraph (a)(1), which sets no notification cutoff.5 Any other claim clears paragraph (a)(2) only if it accrues before the account debtor receives a notification of the assignment signed by the assignor or the assignee,6 and the notification must state that the amount due or to become due has been assigned and that payment is to be made to the assignee.7 A claim that fails subsection (a), such as an unrelated claim accruing after notification, never reaches subsection (b); the account debtor cannot assert it against the assignee for any purpose. The common error is to find a strong claim against the assignor and conclude that the assignee must pay damages. A strong claim answers only the first question, whether the claim may be asserted against the assignee at all. The second question is what the assertion accomplishes, and under subsection (b) it accomplishes reduction.
Michelin Tires (Canada) Ltd. v. First Nat. Bank of Boston arose under the predecessor of subsection (a), which referred to “any . . . claim” of the account debtor. The revision narrowed that phrase to “any . . . claim in recoupment” and inserted subsection (b), whose rule, applied to the facts of Michelin Tire, confines the account debtor to reducing what it owes.8
Michelin pressed Corrigan's default against a bank, and the court's reasoning turned on the cost of supervision. Charging banks with affirmative actions would give them additional burdens of supervision. But the party most interested in adequate performance is the other contracting party, whose vigilance would not slacken because a bank was also watching, so the law would create “two inspections where there was formerly one.” Costs, the court said, “for everyone thus increase, without any discernible benefit.” It did “not believe that the banks are best suited to monitor contract compliance.”9
The reasoning invites an objection. If banks should not have to police their customers, why should a customer's default count even as a defense against the bank?10 The statute separates the two remedies. Subsection (a) keeps the defense: unless the account debtor has agreed not to assert defenses or claims, and subject to subsections (b) through (e), the rights of an assignee are subject to the account debtor's defenses and claims.11 Subsection (b) removes only affirmative liability, the burden that would turn the assignee into a monitor.
The ceiling gives way where subsection (b) says it does. The subsection is subject to subsection (c) and operates except as subsection (d) provides, and the exceptions that follow take those provisions up. Consumer transactions supply one example: as to consumer account debtors, § 9-404(d) preserves the effectiveness of the notice the Federal Trade Commission requires, which says that the consumer's defenses and claims are preserved and assertable against an assignee, including a claim that would lead to affirmative recovery.12 In an ordinary commercial transaction, the rule stands as stated.