invoicehub

n8n node for InvoiceHub — validate, generate, convert and read EU e-invoices (UBL 2.1, UN/CEFACT CII, XRechnung 3.0, Factur-X) against the official EN 16931 rules.

Package Information

Released: 1 mo ago
Downloads: 0 weekly / 0 monthly
Latest Version: 0.1.0
Author: InvoiceHub

Documentation

n8n-nodes-invoicehub

An n8n community node for InvoiceHub — work with EU e-invoices without hand-rolling EN 16931 compliance.

Validate, generate, convert and read UBL 2.1, UN/CEFACT CII, XRechnung 3.0 and Factur-X / ZUGFeRD, checked against the official CEN Schematron rather than a reimplementation of it.

Installation

In n8n: Settings → Community Nodes → Install, then enter:

n8n-nodes-invoicehub

Credentials

You need an InvoiceHub API key — free, no credit card, at invoicehub.dev. The free tier covers unlimited validation plus 50 documents a month.

Operations

Receive (parse any format)

The one most people need first. From 1 September 2026 every VAT-registered business in France must be able to receive an e-invoice; German businesses have had to since January 2025 — and you don't choose the format, the sender does.

Feed it whatever arrived — XML, or a Factur-X/ZUGFeRD PDF as base64 — and get back one consistent JSON shape plus what it turned out to be:

{
  "detected": { "formatId": "XRechnung_CII", "syntax": "cii" },
  "invoice": { "invoiceNumber": "INV-2026-0142", "totals": { "payableAmount": 1190.00 } },
  "report": { "valid": true, "errors": [] }
}

A non-conformant invoice still comes through with its data alongside the report — you can't reject a supplier's invoice just because a validator dislikes it, so you get both and decide.

Validate

Check a document against the official EN 16931 Schematron. Accepts either syntax and detects which. Free and unmetered on every plan.

Generate

Build an EN 16931-conformant UBL 2.1 invoice from structured fields. Validated before it's returned — a document that would fail is never handed back as though it passed.

Convert

Re-serialise an invoice as another format via the shared canonical model. Formats beyond UBL 2.1 need a Pro plan.

Use with AI agents

The node is marked usableAsTool, so n8n's AI Agent node can call it directly — useful for "read this invoice and file it" style automations.

Why the validation is trustworthy

  • EN 16931 — official CEN Schematron artifacts (v1.3.16), both syntaxes, compiled unmodified.
  • XRechnung — KoSIT's own published validator configuration, merged with the EN 16931 core so BR-DE-* rules actually fire.
  • Factur-X — PDF/A-3 output verified against veraPDF in CI.
  • Output is checked in CI against the real KoSIT validator, the same tool German public-sector receivers run. It caught two genuine schema bugs that would otherwise have shipped.

Links

Docs · Receiving guide · Supported formats · npm client for Node

Licence

MIT

Discussion