Skip to content

Charge daily late-payment interest and fixed compensation on overdue business invoices with part payments and credit notes

Exact prompt

# Charge statutory interest and fixed compensation on late invoices Inputs: `invoices.csv` (every invoice issued to business customers, with issue and due dates), `payments.csv`, `credit-notes.csv` and `terms.json` (the annual interest rate, the statement date and the fixed-compensation bands). Work out the late-payment charges as at the statement date: - Interest runs on each day from the day after the due date up to and including the statement date, or up to and including the day the invoice was paid in full if that is earlier. - Each day's interest = outstanding principal x annual rate / 365. A payment reduces the principal from the day after it is received. - A credit note reduces the invoice amount from the start, as if that part had never been billed, whatever its date. - Fixed compensation: one fee per invoice that was paid in full after its due date or is still unpaid after it, chosen by the invoice amount after credit notes from the `fixed_fees` bands (the first band whose `below` is greater than that amount; `null` means no upper limit). - Round each invoice's interest to the cent half-up; totals are sums of the rounded figures. Write `out/late-charges.json`: `{"interest": {"<invoice_id>": <interest>, ...}, "fees": {"<invoice_id>": <fee>, ...}, "total_interest": <...>, "total_fees": <...>}`. List only invoices that have at least one day of interest, in both maps. ## 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.

Work out statutory late-payment interest and a banded fixed fee for every overdue invoice as at a statement date. Interest runs daily from the day after the due date, part payments cut the principal from the next day, and a credit note counts from the start even when it was issued after the due date. Starting a day early, ignoring part payments or applying a late credit note from its own date each change the charges. 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: interest_days part_payments credit_notes fixed_fees

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

Run this on another model

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.ⓘ

Runs for this use case
ModelCostTimeStep-insⓘAutonomyOutcomeTrustⓘDateCompare
AClaude Opus 5.5default · thinking on$0.1421s0Fully autonomouspassTrust 80%2026-10-22
AClaude Haiku 5.5default · thinking on$0.006125s0Fully autonomouspassTrust 80%2026-10-22
AClaude Sonnet 5.5default · thinking on$0.0615s0Fully autonomouspassTrust 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.

UseCaseRank badge for Charge daily late-payment interest and fixed compensation on overdue business invoices with part payments and credit notes

Get new runs and ranking changes weekly

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