COMMENTARY: Generative AI has the potential to deliver up to $340 billion a year in productivity gains to the banking sector — if banks can build Gen AI solutions that scale.Right now, banks are struggling with this, largely because each Gen AI model used in an institution must be validated to comply with government regulations. Validation can be a challenging process, and as the number of Gen AI use cases for banks grow, internal model risk management (MRM) teams are facing overload. As a result, the validation stage is becoming a bottleneck that impedes scalability.[SC Media Perspectives columns are written by a trusted community of SC Media cybersecurity subject matter experts. Read more Perspectives here.] In this article, we’ll examine how integrating compliance considerations into the design of Gen AI models can accelerate model validation and enable banks to realize productivity improvements and revenue gains.This process works well for traditional models like derivative pricing, because the inputs are transparent, the outcome is well-defined, and it’s comparatively easy to compare the model’s outcomes to historical market data to see if the model is working properly. With Gen AI models, the inputs are often a black box, so the MRM team doesn’t know how the model has been trained or what code it uses, so it’s difficult to assess quality. This is where the bottleneck happens.The next step is testing — with ongoing documentation. Testing Gen AI models is more difficult than testing traditional models whose output can be compared to historical data. With Gen AI models, testing may require several months to accumulate enough user feedback or model outputs to assess the results. During this waiting period, documentation of testing and monitoring strategies is another critical element in designing for compliance.
What makes financial Gen AI model validation so difficult now?
Three factors complicate the Gen AI model validation process.Proliferation of Gen AI applications: Thanks to drag-and-drop tools in platforms like Microsoft’s Power Apps, anyone working at a bank or fintech can create a Gen AI model even if they’re not part of the IT team. To avoid the risk of shadow AI, and to comply with risk management rules, every one of these models must be validated by the MRM team. The validation process is the same for each model regardless of complexity, whether it’s a marketing personalization model or a model for pricing derivatives on the market.Absent or limited Gen AI-specific guidelines. Currently, the U.S. has no specific guidelines for Gen AI model validation. In the EU, the AI Act provides some general guidelines on how to test a Gen AI model that can serve as inspiration for a validation checklist, although the guidance is not written specifically for financial services.Lack of model transparency. When banks use third-party platforms for their generative AI models, they often lack visibility into how these tools generate their output. This “black box” nature prevents MRM teams from using standard validation processes.Why traditional model validation falls short with Gen AI
Standard validation models for risk management have three main steps:- Assess the quality and suitability of the input data used to train the model.
- Evaluate the output quality, relevance, fairness, and robustness of model deliverables.
- Verify the context the model operates in to ensure it’s used for its intended purpose.
Compliance by design for Gen AI in banking and finance
Clearing this roadblock requires adapting the end-to-end validation process to the unique characteristics of Gen AI models. Instead of focusing on black-box inputs, the focus is on controls, documentation, and tests. Ideally, the testing and documenting of Gen AI systems starts when they are designed and built and continues through the final validation by the MRM team. This approach allows the MRM team to see how inputs and outputs are managed, what the context is, whether the models’ results are explainable, and how quality is monitored.For example, let’s say a sales manager wants to use a third-party generative AI tool to guide the team on sales calls using internal policy and procedure documents. The first step to making this model compliant by design is ongoing documentation of:- What documents the model ingested
- Why those specific documents were used
- What prompt was used and why
- How the model has been tested
- What results the model generates
- How those results are to be used.
- What guardrails are in place to keep the model within its use case.




