Could Large Language Models work as Post-hoc Explainability Tools in Credit Risk Models?
This study evaluates the use of large language models as post-hoc explainability tools for credit risk models and concludes that while they can reliably reproduce feature-importance rankings under controlled prompts, they are best deployed as narrative interfaces rather than as substitutes for formal attribution methods due to limited alignment in autonomous explanation generation.
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 a loan officer at a bank. You have a super-smart, but mysterious, computer robot (a "machine learning model") that decides who gets a loan and who doesn't. This robot is great at predicting who will pay back the money, but it's a "black box." It gives you a "Yes" or "No," but it doesn't speak human. It just gives you a list of numbers saying, "This factor mattered 5%, that one mattered 3%."
Regulators and customers, however, don't want to see a spreadsheet of numbers. They want a story: "We denied this loan because the applicant has too much debt and a shaky job history."
Enter Large Language Models (LLMs). Think of these as the "translators" or "storytellers" of the AI world. They are the ones who can take those boring numbers and turn them into a friendly, readable paragraph.
This paper asks a very specific question: Can we trust these AI storytellers to tell the truth about why the robot made its decision?
The researchers set up two different tests to find out, using real loan data from LendingClub.
Test 1: The "Dictation" Test (Can the LLM follow orders?)
The Setup: The researchers gave the AI storyteller the exact list of reasons the robot used, ranked from most important to least important. They then asked the AI: "Here is the list of reasons. Please rewrite this list as a story, but make sure you keep the exact same order."
The Result: The AI storytellers were perfect.
Imagine a strict teacher handing a student a list of 24 ingredients and saying, "Write a recipe using these, in this exact order." The AI did exactly that. It didn't swap ingredients, it didn't forget any, and it didn't add its own ideas. It faithfully translated the robot's "number list" into a "word list" without changing the meaning.
The Takeaway: If you give the AI the facts, it is excellent at formatting them into a human-readable story. It acts like a very reliable secretary.
Test 2: The "Detective" Test (Can the AI figure it out on its own?)
The Setup: This time, the researchers did not give the AI the list of reasons. They just gave the AI the applicant's data (income, credit score, etc.) and the robot's decision. They asked: "Based on this person's data, what do YOU think the top reasons for this decision are?"
The Result: The AI storytellers struggled.
Imagine asking a detective to solve a crime without showing them the police report. The AI tried to guess the reasons based on what it knows about the world in general (like, "Oh, usually high debt is bad").
- The Problem: The robot (the machine learning model) makes decisions based on complex, hidden patterns that are different from general human logic. The AI's guesses often missed the mark.
- The "Few-Shot" Trick: The researchers tried helping the AI by showing it two examples first (like, "Here is how we explained a 'Yes' loan, and here is how we explained a 'No' loan"). This helped a little bit, but the AI still couldn't perfectly match the robot's actual reasoning, especially for the more complex robot models.
The Takeaway: When the AI tries to act as a detective and figure out the reasons on its own, it often gets the story wrong. It might pick plausible-sounding reasons, but they aren't the actual reasons the robot used.
The Final Verdict: The "Translator" vs. The "Detective"
The paper concludes with a clear rule for how to use these tools in the banking world:
- Do NOT use the AI as a Detective: You cannot let the AI guess why a loan was denied. If you do, you might give a customer a reason that sounds good but is actually false. This is dangerous for regulations and trust.
- DO use the AI as a Translator: You can use the AI to take the official, mathematically proven reasons (calculated by the robot) and turn them into a nice, easy-to-read letter for the customer.
The Metaphor:
Think of the Machine Learning Model as a Chef who cooks a complex dish.
- The AI Translator is a Food Critic who is excellent at describing the dish if the Chef gives them the recipe. They can write a beautiful menu description.
- But if you ask the Food Critic to guess the recipe just by tasting the food (without the Chef's help), they will likely get the ingredients wrong.
In short: Large Language Models are great at turning math into words, but they are terrible at guessing the math in the first place. In credit risk, you must always let the math (the robot) decide the reasons, and let the AI just write the story.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.