Case Runtime (Bind to Scheme Version)
Each batch creates a case tied to scheme_version + context (Sanction/Disb/Cont/Update/Claim/Recovery).
| Case ID | Context | MLI | Records | Valid | Invalid | Stage | Last Updated |
|---|---|---|---|---|---|---|---|
| CASE-240219-001 | Sanction | MLI-001 | 120 | 112 | 8 | MLI Approver | Today 11:20 |
| CASE-240219-002 | Disbursement | MLI-002 | 88 | 84 | 4 | NCGTC Maker | Today 10:45 |
| CASE-240219-003 | Claims (Interim) | MLI-003 | 12 | 11 | 1 | NCGTC Checker | Today 09:18 |
Click “Audit & Explainability” to show rule traces, calculator snapshots, and edits/overrides by role (demo screens).
Validation Bins (Demo)
Valid vs Invalid split with error report export.
Valid Bin112
URN: UDY-001
Sanction ₹2.50 Cr
✓Sanction ₹2.50 Cr
URN: UDY-002
Sanction ₹4.10 Cr
✓Sanction ₹4.10 Cr
URN: UDY-003
Sanction ₹1.20 Cr
✓Sanction ₹1.20 Cr
Invalid Bin8
URN: UDY-099
Cap breach: exceeds 100 Cr
!Cap breach: exceeds 100 Cr
Loan A/c: 7788
Duplicate (MLI+Loan A/c)
!Duplicate (MLI+Loan A/c)
Demo: Runtime writes to staging tables, then commits approved records to core tables via integration adapters.