TASK 1 / SUBMISSION

Submit Task 1 predictions on the web.

All train, development, and test files are available from the participant hub. No pre-registration or access code is required; submit directly through the separate development and test pages.

Access: Open · no team code
Development: Scores + receipt + rank
Test: Format check + receipt

Test resubmissions: unlimited before the deadline

You may submit revised Test predictions as often as needed before 15 October 2026, 23:59 Anywhere on Earth. There is no daily or total Test submission quota. Keep the same Team Name and Contact Email for all revisions.

Your latest accepted, valid submission before the deadline replaces earlier accepted submissions for final evaluation. An invalid or rejected upload does not replace your last accepted submission. Save each acceptance receipt.

Uploading an identical previously accepted file returns its original receipt and acceptance time; it does not create a new revision or change which submission is latest. Earlier records are retained privately for the competition audit trail. Test scores and ranks remain hidden until final results.

Policy updated 16 September 2026, replacing the previous Test submission-count limits.

HOW TO SUBMIT

Six steps from data to receipt

Follow the phase-specific filenames exactly. Competition predictions and the challenge paper use different submission routes.

Step 1 of 6: Choose a consistent team name.
No pre-registration, approval, access code, or account is required. Choose one Team Name and use it consistently for development and test submissions. The test page also asks for a Contact Email for submission identification, submission-related support, matching final results to the related challenge paper, and selection of the latest accepted test submission and handling repeat uploads through a non-public pseudonymous identifier; the email is not a login and is never published.
Step 2 of 6: Download the correct phase files.
Development: leaderboard_questions.jsonl and leaderboard_expected_ids.json. Do not use dev_questions.jsonl for the 580-row leaderboard upload.
Test: test_questions.jsonl and test_expected_ids.json.
Use the matching expected-IDs file as your checklist: include exactly one prediction for every listed case_id, with no missing, duplicate, or additional IDs.
03
Step 3 of 6: Create predictions.jsonl.
Write one JSON object for every expected case ID: 580 rows for development or 928 rows for test. Every row uses exactly schema_version, dataset_version, case_id, final_answer, and steps.
Start from the sample predictions and check the prediction schema. If useful, generate a separate blank template below, then save your completed system output as predictions.jsonl. The blank template is a format example, not a competitive prediction file.
Optional development template
```
python3 scripts/task1_cli.py baseline-b0 --questions public/task1/data/development/leaderboard_questions.jsonl > blank_predictions.jsonl
```
Optional test template
```
python3 scripts/task1_cli.py baseline-b0 --questions public/task1/data/test/test_questions.jsonl > blank_predictions.jsonl
```

Step 4 of 6: Validate and package one canonical ZIP.

Clone or download the public participant toolkit, run the commands for your phase, and continue only when both validation commands report valid: true and the package command reports status: PASS. The ZIP must contain exactly one root-level file named predictions.jsonl. If an old submission.zip exists, remove or rename it before running the package command.

Development · 580 rows

python3 scripts/task1_cli.py validate --questions public/task1/data/development/leaderboard_questions.jsonl --predictions predictions.jsonl
python3 scripts/task1_cli.py package --questions public/task1/data/development/leaderboard_questions.jsonl --predictions predictions.jsonl --output submission.zip
python3 scripts/task1_cli.py validate-zip --questions public/task1/data/development/leaderboard_questions.jsonl --submission-zip submission.zip

Test · 928 rows

python3 scripts/task1_cli.py validate --questions public/task1/data/test/test_questions.jsonl --predictions predictions.jsonl
python3 scripts/task1_cli.py package --questions public/task1/data/test/test_questions.jsonl --predictions predictions.jsonl --output submission.zip
python3 scripts/task1_cli.py validate-zip --questions public/task1/data/test/test_questions.jsonl --submission-zip submission.zip

Step 5 of 6: Upload submission.zip on the matching webpage.
Development: enter Team Name and select the single submission.zip file. Test: enter the same Team Name, provide a Contact Email, and select the single submission.zip file. Choose Submit once and do not upload individual JSONL files.
Development upload (opens in a new tab)Test upload (opens in a new tab)
Step 6 of 6: Check the correct result.
Development:wait for the result to show the Final answer score, Reasoning steps score, receipt ID, and current rank; the team's best eligible result also appears on the public development leaderboard. Test: check the format feedback and acceptance status, then save the receipt ID when accepted; no test score, rank, answer-correctness feedback, or score-derived signal is shown before the final results are released.

Challenge paper is separate.

Submit the paper PDF through CyberChair SC03, using the IEEE two-column conference template. The FinReason Cup requirement is no more than ten pages total, including references. Working Notes are due by 23 October 2026 at 23:59 Anywhere on Earth; final competition predictions are due earlier, on 15 October 2026 at 23:59 Anywhere on Earth. Follow the organizer schedule updated on 7 September if CyberChair displays a different date. Paper feedback and organizer acceptance decisions are scheduled for 6 November; camera-ready papers are due on 13 November 2026 at 23:59 Anywhere on Earth. Keep author names and affiliations in the PDF, following the conference's single-blind review policy. Task 1 Working Notes must cite the FinReason Cup overview, the Task 1 overview, and the FinChain benchmark paper. Include the overviews for any other tasks you enter; see the required references and available official BibTeX. Do not upload a paper PDF to either prediction workspace.

Direct web upload availableVerified live links

SUBMISSION PAGES

Development and test submission

Development and test use separate submission pages. An accepted development upload shows the Final answer score, Reasoning steps score, receipt ID, and current rank immediately, and updates the public best-per-team leaderboard. Test shows format-check feedback and an acceptance receipt, with no score, rank, answer-correctness feedback, or score-derived signal before the final results are released.

Open development submission Open test submission

No pre-registration, approval, access code, or account is required. The development page asks for Team Name and a ZIP. The test page asks for Team Name, Contact Email, and a ZIP. Contact Email is private and is used only for submission identification, submission-related support, matching final results to the related challenge paper, and selecting the latest accepted test submission and handling repeat uploads through a non-public pseudonymous identifier, not as a login. Review the Terms of Participation and Privacy Notice. Participant support: zhuohan.xie@mbzuai.ac.ae.

01 / TRAIN

Build with public answers.

Train questions, gold answers, and canonical target examples are already available from the participant hub. Train results are not submitted to a leaderboard.

02 / DEVELOPMENT

Receive scores immediately.

Upload the 580-row predictions ZIP. Each accepted submission immediately returns the Final answer score, Reasoning steps score, receipt ID, and current rank, and updates the public best-per-team leaderboard.

03 / TEST

Check format and acceptance.

Upload predictions for the public 928-question test release and retain the receipt identifier. The portal shows format feedback and acceptance status. Test submissions receive no online score or rank. Official test evaluation is performed by the organizers after submissions close.

Open Test submission status

Step 1 of 6: Choose a consistent team name.

Step 2 of 6: Download the correct phase files.

Step 3 of 6: Create predictions.jsonl.

Step 4 of 6: Validate and package one canonical ZIP.

Step 5 of 6: Upload submission.zip on the matching webpage.

Step 6 of 6: Check the correct result.

Development and test submission

Build with public answers.

Receive scores immediately.

Check format and acceptance.