System Building Blocks

Overview

System entities are the core data structures that TimveroOS uses to manage lending operations. These entities store information about customers, applications, loans, documents, and users, and define the relationships between them.

Core Entities

Clients and Participants

Customer information management through two-level structure:

• Clients: Master records with reusable personal information

• Participants: Role-specific instances within applications (borrower, co-borrower, guarantor, collateral provider)

Applications

Aggregating entities that orchestrate lending transactions:

• Container for participants and assets

• Progress through Business Process stages

• Status derived from participant statuses

• Three types: Online, Offline, Pre-approved

Loans

Active credit products requiring ongoing servicing:

• Payment processing and schedule management

• Balance tracking (principal, interest, fees)

• Status updates based on payment performance

• Covenant monitoring and compliance tracking

Business Process vs Workflow

Understanding the distinction between process orchestration and decision logic:

• Business Process: Defines stage sequence and journey flow

• Workflow: Implements algorithmic decision-making within stages

Status Management

Position tracking and automation triggers:

• Current stage within Business Process

• Workflow execution triggers

• Notification and document generation

• Operational visibility and reporting

Document Management

Complete document lifecycle handling:

• Required document definitions

• Template-based generation

• E-signature workflows

• Secure storage and retrieval

User Roles

Access control and permission management:

• Role-based access control (RBAC)

• Feature and data permissions

• Approval authority limits

• Segregation of duties

Entity Relationships

Client
  └── Participant (Role: Borrower, Guarantor, etc.)
        └── Application
              ├── Status (drives automation)
              ├── Documents (required and generated)
              ├── Business Process (stage sequence)
              ├── Workflow (decision logic)
              └── Loan (if approved)
                    ├── Payment Schedule
                    ├── Transactions
                    ├── Covenants
                    └── Status (servicing state)

User + Role
  └── Permissions (what they can access and modify)

How Entities Work Together

Application Journey Example

1. Client Creation

   • Client entity stores master personal information

   • Reusable across multiple applications

2. Participant Assignment

   • Client becomes Participant with specific role (e.g., Borrower)

   • Participant linked to Application

   • Additional Participants added if needed (Guarantors)

3. Application Processing

   • Application status tracks progress

   • Business Process defines stages

   • Workflows execute at specific stages

   • Documents collected and generated

   • Users with appropriate roles perform actions

4. Loan Creation

   • Approved Application creates Loan entity

   • Loan inherits participant and product information

   • Payment schedule generated

   • Servicing begins

5. Ongoing Management

   • Loan status updates based on payments

   • Transactions recorded

   • Covenants monitored

   • Documents generated as needed

Configuration Levels

SDK Configuration (Development team)

Define entity structure and core behavior:

• Entity attributes and relationships

• Status definitions and transitions

• Business Process stages

• Role and permission structure

• Document entity configuration

Admin Panel Configuration

Configure operational aspects:

• User and role assignments

• Document templates

• Status automation rules

• Workflow triggers

• Notification templates

Operational Use

Day-to-day entity interaction:

• Create and update applications

• Process loan payments

• Upload and verify documents

• Assign user roles

• Track entity status

Implementation Resources

Through SDK (Development team)

• Data Model Setup - Entity structure and relationships

• Entity Checkers Setup - Status and transition configuration

• Application Management - Application entity configuration

• Credit Management System - Loan entity configuration

• Document Management - Document entity setup

Through Admin Panel

• Core Configuration - User, document, notification setup

• Credit Products and Pricing - Product entities

• Workflow Management - Workflow configuration

• Servicing and Portfolio Management - Loan and covenant setup

Related Topics

• Lending Process - How entities support origination and servicing

• Product Management - Credit Product entity configuration

• Decision Configuration - Workflow and process configuration

---

TimveroOS: Structured data for lending automation