Piercing the Corporate Veil — the Boundary Is a Conclusion, Not a Filing

The last three pages have been building toward a caveat that keeps appearing and has not yet been explained: a separation protects you to the extent it is real. This page is that sentence, unpacked.

Start with what the veil actually is. "Piercing the corporate veil" is the traditional shorthand — grown up around corporations, applied to LLCs by borrowed principle in many states — for the circumstances in which a court disregards an entity's liability boundary and reaches an owner personally. The "veil" is that boundary: the property sits in the LLC, so a claim arising at the property is directed at the entity that owns it rather than automatically at everything you own.

And here is the framing that matters, because most people have it backwards: the boundary is a legal conclusion, not a permanent fact. Formation establishes the entity and its statutory liability framework. Whether a particular liability is actually limited depends on governing law, the cause of action, your own conduct, any guarantees you signed, and the facts of how the entity was run. Operating it as genuinely separate is what builds the evidence supporting the boundary if it is ever challenged. "I have an LLC" is the beginning of the argument, not the end of it.

What can lead a court to set it aside. The tests are state-specific and multi-factor, drawn from each state's statutes and case law rather than one national rule, and the weight given to each factor varies. Depending on the jurisdiction, courts may consider commingling of funds, misuse of the entity, inadequate capitalization, failure to keep records or maintain legally required separateness, and whether the entity functioned as the owner's alter ego. Some states expressly decline to treat particular LLC formalities as veil factors where those formalities were not required by law or by the entity's own documents.

Hold that framing precisely, because this is exactly where fear-based advice overreaches. Genuine separateness supports the boundary and reduces alter-ego risk; a pattern of poor separateness can support a court's decision to disregard the entity. It is not an equation where a fixed amount of paperwork buys a fixed amount of protection. No single lapse is a universal trigger, and a missing formality is not automatically fatal. What matters is the overall pattern and the evidence it leaves, read under your state's law.

Commingling is the clearest signal, and it is where rentals fail. Running personal and entity money through the same account is the most legible sign that the owner and the entity were not treated as financially separate. And it is easy to fall into. Which brings us to the four questions that decide this in practice for a rental — none of which is exotic, and all of which are settled in an afternoon.

Where does the rent land? In a long-term rental this is usually one recurring deposit a month, and it goes wherever you told the tenant or the property manager to send it. If the entity holds title and the rent is still arriving in your personal account, the entity never touches its own income. That single setup detail — the account number on the lease or on the property manager's owner-disbursement form — is often the difference between an entity that has a financial life and one that exists only on a filing. If you use a property manager, their statement pays out to one account; make it the entity's.

How are security deposits held? This is the discipline a long-term rental has and a short-term one does not, and it is worth taking seriously on its own terms: many states impose specific requirements on how a tenant's security deposit is held, sometimes in a separate or trust account, sometimes with interest, usually with deadlines and itemization rules for return. Those are legal obligations to your tenant regardless of any entity, so the money is not yours to mix in the first place. But notice what handling them properly also produces: identifiable funds, a documented purpose, and a record that the entity was operating like a business with obligations rather than as a pocket. The requirements vary meaningfully by state — check yours — and where you have them, they are separateness evidence you were required to create anyway.

Whose name is on the lease? If the LLC holds title, the LLC is the landlord, and the lease should say so — signed by you in your capacity for the entity rather than personally. A deed in the entity's name and a lease signed in yours is a direct contradiction in your own paperwork about who owns and operates the property. When title moves, the new leases and renewals should move with it, along with the notices, the deposit records, and the insurance.

Who pays the mortgage? On a financed rental the loan and the title can end up in different names, which is a real structural question with its own guide in this domain, and the mechanics belong there. For separateness purposes, the point is narrower: decide deliberately how the entity's obligations are funded and record it consistently, rather than paying whatever bill lands from whichever account is nearest. Money moving between you and the entity is not inherently a problem; money moving with no pattern, no documentation, and no distinction between the entity's obligations and yours is the pattern the doctrine is about.

Capitalization is the quiet one. An entity that owns a property and holds nothing else — no operating cushion, every dollar of rent swept out the day it arrives — may be argued to have been inadequately capitalized for what it was set up to do, in states where that is a factor. Keeping a reasonable operating balance in the entity is ordinary good practice for a rental anyway, since the entity is what pays for the water heater. It also happens to be the more defensible posture.

