Family office asset tracking: one register for every asset and entity.
Family office asset tracking should let an authorised reviewer understand what is held, by which entity, in which currency and on what evidence. A useful register connects liquid, illiquid and digital assets without hiding their different update and verification requirements.
Written by the Fundamental View editorial team. Updated 28 October 2026. Examples below are fictional and illustrate record design, not valuation or accounting advice.
Why asset tracking breaks down
Registers often begin as separate spreadsheets maintained for different purposes. As entities and asset types multiply, familiar failure modes appear: the same asset is duplicated, an internal transfer looks like two external transactions, currencies are combined without rate provenance, and the document supporting a balance remains in an inbox. Illiquid and crypto assets are then placed in side sheets because the main structure cannot represent their evidence.
The underlying problem is not simply the absence of a total. It is the absence of a shared record definition and a repeatable review process.
The minimum useful asset record
| Field group | What to preserve | Review question |
|---|---|---|
| Identity | Stable record ID, entity and asset class | Can this asset or event be confused with another? |
| Instrument | Account, security, property, fund interest, loan or token | Does the category determine which evidence is required? |
| Source value | Original amount, currency, date and counterparty | Do these fields match the source without overwriting? |
| Reporting value | Converted amount, FX rate, rate date and status | Can a reviewer reproduce or explain the conversion? |
| Valuation context | Valuation date, source and document where relevant | Is a current transaction amount being confused with a valuation? |
| Evidence | Statement, contract, confirmation or explorer reference | Can an authorised person retrieve it from this row? |
| Review | Confirmation state, exception and next-action owner | Is unresolved information visibly excluded from confirmed totals? |
| Crypto context | TXID, token and network where applicable | Could the same transaction be entered on the wrong network or twice? |
Do not flatten every asset into the same update rule
- Liquid assets change frequently. Record movements as transactions and retain periodic statements as evidence; a closing balance alone does not explain the activity.
- Illiquid assets may change value infrequently while generating many important events. Link contracts, capital calls, distributions and valuation documents rather than replacing one number and discarding its history.
- Digital assets need network-aware transaction references. An explorer entry can support a transfer record, but it does not by itself establish beneficial ownership, business purpose or accounting treatment.
A single register can use shared identity and review fields while allowing different evidence requirements by asset class. That is more reliable than forcing every asset into identical columns.
Keep valuation and movement separate
A transaction amount, a custodian balance and an estimated valuation answer different questions. Give each its own date and source. For a property or private fund interest, do not present an old valuation as a current market price. For a brokerage account, do not treat a converted reporting total as the original cash amount.
For multiple currencies, preserve the source amount and currency exactly, then record the reporting value with its rate, rate date and method. When a historical rate is unavailable, make the gap and any approved manual override visible.
A quarterly control that takes minutes to understand
- Unlinked records: which confirmed rows have no supporting evidence?
- Stale valuations: which illiquid assets exceed the agreed review interval?
- FX exceptions: which conversions lack a rate, source or reviewer?
- Duplicates: which stable IDs or crypto transaction references collide?
- Internal pairs: do both sides of an internal movement reconcile without inflating external flows?
- Access: who can edit, confirm or only read, and whose access should be removed?
Save the exception output with its review date. The point is not to claim that the register is perfect; it is to show what remains unresolved and who owns the next action.
Spreadsheet or database?
A well-structured spreadsheet register can be a reasonable starting point. Consider a different architecture when volume, concurrent editing, permissions, integrations or reporting requirements exceed what the team can control reliably. Plan migration through a field dictionary, identifier mapping, evidence-link preservation and acceptance tests. “Move to SQL” is not itself a control or a guarantee of scale.
Where Fundamental View fits
Fundamental View is private financial and asset accounting for family offices. Each record carries its entity, currency and USD value, a stable PCD number and links to its documents. Liquid, illiquid and crypto assets can therefore sit in one register while retaining their evidence. Documents are anonymised before AI reads them, a person confirms each field, and the register and evidence live in the client's own Google Workspace. Historical FX rates are retrieved where they exist, with manual override. Crypto records keep TXID, token and network, with a duplicate check.
Fundamental View does not value assets or report investment performance, and it does not replace your accountant. Direct bank and custodian connections are not in the first version.
Continue with a working asset or transaction case
- Define transaction fields and review states
- Record crypto evidence with its network context
- Assess a spreadsheet-to-SQL migration
- Compare accounting software requirements
- Test evidence capture and retrieval
Discuss your workflow
Describe the record-keeping problem you want to solve. Please do not include confidential financial information or documents in the enquiry.
Discuss implementation