Banking and financial services
A proposed workflow for banking and financial services. Revised 17 September 2026. The roles below are design options, not claims that these agents are deployed or that multiple agents are necessary.
The business opportunity
An analyst investigates an account-service or transaction exception. The task needs source records, the relevant policy, and an explanation a reviewer can check.
Start with the simplest useful solution
Compare the agent with existing case-management rules and analyst search tools. Use the same representative cases and count human review, errors, integration, and ongoing operation. Add an agent only where choosing what to investigate or handling varied evidence improves the result.
Proposed responsibilities
- Agent
- Servicing agent
- What it does
- Handles narrow, recoverable customer intents within the customer's own scope
- Autonomy and learning position
- A3, L2
- Notes
- Customer-facing lane, full control set
- Agent
- Financial crime investigation agent
- What it does
- Assembles alert context, retrieves history, drafts the narrative, proposes disposition
- Autonomy and learning position
- A3 on disposition proposal, L2
- Notes
- The strongest internal case in the vertical: alert volume is high, the labels are real, and the analyst stays the decider
- Agent
- Credit file assembly agent
- What it does
- Gathers, validates and structures the evidence a credit decision requires
- Autonomy and learning position
- A3, L1
- Notes
- Assembles evidence. Does not decide credit
- Agent
- Regulatory reporting draft agent
- What it does
- Drafts narrative against governed numbers
- Autonomy and learning position
- A1 to A2, L1
- Notes
- Drafts. Attestation is deterministic and human
- Agent
- Payment exception agent
- What it does
- Investigates failed and returned payments, proposes remediation
- Autonomy and learning position
- A3, L2
- Notes
- Remediation executes through mandate-bound authorisation
Start with one agent and ordinary tools. Separate a responsibility only when it needs different permissions, independent review, or its own operating schedule. The autonomy and learning positions are starting choices to test, not certification levels.
How the architecture supports the task
Identity and policy (direct: two deterministic zones plus model risk management), observability and audit trail (direct: several regimes at once), knowledge and memory (direct), tool gateway (direct), human oversight (direct), evaluation and release (direct), runtime (direct: sovereignty and classification routing).
Controls and human decisions
Keep credit decisions, payment authority, and regulated reporting under the institution's approved controls. Confirm the exact legal requirements for the intended jurisdiction and activity.
Give every tool call a task identity, a limited permission scope, and a recorded result. Before a write, check that the source record has not changed. Stop when required evidence is unavailable, the task budget is reached, or a proposal exceeds the authorised scope.
A useful investigation loop
Observe the exception, identify the missing fact, request that evidence, and check whether it changes the proposed action. Repeat only while there is a concrete unanswered question. End with a reviewed proposal, a confirmed result, or an explicit request for human help.
Economics and measures
Measure review quality, rework, analyst time, customer impact, and completeness of the decision record.
Agree the baseline with the process owner. Count value only after the outcome is confirmed. Compare the value of recovered time and improved outcomes with the full cost of tools, models, evidence preparation, supervision, and correction.
Limits to test
This is a design proposal, not evidence of regulatory compliance. A control at execution does not by itself protect against misleading information earlier in the workflow.
Evaluate ordinary cases, uncommon failures, conflicting evidence, and recovery after an interrupted action before expanding authority.
External reading
The workflow above is the guide's proposal. These sources support the general investigation and risk-management methods; they do not validate the proposed business result.
- ReAct: reasoning and acting with language models, 2022. Research basis for alternating reasoning and tool use.
- NIST AI Risk Management Framework, 2023. General framework for managing AI risks.
Sources reviewed 17 September 2026.
Cite this page
Written by Murali Sid, Founder and AI Systems Architect, last updated 15 October 2026. Licensed CC BY-SA 4.0, so quote it freely with attribution.
Murali Sid (2026). Banking and financial services. Agentic Architecture Skills. https://www.agenticarchitectureskills.com/library/blueprints/verticals/banking-and-financial-servicesMachine-readable version of this page: /library/blueprints/verticals/banking-and-financial-services.md
Manufacturing and supply chain
A proposed workflow for manufacturing and supply chain. Revised 17 September 2026. The roles below are design options, not claims that these agents are deployed or that multiple agents are necessary.
Public sector
A proposed workflow for public sector. Revised 17 September 2026. The roles below are design options, not claims that these agents are deployed or that multiple agents are necessary.