Q1 budget-vs-actual variance table and CFO memo from a raw ledger (out-of-period lines, intercompany, legacy codes, reversals)
Exact prompt
# Task: Q1 budget variance report and memo Finance needs a Q1 2026 budget-vs-actual review. You have `budget.csv` (Q1 budget per department), `ledger.csv` (raw expense lines) and `dept_remap.csv` (legacy department codes still used by some systems). Produce `variance.csv` and `memo.md` in this directory. You may use any method (script or by hand). No network. ## Rules for actuals 1. Only ledger lines dated 2026-01-01 to 2026-03-31 inclusive count; lines dated outside Q1 are excluded whatever their memo says. 2. Lines whose `account` starts with `9` are intercompany transfers and are excluded. 3. A `dept_code` listed as a `legacy_code` in `dept_remap.csv` belongs to the mapped `dept_code`. 4. Amounts may contain thousands separators; an amount in parentheses, e.g. `(1,250.00)`, is negative (a reversal/credit) and reduces the total. ## variance.csv 5. Header `dept_code,budget,actual,variance,variance_pct`, one row per department in `budget.csv`, sorted by `dept_code`. 6. `variance = actual - budget` (positive = overspent). `variance_pct = variance / budget x 100`, rounded half-up to 1 decimal. Money columns with exactly 2 decimals; no `$`, `%` or thousands separators; negative numbers with a leading `-`. Every value must equal the exact result rounded as stated. ## memo.md 7. At most 200 words (counted as whitespace-separated tokens), written for the CFO. 8. It must name the three departments with the highest positive `variance_pct` using their `dept_name` from `budget.csv`, and the first mention of each of those three names must appear in descending order of overspend. Each of the three must be accompanied somewhere in the memo by its percentage written with a sign and one decimal followed by `%`, e.g. `+16.4%`. 9. It must also name the department with the lowest (most negative) `variance_pct` and give its percentage in the same format, e.g. `-7.2%`. 10. Optional (reported, not scored): a line starting with `Recommendation:`. The grader compares `variance.csv` with the correct values and checks `memo.md` against rules 7-9.
Each department has an out-of-period accrual, an intercompany line and a reversal pair; three departments use legacy codes. Missing any rule changes the variance table and usually the top-3 ranking the memo must report. 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: 1. variance_csv_correct: all 8 rows exact (2-decimal money, 1-decimal pct). 2. memo_word_limit: 1-200 whitespace tokens. 3. memo_top3_in_order: the three largest overspenders named in descending order, each with its signed percentage. 4. memo_names_largest_underspend: the largest underspender named with its signed percentage.
Best model for this task so far: Claude Haiku 5.5 (effort default (no --effort flag) · thinking on) (success, $0.0079, 27s).
All runs (4)
100% pass rate across 4 eligible runs: 4 pass, 0 partial, 0 fail. Partial and failed runs are listed below with everything else.ⓘ
| Model | Cost | Time | Step-insⓘ | Autonomy | Outcome | Trustⓘ | Date | Compare |
|---|---|---|---|---|---|---|---|---|
| OGPT-6.1 Soldefault · thinking on | $0.07 | 58s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-22 | |
| AClaude Haiku 5.5default · thinking on | $0.0079 | 27s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-19 | |
| AClaude Opus 5.5default · thinking on | $0.14 | 30s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-19 | |
| AClaude Sonnet 5.5default · thinking on | $0.06 | 14s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-19 |
Embed this result
A live badge for this use case. It links back here and updates as new runs are published.
Get new runs and ranking changes weekly
Which models got better or cheaper on real tasks like this one.