Dev48
Language
  • About
  • Services
  • Industries
  • Technologies
  • Articles
  • Contacts
Book a call
    Home/Articles/Ai governance for financial services starts with the workflow
Dev48
info@dev48.org+375 29 320-40-96WhatsApp@isky_by

© 2026 · All rights reserved.

AI Governance for Financial Services Starts With the Workflow

Source: Endava•November 18, 2026 at 10:41 PM

AI Governance for Financial Services Starts With the Workflow

Learn how financial institutions can embed AI governance into workflows with clear oversight, controls and accountability.

AI governance is becoming a workflow engineering challenge.

Across financial services, AI is already helping organizations interpret policies, monitor activity, create documentation, analyze compliance requirements and explain decisions. It is also supporting employees as they make increasingly complex judgements. What began as a way to summarize information or draft content is moving into the workflows that shape financial outcomes and customer experiences.

That shift is happening across fraud investigations, merchant underwriting, disputes, servicing, compliance, payment exceptions and treasury operations. As AI takes on a larger role in these processes, governance has to move with it.

Recent research on generative AI in financial institutions highlights an important distinction: risk depends not only on whether a workflow uses an AI model, but also on how close the model’s output is to a business decision and what harm could follow if that output is wrong.

That is a useful lens for financial services leaders. A model that summarizes an internal document has a different risk profile from one that drafts adverse-action language, interprets a monitoring alert or recommends how to resolve a fraud investigation. The underlying technology may be similar. The workflow determines how the output is used, who relies on it and what happens next.

Three implications for financial institutions

  • 1. Governance needs to follow the decision Traditional model governance has established disciplines for validation, monitoring, change management and oversight. Generative and agentic AI complicate where those disciplines should apply because AI can influence a decision without making the final calculation or taking the final action.

1. Governance needs to follow the decision

Traditional model governance has established disciplines for validation, monitoring, change management and oversight. Generative and agentic AI complicate where those disciplines should apply because AI can influence a decision without making the final calculation or taking the final action.

  • Consider merchant underwriting. AI might summarize business information, interpret policy, identify missing documentation and draft an analyst recommendation. A deterministic risk model may still produce the score, and a human underwriter may still approve or decline the application. Yet AI has shaped the information the underwriter sees and may have influenced the explanation behind the decision.

Consider merchant underwriting. AI might summarize business information, interpret policy, identify missing documentation and draft an analyst recommendation. A deterministic risk model may still produce the score, and a human underwriter may still approve or decline the application. Yet AI has shaped the information the underwriter sees and may have influenced the explanation behind the decision.

  • Governance should therefore cover the full decision workflow. Leaders need to understand where AI retrieves information, interprets policy, generates content, invokes tools and hands work back to employees. They also need to know what data and sources inform the output, how changes to the workflow are managed, and where responsibility sits when the output is incomplete or incorrect.

Governance should therefore cover the full decision workflow. Leaders need to understand where AI retrieves information, interprets policy, generates content, invokes tools and hands work back to employees. They also need to know what data and sources inform the output, how changes to the workflow are managed, and where responsibility sits when the output is incomplete or incorrect.

  • This broader view helps institutions see AI’s influence even when it does not appear in the final decision record. It also makes it easier to identify where existing controls apply, where they need to be extended and which decisions require additional review.

This broader view helps institutions see AI’s influence even when it does not appear in the final decision record. It also makes it easier to identify where existing controls apply, where they need to be extended and which decisions require additional review.

  • 2. Human oversight has to be engineered

2. Human oversight has to be engineered

  • “Human in the loop” is often treated as if it were a complete control. In practice, the presence of a reviewer is only useful if that person has the information, time and authority to challenge the system.

“Human in the loop” is often treated as if it were a complete control. In practice, the presence of a reviewer is only useful if that person has the information, time and authority to challenge the system.

  • The key question is: what is the person actually expected to review?

The key question is: what is the person actually expected to review?

  • In a fraud investigation, an AI-enabled workflow could query transaction history, connect related entities, summarize alerts, build a timeline and draft a case narrative. These are natural applications for generative AI, but each step can affect what an investigator notices and how the case is understood.

In a fraud investigation, an AI-enabled workflow could query transaction history, connect related entities, summarize alerts, build a timeline and draft a case narrative. These are natural applications for generative AI, but each step can affect what an investigator notices and how the case is understood.

  • A reviewer needs more than a polished final paragraph. They need visibility into the underlying evidence, the sources used, any exceptions or missing information, the system’s confidence and the policy interpretation behind its recommendations. They also need to see what actions have already been taken and know which steps they can reverse or escalate.

A reviewer needs more than a polished final paragraph. They need visibility into the underlying evidence, the sources used, any exceptions or missing information, the system’s confidence and the policy interpretation behind its recommendations. They also need to see what actions have already been taken and know which steps they can reverse or escalate.

  • Effective oversight depends on deliberate workflow design: where judgement is required, what evidence is presented, which actions may proceed automatically and what conditions trigger escalation. When those boundaries are clear, human review can focus on meaningful decisions instead of checking AI output without enough context to assess it.

Effective oversight depends on deliberate workflow design: where judgement is required, what evidence is presented, which actions may proceed automatically and what conditions trigger escalation. When those boundaries are clear, human review can focus on meaningful decisions instead of checking AI output without enough context to assess it.

  • 3. Governance can become an accelerator

3. Governance can become an accelerator

  • Strong governance should make responsible deployment easier to repeat. If every team has to create controls from scratch, AI adoption will be slow and uneven. Shared patterns for identity, access, data retrieval, monitoring, auditability, human review and escalation can give teams a consistent foundation.

