uulucky

Claude Skill Eu Einvoice — Development skill for Claude Code

Development community

Claude skill + Claude Code plugin for European e-invoices (EN 16931): create, validate, read and convert XRechnung, Peppol BIS 3.0 and ZUGFeRD / Factur-X with the official CEN, KoSIT and Peppol rules.

How to install Claude Skill Eu Einvoice

This entry records only its repository, not the path inside it, so there is no exact command to give. Open uulucky/claude-skill-eu-einvoice and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Claude Skill Eu Einvoice does

Alternatives in Development

Career-Ops For Codex — Read CLAUDE.md for all project instructions, routing, and behavioral rules 32.5k ★
Package OfficeCLI Skill As AionUi Assistant — Convert an OfficeCLI skill into a fully wired AionUi assistant preset, or update an existing one 20.3k ★
Gemini Project Context For SaneBar — PRIMARY INSTRUCTION: This project uses a shared configuration with Claude 216 ★

README

eu-einvoice: a Claude skill for European e-invoices

[中文说明](README.zh-CN.md) · [PyPI: eu-einvoice](https://pypi.org/project/eu-einvoice/)

![Demo: creating a validated XRechnung and diagnosing a rejected Peppol invoice](docs/img/demo.gif)

A Claude skill (packaged as a Claude Code plugin) that **creates, validates, reads and converts European structured e-invoices** following EN 16931: **XRechnung** (UBL and CII), **Peppol BIS Billing 3.0**, **ZUGFeRD / Factur-X** hybrid PDFs, and plain UBL 2.1 or UN/CEFACT CII.

Ask Claude in plain words, for example "make this an XRechnung for the city of Köln", "why was my Peppol invoice rejected with BR-CO-15?", or "what's in this xrechnung.xml my supplier sent?". Claude then uses the bundled tooling instead of writing XML by hand:

Amounts are computed, not typed. Line totals, the VAT breakdown per category and rate, document totals, prepayments and allowances are calculated to the cent, the way EN 16931 (BR-CO-10..17) and Peppol (R040, R120) require. Arithmetic is the most common reason e-invoices get rejected.
It is validated with the official rules, the same ones receiving platforms use: XSD, CEN EN 16931 Schematron, KoSIT XRechnung and OpenPeppol BIS 3.0. They run in pure Python through Saxon-HE (saxonche), so no Java is needed. Rule sets are pinned to exact releases and SHA-256 verified.
Errors come with fixes. Each finding shows the official rule ID, its message, the location and a hint written in terms of the invoice data.
It checks what the official rules miss: check digits of Leitweg-IDs, SIREN, SIRET, French and Belgian VAT numbers and GLN/GTIN. A typo there gives an invoice that validates but can't be routed.
It reads and converts invoices. Received XML or Factur-X/ZUGFeRD PDFs become JSON, or a readable HTML/PDF with labels in the seller's language (de/fr/nl/it/es/en). Conversions (UBL ↔ CII, ZUGFeRD → XRechnung, …) keep the source amounts.
**It makes Fac