Historical VaR has a fatal flaw: it can only ever show you tomorrows that already happened. Your one year of data is your one year of data — 252 days, take it or leave it, and the crash you’re really afraid of probably isn’t in there. Parametric VaR fixes the data shortage by assuming a tidy normal bell curve, but then it lies about anything non-linear (hello, options). Monte Carlo VaR is the method that says: fine — if reality won’t give me enough tomorrows, I’ll manufacture them.
The trick is gloriously simple in spirit. Pick a statistical model for how your risk factors move. Use a random-number generator to roll thousands of synthetic tomorrows out of that model. Reprice your entire portfolio in each one. Now you have ten thousand fake P&Ls — sort them, walk into the loss tail, and read off the percentile. It’s historical VaR, except the history is one you invented, and you can invent as much of it as your laptop can stand.
Before you read — take a guess
What is the core idea of Monte Carlo VaR?
Simulate a thousand tomorrows
Analogy. A pilot doesn’t wait for ten real engine fires to learn how the plane handles one — she runs the flight simulator a thousand times, each with slightly different gremlins. Monte Carlo VaR is the flight simulator for your portfolio: you can’t afford to live through ten thousand market days, so you generate them in software and watch how your book reacts.
Definition. Monte Carlo VaR estimates Value at Risk by (1) choosing a statistical model for the risk factors that drive your portfolio, (2) drawing many random scenarios from that model, (3) revaluing the full portfolio in each scenario to get a profit-or-loss, and (4) taking the appropriate percentile of that simulated loss distribution. The name comes from the casino — it’s the dice-rolling, random-sampling family of methods, applied to risk.
A risk factor is any market variable your portfolio’s value depends on: a stock price, an FX rate, an interest rate, an implied volatility. The model is your assumption about how those factors move — most commonly that one-day returns are normal (or that prices are lognormal, i.e. their logs are normal, which keeps prices positive) with a chosen mean , volatility , and — when you have more than one factor — a correlation matrix tying them together so they move realistically in lockstep rather than independently.
That correlation piece is the soul of the method for a real book. If your portfolio holds tech and oil, and your simulator lets them wander independently, you’ll badly misjudge the days they crater together. The correlation matrix is what makes your synthetic tomorrows hang together like real market days.
Why does a multi-asset Monte Carlo VaR need a correlation matrix and not just each asset’s own σ?
The recipe, step by step
Here is the whole method as a five-step cookbook. Memorise the shape — every Monte Carlo VaR engine on earth is some elaboration of these five lines.
- Specify the model and its parameters. Decide the distribution (e.g. lognormal prices), and pin down each factor’s and plus the covariance/correlation matrix linking them. This is the one creative, dangerous step — everything downstream inherits whatever you assume here.
- Generate scenarios. Draw random scenarios — say — from that model. Each scenario is one synthetic “tomorrow”: a complete set of new values for every risk factor, drawn jointly so the correlations hold.
- Fully reprice the portfolio under each scenario. For every one of the scenarios, recompute the portfolio’s value with the new factor values, and subtract today’s value to get that scenario’s P&L. “Fully” is the operative word — you re-run each instrument’s actual pricing formula, not a linear approximation.
- Sort the P&Ls from worst to best. You now hold an empirical distribution of simulated outcomes — a histogram of ten thousand fake tomorrows.
- Read the percentile. The VaR at confidence is the loss at the percentile of that sorted list. For and , that’s the 100th-worst simulated loss (1% of 10,000) — every scenario below it is in the tail.
The chart below is exactly the object you build in steps 4–5: the histogram of simulated outcomes, with the VaR line sitting at the chosen percentile and the loss tail beyond it shaded. Drag the confidence slider and watch the line march deeper into the manufactured tail.
Ten thousand synthetic tomorrows pile up into this distribution. VaR is the percentile line; everything to its left is the simulated loss tail. Crank the confidence and the line slides further into the tail you manufactured.
Fill in the Monte Carlo VaR recipe.
Pick the right option for each blank, then check.
First specify the , then generate , then the portfolio under each, sort the P&Ls, and read VaR as the of the simulated losses.
The killer feature: nonlinear portfolios
This is the reason Monte Carlo VaR exists, and the one argument that wins the meeting. Parametric (delta-normal) VaR approximates every position as a straight line: it takes each instrument’s delta (its first-order sensitivity to the underlying) and assumes the P&L is just delta × move, with moves drawn from a normal bell. That’s fine for a portfolio of plain stocks, whose payoff really is a straight line. It is dangerously wrong for options.
Analogy. Parametric VaR draws the tangent line to a curve and pretends the curve is the line. Near the touch point, the lie is harmless. Out in the tail — exactly where VaR lives — the curve has peeled far away from its tangent, and the line is telling you a fairy tale.
An option’s payoff curves: it has gamma, the curvature of its value as the underlying moves (delta’s own rate of change). Monte Carlo doesn’t approximate — in step 3 it fully reprices every option at each simulated price, running the actual pricing model. So when a scenario throws a violent move, the simulated P&L reflects the option’s true curved payoff, gamma and all. The tail of an optioned book — short straddles, structured notes, anything convex — comes out right instead of linearised into nonsense.
Worked intuition. You’re short a put, delta today, on a $100 stock. Parametric VaR sees a 10% down-move and predicts a loss of about 0.5 × $10 = $5 per share — straight-line. But as the stock falls, the put’s delta steepens toward (that’s gamma at work), so the real loss accelerates past $5, maybe to $8 or $9 per share. Monte Carlo, repricing the put at the simulated $90, sees that accelerating loss. Delta-normal never does — it’s still riding its flat tangent line off the cliff, reporting a comfortable number while the real book bleeds.
Spot the trap. A risk team runs delta-normal (parametric) VaR on a book stuffed with short options and reports a reassuringly small number. What’s the danger?
Convergence and standard error
Monte Carlo gives a different answer every time you run it, because it’s built on random draws. Run 10,000 paths today and 10,000 tomorrow and your VaR estimate wobbles a little between them. That wobble is sampling error, and the central fact about it is how it shrinks.
Definition. The standard error of a Monte Carlo estimate falls like , where is the number of paths. In plain terms: to halve the error, you must quadruple the paths. Accuracy is expensive — it improves only with the square root of effort, so the last digit of precision costs brutally more compute than the first.
Analogy. It’s like polling. A poll of 10,000 people isn’t twice as precise as one of 5,000 — it’s only about times as precise. Doubling the sample barely moves the margin of error; you have to quadruple it to cut that margin in half. Monte Carlo paths are voters, and the VaR is the election.
Worked example. Suppose at paths your VaR estimate has a sampling standard error of $1.0 million. Push to — a 4× increase. The error scales by , so it drops to about $0.5 million. Quadruple the work, halve the noise. Want to halve it again, down to $0.25 million? That’s another 4×, to 160,000 paths. The compute bill compounds fast.
Because brute force is so costly, quants reach for variance-reduction tricks — ways to get the same accuracy from fewer paths:
- Antithetic variates. For every random scenario you draw, also use its mirror image (flip the sign of the random shocks). The pair partly cancels each other’s noise, so the average converges faster.
- Control variates. Lean on a related quantity whose answer you know exactly (say, the parametric VaR of a simplified version), and use the known error in that to correct your simulated estimate.
You don’t need to implement these today — just know they exist, and that a good engine reaches a target precision with far fewer paths than the naive count would demand.
Fill in the convergence rule.
Pick the right option for each blank, then check.
Monte Carlo sampling error shrinks like , so to the error you must the number of paths. reach the same accuracy with fewer paths.
Your Monte Carlo VaR has a sampling error of $800k at 25,000 paths. Roughly how many paths do you need to cut that error to about $400k?
Strengths and weaknesses
Monte Carlo is the most flexible VaR method, full stop. You can feed it any distribution — fat-tailed Student-t instead of the thin-tailed normal, skewed, regime-switching, whatever fits the data. It handles non-linearity (options, convexity) by full repricing. It handles path-dependence (barrier options, anything whose payoff depends on the route, not just the endpoint) by simulating whole paths. Multiple correlated factors? Just enlarge the covariance matrix. Nothing else in the VaR toolkit is this general.
But that power comes with two heavy tolls.
The first is the one that bites in practice: it is only as good as the model you feed it. A normal model with too-low a , a stale correlation matrix, or a thin-tailed distribution doesn’t produce a vague or uncertain VaR — it produces a confidently precise wrong number. Ten thousand beautifully-sorted scenarios drawn from a bad model give you ten thousand beautifully-sorted lies. The pretty histogram launders the bad assumption into something that looks rigorous.
The second is mundane but real: it’s compute-heavy. Full repricing of a large book across tens of thousands of paths — sometimes nested, if instruments themselves need simulation to price — can mean millions of valuations per VaR run. Historical and parametric VaR are nearly free by comparison.
Garbage in, garbage out — at high resolution
Monte Carlo’s realism is a trap as much as a feature. The polished, ten-thousand-path histogram looks authoritative no matter what went in — but if you fed it the wrong σ, a stale correlation matrix, or a thin-tailed normal where the real returns have fat tails, every digit of that VaR is wrong with total confidence. The method never warns you; it just renders your assumption in high resolution. Stress-test the inputs, not only the output, and never mistake a precise number for an accurate one.
Match each Monte Carlo property to what it buys you (or costs you).
Pick a term, then click its definition.
The three methods, side by side
You now hold all three VaR engines. Here’s the cheat-sheet that decides which to reach for.
| Historical | Parametric (delta-normal) | Monte Carlo | |
|---|---|---|---|
| Distribution assumption | None — uses the actual past returns | Assumes normal returns | Any chosen model (normal, t, custom) |
| Handles non-linearity? | Yes (reprices on real past moves) | No — linearises via delta | Yes — full repricing each scenario |
| Data / compute cost | Cheap; limited by data length | Cheapest — a formula and a z-score | Most expensive — many full revaluations |
| Fat-tail capture | Only tails that actually occurred | Poor — thin normal tails | As good as the distribution you pick |
The quick read: parametric is the fast, cheap default for linear books; historical is the assumption-light choice when you trust your data window and your book isn’t wildly optioned; Monte Carlo is the heavyweight you bring out for non-linear, multi-factor, fat-tailed books where getting the tail right is worth the compute.
Which VaR method best fits each job?
Place each item in the right group.
- Reuse real past moves, modestly non-linear book
- A linear FX book where speed beats tail precision
- A simple long-only equity book, need a number in seconds
- Trust the last year’s returns, want no distribution assumption
- Many correlated factors with fat-tailed returns to model
- A book full of exotic options needing full repricing
Why not always just use Monte Carlo, since it’s the most general?
Because generality isn’t free. Monte Carlo costs the most compute, demands the most modelling judgement (you must choose the distribution and estimate the covariance), and rewards a bad choice with a confidently wrong answer. For a plain linear book, parametric VaR gives essentially the same number in a millisecond with one formula — running 50,000 full revaluations to confirm what a z-score already told you is wasted effort. Use the heaviest tool only when the book’s non-linearity, fat tails, or path-dependence actually demand it. The right method is the lightest one that doesn’t lie about your particular portfolio.
Putting it together
Monte Carlo VaR manufactures the tomorrows reality won’t give you: pick a model, roll random scenarios, fully reprice the book in each, sort the P&Ls, and read the percentile of the losses. Its superpower is non-linearity — full repricing captures the gamma curvature that delta-normal linearises away — and its flexibility extends to any distribution, correlation structure, or path-dependence you can model. Its price is compute and, more insidiously, total dependence on the input model: feed it garbage and it returns a beautifully-rendered, high-confidence lie.
Big picture
Monte Carlo VaR — the whole engine
- Monte Carlo VaR
- The recipe
- Specify model + parameters + covariance
- Generate M scenarios (e.g. 10,000)
- Fully reprice the portfolio in each
- Sort the P&Ls
- VaR = the (1−c) percentile loss
- Killer feature
- Full repricing captures non-linearity
- Gamma curvature gets the option tail right
- Parametric linearises and understates it
- Convergence
- Error shrinks like 1/√M
- Quadruple paths to halve the error
- Variance reduction: antithetic, control variates
- Strengths and weaknesses
- Most flexible: any distribution, fat tails, paths
- Garbage in, garbage out — model-dependent
- Compute-heavy: many full revaluations
- The recipe
Recap: Monte Carlo VaR
In the Monte Carlo recipe, what does "fully reprice the portfolio under each scenario" mean?
Check your answer to continue.
Next up — Expected Shortfall (CVaR) — we confront VaR’s deepest flaw: it tells you the line you rarely cross, but says nothing about how bad it gets once you do. A $10M VaR is identical whether the worst 1% averages an $11M loss or a $100M wipeout. Expected Shortfall answers the question VaR ducks — given we’ve blown past the threshold, what’s the average loss in that tail? — and it’s exactly the shaded region you’ve been watching to the left of every VaR line.