A client is never one person. Does the file know that?
A settlor, a protector, four beneficiaries, two underlying companies and a nominee, across three jurisdictions. In Flarion each of them is a name on the file with its own identity evidence, screening result and review date, and the file is not complete until they all are. This is the case Flarion was built for first.
Every connected party, on the same file
Settlors, trustees, protectors, beneficiaries, nominees and underlying entities are names, not footnotes. Each carries identity evidence, a screening result with its decisions, and the review date the file's rating sets. A party added in August is screened on approval, not discovered at the next review.
- People and entities treated alike, each screened
- Roles recorded, not inferred from a chart
- One review date per file, driven by the rating
| Name | Role | Identity | Screening | Review |
|---|---|---|---|---|
| Marie Le Page | Settlor | Verified | Clear | Mar 2027 |
| Ormer Trustees Ltd | Trustee | Entity | Clear | Mar 2027 |
| P. Ozanne | Protector | Verified | Clear | Mar 2027 |
| A. Le Page | Beneficiary | Verified | Clear | Mar 2027 |
| Herm Holdings Ltd | Underlying company | Entity | 1 candidate | Mar 2027 |
Entities from formation to annual review
For the corporate side of the same firm, an entity file holds the type, the incorporation details, the directors and shareholders as they stand, and the controllers traced back to people. Changes are screened as they land and the annual review rolls on the cadence the rating sets.
- Directors and shareholders as named parties
- Changes screened when they happen
- Annual review on the file's own clock
- Type
- Guernsey company
- Incorporated
- 14 Mar 2019
- Directors
- 2, both verified
- Shareholders
- Ormer Family Trust, 100%
- Controllers
- 1 traced to Marie Le Page
- Annual review
- Due 14 Mar 2027
Questions from fiduciaries
Do you support Jersey firms as well as Guernsey?
Yes. The risk model, the review cadences and the registers are the firm's own configuration, so a JFSC-supervised firm runs its own methodology on the same product. The Handbook mapping shipped with Flarion is the GFSC's, chapter by chapter; JFSC mapping is in progress and is not claimed as complete.
We run everything on spreadsheets. How painful is migration?
Less than you expect. Structures and parties import from a CSV export of whatever you have now, mapped column by column, with a dry run before anything is written. Bring a spreadsheet to the demo and you will leave with it loaded, screened and risk rated.
How is this different from an enterprise KYC platform?
Enterprise platforms orchestrate an onboarding journey through a vendor ecosystem, at enterprise pricing, hosted a continent away. Flarion does the compliance officer's reading and writing, publishes its price, and keeps the data on the island. Different job, different buyer, different postcode.
Our clients are entities, not people. Does that work?
Yes. A name is a person or an entity. An entity file carries its type, incorporation details, directors, shareholders and controllers, each of them a name in their own right with their own identity and screening status, and the entity is screened as a name too.
Bring one anonymised structure.
Thirty minutes. We load it, screen every party and show you the file an inspector would read.