Data Flow

This page explains how your data moves from your core systems into RiskScout.

Overview

Steps

1. Data Export

Your institution exports data from your core banking system(s):

• Customers - Full customer master with demographics, identification, and contact info
• Accounts - All account types including deposits, loans, and cards
• Transactions - Daily transaction activity
• Branches - Branch location reference data
• Customer Relationships - Customer-to-account ownership and signer linkages

2. File Transfer

Files are transmitted via SFTP to RiskScout's secure ingest servers:

• Protocol: SFTP (SSH File Transfer Protocol)
• Authentication: SSH key-based (no passwords)
• Encryption: TLS 1.2+ in transit, AES-256 at rest

3. Data Processing

RiskScout processes your files:

1. Validation - Schema validation, required field checks
2. Code Mapping - Your codes mapped to standardized rs_* values
3. Transformation - Data normalization and enrichment
4. Quality Checks - Referential integrity, value range validation

4. Analytics Load

Processed data is loaded into the analytics platform:

• Customers, accounts, and transactions are linked
• Historical data is preserved for trend analysis
• Real-time monitoring rules begin evaluation

File Submission Schedule

Data Type	Recommended Frequency	Notes
Transactions	Daily	Required for real-time monitoring
Customers	Daily or Weekly	Include all changes since last export
Accounts	Daily or Weekly	Include all changes since last export
Branches	As needed	Only when locations change
Relationships	With Customers/Accounts	Link data should accompany entity changes

Data Retention

• Active data: Current customer/account state is always maintained
• Transaction history: Retained per your regulatory requirements (typically 5-7 years)
• Audit trail: All changes tracked with timestamps

Error Handling

If file processing encounters errors:

1. You receive an email notification with error details
2. The file moves to a quarantine folder
3. You can correct and resubmit, or contact support

Common issues:

• Missing required fields
• Invalid date formats
• Unknown reference codes
• Duplicate primary keys