Limited Liability Limited

11 Min Read By: Daniel S. Kleinberger

Limited liability companies went mainstream in 1988, began to capture the market for closely held businesses in 1997, and now have the lion’s share of that market. Since the advent of limited liability companies, a corporate-like liability shield, in addition to pass-through status under federal income tax law, has been one of two hallmarks of a limited liability company. Indeed, for many years courts have described the  limited liability company as “a hybrid business entity [that] provides members with limited liability to the same extent enjoyed by corporate shareholders.”[1]

The LLC shield should therefore be easy to understand: a limited liability company shields its members in essentially the same way as a corporation shields its shareholders. Yet courts and practitioners still occasionally misunderstand the intended purpose and proper effect of the LLC shield.

The two poster children for this problem are Dass v. Yale,[2] a decision of the Illinois court of appeals, and SDIF Limited Partnership 2 v. Tentexkota, an action brought in federal district court in South Dakota.[3] Dass held that the LLC shield immunizes a member-manager for direct liability for the member’s own tortious conduct.[4]  In Tentexkota, members of a South Dakota limited liability company sought to escape their personal guarantees of the LLC’s debt by arguing that the LLC liability shield invalidated the guarantees.  The federal court rephrased the guarantors’ argument as a question and certified the question to the South Dakota Supreme Court.[5]

Both cases turned on what the relevant statutory language did not say.  In Dass, the court noted that “the language of the [Illinois] LLC Act [had been] changed by removing language explicitly providing for personal liability,”[6] pointed out that  “[g]enerally, a change to the unambiguous language of a statute creates a rebuttable presumption that the amendment was intended to change the law,” ignored the possibility that the deleted language had been redundant, and allowed the rebuttable presumption to override the plain meaning of the Illinois shield language.  The defendants in Tentexkota argued that the South Dakota shield language should be interpreted as invalidating personal guarantees, in part because South Dakota had failed to revise its shield language (derived from the first Uniform Limited Liability Company Act) in accord with revisions made in 2006 by the Revised Uniform Limited Liability Company Act).[7]

 Neither Dass nor Tentexkota are still at issue. This year, Illinois legislatively abrogated Dass,[8] and Tentexkota settled before the South Dakota Supreme Court answered the certified question.[9]  However, the problem illustrated by these cases remains. Hence this article, which seeks “to make clear beyond peradventure”[10] the proper purpose and intended effect of the LLC shield.

The analysis is necessarily rooted in history and begins with sole proprietorship and ordinary general partnerships:

Fully understanding the LLC shield requires understanding owner liability in sole proprietorships and ordinary general partnerships, the two principal structures for doing business that predated the advent of corporations. In both these structures, owners are personally liable for the debts of the business merely on account of being an owner. It was the purpose of the corporation to negate that status liability[,] …. sever the relationship between owner status and personal liability[,]… and to do nothing else.[11] 

From this perspective, two fundamental points are clear. As a matter of concept, the liability shield follows ineluctably from an entity’s status as a legal person separate and distinct from each and all the entity’s owners. Because in general one person is not responsible for the obligations of another, “[t]he ‘separate entity’ characteristic is fundamental to a limited liability company and is inextricably connected to … the liability shield.” ULLCA (2013) § 108(a), cmt.

In practical terms, the liability shield’s sole function is to negate the automatic “pass through” liability that owners once had for the obligations of their business. Thus, the shield has nothing to do with liability arising from a person’s own conduct in connection with an entity’s business—whether that person is an owner, a manager, an employee, an independent contractor, or otherwise.

Because the member or manager liability at issue is solely vicarious, the shield is irrelevant to claims seeking to hold a member or manager directly liable on account of the member’s or manager’s own conduct. Put another way, “[t]here is no question” that “the member-manager of a limited liability company who causes his business to breach common law and statutory duties may be held independently liable for his personal torts.”[12] 

The official comments to ULLCA (2013) contain several examples of this proposition, including one applicable to law firms in particular:

EXAMPLE: A limited liability company provides professional services, and one of its members commits malpractice. The liability shield is irrelevant to the member’s direct liability in tort. However, if the member’s malpractice liability is attributed to the LLC under agency law principles, the liability shield will protect the other members of the LLC against a claim that they must make good on the LLC’s liability.[13] 

Put another way:

A Tort Is a Tort Is a Tort—Being an agent does not immunize a person from tort liability. A tortfeasor is personally liable, regardless of whether the tort was committed on the instructions from or to the benefit of a principal. A tortfeasor cannot defend itself by saying, “Well, I did what I did to serve my principal.”[14] 

