NormAPI – XRechnung & ZUGFeRD
Dmytro Yalanskyi v1.0.0
Check and create e-invoices
Save this plugin to Following and return to review observed changes. Follow up to 10 plugins free.
Description
From the marketplace listing
NormAPI checks, reads and creates German e-invoices — XRechnung (UBL and CII XML) and ZUGFeRD/Factur-X PDFs — against the official KoSIT rule set, the one German public-sector portals use. Every result names the rule set version that produced it. What you can do: • Check an invoice. Upload the XML or the PDF and ask whether it is valid. You get the verdict and every finding, and each business-rule finding comes with what the rule requires, why invoices typically break it, and how to fix it, in English or German. • Read a received invoice. NormAPI turns it into structured data — seller, buyer, lines, VAT breakdown and totals exactly as the document states them — and lists anything it could not map, so questions about the invoice are answered from its data. • Look up a rule. Ask what a code such as BR-DE-15 or BR-CO-16 means and how to fix it. • Create an invoice. Describe the invoice and NormAPI produces an XRechnung (UBL or CII XML) or a ZUGFeRD PDF: an XRechnung for a public-sector buyer, a plain EN 16931 invoice for a business. Totals are computed on the server in decimal arithmetic, and the document is validated against the official rules before you get it; data the rules do not permit is refused, with the rules it breaks and how to fix each. Checking, reading and rule lookups need no account. Creating invoices needs a NormAPI account: you sign in the first time you create one, and each generated document counts against that account's monthly allowance. Invoices are processed in memory on servers in the EU and are never stored. NormAPI is technical validation, not tax or legal advice, and it does not send invoices to recipients or portals.
Language: English · Automatically detected from descriptions.
Competitor profile
From the developer’s listing and package; capabilities are not independently tested. Package observed Nov 3, 2026.
Declared capabilities
Check and create e-invoices
Declared limitations
- Tax advice is outside NormAPI: its tools check an invoice's format rules, not which VAT rate applies.
- NormAPI does not transmit invoices; no tool sends anything.
- An invoice must not be created from invented data.
Review scenarios; not an exhaustive list.
Cost & access
Pricing and account requirements have not been established from the available package declarations. Unknown pricing does not mean free access.
Starter prompt
Check this XRechnung against the official rules and explain every error
Keywords
Files & skills
File archives
Skill instructions
get-started2.27 KB
--- name: get-started description: Check, read and create German e-invoices (XRechnung, ZUGFeRD/Factur-X) with NormAPI, and explain the official business rules they break. --- # Working with German e-invoices through NormAPI NormAPI checks e-invoices against the official KoSIT rule set, the one German public-sector portals use, and states the rule set version with every result. It is technical validation: it says whether an invoice meets the EN 16931 and XRechnung rules, not what an invoice should contain for tax purposes. ## Pick the tool by what the user has - **An invoice to check** (XML or a ZUGFeRD/Factur-X PDF): `validate_invoice`. Pass an uploaded file in `file`; XML pasted into the chat goes in `xml` as it is. Report the verdict (`acceptable`), the rule set version, and for each finding its code, what it means and the fix, quoted rather than paraphrased. An INFORMATION finding is a recommendation; only ERROR findings make an invoice unacceptable. - **An invoice to understand** (a received invoice): `parse_invoice`. Answer questions from its data (seller, buyer, lines, totals as stated), and say so when `notMapped` lists something the question touches. Add `validate: true` when the user also wants the verdict. - **A rule code** such as BR-DE-15 or BR-CO-16: `explain_rule`. - **An invoice to create**: `generate_invoice`. It needs the user's NormAPI account, and each document counts against that account's monthly allowance. ## Creating an invoice Build the invoice only from data the user gave. If the seller, the buyer, the lines, VAT or payment details are missing, ask for them instead of inventing them. Choose the profile by the recipient: `xrechnung` for a German public authority (it needs the Leitweg-ID as buyer reference, a seller contact and both electronic addresses), `en16931` for a business. Choose `ubl` or `cii` for an XML file, `zugferd` for a PDF with the invoice embedded. A refusal names the rules the data breaks and how to fix each; correct the data and try again once rather than retrying unchanged. When the allowance is used up, say so; validating and reading invoices keep working. ## What NormAPI does not do It does not send invoices to recipients or portals (Peppol, OZG-RE), does not store invoices, and gives no tax or legal advice.
Release notes
First version: validate_invoice, parse_invoice and explain_rule without an account; generate_invoice after signing in to NormAPI.
Declared in the saved package. Remote tools may change independently.
Package details
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
- Package author
- Dmytro Yalanskyi
- Keywords
- See keywords
- Listing translations
- de-DE
- Getting started skill
- ./skills/get-started/SKILL.md
- Review scenarios
- 5 positive · 3 negativeScenario counts, not test results.
Package observed Nov 3, 2026.
Technical details
- First seen
- Oct 28, 2026 · 18:00 UTC
- Last seen
- Nov 3, 2026 · 18:00 UTC
- Collection status
- Collected
plugin_asdk_app_6ae095cc72f08191abefb95adb793f9f
Download plugin data (JSON)