Bill a freelancer's clients for a month with half days, weekend rates, marked-up expenses and prepaid retainers
Exact prompt
# Bill a freelancer's clients for October Inputs: `timelog.csv` (hours logged per client per day in October 2026), `clients.json` (each client's day rate and the retainer they have already paid in advance) and `expenses.csv` (re-chargeable expenses; mileage rows give miles instead of an amount). Every amount is in pounds. Billing rules, per client: - A day with 4 hours or more logged for a client is a full day; under 4 hours is a half day. Add up a client's hours per date first. - Days on a Saturday or Sunday are charged at 1.5x the day rate. - Expenses are re-charged at cost plus 10%, except mileage, which is charged at 0.45 per mile with no markup. Round each expense line to the cent half-up. - Deduct the client's retainer from fees plus expenses, but never below zero; any unused retainer carries forward. Write `out/invoices.json`: `{"days_charged": {"<client>": <full-day equivalents, e.g. 3.5>, ...}, "fees": {"<client>": <day-rate charges>, ...}, "expenses": {"<client>": <re-charged expenses>, ...}, "amount_due": {...}, "carry_forward": {"<client>": <unused retainer>, ...}}` with every client in `clients.json` (a client with nothing logged has 0 everywhere except carry_forward). ## 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.
Turn a month of logged hours and expenses into client invoices. Hours are summed per day and billed as half or full days, weekend days cost 1.5x, expenses carry a 10% markup except mileage at a flat per-mile rate, and prepaid retainers are deducted with any surplus carried forward. Billing hours pro rata, skipping the weekend rate or marking up mileage each change the invoices. 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: half_days weekend_rate expense_markup retainer
Best model for this task so far: Claude Haiku 5.5 (effort default (no --effort flag) · thinking on) (success, $0.0056, 20s).
All runs (3)
100% pass rate across 3 eligible runs: 3 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 |
|---|---|---|---|---|---|---|---|---|
| AClaude Opus 5.5default · thinking on | $0.12 | 16s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-22 | |
| AClaude Haiku 5.5default · thinking on | $0.0056 | 20s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-22 | |
| AClaude Sonnet 5.5default · thinking on | $0.05 | 11s | 0 | Fully autonomous | pass | Trust 80% | 2026-10-22 |
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.