Build a Buyer-Seller Settlement Reconciliation and Fee Explainer
Cross-reference settled commerce orders against agreed buyer app finder fees, tax deductions, and seller withholdings. Synthesize clear fee breakdown explanations to resolve merchant payout inquiries without executing transfers.
What you are building
The core problem, expected build, and operating context for this challenge.
Cross-reference settled commerce orders against agreed buyer app finder fees, tax deductions, and seller withholdings. Synthesize clear fee breakdown explanations to resolve merchant payout inquiries without executing transfers.
E-commerce merchant support analyst
Parse completed order line items, fulfillment timestamps, and contractual fee agreements from mock settlement files.
Calculate finder fees, logistics deductions, and statutory tax collected at source on gross transactions.
Reconcile differences between merchant invoicing totals and estimated net payouts across order batches.
Produce an explainable settlement audit receipt for merchant dispute teams without initiating banking operations.
Web dashboard showing order-by-order fee deductions, variance alerts, and exportable reconciliation receipts.
Assemble mock ONDC order items and settlement schedules in local JSON files adhering to standard ONDC draft schemas. Starter examples below are synthetic. They are not downloaded records.
ONDC protocol specifications Adopts ONDC protocol draft versioning and buyer-seller network role specifications to map transaction structures.
dspy, pandas, fastapi. Optimizes prompt formulations to synthesize human-readable fee explainability memos from numeric tabular inputs. Fast hosted model suitable for few-shot prompt compilation and arithmetic explanation.
Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.
Matches order line items against agreed platform finder fee percentages exactly.
Identifies fee discrepancies exceeding a one-rupee tolerance threshold.
Produces narrative payout summaries without performing real automated payment movements.
```json [ { "input": { "settlement_id": "SET-1029", "order_id": "ORD-55412", "gross_amount": 1200, "buyer_finder_fee_pct": 3, "logistics_fee": 150, "withholding_tax_pct": 1 }, "expected_output": { "calculated_net_payout": 1002, "deductions": { "buyer_finder_fee": 36, "logistics_charge": 150, "statutory_withholding": 12 }, "status": "balanced", "explanation": "Gross 1200.00 minus 3% finder fee (36.00), logistics (150.00), and 1% withholding (12.00) yields 1002.00." } }, { "input": { "settlement_id": "SET-1030", "order_id": "ORD-55413", "gross_amount": 800, "buyer_finder_fee_pct": 5, "logistics_fee": 200, "withholding_tax_pct": 1 }, "expected_output": { "calculated_net_payout": 552, "deductions": { "buyer_finder_fee": 40, "logistics_charge": 200, "statutory_withholding": 8 }, "status": "balanced", "explanation": "Gross 800.00 minus 5% finder fee (40.00), logistics (200.00), and 1% withholding (8.00) yields 552.00." } } ] ```
Maintains read-only accounting simulations and never executes actual bank debits or digital wallet transactions. Use mock external writes. Require human review before any real deployment.
Participation guide
Maintains read-only accounting simulations and never executes actual bank debits or digital wallet transactions. Use mock external writes and human review.
How work is evaluated
Matches order line items against agreed platform finder fee percentages exactly. Identifies fee discrepancies exceeding a one-rupee tolerance threshold. Produces narrative payout summaries without performing real automated payment movements.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Parse completed order line items, fulfillment timestamps, and contractual fee agreements from mock settlement files. Calculate finder fees, logistics deductions, and statutory tax collected at source on gross transactions. Reconcile differences between merchant invoicing totals and estimated net payouts across order batches. Produce an explainable settlement audit receipt for merchant dispute teams without initiating banking operations.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Matches order line items against agreed platform finder fee percentages exactly. Identifies fee discrepancies exceeding a one-rupee tolerance threshold. Produces narrative payout summaries without performing real automated payment movements.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Web dashboard showing order-by-order fee deductions, variance alerts, and exportable reconciliation receipts.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Maintains read-only accounting simulations and never executes actual bank debits or digital wallet transactions.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Parse completed order line items, fulfillment timestamps, and contractual fee agreements from mock settlement files.
Calculate finder fees, logistics deductions, and statutory tax collected at source on gross transactions.
Reconcile differences between merchant invoicing totals and estimated net payouts across order batches.
Produce an explainable settlement audit receipt for merchant dispute teams without initiating banking operations.
Reference links and supporting material
Assemble mock ONDC order items and settlement schedules in local JSON files adhering to standard ONDC draft schemas. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
DSPy
Prompt and LM program optimization framework.
Evaluated output
No output checks are configured.
- Parse completed order line items, fulfillment timestamps, and contractual fee agreements from mock settleme...
- Matches order line items against agreed platform finder fee percentages exactly. Identifies fee discrepanci...
- Web dashboard showing order-by-order fee deductions, variance alerts, and exportable reconciliation receipts.
- 2 public reference cases
- 3 configured tools
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- DSPy · Optional
- DSPy · Optional
- DSPy · Optional
Evaluation contract
- Complete workflow · Weight 40
- Correctness and evidence · Weight 30
- Review interface · Weight 20
- Safe execution · Weight 10
Reference cases
- 2 public reference cases
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.