A Workflow represents a structured process or series of activities performed using the Subject Record data. Workflows are designed to manage compliance-related operations in a flexible, auditable manner.

Workflows serve as the "verbs" in Kompliant's system, defining what actions are performed on Subject Records (the "nouns"). Each Workflow has a specific type that determines its purpose and required data. The required data is a Subject Record, which must be associated with the Workflow for the Workflow be start.

Workflows progress through three main states:

CREATED: The initial state when a Workflow is first defined
STARTED: The active state when the Workflow is being processed
ENDED: The final state when the Workflow has completed

📘

Note on Workflow State Transitions

Account-Provisioning Workflows have unique state behavior:

• Account-Provisioning workflows can be created independently without a Business-Application workflow
• Account-Provisioning workflows remain in the CREATED/STARTED state and do not transition to ENDED
• This applies to both Pattern 1 (after Business-Application) and Pattern 2 (independent creation)

Business-Application Workflows follow the standard lifecycle and transition through CREATED → STARTED → ENDED states.

Workflow Types

Kompliant supports the following Workflow types:

Business-Application

The Business-Application Workflow manages the onboarding and evaluation of new businesses. It collects, validates, and processes business applications while ensuring compliance with organizational requirements.

For detailed information, see Workflow: Business-Application.

Account-Provisioning

The Account-Provisioning Workflow manages the provisioning of merchant accounts with external payment processing partners. It submits merchant data and supporting documents to external sponsors.

For detailed information, see Workflow: Account-Provisioning.

Business-Underwriting

The Business-Underwriting Workflow manages the undewriting state of the application. It's created after the Business-Application workflow is ended and it's used for every workflow action after Business-Application is ended.

For detailed information, see Workflow: Business-Underwriting