cowork-expense-audit — Claude Code skill: expense audit
The cowork-expense-audit Claude Code skill checks receipts against statement entries and sorts transactions into expense categories. It produces a ledger plus a memo covering gaps and flagged items.
MIT 106 installs ★ 440 updated 2026-10-20
npx skills add OneWave-AI/claude-skills --skill cowork-expense-audit -a claude-codeWhat cowork-expense-audit does
The skill builds a transaction ledger from PDF or image receipts, card or bank statements, and .csv or .xlsx exports. It pairs receipts with statement entries, records unmatched items, and assigns categories. Each reported match points to both source files; unmatched entries note what the search covered.
It writes a CSV ready for expense-report.xlsx and an audit-findings.md memo with category totals, reconciliation gaps, flagged entries, and missing documents. If an .xlsx skill is available, the report can be produced in that format. Amounts are never estimated or silently converted, and flags are framed as questions rather than accusations.
When receipts are missing for more than 20% of transactions, that fact leads the memo. In a monthly Cowork scheduled task, the skill processes new files in an inbox folder and adds them to the running ledger.
What it helps with
- match receipts to statement entries
- sort transactions into expense categories
- find charges without receipts and receipts without charges
- flag possible policy violations and unusual transactions
Example prompts for the agent
- Audit the
receiptsfolder and reconcile its receipts with the statements. - Check this folder for transactions without receipts and list the missing documents.
- Pull the client-billable transactions and group them by client.
How to install cowork-expense-audit
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-expense-audit -a claude-code2Manually: put the files in place
~/.claude/skills/cowork-expense-audit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cowork-expense-audit/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-expense-audit -a codex2Manually: put the files in place
.agents/skills/cowork-expense-audit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-expense-audit -a cursor2Manually: put the files in place
.cursor/skills/cowork-expense-audit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OneWave-AI/claude-skills cowork-expense-audit2Manually: put the files in place
.github/skills/cowork-expense-audit/SKILL.md1Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-expense-audit -a gemini-cli2Platform CLI
gemini skills install https://github.com/OneWave-AI/claude-skills --path cowork-expense-auditManually: put the files in place
.devin/skills/cowork-expense-audit/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OneWave-AI/claude-skills --skill cowork-expense-audit -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cowork-expense-audit
How do I install cowork-expense-audit in Claude Code?
Run npx skills add OneWave-AI/claude-skills --skill cowork-expense-audit -a claude-code. The skill file is at ~/.claude/skills/cowork-expense-audit/SKILL.md.
What does cowork-expense-audit do?
It reconciles receipts with statement entries and expense exports, categorizes transactions, then creates a ledger and a memo listing discrepancies and missing documents.
How does cowork-expense-audit match receipts to transactions?
It checks exact date-and-amount matches first, then allows a date difference of up to three days and a small variance for tips or foreign exchange. The report cites both files for each match.
Source text
SKILL.md · MIT
--- name: cowork-expense-audit description: Cowork-style sweep of a folder of receipts, statements, and expense exports -- categorizes every transaction, matches receipts to statement lines, flags policy violations and anomalies, and outputs a clean expense report plus a findings memo. tools: Read, Glob, Grep, Write, Bash model: inherit --- # Cowork Expense Audit Process an expense folder the way a careful controller does: reconcile receipts against statements, categorize consistently, and separate what is provably documented from what is missing. Input is a directory of receipts (PDF, images), card/bank statements, and any expense exports (.csv/.xlsx). Never invent an amount -- every number in the output traces to a source file. ## Workflow 1. **Inventory.** Catalog every file: receipts, statements, exports, and unclassifiable items. Note date ranges covered. If statements and receipts cover different periods, say so up front. 2. **Extract transactions.** Build a master ledger from the statements/exports: date, merchant, amount, currency. From each receipt: merchant, date, total, tax, payment method, line items when legible. 3. **Reconcile.** Match receipts to statement lines (exact amount+date first, then fuzzy within 3 days and small tip/FX variance). Output three lists: matched, statement lines with no receipt, receipts with no statement line. 4. **Categorize** every transaction (meals, travel, software, equipment, client entertainment, etc.). Use the company's category list if provided; otherwise propose one and apply it consistently. Tag anything client-billable separately. 5. **Flag.** Apply the policy if provided; otherwise apply defaults and label them as defaults: duplicate charges, weekend/holiday spend on business cards, round-number amounts, per-transaction limits exceeded, subscriptions appearing monthly with no owner, personal-looking merchants, and split transactions that dodge an approval threshold. 6. **Report.** Write `expense-report.xlsx`-ready CSV (or .xlsx if the xlsx skill is available) with the full categorized ledger, plus `audit-findings.md`: totals by category, reconciliation gaps, flagged items each with severity and the specific source file cited, and a missing-documentation list to chase. ## Rules - Never fabricate or estimate amounts. An unreadable receipt is logged as unreadable, not guessed. - Flags are questions, not accusations. Write "no receipt located for..." not "unauthorized spend." - Keep personal card statements strictly scoped: extract only lines the user identifies as business expenses; do not summarize personal activity. - Show your matching: every matched pair cites both source files; every unmatched item says what was searched. - Currency: preserve the original currency and note the statement's settled amount; never silently convert. - If more than 20% of transactions lack receipts, lead the findings memo with that fact -- it is the finding. ## Scheduled Mode As a monthly Cowork scheduled task pointed at a receipts inbox folder: process new files, append to the running ledger, and deliver the month's report and findings without re-litigating prior months. ## Quick Commands - "Audit [folder]" -- full workflow - "Reconcile only" -- steps 1-3, the matching report - "What's missing?" -- unmatched statement lines and the chase list - "Billable pull" -- client-billable transactions grouped by client
© OneWave-AI · MIT · OneWave-AI/claude-skills