Likewise, when a member makes a contract in the member’s own name, the member’s contractual obligations are outside the shield—even if the contract’s purpose is to benefit the company. For example: “A manager personally guarantees a debt of a limited liability company. [The liability shield] is irrelevant to the manager’s liability as guarantor.”[15] 

One additional, very practical point warrants mention—namely, role liability.[16] “Provisions of regulatory law [both state and federal] may impose liability on a member or manager due to a role the person plays in the LLC.”[17] In some instances the liability results from conduct, in others from status or position (e.g., more than 10% of the existing ownership interests), in others from a combination.

In any event, when “role liability” is at issue, the LLC shield is inapposite, because the liability is not “of a limited liability company” and almost never arises “solely by reason of the member acting as a member or manager acting as a manager.”[18] 

A New York case, Pepler v. Coyne, provides a good example. A limited liability company terminated an employee, the employee sued the company for unlawful termination on the basis of disability, and named the two manager-members of the company as individual defendants. When one of the member-managers (Coyne) invoked the LLC liability shield as a defense and moved to dismiss, the trial court granted the motion. The appellate court reversed:

Coyne’s contention that he is personally exempt from liability by virtue of [the LLC shield] is without merit. The general statutory exemption [under the LLC statute] from personal responsibility for an organization’s debts, obligations and liabilities does not extend to violations of [the anti-discrimination statute] by a person with an ownership interest in, [and] the power to make personnel decisions for, the organization. Thus, Coyne is amenable to liability upon proof that he became a party to Stone’s discriminatory termination of plaintiff “‘by encouraging, condoning, or approving it.’”[19]

Finally (though contrariwise), the corporate and the LLC shield may differ in one important respect—that is, whether disregard for “entity formalities” is grounds for disregarding the liability shield and “piercing the veil.” This topic is somewhat complicated, and a future column will discuss the issue in some detail. In the meantime, you can hear the topic discussed as part of a panel discussion at the ABA Business Law Section’s 2019 Annual Meeting in Washington, D.C. —“10 Things Corporate Lawyers Must Understand about How a Limited Liability Company is NOT a Corporation” (Thursday, September 12 from 2 to 3:30 PM, Salon 1, M2).

But otherwise, as per a decision of the 11th Circuit: “The limited liability company (LLC) is a … hybrid form of business entity that combines the liability shield of a corporation with the federal tax classification of a partnership.”[20] Thus, consistent with the LLC shield’s corporate law antecedents, the LLC shield’s proper purpose is to disallow purely status-based member liability for an LLC’s debts. The effect of the LLC shield should be limited accordingly.


[1] PacLink Commc'ns Int'l, Inc. v. Superior Court, 90 Cal. App. 4th 958, 963, 109 Cal. Rptr. 2d 436, 439 (2001) (quoting 9 Witkin, Summary of Cal. Law (2001 supp.) Corporations, § 43A, p. 346; internal quotation marks omitted).

[2] Dass v. Yale, 2013 IL App (1st) 122520, 3 N.E.3d 858.

[3] SDIF Limited Partnership 2 v. Tentexkota, LLC (U.S. Dist. Ct. S.D.) 1:17-CV-01002-CBK. The author was retained as an expert by the law firm representing the creditors.

[4] Dass v. Yale, 2013 IL App (1st) 122520, ¶ 28, 3 N.E.3d 858, 864. The South Carolina Supreme Court came very close to making the same error as the Illinois appellate court. In 2012, the Court concluded that the LLC liability shield “only protects non-tortfeasor members from vicarious liability and does not insulate the tortfeasor himself from personal liability for his actions.” but the two of the five justices dissented. 16 Jade St., LLC v. R. Design Const. Co., 398 S.C. 338, 349, 728 S.E.2d 448, 454 (2012). Opinion withdrawn and superseded on reh'g sub nom. 16 Jade St., LLC v. R. Design Const. Co., LLC., 405 S.C. 384, 747 S.E.2d 770 (2013). The superseding opinion decided the case on entirely different grounds, allowing the Court to “find it unnecessary to reach the novel issue of whether the LLC Act absolves an LLC member of personal liability for negligence committed while acting in furtherance of the company business.” 16 Jade St., LLC v. R. Design Const. Co., LLC., 405 S.C. 384, 390, 747 S.E.2d 770, 773 (2013).

[5] SDIF Ltd. P'ship 2 v. Tentexkota, LLC, No. 1:17-CV-01002-CBK, 2018 WL 6493160, at *1 (D.S.D. Dec. 10, 2018).

