Testing the Future: TimeTravel Simulation for Financial Systems

In this session, 𝐑𝐚𝐤𝐞𝐬𝐡 𝐒𝐮𝐤𝐥𝐚, Director of Engineering - Platform and Quality Engineering at Bread Financial, solves a timing problem specific to financial platforms: interest accrual, scheduled and partial payments, delinquency, charge-offs, refunds and settlements all have to be validated before they naturally occur. Waiting weeks or months is not an option when products and partner integrations need to launch quickly. Learn how to make those futures testable today. Rakesh also walks through a lifecycle-aware Test Data Management Portal that creates production-like financial states and programmatically advances accounts and loans through future servicing events, plus the architectural principles, governance considerations and hard-won lessons from building this at enterprise scale. 𝐇𝐢𝐠𝐡𝐥𝐢𝐠𝐡𝐭𝐬: 0:10 Session Opens - Testing the Future: Time-Travel Simulation for Financial Systems 0:20 How Do You Reliably Test Events That Haven't Happened Yet? 1:24 Speaker Intro - Rakesh Sukla, Director of Engineering, Bread Financial 2:59 A Challenge for Any Business That Lends Money 4:21 The Problem: Validating Something That Happens in the Future 5:34 Time Is Not Just Context - It's a Testing Dependency 5:47 The Loan Journey: Day 30, Day 60, Day 90 and Charge-Off 6:41 Nobody Waits 120 Days to Test Settlement Logic 6:59 Why Waiting for Time Doesn't Scale 7:21 Why Database Manipulation Is Fragile and Inconsistent 7:56 Why Mocking Everything Breaks Down in Complex Systems 9:18 The Question: Can We Advance Time Across the Entire System? 10:14 Instead of Waiting for the Future, Bring the Future Into the Test Environment 10:46 The Mental Model: Initial State, Advance Time, Trigger Logic, Validate 11:53 Do Not Fake the Final State - Let the Platform Produce the Outcome 13:02 Rule One: No Business Logic Reads the System Date Directly 13:27 Inject an Explicit As-Of Date Across Every Service 13:50 Rule Two: Build Only One Loan Servicing Engine 14:30 Rule Three: Decouple the Servicing Engine From Everything Else 15:25 Rule Four: External Integrations Behind Adapters 16:04 The Foundation Restated - Every Engine Takes an External As-Of Date 17:03 Where the Simulation Should Live: The Test Data Management Portal 18:03 Expose It Through an API, Not Just a Portal 18:44 Tie the Orchestration to End-of-Day Processing - Day by Day, Not Day 1 to Day 60 19:53 Use Case Walkthrough: Simulating a Delinquent Loan 20:36 Feed the Loan ID Into the Orchestrator on Day Zero 21:28 Day 30: Payment Due, Payment Missed, Downstream Events Fire 22:22 Day 60: Second Missed Payment and Interest Starts Accruing 23:01 Day 90: Delinquency and the Credit Bureau Notification 24:11 The Hard Part: Deterministic, Safe and Repeatable Future States 24:34 What Happens When 100 People Use It on the Same Day? 24:49 Data Integrity: Bankruptcy Must Flow Through to Customer Status and Charge-Off 26:24 From Concept to Enterprise Capability: Scenarios, CI/CD, Governance 27:39 Impact at Bread Financial: Before the Tool 29:23 After: Future States in Minutes, Self-Service, Repeatable Scenarios 30:33 No Lender Can Have a Solid Testing Process Without This 31:41 The Closing Principle: Time Is a Controllable Test Dimension 32:20 Beyond Lending: Insurance, Subscriptions, Rewards, Healthcare, Contracts 33:29 Q&A: Third Parties You Can't Time-Travel, Like Payment Networks 35:49 Q&A: How Many Variables to Factor Into a Simulation 37:43 Q&A: Can It Catch Interest Accrual and Batch Failures? 38:47 Q&A: Simulating Payment Acknowledgement - Pending, Acknowledged, Received 40:30 Q&A: Is This Tool Available to Other Financial Services? 41:39 Q&A: Building Future Test Data Without Breaking Banking Rules 42:41 Q&A: The Hardest Bug It Caught - Double Payments and Refund Logic Register for TestMuConf 2027: https://www.testmuai.com/testmuconf-2027/?utm_source=youtube&utm_medium=organic&utm_term=&utm_campaign=time_travel_simulation_for_financial_systems #TestMuConf #TestMuAI #FinTech #TestData #QualityEngineering #BFSI #TestAutomation #SoftwareTesting