Most multi-property hotel portfolios are not structured as one legal entity. They are structured as a separate LLC per property, sometimes with a management company entity layered on top, for liability isolation and financing reasons. That structure is standard and usually correct, right up until Property A’s front desk pays a shared vendor invoice that actually belongs to Property B, or a regional manager’s expense report needs splitting across three entities she covers. At that point, there is a real question of who owes whom, and how it gets recorded so it does not just sit as an unresolved balance indefinitely. This is the actual mechanic behind intercompany due-to and due-from accounting, including the journal entries, not just the concept.
Why This Comes Up Constantly in Multi-LLC Portfolios
A few scenarios generate the bulk of intercompany activity in a typical portfolio: a shared vendor contract billed to one entity for administrative simplicity but belonging to multiple properties, an expense report from a team member covering work performed across several entities, a cash advance from the management company or a sister property to cover a short-term shortfall, and corporate-level cost allocations passed down to individual property entities under a management agreement. In every case, the paying entity has advanced money on behalf of another entity, and that needs to appear on both sets of books, not as an expense fully absorbed by the paying entity, and not as unrecorded cash movement that never reconciles.
The Core Mechanic: Due To / Due From Accounts
Each entity carries a Due From (Entity) account, an asset representing money owed to this entity by another, and a Due To (Entity) account, a liability representing money this entity owes to another, for every other entity it regularly transacts with. When one entity pays on behalf of another, the transaction is split at the point of entry, not reconciled after the fact.
Worked Example 1: Shared Vendor Invoice
Property A LLC receives and pays a $3,000 quarterly pest control invoice covering both Property A and Property B, split evenly.
At Property A LLC’s books:
| Account | Debit | Credit |
|---|---|---|
| Pest Control Expense (Property A's share) | $1,500 | |
| Due From Property B LLC | $1,500 | |
| Cash | $3,000 |
| Account | Debit | Credit |
|---|---|---|
| Pest Control Expense (Property B's share) | $1,500 | |
| Due To Property A LLC | $1,500 |
Property A’s books show it is owed $1,500 by Property B. Property B’s books show it owes $1,500 to Property A. Both entities have recorded their actual share of the expense, and the intercompany balance is explicit and traceable, rather than sitting inside an inflated expense line at Property A that never gets corrected.
Worked Example 2: Employee Reimbursement Split Across Properties
A regional engineer submits a $900 travel reimbursement: $400 of work performed at Property A, $500 at Property C. Property A LLC’s payroll system processes the reimbursement, since that is the engineer’s home entity.
At Property A LLC’s books:
| Account | Debit | Credit |
|---|---|---|
| Repairs and Maintenance Expense (Property A's share) | $400 | |
| Due From Property C LLC | $500 | |
| Cash | $900 |
At Property C LLC’s books:
Settling the Balance
Intercompany balances do not have to settle immediately. Many portfolios let Due To/Due From balances net out over a quarter through offsetting transactions. But when an entity does cut a check to settle up, for example Property B LLC settling its $1,500 balance to Property A, the entries look like this.
At the paying entity, Property B LLC:
| Account | Debit | Credit |
|---|---|---|
| Due To Property A LLC | $1,500 | |
| Cash | $1,500 |
| Account | Debit | Credit |
|---|---|---|
| Cash | $1,500 | |
| Due From Property B LLC | $1,500 |
Where This Breaks Down in Practice
The mechanics above are standard double-entry accounting, nothing exotic. What breaks down at real portfolio scale is tracking it consistently. Balances go stale when a Due From balance sits unreconciled for a year and nobody remembers which invoice it traces back to. Netting gets skipped when three entities each owe each other and, without a portfolio-wide view, three separate uncollected balances sit on three sets of books instead of netting down to what is actually owed. Allocation splits get inconsistent when the same shared invoice gets split 50/50 one quarter and by square footage the next, with no documented rule, making the history hard to audit later.
Why This Needs a Portfolio-Wide View
Each individual journal entry above is simple. The difficulty is that intercompany accounting only works cleanly when every entity’s books are visible from one place. Otherwise, the paying entity’s bookkeeper and the owing entity’s bookkeeper are relying on someone manually communicating what happened, entity by entity, invoice by invoice. At five, ten, or fifty properties under separate LLCs, that coordination is exactly where Due To/Due From balances stop reconciling and start accumulating as unexplained variance on the consolidated balance sheet. We built our intercompany reconciliation to record the offsetting entries automatically as shared costs, reimbursements, or advances touch more than one property, which pairs naturally with the standardized chart of accounts approach described in Standardizing a Chart of Accounts Across Hotel Brands and Property Types, since consistent account mapping is what makes cross-entity balances comparable in the first place.
For broader context on the financial reporting standards multi-entity hotel portfolios are typically measured against, HFTP and AHLA’s Global Finance Committee jointly maintain the Uniform System of Accounts for the Lodging Industry, which most owners and asset managers use as the common reference point for portfolio-wide comparability.
Summary Recap:
- Multi-LLC hotel portfolios generate intercompany activity constantly: shared vendor invoices, split reimbursements, cash advances, and allocated corporate costs.
- Due To/Due From accounts record each entity’s real share of a shared cost at the point of entry, rather than absorbing it fully into one entity’s books.
- Balances can net out over time, but only if they are tracked consistently. Stale balances, skipped netting, and inconsistent allocation splits are where this breaks down at scale.
- A portfolio-wide view of every entity’s books is what keeps Due To/Due From balances reconciled instead of accumulating as unexplained variance.
Ready to see this in your own portfolio?
Schedule time with our team to walk through how Docyt applies this to your properties. Schedule a consultation with Docyt
