Skip to content

Check and pay staff mileage claims across the April tax-year change

Exact prompt

# Check and pay staff mileage claims across the tax-year change Inputs: `claims.csv` (claim_id, employee_id, trip_date, from, to, miles, passengers, submitted_on), `employees.json`, `rates.json` and `finance-note.txt`. Amounts are in pounds. `rates.json` and these rules are the record; where the finance note disagrees, the rules win. Rules: - A claim submitted more than late_after_days days after its trip_date is rejected as late; it is listed only in rejected_late, even if it is also a duplicate. - Two remaining claims are duplicates if they have the same employee_id, trip_date, from and to (from and to compared ignoring letter case and extra spaces); only the one submitted first is paid (on a tie, the lower claim number), and the others are duplicates. - Business miles are paid at rate_first per mile until the employee's miles in that tax year reach threshold_miles, then at rate_after; a tax year runs from 6 April to 5 April. Count paid claims in trip_date order (ties by claim number), starting from miles_before_2025_26 for the 2025-26 tax year and from 0 for 2026-27; a claim that crosses the threshold is split. - Each passenger adds passenger_per_mile for every mile of the claim; passenger miles don't count toward the threshold. - Write `out/mileage.json`: `{"paid": {"<claim_id>": <pay>, ...}, "rejected_late": [<claim_ids>], "duplicates": [<claim_ids>], "employee_totals": {"<employee_id>": <sum of pay>, ...}}`. `paid` has every paid claim; lists are sorted by claim number; `employee_totals` lists employees with at least one paid claim. ## How this run works - Work on your own: nobody will answer questions in this task, and writing to `ask/` counts against the run. - Write only under `out/`. Create `out/` if it is missing. Inputs are synthetic; don't fetch anything from the network. - Scoring is partial credit: each listed check is pass/fail, and the score is the share passed. Numbers are compared to within 0.005 unless the task says otherwise.

Check a team's car mileage claims and work out what each person is paid. Some claims are late by exactly the cut-off or one day past it, resubmitted trips differ only in letter case or spacing, the higher rate stops at 10,000 miles a tax year that restarts on 6 April, and a claim that crosses the threshold has to be split. A finance note gets the tax year and late rule wrong. Original benchmark task written for usecaserank.com (not based on a specific public post). Headless, offline run on a reproducible fixture. Each run's notes say how its cost was measured (estimates are marked).

Success criteria: late duplicates pay totals

Best model for this task so far: Claude Haiku 5.5 (effort default (no --effort flag) · thinking on) (success, $0.0067, 25s).

Run this on another model

All runs (6)

100% pass rate across 6 eligible runs: 6 pass, 0 partial, 0 fail. Partial and failed runs are listed below with everything else.ⓘ

Runs for this use case
ModelCostTimeStep-insⓘAutonomyOutcomeTrustⓘDateCompare
GGemini 3.8 Flashmedium · thinking on$0.232m0Fully autonomouspassTrust 80%2026-10-23
GGemini 4 Argonmedium · thinking on$0.143m0Fully autonomouspassTrust 80%2026-10-23
OGPT-6.1 Soldefault · thinking off$0.0325s0Fully autonomouspassTrust 80%2026-10-23
AClaude Opus 5.5default · thinking on$0.1421s0Fully autonomouspassTrust 80%2026-10-23
AClaude Haiku 5.5default · thinking on$0.006725s0Fully autonomouspassTrust 80%2026-10-23
AClaude Sonnet 5.5default · thinking on$0.0613s0Fully autonomouspassTrust 80%2026-10-23

Embed this result

A live badge for this use case. It links back here and updates as new runs are published.

UseCaseRank badge for Check and pay staff mileage claims across the April tax-year change

Get new runs and ranking changes weekly

Which models got better or cheaper on real tasks like this one.