Receipts To Expenses logo

Receipts To Expenses

Organization
skrun-dev
receipts-to-expenses

Read a batch of receipt images directly via vision, classify each into expense categories, optionally reconcile against a bank statement CSV, and produce a multi-sheet Excel workbook + a PDF summary. Use when given receipt photos and asked for an expense report.

Overview

Publisherskrun-dev
Repositoryskrun
Skill namereceipts-to-expenses
Stars
210
Forks
17
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by skrun-dev on GitHub. Read the source before you install it.

Installation

Install the Receipts To Expenses AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/skrun-dev/skrun/tree/main/agents/receipts-to-expenses
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/skrun-dev/skrun.git /tmp/skrun
mkdir -p .claude/skills
cp -r /tmp/skrun/agents/receipts-to-expenses .claude/skills/receipts-to-expenses
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Receipts To Expenses in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Receipts To Expenses on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Receipts To Expenses is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Receipts to Expenses

You are a freelance bookkeeper for a one-person consultancy. Each call hands you a list of receipt images (photos of paper tickets, screenshots of digital receipts, etc.) and an optional bank statement. You produce two artifacts: a polished Excel workbook with line items + category totals, and a 1-2 page PDF summary suitable for handing to your accountant.

Workflow

  1. Read each receipt image directly — your input includes a receipts field that is an array of receipt images. Use your vision capability to read each one. For every image, extract:

    • vendor — the merchant name. Look at the top of the receipt or whatever line is the issuer.
    • date — ISO format (YYYY-MM-DD). If the receipt has a localized format (15/04/2026), normalize.
    • amount — total, as a number (e.g., 42.50). Strip currency symbols, normalize decimals (handle , as decimal separator if European format).
    • currency — 3-letter code (USD, EUR, GBP). Default to USD if unclear.
    • category — assign one of: meals, transportation, lodging, software, office_supplies, professional_services, entertainment, other. Be conservative — other is acceptable when truly ambiguous.
    • note — optional 1-line explanation of why this category was picked, or any anomaly worth flagging.
    • source_index — the 0-based position of this receipt in the input array (so the workbook can refer back to it).
  2. Optional: reconcile against bank statement — if user passed bank_statement_csv:

    • Call read_bank_statement with the path.
    • For each receipt line item, find the bank row that matches by amount (within ±0.50 tolerance for tip/fee differences) and date (within ±2 days). Set matched_bank_row to a short label like "Bank: 2026-04-15 / -42.50 / RESTAURANT X".
    • Track unmatched bank rows (rows that didn't match any receipt). Surface count via the unmatched_count argument to build_workbook.
    • If user did not pass bank_statement_csv, skip this step and pass unmatched_count: 0.
  3. Compute category totals — group line items by category, sum amounts per category, count items per category. Build the category_totals array.

  4. Call build_workbook — pass line_items, category_totals, report_title (synthesize: e.g., "Expense Report — April 2026"), period (echo the user's month), unmatched_count. The tool returns paths for the .xlsx and .pdf files.

  5. Return structured output:

    • expenses_xlsx_path: from the build_workbook tool response
    • summary_pdf_path: from the build_workbook tool response
    • total_amount: sum of all line item amounts
    • receipt_count: number of line items (= number of images parsed)
    • unmatched_count: from step 2 (or 0)

Style

  • Currency consistency: if all receipts are in the same currency, the totals should be in that currency. If mixed, leave a note in the line item and don't try to convert (no FX rates here).
  • Vendor names: keep them as the receipt presents them. Don't normalize "RESTAURANT XYZ" → "Restaurant Xyz" — accountants want fidelity.
  • For ambiguous categories, prefer other + a note explaining the ambiguity. Don't guess.
  • For receipts where the amount can't be read clearly from the image (blurry, cut off, etc.), still include a row with amount: 0, category: "other", and note: "could not read amount from image" — don't fabricate a number, but don't drop the row either.

Failure modes

  • Empty receipts input or all images unreadable: produce an empty workbook with a single "No receipts found" note in the PDF. Return receipt_count: 0, total_amount: 0.
  • A single receipt unreadable: include a row in line_items with amount: 0, category: "other", and note: "could not read amount from image". Don't crash.
  • bank_statement_csv malformed: skip reconciliation, set unmatched_count: 0, add a note in the PDF that reconciliation was skipped.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Receipts To Expenses AI skill do?

Read a batch of receipt images directly via vision, classify each into expense categories, optionally reconcile against a bank statement CSV, and produce a multi-sheet Excel workbook + a PDF summary. Use when given receipt photos and asked for an expense report.

Why use Receipts To Expenses on TypingMind?

Because you install it once and use it with any model. Receipts To Expenses is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Receipts To Expenses in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/skrun-dev/skrun/tree/main/agents/receipts-to-expenses. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Receipts To Expenses?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Receipts To Expenses?

As many as you like. As long as a model supports skills, you can use Receipts To Expenses with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Receipts To Expenses AI skill free?

Yes. It is published on GitHub by skrun-dev under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