The applicant declares UBOs in the application
Prefill from the register when it exists, then the applicant adds, updates, or removes. If you need a statement, it goes in the documents for signing.
UBO in the same flow
UBO collection is often slow. Applicants get stuck, documents arrive incomplete, and handlers chase and check. Here the applicant declares UBOs in the application.
- Built for this ticket size
- Applicants are rarely multinationals. The questions match that.
- Only when needed
- Sole proprietorships and single-person entities skip the UBO flow.
- Prefill from the register
- National business-register data when it exists.
- Signed UBO declaration
- If your process requires it, the declaration is generated and attached to the documents for signing.
- On the timeline
- Entries, changes, and declarations are recorded.
Frequently asked questions
- How does the system prefill UBO information?
- National register data when it is available. If the register has no UBO details, known signer information is used so the applicant starts with something.
- Can applicants change the prefilled data?
- Yes. They can add, update, or remove UBOs.
- Is the UBO declaration linked to identity verification?
- Yes. Signing requires digital identity validation, so the declaration is tied to a verified person.
- How is the UBO document produced?
- If your process needs a formal statement, it is generated and included in the documents for signing.
Legal structure
From the register.