Finally, the crossover that confuses nearly everyone, and it is the reason this page follows the tax one. Being disregarded for federal income tax does not make separateness optional. Those are two different questions answered by two different bodies of law. The IRS looking through your single-member LLC for income-tax purposes says exactly nothing about whether a state court will respect the liability boundary. Owners sometimes reason that if the entity is "ignored" for taxes it must not be very real — and then run the property accordingly. It is real where it counts, and only if you treat it that way.

The honest summary. None of this is a safe harbor, and no one can promise you a boundary that holds. What you can do is make the true version of your situation the easy one to prove: the entity has its own account, its own records, its own leases, its own insurance, and enough money in it to meet its own obligations. That is not paperwork for its own sake. It is the difference between a boundary that is a conclusion a court can reach and a boundary that is a receipt from the Secretary of State.

Swipe to view the full figure →

The bottom line

The veil is not something the filing hands you and keeps handing you. Formation establishes the liability boundary; whether a court respects it, if it is ever challenged, can turn on whether the entity was operated as a genuinely separate thing — under state-specific, multi-factor standards where no single lapse decides the question and a missing formality is not automatically fatal. For a rental, the separateness questions are unglamorous and concrete: where the rent lands, how deposits are held, whose name is on the lease, how the entity's obligations get funded, and whether anything is left in it. Being disregarded for federal income tax changes none of that. Keep the boundary real and it is evidence; leave it on paper and it is a receipt.

About the author

Matt Nunn is the founder of Builders Finance. He has spent two decades working with the financial side of real estate businesses, and started Builders Finance to give short-term-rental operators the financial systems, frameworks, and plain-language education that most hosting advice skips over. Builders Finance publishes educational content for STR owners; it is not legal, tax, or investment advice, treatment depends on your facts and circumstances, and it is not a substitute for guidance from your own qualified professionals.

Continue learning

This resource provides general educational information about entity separateness and is not individualized legal advice. Veil-piercing and alter-ego standards are state-specific, multi-factor, and fact-dependent; security-deposit handling requirements vary by state; and none of the practices described is a safe harbor or a guarantee that a court will respect an entity's liability boundary. Work your own situation with your own attorney.

Primary sources (verified at draft; re-verify at publish): BFC Entity Structure P33 — keep the legal boundary real in practice, not just on paper — cited, not coined; the coining page is the deployed /library/guides/piercing-the-corporate-veil/, whose boundary-as-conclusion framing, state-specific multi-factor caution, no-single-lapse restraint and commingling teaching this page adapts for the long-term-rental niche. Of the four operating questions, one is inherent and three are NARROWED at consolidated review. Inherent: security-deposit handling — statutory trust or separate-account, interest, deadline and itemization duties are residential landlord-tenant law and do not attach to transient occupancy. Narrowed: where the rent lands is the antecedent's own commingling example almost verbatim ("the rent still lands in a personal account") — the LTR expression is only the control point, the account named on the lease or the manager's disbursement instruction; whose name is on the lease is generic contracts-in-the-entity's-name doctrine, of which the lease is a long-term rental's principal instance rather than a category the antecedent lacks; and who pays the mortgage is not niche-specific at all, since the corpus treats the mortgage/title interaction at length. Rev 1 also carried an invented causal clause — that a long-term rental's few large familiar transactions are why commingling happens — which cut against the source and is removed. The capitalization paragraph is adapted, not native — the antecedent lists inadequate capitalization as a factor; the sweep-to-zero framing is the LTR expression. Tax disregard (P28) is cited as a contrast and not re-taught; mortgage mechanics are routed to when-a-mortgage-meets-an-llc and not taught here; day-to-day bookkeeping mechanics are described as a discipline rather than routed to a page: the Bookkeeping & Reporting domain is planned and has no registry or contract entry, so no page in this batch may promise it. Veil factors, weights, formality requirements and security-deposit rules are deliberately unquantified and unlisted by state: jurisdictional, fact-dependent, and not evergreen. The restraint in the antecedent is doctrine, not tone — this page must not convert risk-and-evidence teaching into scare-tactic absolutes, and its hedges are load-bearing.