← Latest papers
💬 NLP

FinRAG-12B: A Production-Validated Recipe for Grounded Question Answering in Banking

FinRAG-12B is a production-validated, data-efficient 12B-parameter framework that combines a specialized training pipeline with calibrated refusal mechanisms to deliver highly accurate, grounded, and cost-effective question answering for over 40 financial institutions, outperforming GPT-4.1 in citation quality and query resolution while significantly reducing latency and operational costs.

Original authors: Denys Katerenchuk, Pablo Duboue, Keelan Evanini, David Gondek, Nithin Govindugari, Olivier Allauzen, Joshua Baptiste, David J More, Joshua Schechter

Published 2026-05-08
📖 5 min read🧠 Deep dive

Original authors: Denys Katerenchuk, Pablo Duboue, Keelan Evanini, David Gondek, Nithin Govindugari, Olivier Allauzen, Joshua Baptiste, David J More, Joshua Schechter

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are hiring a new assistant for a bank. You need someone who is incredibly smart, knows the bank's rules inside out, and—most importantly—never makes things up. If they don't know the answer, they must say, "I don't know," rather than guessing and giving you bad financial advice that could get the bank in trouble.

This paper introduces FinRAG-12B, a specialized AI assistant designed exactly for this job. Here is how the authors built it and why it works, explained simply.

The Problem: The "Over-Agreeable" Assistant

Standard AI models (like the ones you might chat with online) are great at writing stories or coding, but they have a bad habit in banking: they are too eager to please. If you ask them a question they can't answer from their memory, they often just make up a plausible-sounding answer. In a bank, this is dangerous. If a customer asks about mortgage penalties and the AI guesses wrong, it could lead to lawsuits or lost money.

The Solution: A "Recipe" for a Smart, Honest Assistant

The team created a 12-billion-parameter AI (think of this as a very large, but not gigantic, brain) and trained it using a specific "recipe" to fix these issues. They didn't just feed it a massive pile of data; they curated a high-quality, smaller dataset (only 143 million "tokens," or words) to teach it three specific skills:

1. The "Citation" Skill (Showing Your Work)

Imagine a student taking a test. A normal AI might just write the answer. FinRAG-12B is trained to act like a student who must show their work.

  • How they did it: They created a training pipeline where the AI had to answer questions using only specific documents provided to it (like a bank's policy manual).
  • The Result: When the AI answers, it points to the exact sentence in the document that supports its answer. It learned to say, "According to page 4 of the policy, the fee is $50," rather than just guessing. In tests, it was better at this than even the most advanced commercial AI models.

2. The "Honesty" Skill (Knowing When to Stop)

This is the most critical part. The team realized that if an AI is trained only on questions it can answer, it will never learn to say "I don't know."

  • The Analogy: Imagine a teacher who only asks questions the student knows the answer to. The student will never learn to admit ignorance.
  • The Fix: The team deliberately fed the AI 22% of questions where the answer wasn't in the provided documents. They taught it that in these cases, the correct answer is "I don't know."
  • The Result: The AI learned to be "calibrated." It refuses to answer when it's unsure (12% of the time), which is much safer than the base model (which guessed 95% of the time) and less annoying than other models that refuse too often (20% of the time).

3. The "Curriculum" Learning (Schooling the AI)

They didn't dump all the data on the AI at once. They used a "curriculum" approach, like a school system:

  • Stage 1 (General School): They taught the AI general financial language using open-source data. This gave it a solid foundation.
  • Stage 2 (Specialized Training): Then, they introduced it to real, private banking conversations and specific rules.
  • Why it matters: If they mixed these two types of data randomly, the AI got confused and performed poorly. By teaching it in stages, it learned the rules first, then how to apply them to real life.

Real-World Results: The "Live Test"

The authors didn't just test this in a lab; they deployed it in 40+ financial institutions. Here is what happened:

  • More Questions Solved: The new AI successfully answered 7.1% more customer questions than the old system without needing a human to step in.
  • Speed and Cost: It is 3 to 5 times faster than using a top-tier commercial AI API. More importantly, it costs 20 to 50 times less to run.
    • Analogy: Using the old commercial AI is like taking a private jet for a short trip to the grocery store. FinRAG-12B is like driving a reliable, efficient electric car. It gets you there faster and for a fraction of the price.
  • Customer Happiness: While the quality of individual answers didn't change drastically, customers were happier overall because more of their questions got answered successfully.

Summary

FinRAG-12B is a specialized banking AI that was trained to be honest, grounded, and efficient. By teaching it to cite its sources and admit when it doesn't know the answer, the authors created a system that is safer for banks, cheaper to run, and actually solves more customer problems than the "off-the-shelf" alternatives.

Note on Limitations: The authors are careful to say this was tested specifically on banking questions (like loans and accounts). They don't claim it works for stock trading or insurance yet, and they couldn't share their private training data due to privacy laws, though they did share their public training methods.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →