Debtor’s Use of LLC As ‘Personal Piggy Bank’ Leads to Turnover and Charging Orders

Golfwood Square, LLC v. O’Malley, 2018 IL App(1st) 172220-U, examines the interplay between a charging order and a third party citation to discover assets turnover order against an LLC member debtor.  The plaintiff in Golfwood engaged in a years’ long effort to unspool a judgment debtor’s multi-tiered business entity arrangement in the hopes of collecting a sizeable (about $1M) money judgment.

Through post-judgment proceedings, the plaintiff learned that the debtor owned a 90% interest in an LLC (Subsidiary or Sub-LLC) that was itself the sole member of another LLC (Parent LLC) that received about $225K from the sale of a Chicago condominium.

Plaintiff also discovered the defendant had unfettered access to Parent LLC’s bank account and had siphoned over $80K from it since the judgment date.

In 2013 and 2017, plaintiff respectively obtained a charging order against Sub-LLC and a turnover order against Parent LLC in which the plaintiff sought to attach the remaining condominium sale proceeds.  The issue confronting the court was whether a judgment creditor could get a turnover order against a parent company to enforce a prior charging order against a subsidiary entity.  In deciding for the creditor, the Court examined the content and purpose of citations to discover assets turnover orders and LLC charging orders.

Code Section 2-1402 empowers a judgment creditor can issue supplementary proceedings to discover whether a debtor is in possession of assets or whether a third party is holding assets of a debtor that can be applied to satisfy a judgment.

Section 30-20 of the Limited Liability Company Act allows that same judgment creditor to apply for a charging order against an LLC member’s distributional interest in a limited liability company. Once a charging order issues from the court, it becomes a lien (or “hold”) on the debtor’s distributional interest and requires the LLC to pay over to the charging order recipient all distributions that would otherwise be paid to the judgment debtor. 735 ILCS 5/2-1402; 805 ILCS 180/30-20. Importantly, a charging order applicant does not have to name the LLC(s) as a party defendant(s) since the holder of the charging order doesn’t gain membership or management rights  in the LLC. [⁋⁋ 22, 35]

Under Parent LLC’s operating agreement, once the condominium was sold, Parent LLC was to dissolve and distribute all assets directly to Sub-LLC – Parent’s lone member.  From there, any distributions from Sub-LLC should have gone to defendant (who held a 90% ownership interest in Sub-LLC) and then turned over to the plaintiff.

However, defendant circumvented the charging order by accessing the sale proceeds (held in Parent LLC’s account) and distributing them to himself. The Court noted that documents produced during post-judgment discovery showed that the defendant spent nearly $80,000 of the sale proceeds on his personal debts and to pay off his other business obligations.

Based on the debtor’s conduct in accessing and dissipating Parent LLC’s bank account with impunity, and preventing Parent LLC from distributing the assets to Sub-LLC, where they could be reached by plaintiff, the trial court ordered the debtor to turn all Parent LLC’s remaining account funds over to the plaintiff to enforce the earlier charging order against Sub-LLC.

The court rejected the defendant’s argument that Parent LLC was in serious debt and that the condo sale proceeds were needed to pay off its debts. The Court found this argument clashed with defendant’s deposition testimony where he stated under oath that Parent LLC “had no direct liabilities.” This judicial admission – a clear, unequivocal statement concerning a fact within a litigant’s knowledge – was binding on the defendant and prevented him from trying to contradict this testimony. The argument also fell short in light of defendant’s repeatedly raiding Parent LLC’s account to pay his personal debts and those of his other business ventures all to the exclusion of plaintiff.

The court then summarily dispensed with defendant’s claim that the plaintiff improperly pierced the corporate veils of Parent LLC and Sub-LLC in post-judgment proceedings. In Illinois, a judgment creditor typically cannot pierce a corporate veil in supplementary proceedings. Instead, it must file a new action in which it seeks piercing as a remedy for an underlying cause of action.

The Court found that the trial court’s turnover order did not hold defendant personally liable for either LLC’s debt. Instead, the turnover order required Parent LLC to turnover assets belonging to the judgment debtor – the remaining condominium sale proceeds – to the plaintiff creditor.

Afterwords:

This case presents in sharp relief the difficulty of collecting a judgment from a debtor who operates under a protective shield of several layers of corporate entities.

Where a debtor uses an LLC’s assets as his “personal piggy bank,” Golfwood and cases like it show that a court won’t hesitate to vindicate a creditor’s recovery right through use of a turnover and charging order.

The case is also noteworthy as it illustrates a court looking to an LLC operating agreement for textual support for its turnover order.

Apparent Agency Questions Defeat Summary Judgment in Guaranty Dispute – IL ND

The Northern District of Illinois recently examined the nature of apparent agency liability in the context of a breach of guaranty dispute involving related limited liability companies (LLCs).  The plaintiff in Hepp v. Ultra Green Energy Services, LLC, 2015 WL 1952685 (N.D.Ill. 2015) sued to enforce a written guaranty signed by the defendant company in connection with a $250K-plus promissory note signed by a company owned by the defendant’s managing member.

The court denied the plaintiff’s summary judgment motion.  It found there were material and triable fact issues as to whether the person signing the guaranty had legal authority to do so.

The court first addressed whether the guaranty was supported by consideration.  Consideration is “bargained-for exchange” where the promisor receives something of benefit (or the promisee suffers detriment) in exchange for the promise.  A guaranty’s boiler-plate provision that says “For Value Received” creates a presumption (but one that can be rebutted) of valid consideration.

