Decision Automation
Overview
timveroOS automates credit decisions through the Workflow Engine. Workflows retrieve data from external and internal sources, apply decision logic, and produce outcomes that route applications to approval, decline, or manual review.
Why This Matters
Credit decisions require balancing consistency with judgment:
Consistency: Standard criteria should apply uniformly across applications
Judgment: Complex or exceptional cases benefit from human expertise
timveroOS addresses this through Fact types. Workflows evaluate data and produce:
Alert Facts for clear declines (consistency)
Warning Facts for cases needing review (judgment)
Info Facts for documentation
This lets institutions automate routine decisions while preserving human oversight where it adds value.
Workflow Engine
Workflows are visual decision flows configured in Admin Panel. They execute at specific Business Process stages defined by SDK.
Workflow
Sequence of nodes that evaluate data and produce decisions
Trigger
Business Process stage that initiates workflow execution
Outcome
Facts that determine what happens next (approve, decline, review)
Data Sources
Workflows retrieve information from external and internal sources:
External
Credit bureaus, open banking, identity verification, fraud detection
Internal
Application data, collateral data, historical performance
Data Sources are integrated at SDK level. Workflows access them through configured connections.
Mappings and Features
Mapping
Script that extracts specific values from Data Source responses
Feature
Named value stored in participant/asset profile for use in decisions
Example: Credit bureau response → Mapping extracts "creditScore" → Feature saved to profile → Workflow uses feature in decision logic.
Fact Types (Decision Outcomes)
Workflows produce Facts that determine routing:
Alert Fact
Red Zone
Automatic decline, processing stops
Warning Fact
Yellow Zone
Routes to manual review (Launchpad)
Info Fact
Green Zone
Informational record, processing continues
Manual Review
When workflows generate Warning Facts, cases route to human specialists:
Department
Team responsible for specific review types
Launchpad
Queue interface where reviewers see assigned cases
Form
Data collection interface for reviewer decisions
Reviewers evaluate the case, complete required forms, and resolve the warning. Workflow then continues.
Where to Configure
Related Topics
Lending Process — Where decision automation fits in origination
System Entities — Business Process vs Workflow distinction
Operations — Launchpad for manual review queues
timveroOS: Automated decisions with human oversight
Last updated
Was this helpful?