Skip to content
Skills Library
Finance & accounting · Conversion & formats

invoice-processing

/invoice-processing

Extract invoice data (PDF, image, text) into structured JSON, validate totals, NIP and IBAN, and export to a spreadsheet. Use when processing, checking or booking invoices or receipts.

Licence
MIT
Last repository change
08.11.2026

Assessment and security

96/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content31 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 08.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/validate_invoice.py

What it does and when to use it

Extract invoice data (PDF, image, text) into structured JSON, validate totals, NIP and IBAN, and export to a spreadsheet. Use when processing, checking or booking invoices or receipts.

Original author description

Extract invoice data (PDF, image, text) into structured JSON, validate totals, NIP and IBAN, and export to a spreadsheet. Use when processing, checking or booking invoices or receipts.

How it works

SKILL.md has no level-two headings · 31 lines, 264 words

SKILL.md preview
---
name: invoice-processing
description: Extract invoice data (PDF, image, text) into structured JSON, validate totals, NIP and IBAN, and export to a spreadsheet. Use when processing, checking or booking invoices or receipts.
---

# Invoice Processing

1. Read each document (PDF text, image, email). One invoice per JSON object, in this shape:

```json
{"number":"FV/12/2026","type":"invoice","issue_date":"2026-11-03","sale_date":"2026-11-03",
 "due_date":"2026-11-17","currency":"PLN",
 "seller":{"name":"Acme sp. z o.o.","tax_id":"1234560007","country":"PL"},
 "buyer":{"name":"Jan Kowalski IT","tax_id":"PL9876540016","country":"PL"},
 "lines":[{"description":"Hosting 11/2026","qty":1,"unit_net":100.00,"net":100.00,"vat_rate":"23","vat":23.00}],
 "totals":{"net":100.00,"vat":23.00,"gross":123.00},
 "iban":"PL61109010140000071219812874","category":null,"notes":[]}
```

- `type`: `invoice` | `correction` | `proforma` | `receipt`. Corrections keep negative amounts.
- `vat_rate`: a number as text, or `zw` / `np` / `oo` (exempt, not taxable, reverse charge).
- Copy values exactly as printed. Never guess a missing field — set `null` and add a note.
- Dates `YYYY-MM-DD`, amounts as numbers with a dot.

2. Run `python scripts/validate_invoice.py invoices.json` (path relative to this skill). It checks line math, totals, gross = net + VAT, Polish NIP checksum, IBAN checksum, due date, and duplicates (same seller + number). Fix extraction mistakes and re-run; issues that are really on the document stay as notes for the user — never "fix" the invoice's numbers.

3. Category: use the user's list or chart of accounts if given; otherwise propose short categories (e.g. software, hosting, hardware, travel, marketing, services) and mark them as proposals.

4. Export: one row per invoice (or per line if asked) to CSV or to .xlsx with the `xlsx-toolkit` skill — columns: number, issue_date, due_date, seller, seller_tax_id, net, vat, gross, currency, category, status, notes.

Hard rules:
- Foreign-currency invoices: keep the original currency. Convert only if the user asks, and then state the rate, its date and source.
- Never pay, send or upload anything. Tax treatment is a hint for the accountant, not advice.
- Report: count processed, count with issues, and each issue in one line.
Files in this package (2)
  • SKILL.md 2 KB
  • scripts/validate_invoice.py 6 KB

Versions

RepositoryScoreLicence
This page · pawelbednarekpunks/aidevbird-skills96MIT
seb1n/awesome-ai-agent-skills100MIT

Database snapshot: 13.11.2026 · package version 59b3be42a976 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95pdf-invoice-extractor
    Extract typed invoice data from supplied text, Markdown, or a PDF/image through process_document. Use for invoice totals, line items, due dates, and extraction anomalies.
  • 100kelly-invoice-sheet
    Extract invoices, receipts, credit notes, statements, PDFs, images, docs, and spreadsheet-like invoice exports into a reviewable table with field confidence, line items, approval decisions, and CSV/JSON export. Use when the user invokes /kelly-invoice-sheet or…
  • 100invoice-reader
    Extract invoice data - vendor, amounts, taxes, dates, line items - from PDFs and scans into structured records, with validation checks. Use for invoice processing and expense tracking.
  • 100receipt-processing
    Extract structured data from receipts and invoices for bookkeeping, expense tracking, and tax preparation. Supports email, photos, scanned images, PDFs, and accounting exports. Outputs vendor, date, amount, tax, line items as table, CSV, or JSON. Trigger on "process receipts",…
  • 90qonto-supplier-detective
    Forensic audit of supplier invoices and payments on a Qonto account. Sweeps every supplier invoice and every debit to find money leaking out — duplicate invoices, invoices paid twice, invoice-vs-payment amount gaps, and the highest-value security signal, a known supplier whose…
  • 90pdf-processing
    Process and extract information from PDF documents. Use this skill when the user asks to read, analyze, or extract data from PDF files.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.