Collateral Configuration
Understanding Assets in timveroOS
Assets represent collateral in the lending system and are fundamental to secured lending operations. Unlike participants, assets lack high-level client abstraction and cannot exist independently—they must be created in association with specific participants who serve as collateral providers.
Core Asset Concepts
According to the system architecture:
Assets have their own attributes, documents, and states
Application business processes depend on asset states
Assets must be linked to participants in collateral provider roles
Different asset types can have different handling processes
The system works with various asset types, with vehicles and real estate being the most prominent examples of collateral implementations.
Asset Configuration Framework
Asset Type Definition
The framework allows configuration of various asset types for collateral management. As documented, the system works with various asset types, with vehicles and real estate being the most prominent examples.
Each asset type can have:
Specific attribute sets
Unique validation rules
Customized workflows
Specialized document requirements
Asset-Participant Relationship
Assets exist within a specific relationship structure:
Created only in association with collateral provider participants
Inherit certain context from the associated participant
Maintain independent status and workflow progression
Influence application status through their own states
Configuration Components
Asset Attributes
The framework allows defining data fields specific to each asset type. Attributes serve various purposes:
Document generation
Scoring process integration
Interface display
Validation and business rules
Asset Documents
Configure required documentation by asset type:
Title documents
Insurance policies
Valuation reports
Inspection records
Legal agreements
Asset Workflows
Design processing flows for different asset types:
Validation procedures
Valuation processes
Documentation verification
Status progression rules
Integration with participant workflows
Implementation Patterns
Pattern 1: Vehicle as Collateral
Configuration Approach:
Define vehicle-specific attributes
Set up VIN validation rules
Configure valuation integration
Establish documentation requirements
Create approval workflows
Process Flow:
Collateral provider participant created
Vehicle asset linked to participant
Vehicle details captured
Validation and valuation performed
Asset status updated based on results
Pattern 2: Real Estate Collateral
Configuration Approach:
Define property attributes
Configure address validation
Set up valuation methods
Establish title requirements
Create verification workflows
Process Flow:
Property details entered
Automated validations triggered
Documentation collected
Valuation completed
Asset approved or flagged for review
Pattern 3: Multiple Assets
Configuration Approach:
Support multiple assets per application
Define aggregation rules
Configure combined valuation logic
Establish priority ordering
Create consolidated workflows
Status Management for Assets
Assets follow status progressions similar to participants:
Common Asset Statuses:
New: Initial creation, pending validation
In Verification: Undergoing checks and valuation
Approved: Acceptable as collateral
Rejected: Does not meet requirements
Released: No longer serving as collateral
Status changes can trigger:
Workflow execution
Document requirements
Notification dispatch
Participant status updates
Integration Capabilities
Data Source Integration
Assets can integrate with external data sources:
Vehicle identification databases
Property information systems
Valuation services
Insurance verification
Title/lien systems
Workflow Integration
Asset workflows integrate with:
Participant evaluation processes
Offer calculation engines
Document management systems
Notification services
Decision workflows
Key Configuration Considerations
System Requirements
As documented, proper asset configuration requires:
Assets must be linked to collateral provider participants
Different asset types support different handling processes
Asset states influence application business processes
Framework-level configuration defines asset behavior
Implementation Resources
Through the Admin Panel (Step 2)
Configure assets through:
Collateral Management - Complete Collateral Management
Through the SDK (Step 1)
For specialized requirements:
Secured Offers - Engine to extend the Products with collateralized options
Operational Capabilities
The asset management framework provides:
Comprehensive attribute management for different asset types
Document tracking and requirement enforcement
Status-based workflow progression
Integration with participant evaluation processes
Support for multiple assets per application
Related Topics
Credit Products - How products utilize collateral
Additives - Collateral-based product variations
Applications - Asset role in applications
timveroOS: Comprehensive asset management for secured lending excellence
Last updated
Was this helpful?