FLIORE for multi family offices: separation that holds technically
Updated: 2026-09
A multi family office carries the same problem as a single family office, multiplied — plus one more: separation between families must be technically guaranteed, not merely organisationally arranged.
A multi family office serves several independent families, each with its own structure, its own advisers, its own reporting requirements and its own compliance cases. The effort does not just multiply, it changes in nature.
The most critical point is separation. No information may flow between two mandates — not in a report, not in a search function, not through an AI answer. Separation implemented only in application logic holds until a filter is forgotten somewhere. Separation at the database layer holds then too.
The second point is repeat effort. Monthly reports, periodic KYC reviews and invoicing arise per mandate. What is a manageable routine for one family becomes the dominant activity across fifteen — and the point at which an MFO grows, or does not.
How it works
- 01
Delimit mandates cleanly from one another
Create each family as its own mandate with its own entity structure; separation is then anchored in the data model rather than in a convention.
- 02
Assign access rights per mandate and person
Establish which staff have access to which mandates, and keep the assignment documented rather than informal.
- 03
Standardise monthly reporting
Set up white-label reports per mandate, multilingual and in the respective reporting currency — otherwise the recurring effort is re-created every month.
- 04
Check data quality before the reporting run
Review missing FX rates, stale valuations and feed errors by severity in advance, rather than discovering the errors in a finished report.
- 05
Oversee KYC deadlines across mandates
Make due reviews visible across all mandates, so that each mandate does not need its own deadline list.
- 06
Tie invoicing to running the mandate
Produce client invoices with VAT, flexible recipients and a Swiss QR reference from the same system in which the mandate is run.
Why it fits here
Tenant isolation runs on row level security at the database layer — it holds even when a filter is forgotten in application code. For an MFO that is not a technical detail but the basis of the business.
FLIORE AI answers only from the data of the mandate in question and cites its sources; information flow across mandates through the assistant is thereby excluded.
White-label monthly reports and integrated invoicing address the repeat effort that decides an MFO’s scalability.
FAQ
How is separation between mandates guaranteed?
Through row level security at the database layer, not only in application logic. That is the harder variant, because it applies regardless of whether a filter was set in application code.
Can the AI assistant mix data across mandates?
FLIORE AI is mandate-bound and answers only from the data of the mandate in question, with citations. Client data is never used for training.
Are the monthly reports white-label?
Yes. Reports are produced per mandate, print-ready, multilingual, and in the respective reporting currency.
How many mandates can sensibly be modelled?
The data model is built for several mandates. The practical limit sits with your own capacity rather than the platform — which is exactly why reporting and invoicing are integrated.
Can we migrate mandate by mandate?
Yes, and that is the usual route: one mandate first via CSV import, then the rest. It limits risk and surfaces the peculiarities of your structures early.
FLIORE
Tenant isolation runs on row level security at the database layer — it holds even when a filter is forgotten in application code. For an MFO that is not a technical detail but the basis of the business.
FLIORE AI answers only from the data of the mandate in question and cites its sources; information flow across mandates through the assistant is thereby excluded.
White-label monthly reports and integrated invoicing address the repeat effort that decides an MFO’s scalability.