One workbook per entity, updated by different hands
Each vehicle has its own file and its own conventions. The consolidated number is a sum of files that were last correct on different days, and everyone in the room knows it.
Consolidation
One picture across every entity, and a way back down to the document
Holdings in a GmbH, a foundation, two SPVs and three banks, each with its own spreadsheet and its own reporting date. Consolidation is not the hard part. Being able to defend the total is.
In use at a small number of family offices and investment managers
Why the group total is never quite trusted
Positions and books drift apart
Holdings live in one place and the bookkeeping for each legal entity in another. At year end, reconciling them back together is archaeology rather than accounting.
Currency and as-of dates get quietly flattened
A euro NAV from last quarter, a dollar balance from this morning and a rate from somewhere in between, added into one figure. It looks precise, which is the problem.
What you get instead
Entities modelled properly, not as tabs
Each GmbH, foundation, SPV and personal holding is a real entity with its own positions, books and access rules. Consolidation is a view over them, and it can be taken at any level of the structure.
Books beside the positions
A full set of books per legal entity (chart of accounts, bank transactions, coding, loans and interest), and an accounting package you can hand to your Steuerberater without rebuilding it first.
Multi-currency, stated honestly
Everything converts into your reporting currency, and the view says which rate and which as-of date each component carries rather than hiding it in a total.
Drill from the total to the paper
Click from the group figure to the entity, the position, the statement and the page. The number your principal asks about is always three clicks from its evidence.
Where the data sits
Hosted in the EU
Every entity's data and documents stay on EU infrastructure, under a DPA that names every subprocessor. Enterprise deployments can run in your own environment.
Separation enforced in the database
Entity separation is row-level security, not a filter in the interface. An advisor with access to one vehicle cannot reach another, whatever they type into the URL.
Role-based access
A family member, an advisor and an accountant each get their own view of the same structure, and every access is logged.
Questions we get about consolidation
Can we consolidate at more than one level?
Yes. Any entity can be a consolidation point, so you can report a single branch of the family, one holding structure, or the whole group, without maintaining three separate models.
Does it handle partial ownership of a vehicle?
Yes. A vehicle held at a percentage consolidates at that percentage, and the view shows both the look-through figure and the vehicle-level figure, because different readers want different ones.
Can our Steuerberater get what they need?
Yes. Each legal entity produces a proper accounting package from its own books, exportable, rather than a report assembled by hand from the portfolio side.
What about assets we do not want in the system?
Then do not put them in it. Entities and positions are added deliberately, and anything you leave out is simply absent. There is no background aggregation reaching for accounts you did not connect.
How current is the consolidated view?
As current as its inputs, and it says so. Bank balances are as of their last sync; fund NAVs are as of the last statement, with the date shown. A total that hides the age of its components is worse than no total.
See the whole structure in one view
Tell us how many entities and banks are involved. You will get a straight answer about whether this fits your structure.