Where the guaranty is signed at the same time as the underlying note, the consideration for the note transfers to the guaranty.  But where the guaranty is signed after the note, additional consideration (beyond the underlying loan) needs to flow to the guarantor.  A payee’s agreement to forbear from suing can be sufficient consideration.

Here, the plaintiff agreed to extend the deadline for repayment of the note by thirty days.  According to the court, this was sufficient consideration for the plaintiff to enforce the guaranty.  **3-4.

Next, the court shifted to its agency analysis and considered whether the LLC manager who signed the guaranty had authority to bind the LLC.  Answer – maybe not.

Apparent agency arises where (1) the principal or agent acts in a manner that would lead a reasonable person to believe the actor is an agent of the principal, (2) the principal knowingly acquiesces to the acts of the agent, and (3) the plaintiff reasonably relies on the acts of the purported agent.

When considering whether a plaintiff has shown apparent agency, the focus is on the acts of the principal (here, the LLC), and whether the principal took actions that could reasonably lead a third party to believe the agent is authorized to perform the act in question (here, signing the guaranty on the LLC’s behalf).

The scope of an apparent agent’s authority is determined by the authority that a reasonable person might believe the agent has based on the principal’s actions.  Also, a third party dealing with an agent has an obligation to verify the fact and extent of an agent’s authority.  **5-6.

The court found there material questions of disputed fact as to whether the plaintiff reasonably relied on the LLC manager’s representation that he had authority to sign the guaranty for the LLC.  The court noted that this was an unusual transaction that was beyond the ordinary course of the LLC’s business (since it implicated a possible conflict of interest (the manager who signed the guaranty was an officer of the corporate borrower) and it resulted in a pledge of the LLC’s assets), and culminated in the LLC taking on another $125,000 in debt in exchange for a short repayment time extension.  * 7.

The anomalous nature of the transaction coupled with the affidavit testimony of several LLC members who said they had no knowledge of the manager signing the guaranty, created too many unresolved facts to be decided on summary judgment.

Take-aways:

1/ A guaranty signed after the underlying note requires additional consideration running to the guarantor;

2/ Great care should go into drafting an Operating Agreement (OA).  Here, because the OA specifically catalogued numerous actions that required unanimous written consent of all members, the LLC defendant had ammunition to avoid the plaintiff’s summary judgment motion.

An Enigma Wrapped Inside A Conundrum: Suing the LLC in Federal Court – How Hard Can it Be?

maze

A limited liability company (LLC) is generally lauded as a flexible business entity that provides the limited liability of a corporation with the tax attributes of a partnership (flow-through, not double, taxation).

Flexibility is another oft-cited hallmark of the LLC form as its members can be one or more individuals, corporations, partnerships or even other LLCs. It’s common to see LLCs that have several other LLC members that are in turn comprised of (still more) LLC members.  With multiple layers of LLC members, tricky jurisdictional issues routinely abound.

When Federal subject matter jurisdiction is at stake, the question of whether a plaintiff can sue an LLC in Federal court quickly morphs from an academic, “fun” one, to an important strategic one.

Here are some useful bullet-points:

– A Federal district court has original subject matter jurisdiction over matters involving citizens of different states and the amount in controversy exceeds $75,000. 28 U.S.C. s. 1332(a)(1).

– There must be “complete diversity” between the parties: each plaintiff must be a citizen of a different state than each defendant.  The easily parroted rule becomes hard to apply the more parties are involved in a given lawsuit; especially where business entities are implicated in a case.

– A corporation is considered a citizen of the state where it has its principal place of business and where it is incorporated.  So, if Corporation X was incorporated in Texas but has its main office in Ohio, Corporation X would be considered a citizen of both Ohio and Texas.  28 U.S.C. s. 1332(c)(1).

– An LLC is considered a citizen of the state of its members;

– An LLC can have as members, partnerships, corporations and other entities;

– When an LLC has multiple members that have varied citizenships, a court must examine each member’s state of citizenship, as well as each member’s members’ citizenship, when determining whether it has jurisdiction over an LLC defendant.

A Case Illustration

Cumulus Radio Corp. v. Olson, 2015 WL 1110592, a case I’ve twice featured for its discussion of Federal TRO guidelines, illustrates the serpentine analytical framework involved with an LLC that’s made up of one or more LLC members.

There, the plaintiff broadcasting company was a Nevada corporation with its principal place of business in Georgia.  The defendant LLC was a Delaware-registered LLC based in Oregon.  The defendant LLC had but one member that happened to be another LLC.  That LLC (the sole member of the defendant LLC) had a single member – an individual who lived in Georgia.

Because the Delaware LLC’s sole member’s sole member was a Georgia resident, there was incomplete diversity between the plaintiff and defendant.  Normally, this would give the defendant a basis to move to dismiss the complaint for lack of subject matter jurisdiction.  The plaintiff would then have to sue the LLC defendant in state court in Delaware (where it was formed) Oregon (where it is based) or Georgia (where its member’s member lived).

While the court ultimately found that the Georgia resident wasn’t truly a member based on the LLC’s Operating Agreement, Cumulus provides a good illustration of the multi-layered jurisdictional analysis required with an LLC defendant that has several individual or business entity constituents.

Sources:

Hicklin Engineering LC v. Bartell, 439 F.3d 346 (7th Cir. 2006);

– 28 U.S.C. s. 1332(a), (c).

http://www.insidecounsel.com/2013/09/12/litigation-carefully-examine-the-layers-of-llc-cit (this is a good article from 2013 that lays out the applicable rules)