Papers › ConvFinQA: Exploring the Chain of Numerical Reasoning in Conversational Finance...

ConvFinQA: Exploring the Chain of Numerical Reasoning in Conversational Finance Question Answering

7 Oct 2022arXiv:2210.03849archive 2025-07-28

Zhiyu Chen, Shiyang Li, Charese Smiley, Zhiqiang Ma, Sameena Shah, William Yang Wang

With the recent advance in large pre-trained language models, researchers have achieved record performances in NLP tasks that mostly focus on language pattern matching. The community is experiencing the shift of the challenge from how to model language to the imitation of complex reasoning abilities like human beings. In this work, we investigate the application domain of finance that involves real-world, complex numerical reasoning. We propose a new large-scale dataset, ConvFinQA, aiming to study the chain of numerical reasoning in conversational question answering. Our dataset poses great challenge in modeling long-range, complex numerical reasoning paths in real-world conversations. We conduct comprehensive experiments and analyses with both the neural symbolic methods and the prompting-based methods, to provide insights into the reasoning mechanisms of these two divisions. We believe our new dataset should serve as a valuable resource to push forward the exploration of real-world, complex reasoning tasks as the next research focus. Our dataset and code is publicly available at https://github.com/czyssrs/ConvFinQA.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 8 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 8 samples from 1 repository, 7 ran (6 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 7 samples that ran has no recorded date.

czyssrs/convfinqa officialmentioned in papermentioned on GitHubpytorchMITSyntology: 8 samples, 7 ran (1 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

8 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
6ran
1unverified

Licence: 1 of the 8 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from czyssrs/convfinqa. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

czyssrs/convfinqa official repository 8 samples, 7 ran (1 instrument-failed) · 1 unverified
cleanhtml code/utils/general_utils.py ran fingerprinted MIT (permissive) · c7368d407afb9277 · report fixture: signature raw_html:str/0/str · returned str · level recorded 2026-09-25
format_time in 140 papers code/finqanet_generator/utils.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 8d7ec010c29e813b · report fixture: signature seconds:float/0/float · returned str · level recorded, date not recorded
prog_token_to_indices code/finqanet_generator/finqa_utils.py ran MIT (permissive) · 21ff8e9f6a35119e · report fixture: signature prog:list/1/str, numbers:list/1/str, number_indices:list/1/int, max_seq_length:int/0/int, op_list:list/1/str, op_list_size:int/0/int, const_list:list/1/str, const_list_size:int/0/int · returned list · level recorded 2026-09-25
read_txt in 41 papers code/finqanet_generator/utils.py ran MIT (permissive) · 5312b6b693f09d8e · report fixture: signature input_path:str/0/str, log_file:str/0/str · returned list · level recorded 2026-09-25
remove_space in 7 papers code/utils/general_utils.py ran fingerprinted MIT (permissive) · edc24c5af3e1a7cd · report fixture: signature text_in:str/0/str · returned str · level recorded 2026-09-25
str_to_num code/finqanet_generator/finqa_utils.py ran fingerprinted MIT (permissive) · 227ac417efac55e8 · report fixture: signature text:str/0/str · returned int · level recorded 2026-09-25
table_row_to_text code/utils/general_utils.py ran MIT (permissive) · 3c93e9aa942bd60c · report fixture: signature header:list/1/str, row:list/1/str · returned str · level recorded 2026-09-25
indices_to_prog code/finqanet_generator/finqa_utils.py unverified MIT (permissive) · 6b93716e4bdcdfde · report

Tasks

Conversational Question AnsweringQuestion Answering

Datasets

Introduced by this paper, per the archive.

ConvFinQA

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Conversational Question Answering ConvFinQA FinQANet (RoBERTa-large) Execution Accuracy 68.90 #2 of 2 Archive leaderboard report
Conversational Question Answering ConvFinQA FinQANet (RoBERTa-large) Program Accuracy 68.24 #2 of 2 Archive leaderboard report
Question Answering ConvFinQA FinQANet (RoBERTa-large) Execution Accuracy 68.9 #2 of 3 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections