Family office accounting software: what to check before you choose.

Family office accounting software should make transactions traceable across entities and currencies, not merely produce an attractive summary. Use this guide to test the register, its supporting evidence, data ownership and the work required to keep it reliable.

Written by the Fundamental View editorial team. Updated 28 October 2026. Fundamental View is one of the approaches discussed; its capabilities and limitations are stated separately from the general buyer checklist.

Start with the layer you actually need

A wealth or portfolio platform typically consolidates positions and reports performance. An operational accounting layer records transactions, preserves their context and links each figure to evidence. A general ledger adds formal books, journals and financial statements. These categories can complement one another, but buying a dashboard will not automatically repair a fragmented transaction process.

Write down the source of truth you need before comparing brands. If the immediate problem is finding the document behind a payment, an evidence-led register may be the first layer. If the requirement is statutory multi-entity consolidation, confirm that the proposed product actually provides a general ledger rather than assuming that “accounting” means the same thing on every website.

Ten checks to make before selection

1. Entities and currencies. Every record should identify its entity, original currency and reporting value. Ask how nested structures and internal transfers are represented.
2. Evidence behind each record. Open the statement, invoice or confirmation from the row it supports. A stable record number and two-way link make later review possible.
3. Original and converted amounts. Keep the source amount unchanged. Record the FX rate, rate date, source, override and review status separately.
4. Data ownership and exit. Ask where records and originals live, who can grant access, how it is revoked and what a complete export contains.
5. AI input. If a model reads documents, establish exactly what leaves your control. Masking identifiers before recognition is different from applying access controls after upload.
6. Human confirmation. Recognition should propose fields, not silently write them. Test correction, rejection and manual entry when recognition fails.
7. Exceptions. Missing documents, duplicate transactions and unavailable rates need visible owners and states, not a note in someone's inbox.
8. Asset-specific context. Illiquid assets need valuation and capital-event documents. Crypto records may need TXID, token and network. One generic amount field is not enough.
9. Connections and boundaries. Distinguish available bank or custodian feeds from roadmap items and manual document intake. Ask for a demonstration of the current version.
10. Implementation and support. Agree responsibilities, test cases, acceptance criteria, handover and support. A timeline is meaningful only with its dependencies.

A demo script that exposes the real workflow

Illustrative exception: one payment, two currencies

Suppose a fictional entity records a EUR 250,000 internal transfer while the register reports in USD. The original EUR amount and currency should remain intact. The USD value needs a rate, date and source. If no historical rate is available, the row should show an exception and then preserve the person-approved override. Replacing the EUR amount with a converted number would destroy part of the source record.

This is an operational example, not an accounting treatment. Your accountants should define the relevant books, elimination entries and reporting policy.

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. The register and evidence live in the client's own Google Workspace. Names, account numbers and other identifiers are masked before a document reaches the recognition model, and a person confirms each field before it is saved. Historical FX rates are retrieved where they exist, with manual override. Crypto records keep TXID, token and network, with a duplicate check.

Implementation is described as typically taking about four weeks; scope and dependencies still need to be agreed. A spreadsheet register can be the starting point, with SQL migration scoped separately where the operating requirements justify it.

What Fundamental View does not do

It does not replace your accountant: accounting judgements, tax positions and filings stay with your professionals. It does not connect directly to banks or custodians in the first version; statements and confirmations are added as documents. It does not hold your records, move money or ask for banking credentials. It is not presented as a performance-reporting or portfolio-analytics platform.

Related working guides

• Design a transaction record that retains its context
• Structure liquid, illiquid and digital asset records
• Question AI document confidentiality
• Review implementation stages and acceptance
• Use the transaction evidence checklist

Source and method

The checklist is an original operational framework based on the product workflow and publicly available implementation guidance. Family Office Exchange discusses software, teams, data readiness and organisational readiness as implementation factors; that external article is vendor-contributed and is used as a buyer-education source, not as an endorsement of Fundamental View. Family Office Exchange, implementation guidance, checked 28 October 2026.

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