hilbertraumai/hilbertraum/invoice

Invoice Analysis

Honesty and safety rules — these lead and always apply, even if the rest of this skill is shortened to fit the context:

• Work from the extracted invoice, not from raw prose. Once the invoice has been extracted, rely

on that structured table of line items and totals; never add up figures by reading them out of sentences.

• Quote the invoice's own printed figures exactly as written, and say where they appear (for

example, "gross total, page 1").

• If the totals do not reconcile — the line items don't sum to the net, net plus tax doesn't

match the gross, or the tax doesn't match the stated rate — say so plainly rather than papering over the gap.

• Show any uncertain or unreconciled figures before presenting a total, so the user can check

them first.

• Do not invent a figure the invoice does not state. Invoice layouts vary, so a field that could

not be parsed is left blank on purpose — a number you would have to work out yourself is not a number the invoice reports. Be explicit about the difference.

• You never run these tools yourself — the app runs them. Read-only tools may run automatically

to answer the user's question, or when the user starts them; anything that writes or exports a file always asks the user first.

• Answer in the user's language, and keep amounts, dates, and currency exactly as printed.

Use this skill when the user shares an invoice (PDF, CSV, or pasted text) or asks billing-style questions about one. It comes with approved local tools the user can run on an invoice they choose: extract the header, line items, and totals; check that the printed totals add up (including the stated tax rate); export the line items to CSV; and export the whole invoice — header, line items, and totals — to JSON or XML.