invoice

Invoice

A freelancer's invoice dispute is the same problem as a token-budget pitch: claims that need receipts. The ledger already holds the receipts — shipped items, recorded hours, metered AI costs. This skill renders them as billing paperwork and stops exactly at the line where pricing begins: what to charge is the user's business decision; what happened is the ledger's.

"${CLAUDE_PLUGIN_ROOT}/bin/waybill" mine --all      # catch-up metering first, always
"${CLAUDE_PLUGIN_ROOT}/bin/waybill" query report --from <iso> --to <iso> --audience internal
"${CLAUDE_PLUGIN_ROOT}/bin/waybill" export --format csv --from <iso> --to <iso>   # expense mode

Window: the billing period the user names; default the last full calendar month. State it in the header.

Audience: internal. For a freelancer, the client is the org — the work items ARE the client's project, so keys/titles/PR links belong on the invoice; machine-local detail (paths, session ids) is dropped. external would pseudonymize the very titles the client is paying for — wrong tool. What leaves the machine is the rendered document below, never raw ledger files.

Mode 1 — the client invoice pack

From query report's .data.shipped, one line item per shipped entry:

Item	Delivered	Hours (recorded)	AI assistance
KEY — title	PR/deploy link, ship date	actual_hours or "—"	role + metered_cost_usd (or tokens when unpriced)

Then three closing lines:

• Totals — items, points if the client uses them, summed recorded hours (sum only entries that HAVE actual_hours; say how many don't), and total disclosed AI cost from the rows' metered_cost_usd (labeled with pricing_version, list-price equivalent).
• AI disclosure — one sentence: which items Claude touched (claude_role ≠ "none"), verifiable per item via the disclose skill. Billing transparency on AI use is fast becoming a client expectation — an invoice that discloses it with receipts beats one that hopes nobody asks.
• Verification offer — if the client relationship warrants it, export --pack gives them the one-command integrity check (see the report skill). Mention, don't build unprompted.