Update to NormAPI – XRechnung & ZUGFeRD

{
  "description": "Check, read and create German e-invoices (XRechnung, ZUGFeRD/Factur-X) with NormAPI, and explain the official business rules they break.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Check, read and create German e-invoices (XRechnung, ZUGFeRD/Factur-X) with NormAPI, and explain the official business rules they break.\n---\n\n# Working with German e-invoices through NormAPI\n\nNormAPI checks e-invoices against the official KoSIT rule set, the one German\npublic-sector portals use, and states the rule set version with every result.\nIt is technical validation: it says whether an invoice meets the EN 16931 and\nXRechnung rules, not what an invoice should contain for tax purposes.\n\n## Pick the tool by what the user has\n\n- **An invoice to check** (XML or a ZUGFeRD/Factur-X PDF): `validate_invoice`.\n  Pass an uploaded file in `file`; XML pasted into the chat goes in `xml` as it\n  is. Report the verdict (`acceptable`), the rule set version, and for each\n  finding its code, what it means and the fix, quoted rather than paraphrased.\n  An INFORMATION finding is a recommendation; only ERROR findings make an\n  invoice unacceptable.\n- **An invoice to understand** (a received invoice): `parse_invoice`. Answer\n  questions from its data (seller, buyer, lines, totals as stated), and say so\n  when `notMapped` lists something the question touches. Add `validate: true`\n  when the user also wants the verdict.\n- **A rule code** such as BR-DE-15 or BR-CO-16: `explain_rule`.\n- **An invoice to create**: `generate_invoice`. It needs the user's NormAPI\n  account, and each document counts against that account's monthly allowance.\n\n## Creating an invoice\n\nBuild the invoice only from data the user gave. If the seller, the buyer, the\nlines, VAT or payment details are missing, ask for them instead of inventing\nthem. Choose the profile by the recipient: `xrechnung` for a German public\nauthority (it needs the Leitweg-ID as buyer reference, a seller contact and\nboth electronic addresses), `en16931` for a business. Choose `ubl` or `cii` for\nan XML file, `zugferd` for a PDF with the invoice embedded.\n\nA refusal names the rules the data breaks and how to fix each; correct the data\nand try again once rather than retrying unchanged. When the allowance is used\nup, say so; validating and reading invoices keep working.\n\n## What NormAPI does not do\n\nIt does not send invoices to recipients or portals (Peppol, OZG-RE), does\nnot store invoices, and gives no tax or legal advice.\n"
}