Overview

Kompliant's system is organized around a few fundamental concepts. From an organizational level, we use Organizations and Accounts. At the operational level we use Subject Records and Workflows. These concepts are designed to provide exceptional flexibility to accommodate a wide range of compliance scenarios.

Organizations and Accounts

Organizations represent the companies that use Kompliant's system for their compliance needs. A given company will typically only ever have a single organization_id issued. This ID represents the company within our systems, whether in your live or your sandbox environment.

Accounts function as distinct operational units within an organization. Each account maintains its own collection of configuration and data, and exists in either a live or sandbox environment. Organizations can have multiple accounts to support different business needs, teams, or integration points.

This hierarchical structure provides several key advantages for you. The flexibility of multiple accounts allows for targeted configuration to meet specific business requirements. This approach enables your institution to maintain separation between different lines of business, create isolated testing environments, and implement granular access controls without duplicating core configurations.

Subject Records and Workflows

You can think of Subject Records and Workflows as the subject and verb of a sentence. Subject Records contain information about an entity, such as a business or a person, as well as related information. For example, the business or person may have bank accounts associated with them. Workflows contain details about the activity that will be performed using the Subject Record data. For example, a Subject Record may be applying to your business, so the Workflow is of type Application.

By separating entities (Subject Records) from processes (Workflows), Kompliant allows its customers to configure both what information they collect and how they process it. This separation enables you to adapt quickly to different customer types, regulatory requirements, or risk profiles without rebuilding your integration. Additionally, this modular approach simplifies compliance updates, as changes to verification requirements can often be implemented within the Workflow configuration rather than requiring system-wide modifications. The clear relationship between Subject Records and Workflows also creates natural audit trails, making it easier to demonstrate regulatory compliance and track the evolution of an application over time.

For a deeper understanding of these core concepts, see the detailed pages in this section.