beliq icon

beliq

Generate, validate, parse and convert e-invoices (XRechnung, ZUGFeRD, Factur-X, Peppol BIS, NLCIUS, FatturaPA, Facturae, e-SLOG, KSeF FA(3))

Actions4

Generate Invoice

AI-generated

Summary

Generate an e-invoice from a beliq EN 16931 invoice object using the selected standard, then optionally validate the generated document. The result includes invoice metadata and the document as binary output; NLCIUS is generated as Peppol BIS with the Netherlands profile and always returns XML.

Inputs

  • Standard (required) — Choose XRechnung (default), Peppol BIS, Factur-X, ZUGFeRD, E-SLOG, Facturae, FatturaPA, KSeF FA(3), or NLCIUS. The national formats are schema-checked only; the others are authority-checked. KSeF supports ordinary PLN VAT invoices between Polish parties at the listed rates and does not submit them to KSeF.
  • Output (required) — Choose XML (default) or PDF. Factur-X and ZUGFeRD PDFs embed the XML in a hybrid PDF/A-3; other standards produce a PDF visualization without embedded XML, while the legal document remains XML. NLCIUS always returns XML.
  • Factur-X Profile / ZUGFeRD Profile — For Factur-X or ZUGFeRD, select the profile (default EN 16931). MINIMUM and BASIC WL carry no invoice lines; EXTENDED CTC FR is available only for Factur-X.
  • Invoice (JSON) (required) — Provide the invoice in beliq EN 16931 shape, including invoice identifiers and dates, currency, seller and buyer, lines, tax summary, payment means, and totals as applicable. The displayed sample is an XRechnung example in EUR with a German seller; replace it with supplied invoice data. KSeF requires PLN and Polish parties.
  • Validate Result — Defaults to true; requests validation of the generated document and includes the validation result.
  • Put Output In Field (required) — Name of the binary output field for the generated document; defaults to data.
  • Advanced (JSON) — Optional raw JSON deep-merged into the generate request body for fields without dedicated controls. It cannot set request headers.

Output shape

One output item per input item. The binary document is written to the configured field; JSON contains success, contentType, and sizeBytes, plus schematronVersion and, when provided, pdfKind.

The generated document is returned as binary data. With NLCIUS the request uses Peppol BIS and the netherlands-nlcius profile, and the output is forced to XML. With continue-on-fail enabled, a failed item returns JSON containing an error instead.

Examples

Example 1: Generate an authority-checked XRechnung from the supplied invoice object, keep XML output, and validate the result.

Select XRechnung, XML, and Validate Result enabled; provide the invoice in beliq EN 16931 shape.

Example 2: Generate a Factur-X hybrid PDF/A-3 using the BASIC profile.

Select Factur-X, BASIC profile, and PDF output; provide invoice data suitable for that profile.

Example 3: Generate a Netherlands NLCIUS invoice.

Select NLCIUS and provide invoice data for that use; the node generates Peppol BIS with the Netherlands profile and returns XML.

Links

Discussion