UBOscope determines the beneficial owners of multi-layer, cross-border structures, including fiduciary roles that shareholding data does not show. The result is a sealed onboarding file that states the reasons for each finding. Built for client relationship managers — including the cross-border rules for client contact and travel abroad. Built to each jurisdiction's own statutory rulebook, not a global template.
20 minutes · A structure pattern of your choosing, rebuilt on synthetic data · Nothing installed.
Example: a Panamanian holding company held by a Liechtenstein foundation, with a protector resident in Dubai and a discretionary class of beneficiaries. The structure spans three registers and two languages; shareholding percentages do not identify the beneficial owners.
Without a structured method, such a determination takes considerable time, and a second person cannot readily follow its reasoning.
Foundations, trusts and Anstalten have no shareholders. Shareholding data covers corporate percentages only; it does not show who controls a fiduciary structure.
Where a separate tool is used for each jurisdiction, or none at all, the determination logic and the audit trail are kept in several places.
A complex file can take several days. The expertise is often held by few people, and the reasons for a finding are not always recorded in the file.
The Swiss TJPG has been in force since 1 October 2026, and with it the federal beneficial-ownership register. Liechtenstein is expected to follow the EU AML package as it is incorporated into the EEA Agreement.
The determination must be documented so that a qualified third party can follow it.
Each of the three jurisdictions has its own rulebook, with the forms, registers, thresholds, vehicle types and regulatory sources of that country. Each rulebook version is dated and has its own set of regulatory-watch rules.
UBOscope determines beneficial ownership through fiduciary roles (settlor, protector, beneficiary, founder) as well as through shareholdings. It follows every path, including converging and circular holdings, down to the natural persons.
CDB 20 Forms A/K/S/T with coordinate-overlay fill, SPG Art. 7/7a fiduciary logic, PGR vehicles, GwG §3 look-through and Transparenzregister filing logic. Sanctions screening uses the lists that apply in each jurisdiction.
UBOscope does not keep client files. Each determination is sealed in an audit chain and delivered, through the institution's interface, to its CRM or document system as the file of record. It can be reconstructed at any time and remains with the institution if the contract ends.
Each jurisdiction is implemented under its own rulebook rather than a general template: the forms used by the supervisory authority, the registers to which filings are made and the vehicle types used in practice. Each rulebook has a set of regulatory-watch rules for the authorities concerned.
Further jurisdictions are built to the same standard as the three above, with their own forms and registers. We assess the requirement and the effort with you before any commitment.
The procedure has five steps. Each result refers to the rule on which it is based.
Choose the jurisdiction in which the client is onboarded. UBOscope applies that country's rulebook (its laws, thresholds, forms, registers and regulatory sources), and the workflow follows it.
The user records the entity and its layers (companies, foundations, trusts and Anstalten) with roles, percentages and jurisdictions, during the client meeting, at the desk or on a phone. The intake is available in English, German and French.
UBOscope follows every ownership and control path: by threshold, by control and by fiduciary role. Converging and circular holdings are resolved without double counting. The result names the natural persons at the end of each chain.
A deterministic scoring assigns the file to standard, enhanced (EDD) or complex due diligence and states the reason for each factor. Sanctions screening uses the official lists of SECO, the EU, the UN and OFAC, which the institution's gateway downloads directly from the authorities; without a gateway, the institution supplies a list bundle it has signed. PEP and adverse-media checks use the institution's own provider.
The relationship manager hands the file over to compliance. A second signed-in person reviews it and decides (four-eyes principle): depending on the approval level the institution's policy sets, compliance, the MLRO or senior management, never the preparer. The sealed file, with its SHA-256 audit chain, is delivered to the institution's CRM as the file of record and can be reconstructed by any later reviewer.
UBOscope is decision-support. It does not discharge your statutory duties — reporting, ongoing monitoring or retention — in any jurisdiction. Your institution remains responsible throughout.
Settlor, protector, beneficiary and founder are treated as control paths in their own right, in addition to shareholdings.
No fixed limit on the number of layers; several jurisdictions within one structure; converging and circular holdings resolved without double counting.
Each score states its factors, weights and legal basis, and whether each factor derives from law or from the institution's policy.
Each determination, screening, sign-off record and policy change is hashed and linked. The file can be reconstructed exactly as it stood on the day the decision was made.
The institution sets its policy: risk thresholds, the approval level for each risk class and escalation targets. Each policy version is approved by a named person; on the gateway the approver must be a second person, not the one who proposed it. Each result states the policy version applied and who approved it. Statutory thresholds cannot be changed.
Each jurisdiction has its own authorities, sources and impact rules; an impact rule links a regulatory change to an action in the cockpit. Drift indicators are shown, and rulebook versions are dated and recorded.
The relationship manager records the file during the client meeting, at the desk or on a phone, and sees which items are still outstanding. Each outstanding item receives an owner and a due date before the file is handed over to compliance for review, decision and filing.
Before contacting a prospect abroad, the relationship manager answers a short series of questions. The answer is Stop, Escalate or Proceed, with the duties or conditions that apply. Available for banking services and for crypto-asset services.
Defined connections for screening, on-chain analytics, identity, registry and tax data.
Connections to providers are operated on the institution's gateway. No provider is connected by default. The institution connects each provider under its own agreement and with its own keys; UBOscope has no access to them.
Guided, statutory intake — the form asks only what the loaded rulebook requires.
The cockpit applies each framework listed below, with the form, register and threshold that apply to the vehicle concerned. Each new rulebook version is dated and recorded; the institution reviews it before adopting it.
| Framework | What UBOscope encodes |
|---|---|
| AMLA (Swiss Anti-Money Laundering Act) · CH | Beneficial-owner identification and risk-based due-diligence classification with documented rationale. |
| CDB 20 (VSB 20) · CH | Form A, K, S and T logic applied to the correct vehicle type, coordinate-overlay filled on the official SBVg forms in EN and DE, with completeness checks before a file can be sealed. |
| TJPG · CH | Structural readiness for the Swiss transparency regime and the federal beneficial-ownership register, in force since 1 October 2026. |
| SPG / SPV · LI | Art. 7 and Art. 7a fiduciary-party logic — founder, settlor, protector, beneficiary and distribution recipient. |
| PGR vehicles · LI | Stiftung, Anstalt, trust and domiciliary company modelled as distinct subject types, each with its own required-document set. |
| VwbP · LI | Beneficial-ownership register filing logic with band and control basis, prepared as a draft for your filing. |
| GwG §3 / §15 · DE | Beneficial-owner look-through including fictitious UBO under §3(2), and enhanced due diligence for foreign and domestic PEPs. |
| Transparenzregister · DE | Filing logic under GwG §§18–23 with band and nature/extent of control per beneficial owner, prepared for your review and submission. |
| EU AMLR (Reg. 2024/1624, applies from 10 July 2027) | Alignment path as Liechtenstein follows the EU single rulebook and the EU Anti-Money Laundering Authority (AMLA) takes up supervision. |
Many compliance services require client data to be transmitted to, and stored on, a platform that the provider controls and shares among its customers. In UBOscope V5 the institution operates the software itself, and no client data is transmitted to UBOscope.
The institution operates a signed UBOscope release on its own web server; the engine computes every result in the user's browser. The institution may also operate the UBOscope gateway on its own infrastructure, with its own signing key, sign-in service, provider agreements and storage. Files are delivered to the institution's CRM or document system. UBOscope operates no service for the institution and receives no usage figures.
Provider keys, the signing key and the sign-in service belong to the institution. The gateway does not connect to UBOscope. The pages may connect only to the institution's own services, as set by the institution in the page's Content-Security-Policy.
The demonstration is hosted by UBOscope on Cloudflare and uses sample data only. It processes the e-mail address used to sign in and the hosting provider's request logs; data entered into a file remains in the user's browser. It runs no automatic checks and consults no register.
UBOscope uses no sub-processor for institution installations, as it processes no client data for them. The hosted demonstration is hosted on Cloudflare's global network; enquiries are received in a mailbox hosted in Switzerland. The No-client-data statement, the sub-processor list and responses to security questionnaires are available on request.
Swiss technology, patent filed.
Security controls are designed to be compatible with ISO/IEC 27001, and have been assessed control by control against the ISO/IEC 27001:2022 control set; that assessment — which is candid about what is not yet in place — is available to institutions under a confidentiality agreement. UBOscope does not hold an ISO 27001 certification.
No. UBOscope is not offered as a shared service, and UBOscope does not keep client files. In V5 the institution operates UBOscope on its own infrastructure and files every result in its own CRM. The hosted demonstration serves evaluation purposes only and uses sample data.
Switzerland, Liechtenstein and Germany, each with its own rulebook covering forms, registers, thresholds, vehicle types and regulatory sources. Switzerland and Liechtenstein are at rulebook v2026.1; Germany at v1.0.
Yes. Further jurisdictions are built to the same standard as the three released, with their own forms and registers. We assess the requirement and the effort with you before any commitment.
Client data remains within the institution. In an institution installation of UBOscope V5, the engine computes in the user's browser, checks run through the institution's own gateway and providers, and files are delivered to the institution's CRM. No client data is transmitted to UBOscope. Walkthroughs and the hosted demonstration use synthetic data only.
On request: the No-client-data statement and the sub-processor list; responses to a standard security questionnaire; and a self-assessment against each control of ISO/IEC 27001:2022, which identifies the controls not yet implemented. The self-assessment is provided under a confidentiality agreement.
No. It is decision-support. Identification, reporting, ongoing monitoring and retention duties remain with your institution in every jurisdiction. UBOscope supports the determination and makes it reproducible; it does not discharge a statutory duty.
Those products focus on corporate shareholdings and screening data. UBOscope does not replace them: connection slots are defined for that purpose, and the institution activates them on its own gateway under its own agreements. UBOscope adds the determination through fiduciary roles and the statutory rules of each released jurisdiction. World-Check, Encompass and Fenergo are trade marks of their respective owners; no affiliation is implied.
The Swiss rulebook is versioned against it, with dated impact rules in the regulatory watcher. The institution reviews and adopts each update, and the change is recorded in the audit chain.
The cockpit runs in English, German and French. Determination output and the generated dossiers are produced in English and German; in a French session they are shown in English. French follows Swiss legal usage by default and EU usage for Liechtenstein and German files. This site is available in all three languages.
The connection slots and their interfaces are built. The institution connects providers on its own gateway, under its own agreements and with its own keys. In the hosted demonstration no provider is connected and no check runs automatically. Before any contract is concluded, we state which connections are in place.
Use the Client login. Enter your registered email address, confirm the one-time code sent to it, then enter the access password you were given. Access is limited to named individuals; if you have not been given access, request a walkthrough instead.
A 20-minute walkthrough on a structure you choose. Nothing is installed, and no client data changes hands during the session.
A 20-minute walkthrough of a structure of your choice, rebuilt with synthetic data in the jurisdiction concerned. Nothing is installed and no client data is exchanged.
Swiss-built · Switzerland · Liechtenstein · Germany · Institution-controlled record