Automate one workflow within the limits of the mandate.

Preparing a report may combine statements with different periods, formats and currencies. Before consolidation, someone must define which source is authoritative and at what date. An absent line is not necessarily a zero position, and overlapping statements should not be added together without checking. Corrections also need a clear route back to the source so that a later report does not silently repeat an earlier error.

Other workflows concern company documents, requests for evidence or questions from family members. Putting everything into one inbox does not resolve access boundaries. Each entity, mandate and recipient may have different permissions. The initial study should map those relationships rather than request broad access to an archive. It should also identify the person authorised to decide when two sources conflict.

A first scope might cover one statement format and a controlled export to the existing reporting tool. Synthetic cases should include cancelled transactions, negative amounts, multiple currencies and missing pages. The aim is to establish what can be recognised and what still needs intervention, without assuming comparable results across every bank or document layout. An attractive consolidated chart is not enough to prove that process.

The proposed review links values to source passages and separates extraction, reconciliation and interpretation. Calculations should use deterministic rules where possible. A language model should not decide a valuation or quietly fill a missing figure. The construction would need to retain meaningful corrections and their context, while avoiding unnecessary copies of sensitive details in a general technical log.

A source of wealth or source of funds file may require declarations, a chronology and supporting documents. The relevant professional determines the requirements for the actual case. Automation can help organise the material and highlight inconsistencies; it does not establish the declared origin on its own or decide whether a relationship may be accepted. A neat narrative should remain open to challenge.

Vedetta is being developed for all professions subject to Monaco vigilance obligations. Its planned banking extension covers wealth, funds and prior approval workflows. Links with a family office platform remain work to design and verify. The presentation does not imply a live integration, a format accepted by every bank or a product already available for public self-service registration.

The mandate should specify access to each entity, particularly where a team member works across several structures. Support access and exports deserve the same attention as the main screens. Discretion cannot be reduced to a private domain or a branded interface. A departure from the team, temporary delegation and emergency access all need a defined procedure before live operation.

A family office needs a controlled route from the source statement to the information shared with its team and advisers. The project should identify where originals, working copies and exports are held, and which people may receive each one. Initial examples can reproduce the statement format without exposing a family’s accounts. When real material is introduced, the agreed scope includes any model service and its records, so the convenience of automation does not obscure responsibility for the underlying information.