invoicehub

Reviewed Jan 1, 2000.

• tools: 4 tools scanned
• metadata: scanned

No findings.

Tools (4)

• validate_invoice

  Validate an EU e-invoice XML string against the official EN 16931 Schematron. Accepts either syntax — UBL 2.1 (Invoice or CreditNote) or UN/CEFACT CII — and auto-detects which. A document declaring the XRechnung 3.0 CustomizationID is additionally checked against KoSIT's XRechnung delta ruleset. Returns whether it is valid and any failing BR-* / BR-DE-* business rules.

• generate_invoice

  Generate an EN 16931-conformant UBL 2.1 invoice from structured fields. The result is self-validated before being returned. Provide seller, buyer, and at least one line; for standard-rated (category "S") lines include a vatRate and the seller vatId.

• convert_invoice

  Convert an e-invoice between formats via the shared EN 16931 canonical model: parse the source document, re-serialize as the target, and validate the result before returning it — never a document that has not been checked. Format ids: "UBL_2.1" (OASIS UBL, the universal Peppol/EN16931 baseline), "UN_CEFACT_CII" (UN/CEFACT Cross Industry Invoice, required syntax for Chorus Pro/France and many ERP back-ends), "XRechnung_UBL" / "XRechnung_CII" (Germany's mandatory B2G format, XRechnung 3.0 — required for invoicing German public-sector buyers), "Factur-X" (France/Germany hybrid PDF+XML — a human-readable PDF/A-3 with the structured invoice embedded, common for French B2B). Binary formats (Factur-X) are base64 in both directions. Requires an API key on the Pro plan or above for any target beyond plain UBL_2.1 — call list_supported_formats to see current availability.

• list_supported_formats

  List the e-invoice formats InvoiceHub validates today and what is on the roadmap.