Featured competition · National · Vendor-neutral

The Great IndianFDE Hackathon 2026

Ship the agent that cleans up a 43-year-old manufacturer — and prove it by the business outcomes it delivers. Four task families, one shared environment, and a hidden key that decides the score. Download the data, build in whatever environment you already use, and upload the output file for automatic scoring.

AgentsEnterprise dataEvaluation
The Great Indian FDE Hackathon 2026 featured artwork
Entrants
Submissions today
Hours to next deadline
Host
AIM Media House

Opens 20 Aug 2026 · Closes 27 Sep 2026, 23:59 IST · Stage at Cypher 2026

Starter kit

Everything you need to go from the downloaded data to a scored submission. Pick whichever path suits how you already work.

how to competeany tool is legal
01

Download the client's data

DRI's datasets and policy documents, from Downloads.

02

Build in your own environment

Any model, any framework, any tool. This platform never runs your code.

03

Run your system against the data

It must handle every invoice and every question, at scale.

04

Submit the output CSV

Scored automatically against hidden ground truth; the leaderboard updates itself.

The leaderboard measures what your system got right. How you built it is your business.

choose your path

Work with a coding agentrecommended

The fastest route in 2026. Open Claude Code, Cursor, or any agentic coding tool in a folder containing the downloaded data, and paste this brief.

You are competing in The Great Indian FDE Hackathon. This folder contains
vendor_invoices.csv, purchase_orders.csv, vendors.csv, products.csv,
sample_submission.csv, and four policy PDFs from a fictional manufacturer
called Deshmukh & Rao Industries.

Build a pipeline that classifies every invoice in vendor_invoices.csv into
exactly one of: CLEAN, QTY_MISMATCH, RATE_MISMATCH, DUPLICATE_INVOICE,
MISSING_PO, VENDOR_MISMATCH, GST_ERROR, UOM_MISMATCH.

Join invoices to purchase orders on po_number. Use deterministic checks
where arithmetic decides: quantity vs PO, rate vs PO, GST at 18%, whether
the PO reference exists, duplicate billing against one PO (the later-dated
invoice is the duplicate), unit-of-measure differences such as Box(10) vs
Nos, and the vendor code on the invoice vs the PO. Where records do not
line up cleanly — vendor names in different formats, ambiguous references —
use model calls or fuzzy matching, and comment your reasoning.

Produce submission.csv with columns invoice_number,status, covering every
invoice exactly once, matching sample_submission.csv's shape. Then report
the class distribution you predicted and the cases you were least sure
about. The metric is macro-F1 across the eight classes, so the rare classes
matter as much as CLEAN.
Write it yourself

Python shown here; any language works. The format is the contract.

download starter_reconciliation.py
Any other way

Agent platforms, workflow builders, spreadsheets with model add-ins, a chat assistant with file uploads — all legal. Whatever produces the CSV counts. One honest note: scored sets are large and rotate weekly, so approaches that automate end to end climb the board, and manual passes stall.