Custom Entities and Documents
Opt-in modules. Custom Registers is still in Beta; Custom Entities and Document Upload are generally available for enabled teams.
Some customers, owners, or counterparties don’t exist in the Knowledge Graph — a newly incorporated entity that hasn’t been registered yet, a private trust, a foreign subsidiary outside Strise’s coverage. Custom Entities lets your team create these records inside Strise so they can be monitored and reviewed like any other entity. Document Upload pairs with this: attach supporting PDFs, certificates of incorporation, or trust deeds directly to an entity.
Both features are opt-in modules. Ask your CSM to enable Custom Entities and Entity Document Upload for your team.
Custom Entities
A custom entity is a company or person record that your team defines manually. Once created, it behaves like any other entity in your portfolio:
- It has its own entity page with assignee, status, tags, and comments.
- It can be added to reviews, including automated reviews driven by review triggers.
- It can be edited by your team — owners, roles, and beneficial owners are all editable like on standard entities.
- It is visible to the whole team, not just the creator.
What You Can Define
| Field | Description |
|---|---|
| Name | The legal or common name |
| Legal form | Freeform legal form string |
| Country | Country of registration or residence |
| Organisation number | Custom identifier; must be unique within your team |
| Addresses | Primary and alternate addresses |
| Roles and owners | Directly editable once the custom entity exists |
Screening
Custom entities are not automatically screened against PEP and sanctions sources — the Knowledge Graph disambiguation step doesn’t run for entities your team has defined manually. If you want screening, add the persons involved through the entity edit flow; those roles feed into standard screening.
Document Upload
Document Upload lets team members attach PDFs and other files to any entity. Attached documents live alongside the entity and are visible to all team members.
Typical use cases:
- Certificates of incorporation and extracts from national registries.
- Customer-provided KYC documentation.
- Board resolutions authorizing specific actions.
- Commercial agreements, where they’re relevant for the risk assessment.
Where Documents Appear
- Entity page — a Documents card lists all files attached to the entity.
- Review — documents attached to the entity are accessible from the review sidebar so the reviewer has supporting material in one place.
Limits
Individual document size is capped by the API. Large binary evidence should be stored in your existing document management system with a link to that system attached as a text document or URL instead.
Custom Registers
For teams that need to maintain their own enrichment sources alongside Strise’s, Custom Registers (currently in Beta) let you upload structured data that shows up on entity pages. Ask your CSM if you need this.