Strong governance should make responsible deployment easier to repeat. If every team has to create controls from scratch, AI adoption will be slow and uneven. Shared patterns for identity, access, data retrieval, monitoring, auditability, human review and escalation can give teams a consistent foundation.

  • Institutions can then adapt those patterns to the risk of each workflow. A document-summary tool and an AI-assisted fraud investigation may use some of the same safeguards, but they will not need identical approval points or escalation rules.

Institutions can then adapt those patterns to the risk of each workflow. A document-summary tool and an AI-assisted fraud investigation may use some of the same safeguards, but they will not need identical approval points or escalation rules.

  • This is where the technology ecosystem matters. Cloud, data and model-monitoring platforms from providers such as AWS, Google, Microsoft, Databricks and Snowflake can supply components of a control environment. But the platforms alone cannot determine how those capabilities should work within a bank’s policies, risk tolerance, regulatory obligations and customer commitments. That requires engineering the controls into the workflows where AI is used.

This is where the technology ecosystem matters. Cloud, data and model-monitoring platforms from providers such as AWS, Google, Microsoft, Databricks and Snowflake can supply components of a control environment. But the platforms alone cannot determine how those capabilities should work within a bank’s policies, risk tolerance, regulatory obligations and customer commitments. That requires engineering the controls into the workflows where AI is used.

Three priorities for the next six months

  • 1. Map AI’s influence, not just the inventory

1. Map AI’s influence, not just the inventory

  • Identify where AI is already interpreting, recommending, drafting, monitoring or initiating actions inside critical workflows. Include tools embedded in existing platforms as well as systems developed specifically for AI use.

Identify where AI is already interpreting, recommending, drafting, monitoring or initiating actions inside critical workflows. Include tools embedded in existing platforms as well as systems developed specifically for AI use.

  • Then assess how close each output is to a customer, financial or compliance decision. This gives leaders a more useful picture of exposure and helps them prioritize where stronger controls or clearer ownership are needed.

Then assess how close each output is to a customer, financial or compliance decision. This gives leaders a more useful picture of exposure and helps them prioritize where stronger controls or clearer ownership are needed.

  • 2. Establish reusable control patterns

2. Establish reusable control patterns

  • Define common requirements for data access, grounding, traceability, monitoring, approvals, escalation and evidence retention. Make clear what must be consistent across the organisation and what teams can configure for a specific workflow.

Define common requirements for data access, grounding, traceability, monitoring, approvals, escalation and evidence retention. Make clear what must be consistent across the organisation and what teams can configure for a specific workflow.

  • These patterns are especially useful for agentic workflows, where work may cross systems, trigger actions and move through repeated hand-offs. Clear controls can help teams understand what an AI agent is authorised to do, when it must pause for review and how its actions can be reconstructed afterwards.

These patterns are especially useful for agentic workflows, where work may cross systems, trigger actions and move through repeated hand-offs. Clear controls can help teams understand what an AI agent is authorised to do, when it must pause for review and how its actions can be reconstructed afterwards.

  • 3. Redesign workflow priorities end-to-end

3. Redesign workflow priorities end-to-end

  • Choose a small number of high-value processes, such as fraud investigations, merchant underwriting, disputes or payment exceptions. Map how work happens today, identify where AI can help and design the controls alongside the new capabilities.

Choose a small number of high-value processes, such as fraud investigations, merchant underwriting, disputes or payment exceptions. Map how work happens today, identify where AI can help and design the controls alongside the new capabilities.

  • Evaluate more than productivity. Measure decision quality, explainability, exception rates and the level of human intervention alongside time saved or processing volume. Those measures help leaders understand whether AI is improving the workflow as a whole, not simply accelerating one step within it.

Evaluate more than productivity. Measure decision quality, explainability, exception rates and the level of human intervention alongside time saved or processing volume. Those measures help leaders understand whether AI is improving the workflow as a whole, not simply accelerating one step within it.

The opportunity ahead

Financial services has spent decades engineering control into payments, credit, risk and compliance. AI introduces a new layer of intelligence across those same processes, bringing opportunities to find patterns sooner, reduce manual effort and help employees make better-informed decisions.

The institutions that create lasting value will connect that capability to workflows designed to make decisions observable, explainable, controllable and accountable. That means treating governance as part of how work gets done: built into the flow of information, decisions, approvals and actions.

That’s why the next chapter of AI governance will require more than policy. It will require workflow engineering.

← All articles

What this article says

More in Software Development

All →
L3Harris Awarded Joint Capability Group Contract for Advanced Capability System Implementation
L3Harris

L3Harris Awarded Joint Capability Group Contract for Advanced Capability System Implementation

Payments Platforms Win by Expanding the Relationship
Endava

Payments Platforms Win by Expanding the Relationship

Real-Time Rails Are Not a Merchant Payment Product
Endava

Real-Time Rails Are Not a Merchant Payment Product

Payments at the Operating Core
Endava

Payments at the Operating Core

The Last Mile of B2B Payments Is an Adoption Problem
Endava

The Last Mile of B2B Payments Is an Adoption Problem

The Atlassian AI SDLC Index
Atlassian

The Atlassian AI SDLC Index

More from Endava

Payments Platforms Win by Expanding the Relationship
Endava

Payments Platforms Win by Expanding the Relationship

Real-Time Rails Are Not a Merchant Payment Product
Endava

Real-Time Rails Are Not a Merchant Payment Product

Payments at the Operating Core
Endava

Payments at the Operating Core

The Last Mile of B2B Payments Is an Adoption Problem
Endava

The Last Mile of B2B Payments Is an Adoption Problem

Payments Modernisation: Dealing With Complexity in Regulated Industries
Endava

Payments Modernisation: Dealing With Complexity in Regulated Industries

From AI Prototype to Production: Scaling AI in Payments
Endava

From AI Prototype to Production: Scaling AI in Payments