Tuesday, November 20, 2018
Tom Rutledge posts the following over at the Kentucky Business Entity Law Blog:
LLC Members Are Not the LLC’s Employees
There is now pending before the Eighth Circuit Court of Appeals of a suit that may turn on whether the relevant question, namely whether an LLC member is an employee of the LLC, has already been determined by a state court. In that underlying judgment, the Circuit Court of Cole County, Missouri, issued a judgment dated October 9 18, 2017 in the case Joseph S. Vaughn Kaenel v. Warren, Case No.: 15 AC-CC 00472. That judgment provided in part:
As an equity partner of Armstrong Teasdale, LLP, [Kaenel] is not a covered employee protected by the Missouri Human Rights Act.
I am curious as to which case this is that is pending. Tom knows his stuff and knows (and respects) the differences between entities, so I assume there is more to than appears here.
For example, the fact that a state court determined that an LLP equity partner is not an employee does not inherently answer the question of whether an LLC member is an employee. It could, but it does not have to do so.
In addition, I'd want to know more about the relationship between the LLC member and the entity. I am inclined to agree that an LLC member is not generally an employee merely by virtue of being a member. But I am also of the mind that an LLC member could also be an employee. In fact, there are times when counsel would be wise to advise a client who is an LLC member to also get an employment contract is she wishes to get paid. I am assuming there is not an employment contract here for the Eighth Circuit case.
However, suppose in the operating agreement all the members agree to pay one member for certain services. Or perhaps the compensated member gets priority payouts because of her agreement to do certain work for the entity. That would, as far as I am concerned, at least muddy the waters.
I'll be interested to see where this one goes (and, perhaps, what I have missed). But as far as I am concerned, LLC members can also be LLCs employees, even though the general answer is that they are not.
Tuesday, August 21, 2018
Senator Elizabeth Warren last week released her Accountable Capitalism Act. My co-blogger Haskell Murray wrote about that here, as have a number of others, including Professor Bainbridge, who has written at least seven posts on his blog. Countless others have weighed in, as well.
There are fans of the idea, others who are agnostic, and still other who thinks it’s a terrible idea. I am not taking a position on any of that, because I am too busy working through all the flaws with regard to entity law itself to even think about the overall Act.
As a critic of how most people view entities, my expectations were low. On the plus side, the bill does not say “limited liability corporation” one time. So that’s a win. Still, there are a number of entity law flaws that make the bill problematic before you even get to what it’s supposed to do. The problem: the bill uses “corporation” too often where it means “entity” or “business.”
Let’s start with the Section 2. DEFINITIONS. This section provides:
(2) LARGE ENTITY.—
(A) IN GENERAL.—The term ‘‘large entity’’ means an entity that—
(i) is organized under the laws of a State as a corporation, body corporate, body politic, joint stock company, or limited liability company;
(ii) engages in interstate commerce; and
(iii) in a taxable year, according to in- formation provided by the entity to the Internal Revenue Service, has more than $1,000,000,000 in gross receipts.
Okay, so it does list LLCs, correctly, but it does not list partnerships. This would seem to exclude Master Limited Partnerships (MLPs). The Alerian MLP Indexlist about 40 MLPs with at least a $1 billion market cap. It also leaves our publicly traded partnerships(PTPs). So, that’s a miss, to say the least.
Section 2 goes on to define a
(6) UNITED STATES CORPORATION.—The term “United States corporation’’ means a large entity with respect to which the Office has granted a charter under section 3.
The bill also creates an “Office of United States Corporations,” in Section 3, even though the definitions section clear says a “large entity” includes more than just corporations.
Next is Section 4, which provides the “Requirement for Large Entities to Obtain Charters.”
(1) IN GENERAL.— An entity that is organized as a corporation, body corporate, body politic, joint stock company, or limited liability company in a State shall obtain a charter from the Office . . . .”
So, again, the definition does not include MLPs (or any other partnership forms, or coops for that matter) as large entities. I am not at all clear why the Act would refer to and define “Large Entities,” then go back to using “corporations.” Odd.
Later in section 4, we get the repercussions for the failure to obtain a charter:
An entity to which paragraph (1) applies and that fails to obtain a charter from the Office as required under that paragraph shall not be treated as a corporation, body corporate, body politic, joint-stock company, or limited liability company, as applicable, for the purposes of Federal law during the period beginning on the date on which the entity is required to obtain a charter under that paragraph and ending on the date on which the entity obtains the charter.
Here, the section chooses not to use the large entity definition or the corporation definition and instead repeats the entity list from the definitions section. As a side note, does this section mean that, for “purposes of Federal law,” any statutory “large entity” without a charter is a general partnership or sole proprietorship? I would hope not for the LLC, which isn’t a corporation, anyway.
Finally, in Section 5, the Act provides:
(1) RULE OF CONSTRUCTION REGARDING GENERAL CORPORATE LAW.—Nothing in this section may be construed to affect any provision of law that is applicable to a corporation, body corporate, body politic, joint stock company, or limited liability company, as applicable, that is not a United States corporation.
Again, I will note that “general corporate law” should not apply to anything but corporations, anyway. LLCs, in particular.
The Act further contemplates a standard of conduct for directors and officers. LLCs do not have to have either, at least not in the way corporations do, nor do MLPs/PTPs, which admittedly do not appear covered, anyway. The Act also contemplates shareholders and shareholder suits, which are not a thing for LLCs/MLPs/PTPs because they don’t have shareholders.
This is not an exhaustive list, but I think it’s a pretty good start. I will concede that some of my critiques could be argued another way. Obviously, I'd disagree, but maybe some of this is not as egregious as I see it. Still, there are flaws, and if this thing is going to move beyond even the release, I sure hope they take the time to get the entity issues figured out. I’d be happy to help.
August 21, 2018 in Corporate Governance, Corporate Personality, Corporations, CSR, Joshua P. Fershee, Legislation, LLCs, Management, Partnership, Shareholders, Unincorporated Entities | Permalink | Comments (0)
Wednesday, August 1, 2018
I am probably late to the game on this, but I just realized that Uber promotes their drivers as "driver-partners." It's even in their ads. This seems unwise.
Uber has a history linked to the question about whether their drivers are employees or independent contractors. But what about the question of whether Uber drivers are partners or independent contractors? That is big, potential liability conundrum.
Now, just because one says they are partners, that does not make it so, at least as to each other. The converse is also true -- saying expressly "this agreement does not form a partnership" does not necessarily mean a court won't find one. See, e.g., Martin v. Peyton, 158 N.E. 77 (NY 1927) ("Statements that no partnership is intended are not conclusive."). But, as to third parties, at a minimum, affirmative statements that one is a partner, can create liability for those involved. The Uniform Partnership Act (1914) § 16. Partner by Estoppel, provides:
(1) When a person, by words spoken or written or by conduct, represents himself, or consents to another representing him to any one, as a partner in an existing partnership or with one or more persons not actual partners, he is liable to any such person to whom such representation has been made, who has, on the faith of such representation, given credit to the actual or apparent partnership, and if he has made such representation or consented to its being made in a public manner he is liable to such person, whether the representation has or has not been made or communicated to such person so giving credit by or with the knowledge of the apparent partner making the representation or consenting to its being made.
(a) When a partnership liability results, he is liable as though he were an actual member of the partnership.
(b) When no partnership liability results, he is liable jointly with the other persons, if any, so consenting to the contract or representation as to incur liability, otherwise separately.
Similarly, the Revised Uniform Partnership Act provides:
SECTION 308. LIABILITY OF PURPORTED PARTNER.
(a) If a person, by words or conduct, purports to be a partner, or consents to being represented by another as a partner, in a partnership or with one or more persons not partners, the purported partner is liable to a person to whom the representation is made, if that person, relying on the representation, enters into a transaction with the actual or purported partnership. If the representation, either by the purported partner or by a person with the purported partner’s consent, is made in a public manner, the purported partner is liable to a person who relies upon the purported partnership even if the purported partner is not aware of being held out as a partner to the claimant. If partnership liability results, the purported partner is liable with respect to that liability as if the purported partner were a partner. If no partnership liability results, the purported partner is liable with respect to that liability jointly and severally with any other person consenting to the representation.
Now, can I come up with plenty of counterarguments and ways to make this liability less likely, and those are compelling arguments, too, in many settings. However, I cannot come up with such a good argument that would make it worth using "Driver-Partner" as my term. How about "Driver-Teammate" or "Driver-Affiliate" or "Driver-Collaborator" or even "Driver-Member?" For me, the specificity of the term "partner," and the liability that can follow without formal action, would warrant avoiding its use. But maybe that's just me.
Monday, April 23, 2018
Call for Papers for the
Section on Business Associations Program on
Contractual Governance: the Role of Private Ordering
at the 2019 Association of American Law Schools Annual Meeting
The AALS Section on Business Associations is pleased to announce a Call for Papers from which up to two additional presenters will be selected for the section’s program to be held during the AALS 2019 Annual Meeting in New Orleans on Contractual Governance: the Role of Private Ordering. The program will explore the use of contracts to define and modify the governance structure of business entities, whether through corporate charters and bylaws, LLC operating agreements, or other private equity agreements. From venture capital preferred stock provisions, to shareholder involvement in approval procedures, to forum selection and arbitration, is the contract king in establishing the corporate governance contours of firms? In addition to paper presenters, the program will feature prominent panelists, including SEC Commissioner Hester Peirce and Professor Jill E. Fisch of the University of Pennsylvania Law School.
Our Section is proud to partner with the following co-sponsoring sections: Agency, Partnership, LLC's and Unincorporated Associations; Contracts; Securities Regulation; and Transactional Law & Skills.
Please submit an abstract or draft of an unpublished paper to Anne Tucker, email@example.com on or before August 1, 2018. Please remove the author’s name and identifying information from the submission. Please include the author’s name and contact information in the submission email.
Papers will be selected after review by members of the Executive Committee of the Section. Authors of selected papers will be notified by August 25, 2018. The Call for Papers presenters will be responsible for paying their registration fee, hotel, and travel expenses.
Any inquiries about the Call for Papers should be submitted to: Anne Tucker, Georgia State University College of Law, firstname.lastname@example.org or (404) 413.9179.
[Editorial note: As some may recall, the BLPB hosted a micro-symposium on aspects of this issue in the limited liability company context in anticipation of a program held at the 2016 AALS annual meeting. The initial post for that micro-symposium is here, and the wrap-up post is here. This area--especially as writ broadly in this proposal--remains a fascinating topic for study and commentary.]
April 23, 2018 in Anne Tucker, Business Associations, Call for Papers, Conferences, Contracts, Corporate Finance, Corporate Governance, Corporations, Joan Heminway, LLCs, Nonprofits, Partnership | Permalink | Comments (0)
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, December 19, 2017
A recent case in Washington state introduced me to some interesting facets of Washington's recreational marijuana law. The case came to my attention because it is part of my daily search for cases (incorrectly) referring to limited liability companies (LLCs) as "limited liability corporations." The case opens:
In 2012, Washington voters approved Initiative Measure 502. LAWS OF 2013, ch. 3, codified as part of chapter 69.50 RCW. Initiative 502 legalizes the possession and sale of marijuana and creates a system for the distribution and sale of recreational marijuana. Under RCW 69.50.325(3)(a), a retail marijuana license shall be issued only in the name of the applicant. No retail marijuana license shall be issued to a limited liability corporation unless all members are qualified to obtain a license. RCW 69.50.331(1)(b)(iii). The true party of interest of a limited liability company is “[a]ll members and their spouses.”1 Under RCW 69.50.331(1)(a), the Washington State Liquor and Cannabis Board (WSLCB) considers prior criminal conduct of the applicant.2
(b) No license of any kind may be issued to:. . . .(iii) A partnership, employee cooperative, association, nonprofit corporation, or corporation unless formed under the laws of this state, and unless all of the members thereof are qualified to obtain a license as provided in this section;
True party of interest: Persons to be qualified
Sole proprietorship: Sole proprietor and spouse.General partnership: All partners and spouses.Limited partnership, limited liability partnership, or limited liability limited partnership: All general partners and their spouses and all limited partners and spouses.Limited liability company: All members and their spouses and all managers and their spouses.Privately held corporation: All corporate officers (or persons with equivalent title) and their spouses and all stockholders and their spouses.Publicly held corporation: All corporate officers (or persons with equivalent title) and their spouses and all stockholders and their spouses.
Multilevel ownership structures: All persons and entities that make up the ownership structure (and their spouses).
(1) A corporation has the officers described in its bylaws or appointed by the board of directors in accordance with the bylaws.(2) A duly appointed officer may appoint one or more officers or assistant officers if authorized by the bylaws or the board of directors.(3) The bylaws or the board of directors shall delegate to one of the officers responsibility for preparing minutes of the directors' and shareholders' meetings and for authenticating records of the corporation.(4) The same individual may simultaneously hold more than one office in a corporation.
Requirement for and duties of board of directors.
(1) Each corporation must have a board of directors, except that a corporation may dispense with or limit the authority of its board of directors by describing in its articles of incorporation, or in a shareholders' agreement authorized by RCW 23B.07.320, who will perform some or all of the duties of the board of directors.(2) Subject to any limitation set forth in this title, the articles of incorporation, or a shareholders' agreement authorized by RCW 23B.07.320:(a) All corporate powers shall be exercised by or under the authority of the corporation's board of directors; and(b) The business and affairs of the corporation shall be managed under the direction of its board of directors, which shall have exclusive authority as to substantive decisions concerning management of the corporation's business.
(4) Persons who exercise control of business - The WSLCB will conduct an investigation of any person or entity who exercises any control over the applicant's business operations. This may include both a financial investigation and/or a criminal history background.
December 19, 2017 in Corporations, Current Affairs, Entrepreneurship, Family Business, Joshua P. Fershee, Legislation, Licensing, LLCs, Management, Nonprofits, Partnership, Shareholders, Unincorporated Entities | Permalink | Comments (0)
Tuesday, October 31, 2017
When the indictment for Paul Manafort and Richard Gates was released yesterday, I decided to take a look, in part because I read that the charges included claims that the defendants "laundered money through scores of United States and foreign corporations, partnerships, and bank accounts." (Manafort Indictment ¶ 1.)
It did not take long for people to note an initial mistake in the indictment. The indictment states that Yulia Tymoshenko was the president of the Ukraine prior to Viktor Yanukovych. (Id. ¶ 22.) But, Dan Abrams' Law Newz notes, "Tymoshenko has never been the president of the Ukraine. She ran in the Ukrainian presidential election against Yanukoych in 2010 and came in second. Tymoshenko ran again in 2014 and came in second then, too." Abrams continues:
The Tymoshenko flub is a massive error of fact, but it doesn’t impinge much–if any–on the narrative contained in the indictment itself. The error doesn’t really bear upon the background facts related to Manafort’s and Gates’ alleged crimes. The error also doesn’t bear whatsoever upon the laws Manafort and Gates are accused of breaking. Rather, it’s an error which bears upon the credibility of the team now seeking to prosecute the men named in the indictment.
Perhaps. It is a high-profile mistake, but it doesn't go to the core of the charges, so I think this may overstate it a bit. Still, it is hardly ideal, and it's definitely an unforced error. And unfortunately, there is a second such error.
Paragraph 12 of the indictment provides a chart of entities that were "owned or controlled" by the defendants. The chart headings provide "Entity Name," "Date Created," and "Incorporation Location." But a number of the entities are not corporations. They are LLCs, and you do not "incorporate" an LLC. You form an LLC. (Also, just to be clear, LLCs are not "partnerships," either. They are LLCs.)
Similar to the Tymoshenko error, the type of entity does not appear to impact the underlying narrative or charges. For example, entity type does not appear to impact the "conspiracy to launder money" count. And other jurisdictions, such as Cyprus, do tend to merge the corporate concept with the company concepts in a way that might make the chart headings less wrong than it is for U.S. entities. Nonetheless, it would not have been that hard to go with "Entity Origin" or "Formation Location."
Okay, so all of this is rather nitpicky, and I get that. The underlying charges are serious, and I hope and expect that the charges and the surrounding facts (not these mistakes) will be the focus of the legal process as it runs its course. But, it is also proper, I think, to work toward getting the entire document right. Details matter, and at some point could mean the difference between winning and losing, even if that does not appear to be the case this time around.
Wednesday, September 20, 2017
Friend of the blog and South Texas College of Law (Houston) Professor Joe Leahy sent over the following post he authored. It is cross-posted at UberLaw.Net and Medium. Embarrassingly, I had not heard about Loftium before reading this post, though at least I know of and have used Airbnb. Joe has some interesting thoughts, and I am happy to include his post on this blog.
Loftium will provide prospective homebuyers with up to $50,000 for a down payment, as long as they are willing to continuously list an extra bedroom on Airbnb for one to three years and share most of the income with Loftium over that time.
At first glance, the arrangement between Loftium and participating homebuyers might sound like a loan. (Indeed, the Times even describes it as such in an infographic.) But upon a closer look, the arrangement that Loftium contemplates with homebuyers clearly is not a loan. First of all, Loftium says it is not a loan; rather, according to Loftium, the down payment assistance it provides to homebuyers is “a part of a services agreement” lasting 12-36 months. Second, and more important, the arrangement between Loftium and homebuyers has none of the characteristics of a traditional (term) loan. There is no “principal” amount that the homebuyer is required to repay in a set period of time, and Loftium does not charge the homeowner any “interest.” In fact, the homebuyer is not required to make anypayments to Loftium in return for the company’s cash (unless the homeowner breaches the parties’ agreement and stops renting on Airbnb before the term expires).
All the homebuyer must do in exchange for Loftium’s money is (1) list her spare room on Airbnb continuously through the term of her agreement with Loftium, (2) be a decent host (i.e., “not be rude to guests”) and (3) split her Airbnb rental revenue with Loftium (with two-thirds going to the company.) If, at the end of the term, Loftium has not been repaid its initial investment, the homeowner is not required to repay Loftium’s initial contribution. Hence, if renting out the homeowner’s spare room is not profitable during the term of the parties’ agreement, “Loftium takes full responsibility for that loss.”
Of course, Loftium expects that the total income from renting out a homeowner’s spare room will greatly exceed the amount that it originally provided to the homebuyer, so that both will profit. If Loftium makes more in rental income than it pays towards the homeowner’s down payment, Loftium will make a profit.
Further, by all appearances, there is no cap on Loftium’s potential profit is its business arrangement with homebuyers. In fact, Loftium makes clear that it wants to maximize the income that it splits with homebuyers: Loftium promises that it will work with them “to increase monthly bookings as much as possible, so both sides can benefit from the additional income.” To that end, Loftium provides homebuyers with some start-up supplies for their spare bedroom (and a keyless entry lock), access to advice and know-how regarding how to rent an Airbnb room, and online tools to help maximize their rental income.
So, if the business arrangement between Loftium and homeowners is not a loan, what is it? It is almost certainly a general partnership for a term (i.e., a “joint venture”).
[Post continues after the page break]
Tuesday, May 2, 2017
It's exam-grading time, so my focus is largely on that. I did do my usual peruse of the news, though, and I found a whole host of news outlets discussing President Trump's tax plan, which proposes to lower income tax rates on pass-through entities. As one of the pieces explains:
Pass-through income, for those of you who aren’t tax nerds, is business income that’s reported on a personal return. It comes from partnerships, limited-liability corporations and other closely held businesses, including Trump’s own family real estate operation.
First of all, knowing about pass-through income does not make you a tax nerd. I don't think.
Beyond that, though, limited liability corporations are not a thing. And, limited liability companies (LLCs) are generally chosen for pass-though tax status, but they don't have to be. They can chose to be taxed as C corporations at the federal level, if they wish. Furthermore, partnerships, such as MLPs, and LLCs don't have to be closely held. They can be publicly traded.
Multiple outlets got on the incorrect"limited-liability corporations" bandwagon. Even Barron's! Oh, well.. For now, I guess I will just continue to note that LLCs are still limited liability companies.
Happy grading to those in the same boat, and good thoughts to the students taking our exams. We really do want you to succeed, so please, show us what you know.
Tuesday, February 14, 2017
I hope this Valentine's Day is a good one for you, dear readers. Mine started with a random (minor) dog bite on my morning run, followed by some time with some very nice health care professionals and quite a few less pleasant needles.
A friend alerted me to the law-related Twitter hashtag #AppellateValentines. Some of them are quite funny. See, e.g.,
Your wish is my mandamus. #AppellateValentines— Emil J. Kiehne (@EmilKiehne) February 14, 2017
There is also a #BusinessValentines hashtag, which is less creative, but has its moments. Of course, there was no #BusinessLawValentines, but there should be and there is now. I went first. Join in, if you're so inclined.
Even if we lived in Delaware, I'd never disclaim my duty of loyalty to you #BusinessLawValentines— Joshua Fershee (@jfershee) February 14, 2017
If you loved me back, we could be Citizens United #BusinessLawValentines— Joshua Fershee (@jfershee) February 14, 2017
And, of course, I could not resist:
Tuesday, January 17, 2017
Here we go again. The Oregon Federal District Court has a rule with an incorrect reference to LLCs on the books:
In diversity actions, any party that is a limited liability corporation (L.L.C.), a limited liability partnership (L.L.P.), or a partnership must, in the disclosure statement required by Fed. R. Civ. P. 7.1, list those states from which the owners/members/partners of the L.L.C., L.L.P., or partnership are citizens. If any owner/member/partner of the L.L.C., L.L.P., or partnership is another L.L.C., L.L.P., or partnership, then the disclosure statement must also list those states from which the owners/members/partners of the L.L.C., L.L.P., or partnership are citizens.
The certification requirements of LR 7.1-1 are broader than those established in Fed. R. Civ. P. 7.1. The Ninth Circuit has held that, “[L]ike a partnership, an LLC is a citizen of every state of which its owners/members/partners are citizens.” Johnson v. Columbia Properties Anchorage, LP, 437 F.3d 894, 899 (9th Cir. 2006). Early state citizenship disclosure will help address jurisdictional issues. Therefore, the disclosure must identify each and every state for which any owner/member/partner is a citizen. The disclosure does not need to include names of any owner/member/partner, nor does it need to indicate the number of owners/members/partners from any particular state.
For federal law purposes, it appears that the rule has excluded LLCs, despite the intent (and likely specific purpose) of the rule. Interestingly, Oregon law, has extended "unless context requires otherwise" the concept of LLCs to apply to partnership and corporate law. Oregon law provides:
Unless the context otherwise requires, throughout Oregon Revised Statutes:
(1) Wherever the term “person” is defined to include both a corporation and a partnership, the term “person” shall also include a limited liability company.(2) Wherever a section of Oregon Revised Statutes applies to both “partners” and “directors,” the section shall also apply:(a) In a limited liability company with one or more managers, to the managers of the limited liability company.(b) In a limited liability company without managers, to the members of the limited liability company.(3) Wherever a section of Oregon Revised Statutes applies to both “partners” and “shareholders,” the section shall also apply to members of a limited liability company.
Tuesday, January 3, 2017
Today is my annual check-up on the use of "limited liability corporation" in place of the correct “limited liability company.” I did a similar review last year about this time, and revisiting the same search led to remarkable consistency. This is disappointing in that I am hoping for improvement, but at least it is not getting notably worse.
Since January 1, 2016, Westlaw reports the following using the phrase "limited liability corporation":
- Cases: 363 (last year was 381)
- Trial Court Orders: 99 (last year was 93)
- Administrative Decisions & Guidance: 172 (last year was 169)
- Secondary Sources: 1116 (last year was 1071)
- Proposed & Enacted Legislation: 148 (last year was 169)
As was the case last year, I am most distressed by the legislative uses of the phrase, because codifying the use of "limited liability corporation" makes this situation far murkier than a court making the mistake in a particular application.
New York, for example, passed the following legislation:
Section 1. Subject to the provisions of this act, the commissioner of parks and recreation of the city of New York is hereby authorized to enter into an agreement with the Kids' Powerhouse Discovery Center Limited Liability Corporation for the maintenance and operation of a children's program known as the Bronx Children's Museum on the second floor of building J, as such building is presently constructed and situated, in Mill Pond Park in the borough of the Bronx. The terms of the agreement may allow the placement of signs identifying the museum.
NY LEGIS 168 (2016), 2016 Sess. Law News of N.Y. Ch. 168 (S. 5859-B) (McKINNEY'S).
This creates a bit of a problem, as Kids' Powerhouse Discovery Center Limited Liability Corporation does not exist. The official name of the entity is as Kids' Powerhouse Discovery Center LLC and it is, according to state records, an LLC (not a corporation). Does this mean the LLC will have to re-form as a corporation so that the commissioner of parks and recreation has authority to act? It would seem so. On the one hand, it could be deemed an oversight, but New York law, like other states, makes clear that an LLC and a corporation are distinct entities.
Several other states enacted legislation using “limited liability corporation” in contexts that clearly intended to mean LLCs. Hawaii, West Virginia (sigh), Minnesota, Alabama, California, and Rhode Island were also culprits.
There was one bit of federal legislation, too. The “Communities Helping Invest through Property and Improvements Needed for Veterans Act of 2016” or the “CHIP IN for Vets Act of 2016." PL 114-294, December 16, 2016, 130 Stat. 1504. This act authorizes the Secretary of Veterans Affairs to carry out a pilot program in which donations of certain property (real and facility construction) donated by the following entities:
(A) A State or local authority.
(B) An organization that is described in section 501(c)(3) of the Internal Revenue Code of 1986 and is exempt from taxation under section 501(a) of such Code.
(C) A limited liability corporation.
(D) A private entity.
(E) A donor or donor group.
(F) Any other non-Federal Government entity.
I have to admit, it is not at all clear to me why one needs any version of (C) if one has (D) as an option. Nonetheless, to the extent it was not intended to be redundant of (D), part (C) would appear to be incorrect.
I addition, I'd be remiss not to note the increase to 1116 uses in secondary sources last year, though only 43 were in law reviews and journals. That part is, at least a little, encouraging.
Last year, I wished “everyone a happy and healthy New Year that is entirely free of LLCs being called ‘limited liability corporations.’” This year, I have learned to temper my expectations. I still wish everyone a happy and healthy New Year, but as to the use of “limited liability corporations” I am hoping to reduce the uses by half in all settings for 2017, and I hope at least three legislatures will fix errors in their existing statutes. That seems more reasonable, if not any more likely.
Wednesday, November 2, 2016
General Electric (GE) and Baker Hughes (BHI) announced on Monday, October 31st, a proposed merger to combine their oil and gas operations. GE and Baker Hughes will form a partnership, which will own a publicly-traded company. GE shareholders will own 62.5% of the "new" partnership, while Baker Hughes shareholders will own 37.5% and receive a one-time cash dividend of $17.50 per share. The new company will have 9 board of director seats: 5 from GE and 4 from Baker Hughes. GE CEO Jeff Immelt will be the chairman of the new company and Lorenzo Simonelli, CEO of GE Oil & Gas, will be CEO. Baker Hughes CEO Martin Craighead will be vice chairman.
Reuters is describing the business synergies between the two companies as leveraging GE's oilfield equipment manufacturing ("supplying blowout preventers, pumps and compressors used in exploration and production") and data process services with Baker Hughes' expertise in " horizontal drilling, chemicals used to frack and other services key to oil production."
Baker Hughes had previously proposed a merger with Halliburton (HAL), which failed in May, 2016, after the Justice Department filed an antitrust suit to block the merger. Early analysis suggests that the proposed GE & Baker Hughes will pass regulatory scrutiny because of the limited business overlap of GE and Baker Hughes.
As I plan to tell my corporations students later today: this is real life! A high-profile, late-semester merger of two public companies is a wonderful gift. The proposed GE/Baker Hughes merger illustrates, in real life, concepts we have been discussing (or will be soon) like partnerships, the proxy process, special shareholder meetings, SEC filings, abstain or disclose rules, and, of course, mergers.
Wednesday, September 28, 2016
On Monday, Doug Moll posted a great question about RUPA 404(e), which also got some great comments. I started to write a reply comment, but it got so long, I though it worked better as a separate post. Doug asks the following (whole post here):
Under the “cabining in” language of RUPA (1997), the action has to fit within § 404(b) to be considered a breach of the duty of loyalty. Section 404(b)(1) prevents the “appropriation of a partnership opportunity.” When a partner attempts to block the partnership from taking an opportunity to protect the partner’s own related business, can it be argued that the partner is, at least indirectly, seeking to appropriate the opportunity for himself?
Alternatively, might the partner’s vote violate the § 404(b)(3) obligation to “refrain from competing with the partnership”?
Here's where I come out it:
As I think about it, I am with Frank Snyder's comment that "a partner is entitled to pursue her own interests in voting her partnership interest, unless there's some agreement to the contrary." I also think, though, that § 404(e) sanctions self-interested votes, subject to “the obligation of good faith and fair dealing” required under § 404(d).
So, I am not that troubled by the example from the comments that Doug cites, though I see where his concern comes from. To repeat the comment:
For example, a partner who, with consent, owns a shopping center may, under subsection (e), legitimately vote against a proposal by the partnership to open a competing shopping center.
First, because it’s clear that the partner first got consent to own the shopping center, the partner is not competing with the partnership, as I see it. Actually, the partnership wants to compete with the existing center, which one partner owns with consent of the partnership. As such, because of the consent, I don’t think § 404(b)(3) is a concern here. Section 404(e) says a self-interested vote is permissible, so the question is whether such a vote is consistent with the obligation of good faith and fair dealing from § 404(d).
Given that the partnership consented to ownership of the shopping center, it seems that the rest of the partnership would reasonably expect that the partner would not be excited to create a competitive shopping center. With this knowledge on both sides, it seems to me that casting a vote against a new shopping center can occur in good faith and mean the partner dealt fairly. The rest of the partnership can still proceed with the plan if they have enough votes under the partnership agreement, and if not (e.g., unanimous vote was needed), too bad.
Even without disclosure and consent, this might be permissible. Suppose existing partnership A owns a car dealership. The dealership was a Pontiac, Oldsmobile, and Saturn, dealer, and they are done and new use for the property will be needed. Suppose that one of the partners also owns a shopping center with another group of people, as part of partnership B. Should that partner be precluded from voting against converting the dealership in partnership A to a shopping center? I don’t think so.
In addition, Gottacker v. Monnier, 697 N.W.2d 436 (Wis. 2005) provides an interesting LLC parallel to this situation. Under the Wisconsin LLC act, the court says:
We determine that the WLLCL does not preclude members with a material conflict of interest from voting their ownership interest with respect to a given matter. Rather, it prohibits members with a material conflict of interest from acting in a manner that constitutes a willful failure to deal fairly with the LLC or its other members. We interpret this requirement to mean that members with a material conflict of interest may not willfully act or fail to act in a manner that will have the effect of injuring the LLC or its other members. This inquiry contemplates both the conduct along with the end result, which we view as intertwined. The inquiry also contemplates a determination of the purpose of the LLC and the justified expectations of the parties.
Id. ¶ 31. In that case, two members effectively transferred property from one entity to another, leaving a third member out. There was no question they were conflicted in their votes, but the test was not whether they could act vote in a conflicted manner (as they did). Instead, the question was whether they dealt fairly and in good faith, which had to be decided on remand (the court said they did). In assessing whether the entity or other members are injured, then, as long at the voting was done consistent with the organizing agreement, I think the test is whether the partner in question is getting something unfairly to the detriment of the other members.
Lastly, to Doug's example, in the comments to his post, he said: “[W]hen I vote to, for example, block the partnership from raising the rent on a property that I originally leased several years ago from the partnership (and with the partnership's permission), it is hard for me to understand why that vote should not be considered a breach of duty.” It seems to me that should not be a breach of fiduciary duty unless it violates some express agreement to the contrary.
There can be good faith and fair dealing under § 404(d) in such a case, and the partnership agreed to the terms up front. The question to me is simply, what kind of vote is needed to raise the rent? Again, if it requires unanimous consent, that’s the partnership’s problem. They could have changed that when they originally agree to the deal. If it’s majority vote, the other partners can change the rent despite the conflicted partner's no vote. I see no need to protect this kind of transaction with mandatory fiduciary duties. There’s not a disclosure or fair dealing problem to me, so I would sanction it, and I think that's the specific intent of § 404(e).
I admit, I am sometimes amazed at how much of a contractarian I have become.
Tuesday, September 6, 2016
Private Ordering in the Uncorporation: Modified and Eliminated Fiduciary Duties Are Often the Same Thing
What does it mean to opt out of fiduciary duties? In follow-up to my co-blogger Joan Heminway's post, Limited Partnership Law: Should Tennessee Follow Delaware's Lead On Fiduciary Duty Private Ordering?, I will go a step further and say all states should follow Delaware's lead on private ordering for non-publicly traded unincorporated business associations.
Here's why: At formation, I think all duties between promoters of an unincorporated business association (i.e., not a corporation) are always, to some degree, defined at formation. This is different than the majority of other agency relationships where the expectations of the relationship are more ingrained and less negotiated (think employee-employer relationship).
As such, I'd make fiduciary duties a fundamental right by statute that can be dropped (expressly) by those forming the entity. I'd put an additional limit on the ability to drop fiduciary duties: the duties can only be dropped after formation if expressly stated in formation documents (or agreed unanimously later). That is, if you didn't opt out at formation, tell all those who could potentially join the entity how you can change fiduciary duties later. This helps limit some (though not all) freeze-out options, and I think it would encourage investors to check the entity documents closely (as they should).
At formation, the concerns we might have of, for example, an employee without fiduciary duties, are not the same as they are for co-venturers. Those starting an entity have long negotiated what is a breach of the duty of loyalty, for example. In contrast, I think fiduciary duties in most employer-employee (and similar) relationships reflect the majoritarian default and they facilitate the relationship existing at all. For LLCs and partnership entities, I think that's less clear. Entity formation is relatively rare compared to how often we enter other agency relationships, and they almost always involve significant negotiation (if not planning). And if they don't, the rules we expect traditionally should be the default. But where the parties talk about it, and they usually do, allowing a more robust sense of freedom of contract has value.
Even in Delaware, where one can negotiate out of fiduciary duties, there remains the duty of good faith and fair dealing. I think of that as meaning that the parties still have a right to the essence of the contract. That is, the contract has to mean something. It has to have had a purpose and potential value at formation, and no party can eliminate that. But, the parties only have a right to what was bargained for. As such, what we might traditionally consider a breach of the duty of loyalty could also breach the duty of good faith and fair dealing, but a traditional breach of the duty of loyalty might not be sufficient to find liability where there is expressly no duty of loyalty. Instead, the act must so contradict the purpose of the contract that it rises to the level of a breach the duty of good faith and fair dealing.
Part of the reason I support this option is that I think case law has already validated it, but in such an inartful manner that it confuses existing doctrine. See, e.g., McConnell v. Hunt Sports Enterprises, 132 Ohio App. 3d 657, 725 N.E.2d 1193 (Ct. App. 1999) (“An LLC, like a partnership, involves a fiduciary relationship. Normally, the presence of such a relationship would preclude direct competition between members of the company. However, here we have an operating agreement that by its very terms allows members to compete with the business of the company.”).
In closing, I will note that I am all for express provisions that require investors to pay attention at the outset. I don't believe in helping cheaters hide the ball. I just think law that encourages investors and others joining new ventures to pay attention is useful and will provide long-term value to entities. I don't think that eliminated fiduciary duties at formation raise any more of a risk than we already have with limited or modified fiduciary duties at formation. With the more limited protections described above, freedom of contract should reign.
Monday, September 5, 2016
Limited Partnership Law: Should Tennessee Follow Delaware's Lead On Fiduciary Duty Private Ordering?
I originally was going to write about overconfidence today. But I will reserve that post for a later date. Instead, for today, I am sharing with you a Tennessee legislative drafting issue on which my voice (together with the voices of others) has been solicited and asking for your views and comments.
A committee of the Tennessee Bar Association has been working on proposed revisions to the Tennessee Revised Uniform Limited Partnership Act. Several thorny issues remain for consideration and final decision making, among them, whether Tennessee law, like Delaware limited partnership and limited liability company law, should allow for the elimination of general partner fiduciary duties. The committee soon will be voting on this issue, and we are circulating among us our current views (having earlier debated the matter in telephone conference calls). I took a shot at writing down my views for the group and circulated them last night. I am including the main substantive part of what I wrote here, minus some typos that I caught after the message was sent (and please forgive the disfluencies in places), and requesting comments from you:
Monday, August 29, 2016
Wednesday, July 27, 2016
Just in case you haven't gotten the message yet: Delaware law means fiduciary duty freedom of contract for alternative entities. In May 2016, the Delaware Chancery Court upheld a waiver of fiduciary duties in a master limited partnership. In Employees Retirement System of the City of St. Louis v. TC Pipelines GP, Inc., Vice Chancellor Glasscock upheld challenges to an interested transaction (sale of a pipeline asset to an affiliated entity) that was reviewed, according to the partnership agreement, by a special committee and found to be fair and reasonable. The waiver has been described as "ironclad" to give you a sense of how straight forward this decision was. No close call here.
Vice Chancellor Glasscock's letter opinion starts:
Delaware alternative entity law is explicitly contractual;1 it allows parties to eschew a corporate-style suite of fiduciary duties and rights, and instead to provide for modified versions of such duties and rights—or none at all—by contract. This custom approach can be value enhancing, but only if the parties are held to their bargain. Where equity holders in such entities have provided for such a custom menu of rights and duties by unambiguous contract language, that language must control judicial review of entity transactions, subject only to the cautious application of the implied covenant of good faith and fair dealing. Such is the case in the instant matter, which involves a master limited partnership (“MLP”) created with interested transactions involving the general partner as part of its business model.....
The Defendants point out that the [transaction] was approved by a special committee (the “Conflicts Committee”), which approval, in accordance with the partnership agreement, creates a conclusive presumption that the transaction is fair and reasonable to the Partnership. I find that the Conflicts Committee’s approval, in these circumstances, precludes judicial scrutiny of the substance of the transaction and grant the Defendants’ Motion.
Importantly, the contractual safe harbor for interested transactions established a process which, if followed, created a fair and reasonable transaction outside of judicial scrutiny and without recourse by the other partners. The court found that the partnership agreement precluded a good faith analysis of the Conflicts Committee's review and limited the court's review purely to matters of process.
The relevant portions of the Special Approval provision, importantly, are silent as to good faith.....According to the contractual language, the Special Approval of a duly constituted and fully informed Conflicts Committee is conclusive evidence that such transaction is fair and reasonable, and such approval is, therefore, preclusive of further judicial review. The Plaintiff does not allege that the Conflicts Committee was not duly constituted—that is, directors who are neither security holders nor employees or officers of the General Partner or its affiliates. Nor does the Plaintiff allege that the Conflicts Committee was not fully informed. Thus, the approval here is conclusive that the [transaction] is “fair and reasonable” to TCP. According to the explicit language of the LPA, when a conflicted transaction is deemed “fair and reasonable” by the terms of the agreement, such conflicted transaction is incapable of breaching the LPA.
Get the message? LOUD and CLEAR!
The opinion contains more analysis and excerpts of the relevant portions of partnership agreement. Look for an excerpt on this case in my ChartaCourse (electronic platform) Business Organizations casebook.
Monday, June 13, 2016
This past week, I completed the second leg of my June Scholarship and Teaching Tour. My time at "Method in the Madness: The Art and Science of Teaching Transactional Law and Skills" at Emory University School of Law last week was two days well spent. I had a great time talking to attendees about my bylaw drafting module for our transaction simulation course, Representing Enterprises, and listening to others talk about their transactional law and skills teaching. Great stuff.
This week's portion of my academic tour begins with a teaching whistle-stop at the Nashville School of Law on Friday, continues with attendance (with my husband) at a former student's wedding in Nashville on Saturday evening, and ends (my husband and I hope) with Sunday brunch out with our son (and his girlfriend if she is available). Specifically, on Friday, I teach BARBRI for four hours in a live lecture. The topics? Well, I drew a short straw on that. I teach agency, unincorporated business associations (including a bit about both extant limited liability statutes in Tennessee), and personal property--all in four hours. Ugh. Although I am paid for the lecture and my expenses are covered, I would not have taken (and would not continue to take) this gig if I didn't believe that I could be of some help to students. These topics--especially agency and partnership law, but also personal property--often are tested on the bar exam. So, on I press.
I also am completing work this week on the draft article that I will present in Chicago and Seattle on the last two stops of my tour. I will say more about that article in next week's post. In the mean time, let me know if you have any suggestions (or good jokes) on the law of agency, partnerships, LLCs, or personal property (e.g., tenancies, gifts, bailments, adverse possession, replevin) for my lecture on Friday . . . . It's so hard to make these speed-lectures somewhat engaging for the students. [sigh]
Wednesday, May 18, 2016
California is the back on my short list for the state's inability to successfully differentiate between corporations and limited liability companies (LLCs). Last week, an "unpublished/noncitable" decision that was published on Westlaw provided a good example.
The opinion states:
A corporation—including a limited liability corporation—may be served by effecting service on its agent for service of process. (Code Civ. Proc., § 416.10, subd. (a); see also Corp.Code, § 17701.16, subd. (a) [allowing service on limited liability corporations under Code Civ. Proc., § 413.10 et seq.].)7
*12 One of the ways a limited liability corporation can be served is by substituted service. (1 Weil & Brown, Cal. Practice Guide: Civil Procedure Before Trial (The Rutter Group 2015) ¶ 4:172, p. 4–26.) This requires that a copy of the summons and complaint be left at the office of the person to be served (or, in some cases, at the mailing address of the person to be served), in the presence of a person who is apparently in charge, “and by thereafter mailing a copy of the summons and complaint by first-class mail, postage prepaid to the person to be served at the place where a copy of the summons and complaint were left.” (Code Civ. Proc., § 415.20, subd. (a).)
No, no, no. First, even in California, an LLC is a "limited liability company." It says so right in the act. Cal. Corp. Code § 17701.01 (West) ("This title may be cited as the California Revised Uniform Limited Liability Company Act.").
And, yet, I have to admit, if you note the cite to the LLC act, California lawmakers have made this less clear than in other states. Yes, that's right. In California, the LLC Act is part of the California Corporations Code. Cal. Corp. Code §§ 17701.16 - 17713.13 (West). For that matter, so are partnerships, under Title 2. Sigh.
Would it be so terrible if the Corporations Code were called what it is: the Business Entities Code? As currently structured, LLCs and partnerships are arguably types of corporations under California law, as the above cases suggests. One could argue the headings don't change the meaning or intent of the laws. See Cal. Corp. Code § 6 (West) ("Title, division, part, chapter, article, and section headings contained herein do not in any manner affect the scope, meaning, or intent of the provisions of this code."). The problem with that is that the code text says otherwise: "This act shall be known as the Corporations Code." Cal. Corp. Code § 1 (West).
To reinforce that notion, the Code Commission notes from the 2014 main volume explain:
This code was listed in the appendices of Code Commission reports showing code classification as the “Corporations, Partnerships, and Associations Code.” The 14 syllables of that title appear to make it impractical, but no shorter phrase indicative of the full subject-scope has been found. Therefore, resort has been had to the rhetorical device of synecdoche, and the entire code designated by the name of longest part.
I admit I had to look up synecdoche to be sure I was on the right track, but the term supports, I think, my point that California is treating LLCs and partnerships as corporations (or some subset thereof). See, for example, this explanation:
Synecdoche is a literary device in which a part of something represents the whole or it may use a whole to represent a part.
Synecdoche may also use larger groups to refer to smaller groups or vice versa. It may also call a thing by the name of the material it is made of or it may refer to a thing in a container or packing by the name of that container or packing.
Still, even if it were accurate to says LLCs and partnerships are "types" of corporations under the California code, one thing is still clear: an LLC is a limited liability company, which is, at a minimum, a specific type of "limited liability corporation."
I suppose I can see how "14 syllables" might be deemed "impractical," but not at the cost of imprecision. The "Business Entities" -- or even just "Entities" or "Associations" -- Code would seem like a better, more accurate, option.
Oh well. At least the court cited the part of the California code for service of an LLC. That much, they got right.