Sort the finance inbox before anyone opens it
Labels everything landing in your finance mailbox — invoices, credit notes, statements, billing questions — and routes each to the right place.
- How it works
- The small model reads what lands in your finance@ or invoices@ mailbox and labels it: supplier invoice, credit note, payment reminder addressed to you, bank or statement mail, customer billing question, spam. Invoices can be forwarded to whatever handles them next — a person, a folder, or an invoice-extraction step — and questions go straight to a person. It runs continuously, so classification is quick and cheap.
- Data you need
- Access to the finance mailbox (IMAP or an export) and a list of your routing buckets. A hundred or so past emails tagged with their correct bucket makes the prompt examples concrete — this labelled set rarely exists up front, but an hour of tagging a recent export produces it.
- What to expect
- Classification is the easy part; the risk is over-trusting it. Attachment-only emails are the weak spot: PDFs with a text layer can be read, but scanned or photographed invoices cannot (no vision model is served), so those get classified on subject line and sender alone and more of them land in 'unsure'. The mailbox contains personal and commercial data — processing stays on the EU-hosted cluster, but check your own data-handling policy before connecting it.
- Where people stay involved
- Misrouted mail must be easy to re-label, and a daily glance at the 'unsure' bucket is non-negotiable. Anything from tax authorities, banks or lawyers is always surfaced to a human regardless of the model's label.
Which model, and what it costs to run
Qwen3-32B
This job answers while someone waits, so latency comes first: we hold it to a single small card and, within that, take the best independent score on structured output and tool calls.
- Licence
- Apache-2.0
- Weights at 4-bit
- 18 GB
- Context
- 32K tokens
- Publisher
- Alibaba (Qwen Team)
What the hardware costs
One 48 GB card holds it
- Rent in the EU
- $1.60/hrScaleway, Paris (PAR2)
- Buy the card
- $7,569new, one-off
- Or rent it by the token
- $0.12 / $0.12per M in / out · Nebius AI Studio · EU
Hardware only, third-party prices from 2026-07. The figure excludes the KV cache, which grows with context length and how many people use it at once — sized properly in a conversation, not guessed here. Renting by the token is cheaper up front; why our customers still self-host is below.
Structured output and tool calls
Measured in a sandbox, on somebody else's functions. It tells you which models are capable of the shape of the job, not which one will survive contact with your API.
Independent measurement · UC Berkeley (Gorilla project) · board updated 2026-04-12
Reading a long document whole
No benchmark measures this
No current benchmark ranks today's open models here. HELMET showed that the popular test — finding a planted sentence — predicts nothing, and its own table has not been rerun on 2026 models.
So we do not show a chart here. We measure it on your own content, in the first week, and you see the result before anything ships.
Sticking to the document
Measured on public documents, by a model acting as judge. Read it beside the answer rate: the lowest hallucination rates on this board belong to models that simply decline more often.
Independent measurement · Vectara · board updated May 11, 2026
The API is cheaper per token. Here is why our customers don't use it.
We will not pretend otherwise: renting a model by the token from a serverless API costs less per million tokens than a card we run for you. We show that price on every use-case page. What it does not include is the part a shop with a customer database actually pays for.
- 01
Your data never leaves hardware you can point at
A serverless "we don't retain your data" is a clause in a contract. Running the model on a card in Amsterdam is a fact of architecture: your catalogue, tickets and customer records are never sent to a third party at all. For a GDPR audit, that is the difference between a promise and a floor plan.
- 02
The price cannot move without your say-so
A serverless rate card is somebody else's lever. The provider can raise the price, retire the model, or change the terms, and your cost moves with it. The same model on the same card costs the same next year — you own the number.
- 03
The model cannot be taken away
Hosted APIs deprecate models on their own schedule; the one you built on can be gone in a quarter. An open-weight model on your own hardware runs for as long as you keep the lights on. No vendor can end-of-life it out from under you.
And the price gap closes with volume: past a card you keep busy — very roughly four billion tokens a month — owning is cheaper outright, even before the three reasons above.
Getting a case like this one from a conversation to production takes about two months, and you can stop at the end of any phase.
Also in finance & admin
All 15 →Pull the details off supplier invoices into your bookkeeping
Pulls supplier name, invoice number, dates, line items and VAT out of PDF invoices into records your accounting software can import.
Turn expense receipts into draft expense entries
Turns OCR'd receipt text into draft expense entries — merchant, date, amount, VAT and likely category — for the submitter and finance to confirm.
Sort expenses into your bookkeeping categories
Reads cryptic bank and card descriptions and proposes a category from your own chart of accounts, backed by your past bookings as evidence.
Match incoming bank payments to open invoices
Proposes matches between bank statement lines and open invoices when references are mistyped, names differ or one transfer covers two invoices.
Next
Tell us what your team does by hand
Describe the process that takes the most time. We will say plainly whether a model is the right tool for it.