How many QuickBooks files does a multi-entity owner actually need?

Ask this question in any bookkeeping forum and you will get both answers with equal confidence: "one file, use classes for each entity" and "separate files always, one per LLC." The people telling you to cram everything into one file are usually trying to save you subscription money. The people telling you to separate everything are right about the accounting — and about to hand you a very real software bill.

Here is the honest version of both halves.

The floor: one set of books per taxpayer

Start with what is not optional. Entities that file their own tax return — an S-corp filing an 1120-S, a partnership filing a 1065 — each need books that stand alone. Their returns include balance sheets; owner basis, distributions, and intercompany balances are computed from those books; an examiner looks at that entity's ledger, not your consolidated view. Two taxpayers sharing one file means every report needs filtering, every filter can be forgotten, and one miscoded transaction quietly moves money between tax returns. Never do it.

Why separate books per entity was the right instinct

For your disregarded LLCs — single-member, no federal return of their own — the tax code technically lets you combine them into one file with a class per entity. Plenty of bookkeepers will tell you to stop there. But think about what each of those LLCs actually has to do in the real world:

• Face a lender. When the DSCR refi or the commercial banker asks for "entity financials," they mean that LLC's own P&L and balance sheet — not a class-filtered report where one unchecked box leaks another entity's numbers into the package.
• Hold up the liability wall. Your attorney put each property in its own LLC so a problem stays in one box. Commingled books are exactly what opposing counsel asks for when arguing the boxes were never real. Separate books are cheap evidence that the structure was respected.
• Be sellable. When you sell the property — or the entity — clean standalone books are the difference between a smooth diligence process and re-deriving three years of numbers from a shared file.
• Balance. A class-filtered P&L works passably; a class-filtered balance sheet mostly does not. If an entity carries a mortgage, holds a security deposit, or owes its sibling money, you want a real balance sheet that actually balances — per entity.

So the instinct behind "one file per LLC" was right all along. Each entity standing on its own books is the correct end state, not overkill.

The real problem: what doing it right costs

Here is where the traditional stack punishes correctness. On QuickBooks Online, "its own books" means its own subscription. Six entities at current prices is thousands of dollars a year — before payroll, before apps. And after paying six times, you still cannot answer the one question every owner actually asks: how did the whole portfolio do? There is no roll-up. Consolidation is you, stitching six P&Ls into a spreadsheet, every month, forever — or buying a seventh tool to do the stitching.

Worse, the files are blind to each other. When LLC #3 pays a bill for LLC #5, neither file knows the other exists — so the transfer gets categorized as an expense in one and income in the other, and both sets of books are quietly wrong.

That software bill — not the accounting — is why so many owners get talked into the one-file-with-classes compromise.

Two disciplines that matter regardless of software

Income follows title. Rental income belongs to whoever is on the deed. If the properties are deeded to you personally, that's your Schedule E income even if every dollar flows through your S-corp's bank account. An S-corp that manages properties it doesn't own should book a real, invoiced management fee — while rents and property expenses stay on the owner's books. "We just ran everything through the company" does not survive contact with a return preparer, a lender, or an exam, and unwinding three years of it costs far more than structuring it correctly on day one.

Due-to/due-from, reconciled monthly. Money moves between related entities constantly — covering a shortfall here, paying a shared bill there. Every one of those transfers lands in due-to/due-from accounts, not income or expense, and the pairs must mirror: Entity A's due-from-B against Entity B's due-to-A, to the penny, every month. Maintained, it's minutes. Neglected for a year, it's the most expensive part of any multi-entity cleanup — because you're reconstructing intent ("was that $5,000 a loan, a distribution, or a reimbursement?") and the owner is the only person who remembers. Usually they don't.

What this looks like when the software isn't the constraint

Disclosure: Woven is our product, and this exact squeeze — right structure, punishing price — is one of the reasons it exists.

In Woven, entities are first-class citizens under one roof. Every entity gets its own complete double-entry books with its own balance sheet — the standalone financials your lender, your preparer, and your attorney all want. Ownership links between entities drive the consolidated view: portfolio P&L, per-property columns, holding-company roll-ups, one click instead of a stitched spreadsheet. Intercompany transfers are recognized automatically and held so they post to both books or neither — no more orphaned halves. And it's priced like one platform, because it is one.

It was built by the owner of an accounting firm whose practice serves exactly these clients. If you're staying on QBO, the rules in this article still work — budget for a file per taxpayer at minimum, per entity ideally, and hold the line on the two disciplines above.

The short version

• Separate returns → separate books, always. That part is not negotiable.
• Separate books for every entity was the right instinct — lenders, liability, and sale-readiness all want standalone financials with real balance sheets.
• The obstacle was never the accounting; it's software that charges per entity and still can't show you the portfolio.
• Income follows title. Management activity bills a management fee.
• Every intercompany transfer hits due-to/due-from, and the pairs reconcile monthly.

If your structure is right but the books are tangled — or you're paying six subscriptions to stay compliant — [book a demo](/demo) and we'll show you what it looks like when every entity has its own books and the roll-up is built in.