In re: CS Assocs. [1990]
121 B.R. 942 · United States Bankruptcy Court for the District of Rhode Island · United States
Issue
Whether an anti-assignment clause in a government contract prevents the creation or attachment of a security interest under UCC § 9-406(d).
Held
The anti-assignment clause did not prevent attachment of the security interest; such clauses are ineffective under UCC § 9-406(d) for assignments of accounts and chattel paper.
Exam use
In an exam, introduce In re: CS Assocs. with the citation only if you can remember it accurately; otherwise use the case name and court, then focus on the rule and application. A strong answer should say what In re: CS Assocs. decided, why the facts mattered, and how the authority helps resolve the new facts. Avoid treating the case as a decorative reference. Use it to prove a doctrinal step in Security interest in government receivables / anti-assignment clauses, then move quickly to analysis.
Summary
In re: CS Assocs. is included in the Secured Transactions (Article 9 of the Uniform Commercial Code) case database because it gives students a concrete authority for Security interest in government receivables / anti-assignment clauses. The reported citation is 121 B.R. 942, and the decision is associated with United States Bankruptcy Court for the District of Rhode Island. In revision, treat the case as a way to connect the legal issue to a real dispute rather than as an abstract rule. The key exam move is to state the holding, identify the fact pattern that made the rule matter, and then decide whether a new problem question should apply, distinguish, or limit the authority.
Facts
Procedural History
Issue
Whether an anti-assignment clause in a government contract prevents the creation or attachment of a security interest under UCC § 9-406(d).
Held
The anti-assignment clause did not prevent attachment of the security interest; such clauses are ineffective under UCC § 9-406(d) for assignments of accounts and chattel paper.
Ratio Decidendi
A term in a contract between the debtor and an account debtor prohibiting assignment of an account is ineffective to prevent creation, attachment, or perfection of a security interest under Article 9.
Obiter Dicta
Check the linked source for concurring, dissenting, or obiter observations before quoting this case. If the case includes non-binding reasoning, use it as persuasive support rather than as the core rule.
Reasoning
Plain-English Explanation
Essay-Ready Explanation Generator
Version 1 of 4
Reference to In re: CS Assocs. (121 B.R. 942) strengthens a Secured Transactions (Article 9 of the Uniform Commercial Code) answer because the case reflects the principle that A term in a contract between the debtor and an account debtor prohibiting assignment of an account is ineffective to prevent creation, attachment, or perfection of a security interest under Article 9. Applied to a problem question, the case should be used after identifying the issue as Whether an anti-assignment clause in a government contract prevents the creation or attachment of a security interest under UCC § 9-406(d). The stronger essay move is to connect the material facts to the court's holding, then explain whether the present facts support the same conclusion or justify distinguishing the authority.
Underlying Concepts
- secured-transactions-article-9-of-the-uniform-commercial-code
- Secured Transactions (Article 9 of the Uniform Commercial Code)
- Security interest in government receivables / anti-assignment clauses
- case authority
- exam application
Key Passages
- Verify exact wording in the linked source before quoting.
Significance
Related Cases
No related cases listed.
Exam Tips
Revision Checklist
- Name the issue before discussing facts so the marker sees the legal question immediately.
- State the holding in one sentence, then use the ratio to explain why the court reached that result.
- Use the citation and jurisdiction to show why this authority matters for the problem you are answering.
- Pair this case with one supporting or contrasting authority if the question tests limits, policy, or exceptions.
Problem Question Use
Common Pitfalls
- Name-dropping the case without applying the facts
- Ignoring jurisdiction or procedural posture
- Quoting without checking the linked source