Concept
Controllable Records Exception
Limitation on secured party's liability
Controllable Records Exception
Subsection (f) of § 9-628 withdraws the two knowledge-based shields, subsections (a) and (b), in one setting. Both shields turn on what the secured party knows about a person. Under subsection (f), they do not limit the secured party's liability to a person if two conditions are met at the later of two moments: when the secured party obtains control of collateral that is a controllable account, controllable electronic record, or controllable payment intangible, and when the security interest attaches.1 The first condition is that the person is a debtor or obligor.2 The second is that the secured party knows that the collateral, a record attached to or logically associated with it, or the system in which it is recorded does not provide the information about the person's status, identity, or means of communication.3 Both conditions must be present together, so the exception is a conjunctive test, like the knowledge test it overrides.
Subsection (f) tests the secured party's knowledge at one fixed moment, the later of two events. A secured party may obtain control before the interest attaches, or the interest may attach first, so the statute names whichever comes later. By then the secured party holds both control and an attached interest, and what it knows at that point decides whether the exception applies. What it learns afterward does not.
The fixed moment has a clear function. Collateral of this kind can be recorded in a system that never reveals who the debtor is or how to reach the debtor. If the knowledge shields applied without subsection (f), a secured party could take control of such collateral already aware that the system would never supply those facts, then invoke the no-knowledge shield for the very gap it saw at the start. Measuring knowledge at control or attachment closes that route: ignorance the secured party saw coming at the outset cannot later excuse its noncompliance.
A typical exam stem describes a lender and a digital asset and asks whether the no-knowledge shield survives. The answer depends on what the lender knew about the system when it took control.
The second condition requires that the secured party know the information is missing. The text does not reach what the secured party should have known, so a lender that never checked what the system supplies has not been shown to meet that condition. Two limits keep the exception narrow. It reaches only the three kinds of controllable collateral, so a loan secured by equipment or inventory never triggers it. It also withdraws only subsections (a) and (b), the only subsections the text names. Subsections (c), (d), and (e) stay in place, and the sections below take them up along with subsection (b).
Status-Based Nonliability
Subsection (b) of § 9-628 protects a secured party against a claim that rests on nothing but its status as secured party, subject to subsection (f).5 A secured party's status is its position as holder of a security interest, which it occupies from the moment the interest exists and without doing anything further. Like subsection (a), the protection lasts only while the secured party lacks certain knowledge about the claimant. The two subsections differ in the kind of claim each answers.
The difference follows from the wording of subsection (a), which relieves a secured party of liability for failure to comply with Article 9.6 That shield answers the allegation that the secured party broke a rule. A claimant who alleges no broken rule, and says only that the secured party is liable because it is the secured party, has not made that allegation. If subsection (a) stood alone, a claimant could avoid it by framing the grievance around who the defendant is rather than what the defendant did. Subsection (b) closes that gap by giving status-based claims their own knowledge condition. On an exam, ask first whether the claim alleges noncompliance with an Article 9 duty, which sends you to subsection (a), or rests on status alone, which sends you to subsection (b).
Conditioning status-based liability on knowledge limits a liability that would otherwise attach without any dealing between the parties. A secured party acquires its status without acting toward the claimant, so liability grounded in status alone could reach a person the secured party has never encountered. Tying the protection to the secured party's own knowledge leaves exposure in place only for persons it knows about.
The knowledge condition has two versions, depending on who is claiming. Against a person that is a debtor or obligor, the protection ends only if the secured party knows that the person is a debtor or obligor, who the person is, and how to communicate with the person.7 These are the same three items that govern subsection (a), and all three must be known, so the absence of any one keeps the protection in place. Against a secured party or lienholder that has filed a financing statement against a person, the test is shorter: the secured party must know that the person is a debtor and must know the person's identity.8 Both items concern the person against whom the financing statement was filed, not the filing creditor, and the test has no communication element. The protection is therefore easier to lose against a filing creditor than against a debtor or obligor. It also departs from subsection (a), which applies the three-item test to a filing creditor's claim as well.
An exam stem on this subsection usually describes a claim that never mentions a violated rule and asks whether the lender is liable. The answer turns on who is claiming and what the lender knew.
Suppose instead that the lender's file held a signed assumption agreement listing Buyer's name and mailing address. The lender then knows each of the three things, and subsection (b)(1) gives no protection against the status-based claim. Losing the shield only removes a defense. It does not make the lender liable, and the claim returns to whatever law would otherwise govern it.
The usual error is to carry the third element from subsection (b)(1) into subsection (b)(2). The lender's ignorance of how to reach Hale protects it against Hale and does nothing against the filing creditor. Both versions share one feature: the opening words of subsection (b) make it subject to subsection (f), so the controllable-records exception can switch this protection off just as it switches off subsection (a).
Reasonable Belief on Consumer Status
Subsection (c) protects a secured party that misjudged a deal's character. A secured party is not liable to any person, and a person's liability for a deficiency is not affected, because of an act or omission arising out of the secured party's reasonable belief that a transaction is not a consumer-goods transaction or a consumer transaction, or that goods are not consumer goods, if the belief is based on reasonable reliance on a particular kind of representation.12 Consumer status depends on purpose: what the collateral is for and why the debt was incurred. Article 9 attaches extra duties and remedies to deals of that character, so a secured party that misjudges the character can end up omitting something the Article required.
The subsection names two sources of reliance, and either can carry the protection. The first is a debtor's representation about the purpose for which the collateral was to be used, acquired, or held.13 The second is an obligor's representation about the purpose for which the secured obligation was incurred.14 The two sources match the two facts that consumer status depends on, since the debtor knows what the collateral is for and the obligor knows why the debt was taken on. Together they form one test: the secured party must hold a reasonable belief about the deal's character, and that belief must rest on its reasonable reliance on what the debtor said about the collateral or what the obligor said about the debt.
Each reasonableness requirement does separate work. A secured party usually cannot see how an applicant will use goods or why the applicant is borrowing, so the applicant's own statement is the only practical source. A lender that relies on such a statement and is later proved wrong has done what a lender can be asked to do. The requirement of a representation gives the belief a source outside the secured party's own assumptions, so a bare guess about the deal's character earns no protection. The requirement that reliance be reasonable keeps the representation from working as a password. A secured party whose own file contradicts a statement cannot treat the statement as settling the question, because the misclassification then comes from its own inattention.
Subsection (c) also preserves the person's liability for a deficiency, which parallels the second limb of the knowledge-based shield.15 The protection therefore runs on two fronts: the secured party is shielded from damages claims, and the noncompliance cannot be used as a defense to shrink the shortfall. A deficiency is a debt the person genuinely owes, and reducing it for a lapse the secured party made in reasonable reliance on the person's own description of the deal would excuse part of a real debt.
When a debtor later insists the deal was a consumer one, ask what the secured party reasonably believed from the information it held when it acted. The goods' actual use is not the test.
A false statement does not by itself defeat the protection, as the tractor scene shows: the debtor misdescribed the use, and the lender still prevails, because the statute protects reasonable reliance on a statement that turns out to be wrong. Two features of the text keep the protection from spreading too far. It covers an act or omission arising out of the mistaken belief, so a lapse unrelated to the deal's classification stays under the ordinary rules. It also operates independently of the knowledge-based shields. Its text asks nothing about whether the secured party knows who the person is or how to reach the person, and its opening words, unlike those of subsection (b), contain no reference to subsection (f).16 A secured party that knows every detail about the person can therefore still invoke subsection (c) for a classification mistake.
No Damages for Explanation Failures
Section 9-628(d) removes one remedy for one lapse: a secured party is not liable to any person under § 9-625(c)(2) for its failure to comply with § 9-616.18 Two cross-referenced sections explain the rule. Section 9-616 is the duty to explain: after a sale, the secured party must give the debtor an explanation of how it calculated a surplus or deficiency. Section 9-625(c)(2) is a remedy: when the collateral is consumer goods, a person who was a debtor or secondary obligor may recover a statutory minimum amount without proving that the violation cost anything. Subsection (d) disconnects the two. The explanation duty stays in force, but breaching it no longer triggers the automatic payment.
The carve-out fits what a statutory minimum is for. The remedy attaches whether or not the debtor lost anything, which makes sense chiefly for violations that take away something hard to measure. A debtor who never hears about a sale, for example, may lose the chance to redeem the collateral or to bid on it, and a consumer who has lost such a chance usually cannot prove its value. The explanation, by contrast, follows a sale already finished. Those opportunities ended with the sale, so a missing or flawed explanation cannot have cost the debtor one. Its function is to let the debtor check the arithmetic behind a demand for payment, and a lapse of that kind does not call for an automatic payment that could exceed any harm.
The limit is narrow in one direction and unconditional in the other. It is narrow because it names only the statutory-minimum provision and only the explanation duty, so every other pairing of duty and remedy stays where Article 9 would otherwise put it. Because the text mentions only § 9-625(c)(2), it does not by its terms address a debtor's claim for loss the debtor can actually prove, and it says nothing about any other duty. It is unconditional because, unlike subsections (a) and (b), its text contains no knowledge condition and no reference to subsection (f), and unlike subsection (c), it asks nothing about the secured party's belief.19 The protection therefore applies even when the secured party knows exactly who the debtor is and how to reach the debtor.
An exam stem will usually describe a consumer-goods repossession, a lapse by the secured party, and a demand for statutory minimum damages. The question to answer is which duty the secured party failed to perform.
A lender that sells the same minivan without ever sending the notification of disposition has failed at an earlier stage. That duty is owed before the sale, and breaching it can cost the debtor the chance to redeem the vehicle or to bid on it. Subsection (d) names only the explanation duty in § 9-616, so it gives no cover for this omission. The claim is then decided under the rest of Article 9 and the other limits in § 9-628, including the knowledge-based shield if the lender lacked the required knowledge about the person. The usual error is to read subsection (d) as an exemption from consumer-goods damages generally. It removes a single remedy for a single duty, and the identity of the duty breached decides whether it applies.
One Statutory Recovery Per Obligation
Section 9-628(e) caps a single remedy: a secured party is not liable under § 9-625(c)(2) more than once with respect to any one secured obligation.21 The cap leaves alone the duties that trigger the statutory minimum and the question whether a given violation supports it. It limits only how often that recovery can be collected, and its unit is the secured obligation, the debt the collateral secures. The number of violations the secured party commits in enforcing that debt does not change the count.
Counting obligations keeps the remedy proportionate to the transaction it relates to. The statutory minimum is measured against one debt, so a total that grew with every violation would climb past the amount the remedy was built around. Enforcing even a single loan involves several moves, including notice before a sale, the sale itself, an accounting afterward, and a demand for any shortfall, and each is a chance for error. A debtor with one debt and one enforcement effort would collect more with every added slip if each violation earned its own payment. A single recovery per obligation avoids rewarding the counting of violations.
An exam stem that stacks several lapses in one repossession and asks for the total statutory recovery is testing the unit of the cap. The question to ask is how many secured obligations are involved.
Two features of the text keep the cap in its place. It names only § 9-625(c)(2), so it limits that remedy and no other, and it says nothing about whether a given violation supports a recovery at all. Like subsection (d), and unlike subsections (a) and (b), its text contains no knowledge condition and no reference to subsection (f), so the cap applies whatever the secured party knows about the person.22 The usual exam error is to count violations: a debtor who proves three lapses in enforcing one loan has not earned three recoveries.