Running expenses across multiple SPVs without a spreadsheet per entity

If your company's property portfolio has more than a few SPVs and you are using spreadsheets to track spend, you know it's no easy feat. Now, the "one spreadsheet per entity" model can work if you have multiple finance teams, each handling a handful of portfolios.

That said, in the real world, that is largely the case. If you are overseeing the spend management for a real estate group with even a moderate portfolio, you'll know this to be true.

This guide explains how to structure a multi-entity expense management system properly, and what to look for before investing in any such solution.

Why property groups end up with so many entities

Property groups end up with several entities as it's the best structure from the POV of administrative convenience. A separate entity or SPV for each building, development, investment, or joint venture allows for:

• Isolation of assets and liabilities
• Simplification of financing arrangements.
• Accommodating different investor groups' requirements.
• Keeping financial reporting specific to a single project or property.

A finance team may therefore find itself managing ten, twenty, or even fifty separate ledgers, bank accounts, statutory records, and audit files. Despite that, the operational spending often remains centralised.

That said, this isn't the primary challenge they face. It's maintaining a clear separation between them while still allowing finance to operate efficiently across the entire property group.

What breaks when spend runs across all of them

Most spend management issues stem from finance teams being unable to stay on top of entity ownership. Here are five ways these issues manifest.

The wrong entity pays the bill

A supplier invoice often relates to one SPV but gets paid by another because the finance team has access to a single banking platform or because payment is processed centrally. The issue now becomes determining whether the transaction should remain where it was paid or be recharged to the entity that actually incurred the expense.

Intercompany balances slowly drift apart

When the above scenarios happen repeatedly throughout the month, intercompany balances drift apart. This is because every shared payment creates two accounting entries, i.e an expense or receivable and the payable or recharge.  If either side gets this entry wrong or uses a different amount, or lists it in another accounting period, the balances stop matching.

One corporate card gets used across multiple SPVs

This is one of the most common operational issues in growing property groups. While it is easier administratively to issue fewer cards, one card ends up covering the spend for multiple entities. This creates a scenario where every transaction needs to be split manually before it can be booked correctly.

Every entity develops its own coding rules

As portfolios expand, different members of the finance team often begin coding similar expenses differently across entities. The financial statements may still balance, but comparing property performance becomes significantly more difficult because similar costs are no longer classified consistently.

Consolidation takes longer than it should

Multiple entities coding the same cost type five different ways now means that every entity's coding needs reviewing, intercompany balances require reconciliation, and shared costs need reallocating. What should be a straightforward month-end close process instead becomes a reconciliation project.

How to fix these issues from the ground up

There are three simple changes you can make to your spend management process that can help you address these issues from the ground up:

Implement a common chart of accounts

Implementing and enforcing a common chart of accounts ensures that the same cost type gets coded the same way regardless of which SPV it sits in.  Alaan's guide to setting up a chart of accounts covers how to structure one that scales across entities.

Apply entity coding at the point of spend

Develop a system of tagging a transaction to the correct entity the moment a spend happens. Doing so will eliminate the wrong-entity-pays problem and the inconsistent-coding problem at the source.

Enforce a single policy across SPVs

Enforcing one policy consistently across all the entities you manage will avoid the drift that happens when each SPV's finance handling quietly develops its own local rules over time.

How to perform Intercompany allocations without the spreadsheet

Intercompany allocations are unavoidable when multiple SPVs share people, suppliers, or services. That said, the task can still be performed efficiently like so:

1. Decide whether a cost should be allocated or recharged

Allocate a shared cost when several SPVs genuinely benefit from the same expense, such as group insurance, audit fees, or shared management costs. Alternatively, recharge a cost when one SPV has simply paid an expense that belongs entirely to another entity.

2. Support every allocation with an audit trail

Regardless of how costs are distributed, each intercompany entry should be backed by documentation that answers the following questions:

• Which entity originally incurred the expense?
• Which entities benefited from it?
• What allocation method was used, such as floor area, occupied units, revenue, or another documented basis?
• Has every receiving entity recorded the corresponding entry?

Following robust account reconciliation discipline will save your finance teams hours of investigation into historical transactions when an audit is upon you.

3.  Understand the difference between VAT grouping and corporate tax grouping

A point that often causes confusion is the relationship between SPVs, VAT groups, and corporate tax groups.

What to enquire before deciding on multi-entity accounting software?

When evaluating any solution, work through the following checklist.

• Can every SPV operate as a genuinely separate entity?
  Each entity should maintain its own users, approval workflows, accounting exports, budgets, and audit history without relying on manual filtering.

• Can one employee spend across multiple entities without sharing cards?
  Senior managers, project directors, and executives often work across several SPVs. The system should allow them to spend on behalf of different entities while ensuring every transaction is assigned correctly.

• Is the entity selected before the expense reaches finance?
  Entity coding should happen during submission or payment, not during month-end review. Correct data at source eliminates most manual corrections later.
• Does each SPV export cleanly into its own accounting system?
  Whether you use one ERP or separate ledgers, every entity should be able to produce its own complete accounting export without additional manipulation.
• How are intercompany transactions handled?
  Look for systems that preserve the originating entity, supporting documents, approval history, and allocation details instead of relying on separate spreadsheets.
• Is the audit trail complete?
  Auditors should be able to see:
  • who made the purchase,
  • which entity approved it,
  • when approvals occurred,
  • the supporting receipt or invoice, and
  • any allocation or recharge history.

Alaan is built to check all of the above boxes. It offers Corporate cards that separate spend by entity at the point of issue, combined with expense management that codes and categorises consistently across every entity a group runs.

Summing it up

Running multiple SPVs is standard practice for property groups and can be made easy if you get entity coding right at the point of spend. Back this up with consistent entity structures, documented allocation policies, and complete audit trails, and you have a system that will hold its ground regardless of the number of SPVs you keep adding to your portfolio.

Book a demo with Alaan to see how.

FAQs

What is multi-entity expense management?

Multi-entity expense management is the process of tracking, approving, and reporting expenses separately for multiple legal entities. This is while being managed from a single system.

When do property companies need multi-entity expense management?

Property companies tend to need multi-entity expense management once they begin to operate multiple SPVs, each with separate accounting records, bank accounts, or reporting obligations, and need a way to manage them centrally while preserving entity separation.

How should intercompany expense allocations be handled?

Intercompany expenses should be handled in a manner such that any direct recharge or shared allocation is captured and supported with the supporting calculations and approvals for both entities.

Can one system manage expenses for every SPV?

Yes, one system can manage expenses for every SPV, provided it maintains separate approval workflows, accounting exports, audit trails, and entity-level reporting.