[6] Dass v. Yale, 2013 IL App (1st) 122520, 3 N.E.3d 858. The deleted language was: “A manager of a limited liability company shall be personally liable for any act, debt, obligation, or liability of the limited liability company or another manager or member to the extent that a director of an Illinois business corporation is liable in analogous circumstances under Illinois law.” Id. (quoting 805 ILCS 180/10–10(b) (West 1996)). For a more detailed discussion of Dass, see Steven G. Frost, Jeff Close and Joe Lombardo, Dass v. Yale: Members and Managers of an Illinois LLC Are Not Liable for Their Tortious Conduct, J. Passthrough Entities (May-June 2014) 31-37.

[7] Brief of Defendants to S.D. Sup. Ct., at 10. The Defendants’ Brief cited and relied on Dass. Brief at 2, 12,13.

[8] Ill. Public Act 101-0553, amending 805 ILCS 180/10-10 by adding a new Section 10-10(a-5).  The new section refers specifically to Dass and a tort-related case which Dass cited:  “The purpose of this subsection (a-5) is to overrule the interpretation of subsections (a) [shield] and (d) [powers of the articles to change shield] setvforth in Dass v. Yale, 2013 IL App (1st) 122520, and Carollo v. Irwin, 2011 IL App (1st) 102765, and clarify that under existing law a member or manager of a limited liability company may be liable under law other than this Act for its own wrongful acts or omissions, even when acting or purporting to act on behalf of a limited liability company.” http://www.ilga.gov/legislation/BillStatus.asp?DocNum=1495&GAID=15&DocTypeID=SB&LegId=118397&SessionID=108&GA=101 , last visited 8/28/19.

[9] The federal court accordingly dismissed the case, and the South Dakota Supreme Court promptly deemed the certified question moot. SDIF Ltd. Phip 2 v. Tentexkota, LLC, Order Rendering Certification Moot (South Dakota Supreme Court; File No: 1:17-CV1002-CBK; #28825) August 27, 2019. 

[10] Cyan, Inc. v. Beaver Cty. Employees Ret. Fund, 138 S. Ct. 1061, 1074, 200 L. Ed. 2d 332 (2018).

[11] Carter G. Bishop & Daniel S. Kleinberger, Limited Liability Companies: Tax and Business Law (Warren Gorham & Lamont, 1994; Supp. 2019-1) (“Bishop & Kleinberger, LIMITED LIABILITY COMPANIES”), ¶ 6.01[1][b] (The Shield as Negating the “Status Liability” of a Sole Proprietor and Partner) (emphasis in original; footnotes omitted).

[12] ULLCA (2013) § 304, cmt. (Shield Inapposite for Claims Arising from a Member’s or Manager’s Own Conduct) (quoting Dep't of Agric. v. Appletree Mktg., L.L.C., 485 Mich. 1, 4, 18, 779 N.W.2d 237, 239, 247 (2010)).

[13] ULLCA (2013) § 304(a), cmt., Shield Inapposite for Claims Arising from a Member’s or Manager’s Own Conduct.

[14] Daniel S. Kleinberger, Agency, Partnership and LLCs: Examples and Explanations (5th ed.; Wolters Kluwer; 2017) § 4.2.3a at 182 (footnote omitted).

[15] ULLCA (2013) § 304(a), cmt., Shield Inapposite for Claims Arising from a Member’s or Manager’s Own Conduct.

[16] This phrase was coined as the caption for a section of Bishop & Kleinberger, LIMITED LIABILITY COMPANIES, ¶ 6.04[4].

[17] ULLCA (2013) § 304, cmt., Shield Inapposite to Role Liability Claims

[18] ULLCA (2013) § 304(a), cmt. (emphasis added).

[19] Pepler v. Coyne, 33 AD3d 434, 435, 822 NYS2d 516 (2006) (quoting Matter of State Div. of Human Rights v. St. Elizabeth’s Hosp., 66 NY2d 684, 687 (1985)).

[20] United States v. ADT Sec. Servs., Inc., 522 F. App'x 480, 486 (11th Cir. 2013) (emphasis added) (quotation marks and citation omitted).

ABOUT THE AUTHOR

St Paul, MN

Daniel S. Kleinberger

Daniel S. Kleinberger
Education
A.B., 1972, Harvard University
J.D., 1979, Yale Law School

Experience
Mitchell Hamline School of Law: emeritus professor of law, 2015-.

William…

MORE FROM THIS AUTHOR

Login or Registration Required

You need to be logged in to complete that action.

Register/Login