Tuesday, May 22, 2018
I was browsing through some recent veil piercing cases (because that's how I roll), and I came across this gem:
[I]t is unclear that merely using a corporation to limit personal liability rises to the level of fraud required to pierce the corporate veil.
Indagro SA v. Nilva, No. 16-3226, 2018 WL 2068660, at *3 (3d Cir. May 3, 2018). Given that limited liability is one of the primary benefits of incorporation, I think it is at least implied that using a corporation to limit personal liability is not fraud at all.
Moreover, the corporation at issue was a New Jersey corporation, and the state law provides:
N.J. Stat. Ann. § 14A:5-30 (West). This is pretty unequivocal. I get that fraud may be one of the acts that could give rise to personal liability, but the use of an entity to limit personal liability, when that is a core facet of the entity, is some pretty serious attempted bootstrapping.
The case gets it right, in the end, but still, I had to point this out. To imply that it could be fraud to use a corporation for the purpose of limiting personal liability, without anything more, is simply incorrect.
Tuesday, May 15, 2018
The Goldens contend that the trial court erred by denying their motion for summary judgment as to negligence claims asserted against them personally. They assert that corporate law insulates them from liability and that, while a member of an [sic] limited liability corporation may be liable for torts in which he individually participated, Ugo Mattera has pointed to no evidence that the Goldens specifically directed a particular negligent act or participated or cooperated therein. We agree with the Goldens that they were entitled to summary judgment on Ugo Mattera's negligence claim.An officer of a corporation who takes part in the commission of a tort by the corporation is personally liable therefor, and an officer of a corporation who takes no part in the commission of a tort committed by the corporation is not personally liable unless he specifically directed the particular act to be done or participated or cooperated therein.Jennings v. Smith, 226 Ga. App. 765, 766 (1), 487 S.E.2d 362 (1997) (citation omitted). Thus, if Baja Properties was negligent in constructing the house, an officer of the corporation could be held personally liable for the negligent construction if he specifically directed the manner in which the house was constructed or participated or cooperated in its negligent construction. See Cherry v. Ward, 204 Ga. App. 833, 834 (1) (a), 420 S.E.2d 763 (1992).
(a) A person who is a member, manager, agent, or employee of a limited liability company is not liable, solely by reason of being a member, manager, agent, or employee of the limited liability company, under a judgment, decree, or order of a court, or in any other manner, for a debt, obligation, or liability of the limited liability company, including liabilities and obligations of the limited liability company to any member or assignee, whether arising in contract, tort, or otherwise, or for the acts or omissions of any other member, manager, agent, or employee of the limited liability company, whether arising in contract, tort, or otherwise.
Tuesday, May 8, 2018
If I have learned anything over the years, it is that I should not expect any court to be immune from messing up entities. Delaware, as a leader in business law and the chosen origin for so many entities, though, seems like a place that should be better than most with regard to understanding, distinguishing, and describing entities. Sometimes they get things rights, as I argued here, and other times they don't. A recent case is another place where they got something significant incorrect.
The case starts off okay:
Plaintiffs brought this action under federal diversity jurisdiction, 28 U.S.C. § 1332(a)(1), asserting that complete diversity of citizenship exists among the parties. In Defendants’ Motion to Dismiss, however, they argue that complete diversity of the parties is lacking. Federal jurisdiction under § 1332(a)(1) requires complete diversity of citizenship, meaning that “no plaintiff can be a citizen of the same state as any of the defendants.” Midlantic Nat. Bank v. Hansen, 48 F.3d 693, 696 (3d Cir. 1995); Exxon Mobil Corp. v. Allapattah Servs., Inc., 545 U.S. 546, 553 (2005).
A natural person is a citizen of “the state where he is domiciled,”1 and a corporation is a citizen of the state where it maintains its principal place of business, as well as the state where it is incorporated. Zambelli Fireworks Mfg. Co. v. Wood, 592 F.3d 412, 418 (3d Cir. 2010). For purposes of § 1332, the citizenship of a limited liability corporation2 (“LLC”) is determined “by the citizenship of each of its members.” Id. Plaintiff Cliffs Natural Resources Inc. is incorporated in Ohio, and Plaintiff CLF Pinnoak LLC is incorporated3 in Delaware and maintains its principal place of business in Ohio. Third Am. Compl. ¶¶ 3–4, ECF No. 162. In moving to dismiss this action for lack of jurisdiction, Defendants assert that Seneca Coal Resources, LLC, a Delaware corporation,4 includes members who are Ohio citizens, thus destroying complete diversity as required for § 1332.
Wednesday, May 2, 2018
II. UNDISPUTED FACTS.. . . . The facts, viewed in the light most favorable to the Plaintiffs, are as follows. Plaintiff Edgar Lopez is a New Mexico resident. Compl. at 1, ¶ 1. Lopez owns and operates Plaintiff IMA, LLC, a New Mexico limited liability corporation that formerly managed the Perry Corners Shopping Center. . . . Lopez is the managing partner and the only surviving voting member of Hunt Partners, LLC, a Nevada corporation that has its principal place of business in New Mexico. . . . . Hunt Partners wholly owns, as the “sole equity member,” another LLC called “Perry Corners Shopping Center, LLC,” a Delaware Corporation with its principal place of business in New Mexico, which, in turn, owns as its only asset the Perry Corners Shopping Center, which is located in Georgia.
Monday, April 30, 2018
My essay on the use of traditional for-profit corporations as a choice of entity for sustainable social enterprise firms was recently published in volume 86 of the UMKC Law Review. I spoke on this topic at The Bryan Cave/Edward A. Smith Symposium: The Green Economy held at the UMKC School of Law back in October. The essay is entitled "Let's Not Give Up on Traditional For-Profit Corporations for Sustainable Social Enterprise," and the SSRN abstract is included below:
The past ten years have witnessed the birth of (among other legal business forms) the low-profit limited liability company (commonly known as the L3C), the social purpose corporation, and the benefit corporation. The benefit corporation has become a legal form of entity in over 30 states. The significant number of state legislative adoptions of new social enterprise forms of entity indicates that policy makers believe these alternative forms of entity serve a purpose (whether legal or extra legal).
The rise of specialty forms of entity for social enterprise, however, calls into question, for many, the continuing role of the traditional for-profit corporation (for the sake of brevity and convenience, denominated “TFPC” in this essay) in social enterprises, including green economy ventures. This essay argues that TFPCs continue to be a viable—and in many cases desirable or advisable choice of entity for sustainable social enterprise firms. The arguments presented are founded in legal doctrine, theory, and policy and include both legal and practical elements.
Somehow, I managed to cite to four BLPB co-bloggers in this single essay: Josh, Haskell, Stefan, and Anne. Evidence of a business law Vulcan mind meld? You decide . . . .
Regardless, comments, as always, are welcomed as I continue to think and write about this area of law and practice.
April 30, 2018 in Anne Tucker, Business Associations, Corporate Governance, Corporations, Haskell Murray, Joan Heminway, Joshua P. Fershee, Social Enterprise, Stefan J. Padfield | Permalink | Comments (2)
Tuesday, April 24, 2018
As I am inclined to do with cases and statutes, I spent some time this week chasing down incorrect definitions of the LLC (correctly defined as a "limited liability company"). I did some perusing of the Code of my home state of West Virginia for incorrect uses of "limited liability corporation," where limited liability company was intended. As I expected, there are multiple errors. Take, for example:
§ 31D-11-1109. Conversion of a domestic corporation to a domestic limited liability company.
. . . .
(i) When a corporation has been converted to a limited liability corporation pursuant to this section, the limited liability company shall, . . . .
This part of the Code uses "limited liability company" correctly throughout this provision, except in this one spot. This should be cleaned up, but it appears to be an error related to repeated use of corporation and company in the same statute (as opposed to a misunderstanding of the concept).
The West Virginia Code has adopted the use of "limited liability corporation" in place of "limited liability company" in a couple definitions provisions, too, which could be a little more problematic.
In the Motor Fuel Excise Tax portion of the Code, we have this, § 11-14C-2. Definitions:
(66) "Person" means an individual, firm, cooperative, association, corporation, limited liability corporation, estate, guardian, executor, administrator, trust, business trust, syndicate, partnership, limited partnership, copartnership, organization, limited liability partnership, joint venture, receiver and trustee in bankruptcy. "Person" also means a club, society or other group or combination acting as a unit, a public body including, but not limited to, this state and any other state and an agency, commissioner, institution, political subdivision or instrumentality of this state or any other state and, also, an officer, employee or member of any of the foregoing who, as an officer, employee or member, is under a duty to perform or is responsible for the performance of an act prescribed by the provisions of this article.
Literally, anyway, LLCs are not defined as persons in this Code section. I am confident that the intent here is quite clear, even if the execution is flawed, but still, this exhaustive list leaves out the West Virginia limited liability company created in WV Code § 31B, the Uniform Limited Liability Company Act.
A similar error occurs in Code Chapter 16, Public Health. Code § 16-2D-2 provides:
(29) “Person” means an individual, trust, estate, partnership, limited liability corporation, committee, corporation, governing body, association and other organizations such as joint-stock companies and insurance companies, a state or a political subdivision or instrumentality thereof or any legal entity recognized by the state.
Here, at least, the catch-all "any legal entity" does include LLCs, but LLCs are still not listed specifically.
This definition language is being repeated in draft legislation, as well, so the error is spreading. See, e.g., House Bill 2873, Budget and Spending Transparency Act ("(c) "Entity" or "recipients" means any corporation, association, union, limited liability corporation, limited liability partnership, legal business entity including nonprofit organizations, grantee, contractor or any county, municipal or other local government entity . . ..")
I am planning to spend some time this summer sending proposed fixes to some key legislators to see if we can get this corrected. Though I concede this is a small fix, it is also an easy fix, and I see no reason not to get it right. Maybe if I do the legwork, it can get done.
Tuesday, April 17, 2018
LLCs Are Not Corporations & You Can't Have A Parent-Subsidiary Relationship When There is Only One Entity
Oh boy. A 2010 case just came through on my "limited liability corporation" WESTLAW alert (that I get every day). This one is a mess. Recall that LLCs are limited liability companies, which are a separate entity from partnership and corporations, despite often having some similar characteristics to each of those.
CBOE, along with the six other exchanges, has an interest in OPRA but OPRA was not incorporated as a separate legal entity until January 1, 2010, when it incorporated as a limited liability corporation. Id. (describing the restructuring of OPRA following its incorporation). At the time this lawsuit was filed, however, there remains a question as to whether there were any formalities in place to separate OPRA from CBOE operations. In short, the parties dispute whether, at the time the suit was filed, OPRA operated independently or was operated jointly with CBOE.
*2 To this end, Realtime asserts that the lack of any corporate governance at OPRA [an LLC], such as Articles of Association or a partnership agreement, renders OPRA “simply a label with no formal business structure.” RESPONSE at 2, 4 (citing SEC RELEASE at 2) (“OPRA was not organized as an association pursuant to Articles of Association or as any other form of organization. Instead, OPRA simply served as the name used to describe a committee of registered national securities exchanges.”).
CBOE fails to identify grounds for institutional independence from OPRA at the time this suit was filed, and Realtime presents sufficient evidence to impute OPRA's contacts [for obtaining personal jurisdiction] to CBOE.
*5 In applying the Texas long arm statute, courts in this Circuit have followed the rule established by the Supreme Court in 1925 that “so long as a parent and subsidiary maintain separate and distinct corporate entities, the presence of one in a forum state may not be attributed to the other.” Hargrave v. Fibreboard Corp., 710 F.2d 1154, 1159 (5th Cir. 1983) (citing Cannon Manufacturing Co. v. Cudahy Packing Co., 267 U.S. 333 (1925)). In this case, however, at the time the lawsuit was filed there were no clear legal boundaries to affirmatively identify a parent-subsidiary or sister-sister corporate relationship. . . . It is undisputed that prior to January 1, 2010, OPRA did not seek the protections of incorporation, RESPONSE, EXH. 13, OPRA LLC AGREEMENT (Doc. No. 238-14), and based on the current record, Realtime has put on more than a minimal showing that OPRA was under the managerial and day-to-day control of CBOE. See, e.g., Oncology Therapeutics Network v. Virginia Hematology Oncology PLLC, No. C 05-3033-WDB, 2006 WL 334532 (Feb. 10, 2006 N.D. Cal.) (noting, in the context assessing whether two related entities formed a single enterprise, that “At this juncture, plaintiff merely has to allege a colorable claim. Plaintiff does not have to prove the claim.”). Therefore, the strict separateness required under Cannon need not be applied here because OPRA did not seek protections to formally divide its dealings from that of its counterpart CBOE.
Instead, these facts make it appropriate to apply the single business enterprise doctrine. The single business enterprise doctrine applies when two or more business entities act as one. Nichols, 151 F. Supp.2d at 781–82 (citing Beneficial Personnel Serv. of Texas v. Rey, 927 S.W.2d 157, 165 (Tex. App.- El Paso 1996, pet. granted, judgm't vacated w.r.m., 938 S.W.2d 717 (Tex. 1997)). Under the doctrine, when corporations are not operated as separate entities, but integrate their resources to achieve a common business purpose, “each corporation may be held liable for debts incurred during the pursuit of the common business purpose.”Western Oil & Gas J.V., Inc., v. Griffiths, No. 300-cv-2770N, 2002 WL 32319043, at *5 (N.D. Tex. Oct. 28, 2002) (internal citations omitted). Being a part of a single business enterprise imposes partnership-style liability. Id. The facts presented here demonstrate that OPRA and CBOE operate as a single business entity, at least for the threshold inquiry of establishing jurisdiction.
Traditionally, courts have applied this doctrine when two corporations are acting as one. However, despite OPRA not having a defined corporate status at the time this suit was filed, there is demonstrable proof that CBOE was controlling OPRA's “business operations and affairs,” permitting the two entities to be fused for jurisdictional purposes.
include: (1) the agent having the power to act on behalf of the principal with respect to third parties; (2) the agent doing something at the behest of the principal and for his benefit; and (3) the principal having the right to control the conduct of the agent).
Fasciana v. Elec. Data Sys. Corp., 829 A.2d 160, 169 n.130 (Del. Ch. 2003) (citing J.E. Rhoads & Sons, Inc. v. Ammeraal, Inc., 1988 WL 32012, at *4 (Del. Super. Mar. 30, 1988)).
Tuesday, April 10, 2018
I often use my space here to complain about courts and lawmakers being imprecise with regard to limited liability companies (LLCs). Today, I will focus on my home state of West Virginia, which recently passed a bill to support (and provide loans for cooperatives designed to provide) much-needed broadband development in the state. I applaud the effort, but the execution was not great.
Here's an example from the West Virginia Code:
12-6C-11. Legislative findings; loans for industrial development; availability of funds and interest rates.
. . . .
(f) The directors of the board shall bear no fiduciary responsibility with regard to any of the loans contemplated in this section.
This applies to a cooperative board that takes on loans for broadband projects. But it doesn't make sense. I think they used "fiduciary" when they meant "financial," as I assume they meant to say that the board members of the organization would not have “financial liability.” I am pretty sure they did not mean to remove fiduciary duties. Then again, who knows. Maybe they are fine with the directors using loans for personal vacations. (Just kidding. I am pretty sure they'd care.) I know that in finance, the term fiduciary can be used to describe money (meaning some that that relies on public trust for value), but that does not make sense here, either.
When the legislature returns for the next session, I plan to see if I can get this amended to track the LLC liability defaults. Maybe something like:
"(f) The directors of the board are not personally liable for any of the loans contemplated in this section."
I won't hold my breath, but it's worth a try.
Tuesday, April 3, 2018
Keith Paul Bishop, at the California Corporate and Securities Blog, provides an example of a court that actually pays attention to entity type. As he says, "it is nice to see that some judges do recognize that LLCs are not corporations." It sure is. In the case he cites, D.R. Mason Constr. Co. v. GBOD, LLC, 2018 U.S. Dist. LEXIS 41236, the court gets a lot right:
[A]lthough Plaintiff's Complaint does separately mention the term "shareholder," [*13] the Court will not draw the inference that this term means Plaintiff was promised traditional "stock." This inference would not be reasonable in these circumstances because Plaintiff alleges in its Complaint that Defendant GBOD is a limited liability company, not a corporation. (Compl. ¶ 3.) Under California law, LLCs distribute "membership interests," not shares of stock. See Cal. Corp. Code § 17704.07. Consequently, Plaintiff's pleading indicates the financial instrument at issue is not traditional stock. Moreover, courts tasked with deciding whether LLC membership interests constitute a security under the Exchange Act generally evaluate whether such interests are "investment contracts," not "stocks."
It is nice to see a court that acknowledges the different entity types and frustrating that this is not the norm. As Bishop explains:
Obviously, this case does not stand for the proposition that a membership interest never meets the definition of a "security" under the Exchange Act. Nor does the case deal with the issue of whether a membership interest constitutes a security under state law. It does demonstrate that some courts recognize the fact that LLCs are not corporations.
So, I sincerely hope people don't read to much into this. But I will acknowledge that some courts are getting it right. And thank Bishop for helping further the cause.
Tuesday, March 27, 2018
International law is usually not my thing (only in a few instances), but it's definitely Larry Catá Backer's thing. He has a new article out that may be of interest. If it's your thing, I recommend checking it out. He knows his stuff.
"Theorizing regulatory governance within its ecology: the structure of management in an age of globalization,"
Larry Catá Backer
Contemporary Politics 24(3):-- (2018)
Abstract: This article examines regulatory governance (‘RG’) within its own ecology. It considers RG as an ideology of governance, as its own set of techniques to that end, and as a methodology andpsychology of the relations of regulatory organisms to one another and to their context. The object is first to chart the structures and modalities of this ecology, and second to understand the properties that makes RG both coherent (singularly as the method of regulating a field, as the framework for the use of RG techniques, and as an ideology of governance), and structural (as a means of structuring regulation as an exercise of ordering power. After a brief introduction, the article introduces the regulatory context through a close reading of the operation of global garment supply chains in Bangladesh, examining RG in action within the ecology of global production. It then theorizes the meta structures of RG within this ecology as a mechanics for governance within institutions, and as an ideology for ordering systems of governance among institutions.
Tuesday, March 20, 2018
My goodness. In a recent case, a Massachusetts court deals with issues related to Bling Entertainment, LLC, which is, as you would expect, a limited liability company. It is NOT a partnership (as the court correctly notes), but ...
Yiming alleges Bling Defendants—as “managers, controlling members, and fellow members of Bling”—owed a duty of utmost good faith and loyalty to Yiming that they breached through their actions of fraud, self-dealing, embezzlement, and mismanagement. D. 16 ¶¶ 70-71. “It is well settled that partners owe each other a fiduciary duty of the utmost good faith and loyalty.” Karter v. Pleasant View Gardens, Inc., No. 16-11080-RWZ, 2017 U.S. Dist. LEXIS 50462, at *13 (D. Mass. Mar. 31, 2017) (quoting Meehan v. Shaughnessy, 404 Mass. 419, 433 (1989)). Bling is not a partnership, however, but is rather a limited liability corporation. D. 16 ¶ 10.
Nevertheless, Yiming argues the same duty applies, which is correct if Bling were a closely held corporation. See, e.g., Demoulas v. Demoulas Super Mkts., 424 Mass. 501, 528-29 (1997) (explaining that in Massachusetts, close corporations shareholders owe one another the duty of utmost good faith and loyalty); Zimmerman v. Bogoff, 402 Mass. 650, 657 (1988). In Massachusetts, a closely held corporation is “typified by: (1) a small number of stockholders; (2) no ready market for corporate stock; and (3) substantial majority stockholder participation in the management, direction and operations of the corporation.”Demoulas, 424 Mass. at 529 n.34 (quoting Donahue v. Rodd Electrotype Co. of New Eng., Inc., 367 Mass. 578, 586 (1975)).
In this context, the duty of “utmost good faith and loyalty” applies to majority and minority shareholders alike. See Zimmerman, 402 Mass. at 657-58. Although Yiming did not affirmatively plead that Bling is a close corporation, he did plead that this duty applied to Bling Defendants. D. 16 ¶ 70. Bling Defendants did not contest that they owed a fiduciary duty to Yiming. See D. 26 at 8-9. Accordingly, the Court declines to dismiss this claim.
Tuesday, March 13, 2018
A recent Georgia case highlights a whole host of things that frustrate me with litigation related to limited liability companies (LLCs). This one features an LLC making incorrect arguments and a court sanctioning that silliness. For example
Baja Properties argues that it is exempted from the rule set out in OCGA § 43-41-17 (b) by a provision in OCGA § 43-41-17 (h). Subsection (h) states, in part:
Nothing in this chapter shall preclude any person from constructing a building or structure on real property owned by such person which is intended upon completion for use or occupancy solely by that person and his or her family, firm, or corporation and its employees, and not for use by the general public and not offered for sale or lease. In so doing, such person may act as his or her own contractor personally providing direct supervision and management of all work not performed by licensed contractors.
contend that the trial court erred by denying their motion for summary judgment as to negligence claims asserted against them personally. They assert that corporate law insulates them from liability and that, while a member of an limited liability corporation [sic] may be liable for torts in which he individually participated, Ugo Mattera has pointed to no evidence that the Goldens specifically directed a particular negligent act or participated or cooperated therein. We agree with the Goldens that they were entitled to summary judgment on Ugo Mattera's negligence claim.An officer of a corporation who takes part in the commission of a tort by the corporation is personally liable therefor, and an officer of a corporation who takes no part in the commission of a tort committed by the corporation is not personally liable unless he specifically directed the particular act to be done or participated or cooperated therein.Jennings v. Smith, 226 Ga. App. 765, 766 (1), 487 S.E.2d 362 (1997) (citation omitted). Thus, if Baja Properties was negligent in constructing the house, an officer of the corporation could be held personally liable for the negligent construction if he specifically directed the manner in which the house was constructed or participated or cooperated in its negligent construction. See Cherry v. Ward, 204 Ga. App. 833, 834 (1) (a), 420 S.E.2d 763 (1992).
Tuesday, March 6, 2018
Prof. Jena Martin's New Human Rights Paper: Applying Bystander Intervention Training to Corporate Conduct
Friend and colleague Jena Martin has posted her new paper, Easing "the Burden of the Brutalized": Applying Bystander Intervention Training to Corporate Conduct. And when I say new, I mean new. It went on SSRN within the last hour.
Prof. Martin is an expert in business and human rights, and her new paper offers a new framework for corporations that are seeking to reduce or eliminate human rights violations. Her paper is designed to help corporation beyond due diligence and reporting to allow them to "engage with either the oppressor or the oppressed in a way that directly minimizes human rights abuses." It is a timely piece with some interesting and innovative suggestions. I look forward to seeing where the final version ends up.
The last few years have borne witness to a shift regarding how to address issues of oppression and social injustice. Across many different advocacy points - from police brutality to sexual violence - there seems to be a consensus that simply engaging the oppressor or the victim is not enough to affect real social change. The consensus itself is not new: it has been at the heart of many social justice movements over the years. However, what is new is the explicit evocation of the bystander within this framework. Too often, in conversations on conflicts generally (and negative human rights impact specifically), bystanders have been relegated to the sidelines, with no defined, specific role to play and no discussion within the larger narrative. Now, however, -- through the use of bystander intervention training -- these actors are taking on a more prominent role.
In previous articles, I have stated that the rhetoric and posture that transnational corporations (TNCs) maintain vis-à-vis human rights impacts is that of a bystander. Frequently, when human rights abuses occur, TNCs find themselves in the position of having to acknowledge their presence in the area of the underlying conflict, while profusely maintaining that none of their actions caused the harm against the community. Building off this prior work, this article seeks to answer the following question: are there lessons that can be learned from bystander intervention training in other contexts, that can be used for the benefits of TNCs within the field of business and human rights? I conclude that what is lacking in the current discourse on corporate policies regarding addressing negative human rights impacts is an articulation regarding when, and under what circumstances, it is appropriate for corporations to intervene in negative human rights disputes. This goes beyond the current proposals for human rights due diligence frameworks in that, rather than merely undergoing an assessment and then reporting this information out (as is required by most current legal frameworks that address business and human rights reporting) this would help corporations – informed by a bystander intervention framework – to engage with either the oppressor or the oppressed in a way that directly minimizes human rights abuses.
Tuesday, February 27, 2018
Another unforced error on the LLC front, again with a limited liability company being called a corporation.
This time, it is a recent Texas appellate court case where the court states: “In its pleadings, AMV contends that it is presently a limited liability corporation known as ArcelorMittal Vinton LLC.” Wallace v. ArcelorMittal Vinton, Inc., 536 S.W.3d 19, 21 n.1 (Tex. App. 2016), review denied (Mar. 31, 2017). As is so often the case, that is not accurate.
In its brief, the entity AMV simply stated, that it was a Defendant-Appellee as named in the suit, ArcelorMittal Vinton, Inc., was “n/k/a [now known as] ArcelorMittal Vinton LLC.” Carla WALLACE, Plaintiff-Appellant, v. ARCELORMITTAL VINTON, INC., Defendant-Appellee., 2015 WL 7687420 (Tex.App.-El Paso), 1. AMV’s counsel never said it was a corporation. The court did that on its own.
Sigh. Even in Texas, LLCs are not corporations. I swear! I looked at the statute.
And yet, a close look at the statute shows why this gets confusing for some people. The Texas statute provides specific cross-references to certain business provisions (emphasis added):
Sec. 101.002. APPLICABILITY OF OTHER LAWS.
(b) For purposes of the application of Subsection (a):
(1) a reference to "shares" includes "membership interests";
(2) a reference to "holder," "owner," or "shareholder" includes a "member" and an "assignee";
(3) a reference to "corporation" or "corporate" includes a "limited liability company";
(4) a reference to "directors" includes "managers" of a manager-managed limited liability company and "members" of a member-managed limited liability company;
(5) a reference to "bylaws" includes "company agreement"; and
(6) the reference to "Sections 21.157-21.162" in Section 21.223(a)(1) refers to the provisions of Subchapter D of this chapter.
Added by Acts 2011, 82nd Leg., R.S., Ch. 25 (S.B. 323), Sec. 1, eff. September 1, 2011.
Tuesday, February 20, 2018
Law Teaching for Adjunct Faculty and New Professors Conference
Law Teaching for Adjunct Faculty and New Professors is a one-day conference for new and experienced adjunct faculty, new full-time professors, and others who are interested in developing and supporting those colleagues. The conference will take place on Saturday, April 28, 2018, at Texas A&M University School of Law, Fort Worth, Texas, and is co-sponsored by the Institute for Law Teaching and Learning and Texas A&M University School of Law.
Sessions will include:
Course Design and Learning Outcomes – Michael Hunter Schwartz
Assessment – Sandra Simpson
Active Learning – Sophie Sparrow
Team-based Learning – Lindsey Gustafson
Technology and Teaching – Anastasia Boles
Details are here.
CALL FOR PRESENTATION PROPOSALS
Institute for Law Teaching and Learning—Summer 2018 Conference Exploring the Use of Technology in the Law School Classroom June 18-20
Gonzaga University School of Law
The Institute for Law Teaching and Learning invites proposals for conference workshops addressing the many ways that law teachers are utilizing technology in their classrooms across the curriculum. With the rising demands for teachers who are educated on active learning techniques and with technology changing so rapidly, this topic has taken on increased urgency in recent years. The Institute is interested in proposals that deal with all types of technology, and the technology demonstrated should be focused on helping students learn actively in areas such as legal theory and knowledge, practice skills, and guided reflection, etc. Accordingly, we welcome proposals for workshops on incorporating technology in the classrooms of doctrinal, clinical, externship, writing, seminar, hybrid, and interdisciplinary courses.
The Institute invites proposals for 60-minute workshops consistent with a broad interpretation of the conference theme. The workshops can address the use of technology in first-year courses, upper-level courses, required courses, electives, or academic support roles. Each workshop should include materials that participants can use during the workshop and when they return to their campuses. Presenters should model effective teaching methods by actively engaging the workshop participants. The Institute Co-Directors are glad to work with anyone who would like advice on designing their presentations to be interactive.
Second, our summer conference will be at Gonzaga Law, June 18-20 and will focus on the use of technology in the classroom. We're currently accepting proposals for that conference (and the deadline has been extended to March 2). More info here.
Tuesday, February 13, 2018
I suspect click-bait headline tactics don't work for business law topics, but I guess now we will see. This post is really just to announce that I have a new paper out in Transactions: The Tennessee Journal of Business Law related to our First Annual (I hope) Business Law Prof Blog Conference co-blogger Joan Heminway discussed here. The paper, The End of Responsible Growth and Governance?: The Risks Posed by Social Enterprise Enabling Statutes and the Demise of Director Primacy, is now available here.
To be clear, my argument is not that I don't like social enterprise. My argument is that as well-intentioned as social enterprise entity types are, they are not likely to facilitate social enterprise, and they may actually get in the way of social-enterprise goals. I have been blogging about this specifically since at least 2014 (and more generally before that), and last year I made this very argument on a much smaller scale. Anyway, I hope you'll forgive the self-promotion and give the paper a look. Here's the abstract:
Social benefit entities, such as benefit corporations and low-profit limited liability companies (or L3Cs) were designed to support and encourage socially responsible business. Unfortunately, instead of helping, the emergence of social enterprise enabling statutes and the demise of director primacy run the risk of derailing large-scale socially responsible business decisions. This could have the parallel impacts of limiting business leader creativity and risk taking. In addition to reducing socially responsible business activities, this could also serve to limit economic growth. Now that many states have alternative social enterprise entity structures, there is an increased risk that traditional entities will be viewed (by both courts and directors) as pure profit vehicles, eliminating directors’ ability to make choices with the public benefit in mind, even where the public benefit is also good for business (at least in the long term). Narrowing directors’ decision making in this way limits the options for innovation, building goodwill, and maintaining an engaged workforce, all to the detriment of employees, society, and, yes, shareholders.
The potential harm from social benefit entities and eroding director primacy is not inevitable, and the challenges are not insurmountable. This essay is designed to highlight and explain these risks with the hope that identifying and explaining the risks will help courts avoid them. This essay first discusses the role and purpose of limited liability entities and explains the foundational concept of director primacy and the risks associated with eroding that norm. Next, the essay describes the emergence of social benefit entities and describes how the mere existence of such entities can serve to further erode director primacy and limit business leader discretion, leading to lost social benefit and reduced profit making. Finally, the essay makes a recommendation about how courts can help avoid these harms.
February 13, 2018 in Business Associations, Corporate Governance, Corporate Personality, Corporations, CSR, Current Affairs, Delaware, Joshua P. Fershee, Law and Economics, Lawyering, Legislation, LLCs, Management, Research/Scholarhip, Shareholders, Social Enterprise, Unincorporated Entities | Permalink | Comments (0)
Tuesday, February 6, 2018
A brand new Arizona case continues the trend of incorrectly discussing limited liability companies (LLCs) as limited liability corporations, but it does allow for an interesting look at how entities are sometimes treated (or not) in laws and regulations. Here’s the opening paragraph of the case:
Noah Sensibar appeals from the superior court's ruling affirming the Tucson City Court's finding that he had violated the Tucson City Code (TCC). He argues that the municipal ordinance in question is facially invalid because it conflicts with a state statute shielding members or agents of a limited liability corporation from personal liability.
City of Tucson v. Noah Sensibar, No. 2 CA-CV 2017-0087, 2018 WL 703319 (Ariz. Ct. App. Feb. 5, 2018).
About three years ago, the City of Tucson alleged that Sensibar, as “the managing member and statutory agent of Blue Jay Real Estate LLC, an Arizona corporation, was responsible for building code violations.” Id. (emphasis added). Notwithstanding the incorrect characterization of the entity type, it looks like the court at least reasonable (though not clearly correct) to hold Sensibar individually liable. Here’s why:
The Tuscon City Code states that “Any owner or responsible party who commits, causes, permits, facilitates or aids or abets any violation of any provision of this chapter . . . is responsible for a civil infraction and is subject to a civil sanction of not less than one hundred dollars ($100.00) nor more than two thousand five hundred dollars ($2,500.00).” Tucson Code Sec. 16-48(2) (Violations and penalties).
The Code Definitions in Sec. 16-3 provide the following:
Owner means, as applied to a building, structure, or land, any part owner, joint owner, tenant in common, joint tenant or tenant by the entirety of the whole or a part of such building, structure or land.
. . . .
Person means any natural person, firm, partnership, association, corporation, company or organization of any kind, but not the federal government, state, county, city or political subdivision of the state.
. . . .
Responsible party means an occupant, lessor, lessee, manager, licensee, or person having control over a structure or parcel of land; and in any case where the demolition of a structure is proposed as a means of abatement, any lienholder whose lien is recorded in the official records of the Pima County Recorder's Office.
As such, the Code seems to contemplate holding both entities and individuals liable. Still, Sensibar had an argument. The use of the term “manager” here causes some potential confusion because one can be a manager of an LLC, while the LLC might serve as the manager of the property. Thus, it could be that only the LLC should be liable. Another plausible reading, though, is that “manager” meant the natural person doing the managing as is common in property situations. Manager, like occupant, lessee, and lessor, is not defined in the Code, so it would seem the intended source of the definitions should be from a property perspective, not an entity perspective.
Similarly, the Code could mean a natural “person having control over a structure” can be liable. If that’s the case, and the court seems to have gone down this road, the argument would be that Sensibar was being held liable directly for his role as manager or person in control of the property and not vicariously for violations of the LLC. Given that occupants, lessors, and lessees, among others, can be held liable, it does appear that the Code could have intended to impose liability directly on multiple parties, including both individuals and entities. This would be sensible, in many contexts, though it would also be sensible to say explicitly, especially given that the term “person” clearly includes entities.
A simple improvement might be to update the definition of “responsible party,” as follows:
Responsible party means an, whether as an individual or entity, any occupant, lessor, lessee, manager, licensee, or person having control over a structure or parcel of land and in any case where the demolition of a structure is proposed as a means of abatement, any lienholder whose lien is recorded in the official records of the Pima County Recorder's Office.
That would, at least, be consistent with the decision. Because if the court is holding Sensibar liable for merely being the manager of the LLC, and not as the manager of the property, the case is wrongly decided. Too bad the notice of appeal was not timely filed – maybe we could have found out.
UPDATE: Based on a good comment from Tom N., I did a little more research. As of an LLC filing in 2009, Noah Sensibar owned at least a 20% interest. (It may be 50% because there were two listed members, but it was at least 20%.) As such, this suggests that the LLC does not have funding to cover the fines or that express indemnification is lacking and the other member(s) won't agree to cover the costs from LLC funds.
I will also note that a 2016 decision denying Sensibar's appeal stated, "The court also heard evidence that Sensibar, the managing partner of the LLC, was 'the person in charge' of the property." City of Tucson v. Sensibar, No. 2 CA-CV 2016-0051, 2016 WL 5899737, at *1 (Ariz. Ct. App. Oct. 11, 2016). Seriously? He's an LLC manager. That's all. LLCs are not corporations OR partnerships. THEY ARE LLCS!
Wednesday, January 31, 2018
After spending a little time with the new tax bill, I couldn't help but think, "there must be a better way." That reminded me of an article from a little while back in the West Virginia Law Review, titled, Legislation's Culture, by Richard K. Neumann, of Hofstra University - School of Law (PDF). Here’s the abstract:
American statutes can seem like labyrinthine mazes when compared to some countries’ legislation. French codes are admired for their intellectual elegance and clarity. Novelists and poets (Stendhal, Valéry) have considered the Code civil to be literature. Swedish legislation might be based on empirical research into problems the legislation is intended to remedy, and the drafting style, though modern today, is descended from an oral tradition of poetic narrative.
Comparing these legislative cultures with our own reveals that the main problem with American legislation is not too many words. It is too many ideas — a high ratio of concepts per legislative goal. When American, French, and Swedish legislatures address similar problems, the French and Swedes draft using far fewer concepts than Americans do. In both countries, simple solutions are preferred over convoluted ones. The drafters of the Code civil thought the highest intellectual and legislative accomplishment to be simplicity. The Swedes got to approximately the same place through a cultural value that law be understandable to the public. Where the American legislative process can seem chaotic, there has been some respect for Cartesian rationality in France and for empirical evidence in Sweden.
Even if American statutes were to be translated into ordinary English, they would still be labyrinths because our legislatures insist on addressing every conceivable detail that legislators can imagine. The result is excessively conceptualized legislation, imposing large numbers of duties. Statutory concepts cost money. They create issues, which must be decided by publicly funded courts and agencies with additional costs to the parties involved. Every unnecessary statutory concept wastes social and economic resources. And to the extent law seems incomprehensible to the public, it loses moral authority.
Having studied law in Louisiana, I admit to a certain soft spot for the civil code, even if my fondness is rooted firmly in this country. (In fact, about one year ago, we lost a giant in the civil law, Athanassios Nicholas "Thanassi" Yiannopoulos. See, for example, his work, A.N. Yiannopoulos, Requiem for a Civil Code: A Commemorative Essay, 78 TUL. L. REV. 379 (2003), available via Hein Online here.)
I digress. Back to my point, I think this statement from Neumman is spot on: "[T]o the extent law seems incomprehensible to the public, it loses moral authority." Absolute truth. And the same applies to regulations.
Tuesday, January 23, 2018
As regular readers know, I am particular about language and meaning, especially in the business-entity space related to limited liability companies (LLCs). I think because of that, I was drawn to a new paper from Shu-Yi Oei (Boston College), The Trouble with Gig Talk: Choice of Narrative and the Worker Classification Fights, 81 Law & Contemp. Probs. ___ (2018). The abstract:
The term “sharing economy” is flawed, but are the alternatives any better? This Essay evaluates the uses of competing narratives to describe the business model employed by firms like Uber, Lyft, TaskRabbit, and GrubHub. It argues that while the term “sharing economy” may be a misnomer, terms such as “gig economy,” “1099 economy,” “peer-to- peer economy” or “platform economy” are just as problematic, possibly even more so. These latter terms are more effective in exploiting existing legal rules and ambiguities to generate desired regulatory outcomes, in particular the classification of workers as independent contractors. This is because they are plausible, speak to important regulatory grey areas, and find support in existing laws and ambiguities. They can therefore be deployed to tilt outcomes in directions desired by firms in this sector.
This Essay’s analysis suggests that narratives that are at least somewhat supportable under existing law may be potent in underappreciated ways. In contrast, clearly erroneous claims may sometimes turn out to be hyperbolic yet harmless. Thus, in evaluating the role of narrative in affecting regulatory outcomes, it is not only the obviously wrong framings that should concern us but also the less obviously wrong ones.
There are several interesting points in the piece, and find this part of the conclusion especially compelling:
I cannot prove that the deployment of gig characterization is the only reason certain legal treatments and outcomes (such as independent contractor classification for workers) seem to be sticking, at least for the moment. My narrower point is that while gig and related characterizations appear innocuous and accurate relative to the sharing characterization, this set of descriptors may actually be doing more work in terms of advancing a desired regulatory outcome. The reasons they are able to do more work are that (1) gig characterization speaks to an important and material legal ambiguity, (2) the gig characterization is plausibly accurate, even if deeply contested, and (3) the proponents of gig characterization have been able to use procedural and other tools to shore up gig characterization and defeat its competitors. These observations may be generalized beyond the gig context: While the temptation is to focus on narratives and characterizations that are clearly wrong, this Essay suggests that we should also pay attention to more subtle narratives that are less clearly wrong, because such narratives may be doing more work by virtue of being “almost right.”
This last point is one that resonates with me on the LLC front, where people insist on comparing or analogizing LLCs to corporations. There are times when such a comparison or analogy is "almost right," and it is in these circumstances that the perils of careless language can cause the most trouble because the same comparison or analogy can get made later when doing so is clearly wrong.
Tuesday, January 16, 2018
I have had reason to look back on some foundational scholarship in LLCs recently, and one article really stood out for me. Larry Ribstein's The Deregulation of Limited Liability and the Death of Partnership. It's another snow day with kids, so I haven't had a lot of time to delve into the thoughts this raised for me, so I'll let Larry's words speak for themselves. Keep in mind this is from 1992:
The popularity of the partnership form of business1 indicates that an organizational form in which some owners can be held personally liable for the firm's debts is efficient for many firms. This could be because, for many firms, individual liability reduces the firm's credit costs more than it increases owners' risk-bearing, monitoring, or other costs. This Article, however, suggests an alternative explanation: the partnership form is attractive for many firms on the margin only because of the regulatory costs of limited liability, including double corporate taxation and limitations on organizational form.
Recent developments provide a valuable opportunity to test this explanation. Many lawyers and legislators have become interested in a new limited liability business form, the "limited liability company" (LLC), that lets firms adopt limited liability without many of the tax and other costs that once attended limited liability. If this Article's regulatory explanation of partnership is correct, the partnership form of business will greatly diminish in importance. After a transitional period, partnership will survive, if at all, as a residual form for firms that have no customized agreement.