Quant Memo
Core

Utility-Based Model Evaluation

Accuracy and AUC treat every mistake as equally bad, but in trading and risk the cost of a false positive and a false negative are almost never the same — evaluating a model on its actual economic payoff often changes which model wins.

Prerequisites: Objective Functions vs Evaluation Metrics

Two credit models are compared on accuracy and the second one wins, 91% versus 89%. A firm deploys it and loses more money than the first model would have. This happens more often than it should, because accuracy — and most standard classification metrics — silently assumes that every kind of mistake costs the same. In finance that assumption is almost never true: missing a default costs far more than declining a good borrower; missing a fraud alert costs far more than a false alarm that an analyst spends five minutes dismissing. Utility-based evaluation replaces "how often is the model right" with "how much money does using this model actually make or lose."

From a confusion matrix to a dollar figure

Any binary classifier's mistakes fall into four buckets: true positives, false positives, true negatives, and false negatives (see the confusion matrix for the mechanics). Standard accuracy just counts how many predictions land in the "correct" buckets. Utility-based evaluation instead assigns a payoff to each of the four buckets — a benefit for the two correct outcomes, a cost for the two wrong ones — and sums the model's total expected value across a population of decisions, rather than its hit rate.

U=nTPvTP+nFPvFP+nTNvTN+nFNvFNU = n_{TP}\, v_{TP} + n_{FP}\, v_{FP} + n_{TN}\, v_{TN} + n_{FN}\, v_{FN}

In words: take the count of predictions in each of the four buckets, multiply each count by that bucket's dollar payoff (positive for the two correct buckets, negative for the two wrong ones), and add them up. This total is what actually matters to a desk — not the raw count of right-versus-wrong calls, which treats a missed $2 million default identically to a wrongly declined $5,000 loan.

Worked example: two models, one clear winner once cost enters

A default-prediction model is tested on 1,000 loan applications. Suppose catching a true default correctly (true positive) saves the firm an average $8,000 in avoided losses net of the lost interest income; a missed default (false negative) costs $40,000 on average; wrongly declining a good borrower (false positive) costs $500 in lost profit; correctly approving a good borrower (true negative) is worth $300 in expected profit.

Model A: 850 true negatives, 90 true positives, 40 false positives, 20 false negatives. Accuracy = (850+90)/1000 = 94%. Model B: 800 true negatives, 100 true positives, 90 false positives, 10 false negatives. Accuracy = (800+100)/1000 = 90%.

By accuracy, Model A wins. By utility:

Model A: 90(8000)+40(500)+850(300)+20(40000)=720,00020,000+255,000800,000=155,00090(8000) + 40(-500) + 850(300) + 20(-40000) = 720{,}000 - 20{,}000 + 255{,}000 - 800{,}000 = 155{,}000. Model B: 100(8000)+90(500)+800(300)+10(40000)=800,00045,000+240,000400,000=595,000100(8000) + 90(-500) + 800(300) + 10(-40000) = 800{,}000 - 45{,}000 + 240{,}000 - 400{,}000 = 595{,}000.

Model B, with lower accuracy, generates roughly $595,000 in expected value against Model A's $155,000 — because Model B catches more of the expensive false negatives even at the cost of more cheap false positives. Accuracy picked the wrong model.

Accuracy Utility (\$) A 94% B 90% A 155k B 595k
Model A wins on accuracy; Model B wins on expected dollar value by nearly 4x, because it catches more of the costly missed defaults.

A metric that weighs every mistake equally is a modeling choice, not a neutral default. When the real costs of a false positive and a false negative differ — which in finance they almost always do — evaluate on expected utility, not accuracy or F1, or you can end up selecting the worse model.

What this means in practice

Utility-based evaluation also changes how a decision threshold should be chosen: the threshold that maximizes accuracy is not, in general, the threshold that maximizes expected utility, because shifting the threshold trades false positives for false negatives at a rate that depends on the class costs, not on the raw counts (see decision thresholds and cost-sensitive learning). The practical challenge is that the cost figures themselves — what a missed default really costs on average, what a false alarm really costs in analyst time — are estimates, often rough ones, and utility-based evaluation is only as good as those estimates. A sensitivity check, rerunning the comparison across a plausible range of cost assumptions, is standard practice before trusting a utility-based model choice.

Practice

  1. In the worked example, if the cost of a missed default were only $10,000 instead of $40,000, would Model B still win? Recompute both utilities.
  2. Explain why the "best" decision threshold for a fraud model is not, in general, the threshold that maximizes precision or recall in isolation.

The common mistake is comparing models on AUC or accuracy because those numbers are easy to report on a slide, then deploying the winner without ever translating the confusion matrix into the actual costs the business faces. A model can look strictly better on every standard classification metric and still destroy more value once the asymmetric costs of the two mistake types are accounted for.

Related concepts

Practice in interviews

Further reading

  • Elkan, The Foundations of Cost-Sensitive Learning (2001)
ShareTwitterLinkedIn