A leaderboard is a screening tool, not a model approval.
Use public benchmarks to screen models; approve deployments with bank-owned use-case, control and operational tests.
Use public benchmarks to screen models; approve deployments with bank-owned use-case, control and operational tests.
Read across 18 workflows spanning customer, product, markets, finance, risk and enterprise operations. The taxonomy is condensed from the BIAN 14.0 service landscape ↗; every cell opens the catalogue at the relevant workflow and evaluation layer.
Public evidence is labelled direct, adjacent or absent| Financial-services workflow | External screenPublic benchmarks and standards used to shortlist systems. | Golden setRepresentative institution-owned cases for the intended use. | ControlsSafety, conduct, security and policy-boundary testing. | OperationalWorkflow, tool-use, cost, latency and human-escalation evidence. | ContinuousRepeatable regression and production-change evaluation. |
|---|---|---|---|---|---|
| Customer & distribution | |||||
| Customer service, complaints & conductIntent, service resolution, complaints, vulnerable customers and policy-bound conversations.Direct | 3assets | RequiredInstitution-owned | 1assetAdjacent only | 2assets | —No mapped asset |
Learn the concepts in four minutes: what a benchmark is, what an eval adds, how evidence moves from market comparison to bank approval, and how to challenge a headline score.
Open the full glossary →A benchmark is a standardised test: the same tasks, conditions and scoring method are applied to multiple models or systems.
Use public benchmarks to shortlist models and expose obvious weaknesses.
Understand this layer →02Use-case golden setTest representative, difficult and high-risk cases drawn from the bank's work.
Understand this layer →03Controls & adversarialProbe leakage, entitlements, prompt injection, conduct, bias and unsafe actions.
Understand this layer →04Operational fitnessMeasure latency, cost, availability, fallbacks, auditability and human escalation.
Understand this layer →05Continuous evaluationRerun on model, prompt, data, tool and policy changes; monitor production drift.
Understand this layer →Filter by financial-services workflow, capability area or evaluation type. Open any entry for measured capability, recommended banking use, metrics, limitation and primary source.
Primary sources linked| Compare | ||||||||
|---|---|---|---|---|---|---|---|---|
| Public benchmark | Finance & investment, Legal & compliance, Operations & agents | Onboarding, KYC & customer due diligence, Lending, credit & collections +4 | Growing | Open source | 2026-08-21 | The FinAI Open ↗ | ||
| Public benchmark | Finance & investment, Legal & compliance, Operations & agents | Onboarding, KYC & customer due diligence, Payments, cards, fraud & scams +1 | Growing | Open source | 2026-08-21 | Feedzai Research Open ↗ | ||
| Public benchmark | Legal & compliance | Financial crime, sanctions & compliance, Internal audit & assurance +1 | Established | Open dataset | 2026-07-25 | Stanford and legal contributors Open ↗ | ||
| Public benchmark | Finance & investment, Knowledge & RAG, Operations & agents | Onboarding, KYC & customer due diligence, Corporate, commercial & trade finance +5 | Emerging | Open source | 2026-07-26 | Databricks Open ↗ | ||
| Assurance standard | Finance & investment, Legal & compliance, Operations & agents | Risk, model risk & stress testing, Financial crime, sanctions & compliance +1 | Established | Public methodology | 2026-08-21 | Prudential Regulation Authority Open ↗ |
The FinAI
Open credit and risk evaluation covering credit scoring, fraud detection, financial distress and insurance claim classification across nine datasets.
Onboarding, KYC & customer due diligence · Lending, credit & collections · Payments, cards, fraud & scams · Insurance underwriting, pricing & claims · Risk, model risk & stress testing · Financial crime, sanctions & compliance
Use as a tabular-risk and fairness screen before testing institution-specific lending, fraud, collections and underwriting decisions.
Latest evidence from the existing OneBench source network that explicitly concerns model evaluation, benchmarks, assurance, red-teaming or measurable AI quality.
Updated with the main intelligence pipelineFinTrace benchmark introduces trajectory-level evaluation for LLM tool-calling in long-horizon financial tasks, addressing limitations of call-level metrics.
Open source ↗Research proposes a new method, "Behavioral Canaries," to audit if private retrieved contexts are illicitly used in LLM RL fine-tuning.
Open source ↗FinGround is a new research method to detect and ground financial hallucinations in LLMs by verifying atomic claims against regulatory filings, improving accuracy by 43%.
Open source ↗Research identifies a benchmark, CiteAudit, to detect hallucinated citations from LLMs, which are present in scientific submissions.
Open source ↗Research introduces CoRT, a black-box multi-turn red-teaming framework to find concealed regulatory-violating risks in financial LLMs.
Open source ↗OneBench includes a benchmark when its dataset, code or methodology is publicly inspectable, or when it provides a useful assurance pattern for a regulated enterprise. “Established” describes reuse and methodological maturity, not regulatory approval. Catalogue entries are editorial assessments; live stories link to the underlying publication. Public benchmark results should always be checked for dataset contamination, judge-model bias, version mismatch and unreported inference budgets.
The daily briefing flags material benchmark and assurance developments. For catalogue governance or team access, speak to OneBench directly.
Free. Daily at 06:30 UK. Unsubscribe with one click.
| Products & balance sheet |
|---|
| Lending, credit & collectionsOrigination, underwriting, affordability, credit monitoring, early warning, collections and recoveries.Direct | 4assets | RequiredInstitution-owned | 1asset | 1asset | —No mapped asset |
|---|
| Markets & investing |
|---|
| Finance, risk & control |
|---|
| Enterprise operations |
|---|
“Direct” means at least one public asset tests the named workflow. “Adjacent” means the asset tests a transferable capability, not the banking workflow itself. A count is not a quality score.
Research identifies and evaluates 'sycophancy' in LLMs within agentic financial tasks, where models prioritize agreement over correctness.
© 2026 OneBench: AI Insights. All rights reserved.
Evidence before opinion