Invoice Line Item Summarizer

How Invoice Line Item Summarizer works

Press Load model once: your browser downloads Gemma 4 E2B instruction-tuned (web build) (2.0 GB) from this site and keeps it in its cache. Then add your text and press Summarize locally. The model runs on this device using your graphics card, so nothing you enter is sent to a server. Until the model is loaded, or if your device cannot run it, the tool falls back to a simple keyword check and labels the result as the fallback.

Gemma 4 E2B instruction-tuned (web build) is a small open language model from Google. The tool sends it the instruction below plus your text, asks for a JSON answer with fixed fields, and shows each field as a card. It runs at temperature 0, so the same input gives the same answer on the same device, though different graphics cards can word it slightly differently.

Inputs longer than 6,000 characters are cut to that length before they reach the model, and the result says so. The model only sees what you paste: it does not look anything up.

The instruction the model gets

You summarise the line items on an invoice so the reader can check it. List each line with its quantity, hours, rate or amount exactly as written, say how each is billed (hourly, flat fee, reimbursement, discount, tax, deposit), and note the payment terms. Point out lines that are vague or missing a rate, quantity or amount, so the reader knows what to ask about. Do not add up the invoice, multiply hours by rates or work out a balance. This is not financial, tax or legal advice, so do not tell the user what they should do with their money. Do not do any arithmetic: copy every amount, date and percentage exactly as written, and never compute totals, differences, gaps, averages or percentages.

What it returns

• Line items: One entry per line, written as 'item → how it is billed: quantity, rate or amount as written'.
• Payment terms: Due date, net terms, late fees or deposit terms exactly as written.
• Lines to question: Lines missing a rate, quantity or amount, or described too vaguely to check.
• Questions for the sender: Two or three questions to ask before paying.

Worked example

The model's output for the built-in sample, recorded on a desktop browser. Your run may word things slightly differently.

Invoice lines: discovery call 1.5 hr, implementation 12 hr at $110/hr, emergency hotfix 2 hr, hosting reimbursement $38, discount -$75, net due in 15 days.

Line items

discovery call → billed as: 1.5 hr implementation → billed as: 12 hr at $110/hr emergency hotfix → billed as: 2 hr hosting reimbursement → billed as: $38 discount → billed as: -$75

Payment terms

net due in 15 days

Lines to question

discovery call: missing rate or amount emergency hotfix: missing rate or amount

Questions for the sender

What was the rate for the discovery call? What was the rate for the emergency hotfix? Can you clarify the nature of the hosting reimbursement?

The model

The files are served from this site, versioned so a cached copy is never stale. Nothing is fetched from a third party while you use the tool.

Limitations

• Small language models make mistakes: they can miss an item, merge two, or state something more confidently than the text supports. Check the result against your input before you rely on it.
• It needs WebGPU and about 8 GB of memory, so it is offered on desktops and laptops, not on phones and tablets. Devices that cannot run it get the keyword fallback, clearly labelled.
• Results describe the input you gave, not the real-world situation behind it. Review them yourself before acting.
• This is not financial, tax or legal advice. Confirm anything important against your own records and with a qualified professional.

Good uses

• Check a contractor or agency invoice before you approve it
• Split a mixed invoice into billable and non-billable buckets
• Find the fee, penalty, or rate change buried in the middle
• Normalize inconsistent vendor wording into one label set
• Summarize a month of invoices before handing them to a bookkeeper
• Sanity-check a total that looks higher than the last one