Entities

An entity in BNDRY is the record of a person or organisation the platform knows about — the natural person being onboarded, the company being screened, the trust whose beneficial ownership is being assessed. Each entity has a display name, a sub-type (individual, company, or trust), contact and registration details, risk details, related entities, tags, and any custom fields the tenant has configured. Entities are the durable record that other BNDRY artefacts — workspaces, forms, jobs, activity logs — attach themselves to.

Why entities exist

AML, KYC, and broader risk work is fundamentally about people and organisations. A workspace describes a piece of work; a form captures a moment of data collection; a job runs a check. None of those make sense without the underlying subject — the customer, the patron, the corporate counterparty, the trust the obligation attaches to. The entity is BNDRY's answer to "who is this about?".

Holding entities as first-class records also lets BNDRY do the things regulators expect of a compliance platform: maintain a single, identifiable customer record over time, attach screening and verification history to it, surface its current risk status, and reconstruct the audit trail when asked. A workspace closes; an entity persists.

Key properties and sub-types

Every entity carries a small set of properties shared across all sub-types:

• Display name — the human-readable label used in lists, search results, and entity pages. Tenants can configure how the display name and a small set of header fields are derived, so reviewers can identify the right record quickly.
• Sub-type — exactly one of individual, company, or trust. The sub-type determines which extended fields are available on the record.
• Contact information — telephone numbers, email addresses, websites, and postal addresses (residential, registered business, principal business).
• Registration — jurisdictional identifiers such as ABN or ACN, with the registered name, trading name, and region.
• Risk details — the entity's current risk status (active, pending review, suspended, offboarded, inactive), an optional risk status reason, and a tenant-configurable risk rating label (typically low, medium, high, critical).
• Entity relationships — typed links to other entities, such as director, shareholder, ultimate beneficial owner, trustee, or customer. Relationships are covered in their own concept article.
• External IDs — identifiers for the same entity in third-party systems, used for cross-referencing.
• Tags and custom fields — tenant-defined categorisation and additional fields beyond the core schema.
• Timestamps and etag — create, update, and purge times, plus an etag for optimistic concurrency. Entities are soft-deleted before they are purged.

The three sub-types each add their own fields:

• Individual — a natural person. Carries given name, middle name, family name, title, date and place of birth, gender, nationality, country of residence, citizenship countries, occupation, employer, and aliases. Within Individual, BNDRY distinguishes between people held as a customer of your business and people held as an employee of your organisation — the same record shape, used for two different operational purposes.
• Company — a legal entity. Carries a company type (public, private, non-profit, governmental, association/incorporation) and industry.
• Trust — a trust arrangement. Carries a trust type (discretionary, fixed, hybrid, deceased estate, special disability, public unit, fixed unit, cash management unit) and the names of the settlor, trustee, and deed.

Other roles a person plays in compliance work — director, shareholder, beneficial owner, trustee, family member — are not properties of the Individual record. They are relationships from one entity to another. A director, for example, is an Individual entity linked to a Company entity via a director of relationship; the same person held as an employee or a customer is a property of their Individual record rather than something layered on through a relationship.

How entities relate

An entity is the subject that other BNDRY records attach to. A workspace can reference one or more entities so reviewers see at a glance who the work concerns; a form response can be reconciled back to the entity it was collected from; jobs (verification, screening, risk rating, KYB profile generation) run against an entity and write their outcomes back to it.

Entities link to each other through relationships — director of, shareholder of, ultimate beneficial owner of, trustee of, customer of, family of, and so on. Relationships are how BNDRY models corporate structures, trust arrangements, and the people-to-organisation connections that compliance work depends on.

How an entity is identified in the user interface — its primary label, its secondary identifiers, and the header fields surfaced at the top of the record — is configurable at the platform settings level. The goal is to make it easy for staff to pick the right record quickly and reduce misidentification, especially when several entities share a similar name.