Skip to content
Salt.
Real estate · 🇺🇸 United StatesScenario

Standardising bookkeeping across a portfolio of SPV entities

Assets held in separate SPVs cannot be compared until they share one chart of accounts and one written capitalisation policy, because the same category of spend capitalised in one entity and expensed in another produces returns that differ for accounting reasons rather than operating ones. This is an illustrative example of how Salt approaches multi-entity property accounting, using a US operator with 14 SPVs as the profile.

Scenarioan illustrative example of how Salt approaches this problem. Not a description of a specific client engagement.

The business shape it describes: US real estate operator, 14 SPV entities.

Scenario covers
Multi-entity bookkeeping standardisation and investor reporting
Jurisdiction
United States
Sector
Real estate
The setup
  • Take a US real estate operator holding each property in its own SPV, several of them set up by different accountants at different times.
  • There is no way to compare operating performance between assets, and investor reporting is assembled by hand each quarter from fourteen different starting points.
What usually turns out to be wrong
  • Fourteen different charts of accounts, so no line item is comparable and the portfolio view is a manual mapping exercise repeated every quarter.
  • Capitalisation policy applied inconsistently. The same roof, boiler or fit-out spend is capitalised in some entities and expensed in others, which moves reported net operating income without anything happening on the property.
  • Intercompany funding between the holding entity and the SPVs recorded inconsistently, so several balances exist on one side only.
  • No consistent treatment of the split between land and building, or of what falls into each depreciable class, which affects both reported returns and the tax position.
How this would be worked
  • Standardise the chart of accounts across all entities, with the property-level detail that per-asset reporting actually needs rather than a generic template.
  • Write one capitalisation policy, including thresholds and the treatment of repairs versus improvements, and apply it consistently across every entity.
  • Restate where the previous treatment diverged from the new policy, so the comparison is like for like rather than partially corrected.
  • Introduce consistent intercompany treatment with a rule about which entity books first, then match balances before each close.
  • Build per-asset reporting that is generated from the ledger rather than assembled in a spreadsheet each quarter.
Why we'd be the right fit
  • Standardising entities built by different accountants means settling one capitalisation policy and then restating everything that departed from it, including figures investors have already been shown.
  • The mechanics are ordinary multi-entity work. Agreeing in advance that the restatement will be published is the part that decides whether the project gets finished.
What the business would be able to do
  • Asset-level performance would be comparable, so an underperforming property is visible as an operating problem rather than an accounting artefact.
  • Investor reporting would be generated from the ledger rather than assembled by hand each quarter.
  • Intercompany balances would agree, because they are matched before the close under a rule rather than reconciled afterwards.

What we'd flag

Standardising capitalisation policy changes reported returns on individual assets in both directions, and some of those figures have already been shown to investors. That conversation has to happen, and it is not a comfortable one.

Answers

Standardising bookkeeping across a portfolio of SPV entities

Start with a number

Recognise this shape in your own books?

Tell us where you trade and what shape the books are in. You get scope, price and a start date in writing within one business day — no obligation.

Get a quote