QuantCode-Eval: Benchmarking Quantitative Strategy Code Reproduction from Finance Papers
Open accessAbstract
Large language models (LLMs) have enabled impressive coding agents for various domains, driving growing interest in applying them to automate domain-specific workflows. In quantitative strategy development, a domain with high stakes and high potential returns, reproducing executable strategy code from financial papers and reports is valuable for both academic research and industrial gains. However, it remains unclear whether LLMs can faithfully reproduce such domain-knowledgeintensive strategy code from finance papers. These papers often omit critical implementation details, while high-quality strategy code is scarce as pretraining data for latest LLMs. This paper presents QuantCode-Eval, a benchmark for evaluating the ability of LLMs to reproduce strategies from 30 leading quantitative finance papers published (or released) between 2010 and 2026 into executable trading strategies. To support rigorous evaluation, each reproduction task includes around 20 property-based executable checkers that return a binary pass/fail result. We conduct extensive evaluation on 7 proprietary and open-source LLMs with coding-agent scaffolds. The results show that even the best-performing setup, Claude Opus 4.7 with Claude Code, achieves a 43% pass@5 rate when reproducing code that satisfies all properties. We also perform a fine-grained analysis of violated properties by jointly examining their semantics and the agent trajectories. Our findings reveal diverse failures in strategy-sensitive aspects: (i) maintaining temporal consistency, (ii) correctly interpreting and formalizing strategy definitions, and (iii) preserving the intended signal direction during trade execution.
Integrity signals
Registry
Cites
Statistics
Claims the paper makes
Claims other papers make about this one
Each is checked against this paper’s own text: does it say what the citing paper says it does?
QuantCodeEval [34], released in May 2026, is unlikely to have appeared in model training data.
“Moreover, QuantCodeEval [34], released in May 2026, is unlikely to have appeared in model training data.”
From Guiding Human Validation of LLM-Generated Code via Verifiable Literate Programming (2026) · cites this paper as [34]
Cited by
Sorted by citations
Guiding Human Validation of LLM-Generated Code via Verifiable Literate Programming
Yuan, Z., Lu, W., Wu, H., Jin, D., & Wu, C. (2026) · arXiv · doi:10.48550/arxiv.2607.02333
Self-citation
- Authors
- Lu, W., Yuan, Z., Wu, H., Jin, D., & Wu, C.
- Affiliations
- University of Hong Kong (HK)
- ORCID
- Venue
- SSRN Electronic Journal
- Publisher
- Elsevier BV
- Published
- 2026
- ISSN
- 1556-5068 (ISSN-L)
- OpenAlex
- W7161944925
- Cited by
- 0
- References
- 0
- Type
- posted content
- Language
- en
- Open access
- green
- doi.org
- Locations
- SSRN Electronic Journal (acceptedVersion)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Research
- Social Sciences › Decision Sciences › Information Systems and Management › Scientific Computing and Data Management
- Social Sciences › Decision Sciences › Management Science and Operations Research › Stock Market Forecasting Methods
- Keywords
- quantitative trading strategies, reproducibility, benchmarking
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review