Concept
When the Duty Arises
Duty to release deposit-account control after the obligation ends (§ 9-208(b))
Releasing Deposit Account Control
When the Duty Arises
Section 9-208 of the UCC is the end-of-deal counterpart to taking control.1 It requires a secured party that controls a deposit account to release that control once no secured obligation remains and the secured party has no commitment to give value.2 A lender takes control so that it can direct the debtor's funds, and that power protects the lender only while the secured deal is live. When the debtor has performed and the lender has nothing left to extend, the reason for holding the lever is gone, and the statute makes the lender let go.
The duty does not run on its own. The secured relationship must first be over, and the debtor must then ask for release. The debtor moves first because the debtor has the information. A secured party looking at a paid-off loan cannot tell whether the debtor wants the account freed now or means to leave the arrangement in place for later borrowing. A demand settles that question and gives the secured party a defined obligation in place of a guess.3
This unit is therefore the first step in the path an exam question on deposit-account release calls for. Confirm the preconditions first. Then identify how the secured party obtained control, because the required action differs by route. Last, apply the matching duty. The first subsection below covers the end of the secured deal; the second covers the debtor's demand and the clock that starts when the secured party receives it.
No Outstanding Obligation
Section 9-208(a) opens the release provisions with a statement of scope: the section applies to cases in which there is no outstanding secured obligation and the secured party is not committed to make advances, incur obligations, or otherwise give value.4 A secured obligation is the debt or other duty that the security interest stands behind, and it is outstanding until the debtor has satisfied it. The two conditions are joined by "and," so both must hold before anything else in § 9-208 can operate. Subsection (a) works as a gate: it decides whether the duties in subsection (b), which the rest of this chapter takes up, can apply at all.
The first condition follows from what control is for. A secured party holds control of a deposit account so that it can direct the funds on deposit, and that dominion is justified as a safeguard for money the debtor owes. Once the debtor has paid everything, the account protects no claim. Continued control would leave the debtor's cash answerable to the instructions of a creditor that is owed nothing, and it would leave in place a position the debtor might have to clear before offering the account to a new lender. The same logic underlies the secured party's duty to file a termination statement under § 9-513, and the commentary calls the duty to terminate control analogous to it.5
A zero balance does not satisfy the gate by itself, because the second condition asks what the secured party must still do in the future. A security agreement may contain a future advance clause, which lets the same collateral secure money the lender advances later: if a bank holding a $10,000 security interest in a borrower's cattle advances another $5,000 under such a clause, its interest in the cattle totals $15,000.6 The same logic applies to a lender that is committed to advance funds. Even when nothing is owed today, that lender has a live reason to keep its security, because the collateral also stands behind advances the lender may yet have to make. The phrase "otherwise give value" reaches commitments that are not literally loans, so any binding undertaking by the secured party to give something of value keeps the second condition unmet. Together the two conditions mean that the release duty arises only when no obligation is outstanding and no commitment to give value remains, and then only when the debtor demands release.7
An exam stem that reports a zero balance invites you to conclude that the lender must let go. Ask instead whether the lender is still committed to give value. The two borrowers below show how the answer changes.
In both scenes the debtor owes nothing, so the first condition is met each time; the commitment to lend alone separates the outcomes. The gate can also fail from the other side. A lender with no commitment to lend whose borrower still owes installments holds an outstanding secured obligation, so the first condition is unmet and the lender may keep control. Passing the gate does not require the secured party to act at once. The debtor must still make its demand, and the action the secured party must then take depends on how it obtained control, which the following sections address.
Demand and Ten Days
Section 9-208(b) opens with a clause that governs every release action listed beneath it: the secured party must act "[w]ithin 10 days after receiving a signed demand by the debtor."9 That short phrase holds two features. The trigger is a signed demand from the debtor. The deadline is ten days, measured from the moment the secured party receives that demand. The specific action the secured party must take within the period depends on the collateral it controls, and the following sections teach that part of the rule for deposit accounts.10
The demand requirement gives the first move to the party that holds the relevant information. Whether a paid-off debtor wants control ended today depends on its plans, and the secured party cannot read those plans from a zero balance. The debtor may want the account freed so that it can be offered to a new lender, or it may be content to leave the arrangement in place for a further credit line the parties expect to sign. A demand answers that question in the debtor's own words and leaves the secured party with a defined obligation to meet. The signature adds a second benefit: the secured party holds a verifiable record of what was asked, which gives the deadline a clear starting point. The cited sources use "signed" in the statutory text and "authenticated" in secondary summaries, and both describe the same requirement of a record the debtor has signed.
The ten-day period answers a different concern. It gives the secured party a fixed window in which to act, and it caps how long the debtor's account can stay subject to a creditor that no longer has any claim. Without a deadline, the debtor's demand would start nothing definite.
Because the period runs from receipt, neither the payoff date nor the date the debtor signed or mailed the demand starts it. A secured party cannot act on a demand that has not reached it, so the count begins on the day the demand arrives. The debtor therefore controls the timing, since the period cannot begin until the debtor chooses to send a demand.
An exam stem will often supply a payoff date and a mailing date and then ask whether the secured party met the deadline. Count from the day the secured party received the demand; a stem that never mentions a demand has not started the clock at all. A similar demand-then-ten-days structure appears in § 9-209, which requires a secured party that has notified an account debtor of an assignment to send a notice that it has no obligation to the secured party within ten days after the debtor makes an authenticated demand. That is a separate rule with its own conditions and its own trigger.11