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

Convert Invoice

AI-generated

Summary

Convert an XML or PDF invoice to a selected EN 16931 family format by sending its document bytes to the beliq API. The result includes the converted document as binary data and conversion metadata; conversion losses may be reported in that metadata.

Inputs

  • Input — Choose Binary (default) to read the document from an n8n binary field, or Text to supply XML invoice text.
  • Input Binary Field (required) — Binary property containing the source XML or PDF; defaults to data and is used when Input is Binary.
  • Input Text (required) — Source XML invoice text; used when Input is Text.
  • Input Content Type — Set to Auto-Detect (default), XML, or PDF. Auto-Detect checks for the PDF signature and otherwise treats the input as XML.
  • Source Format — Choose Auto-Detect (default), CII, Factur-X, Peppol BIS, UBL, XRechnung, or ZUGFeRD to identify the source format.
  • Target Format (required) — Format to convert to: CII, Factur-X, Peppol BIS, UBL (default), XRechnung, or ZUGFeRD.
  • Target Profile — Profile identifier for Factur-X or ZUGFeRD targets. Defaults to EN 16931. This only rewrites the profile identifier; it does not adapt invoice content, so invoices with lines may fail the MINIMUM or BASIC WL profile schema.
  • Drop France CTC Overlay — Whether to drop the French CTC overlay if the target cannot carry it; dropping it is lossy. Defaults to false.
  • Put Output In Field (required) — Binary property to write the converted document to; defaults to data.
  • Advanced (JSON) — JSON values deep-merged into the conversion query string for parameters without controls above. Request headers cannot be set here.

Output shape

One n8n item per input item, containing conversion metadata in JSON and the converted document in binary data.

The binary property uses the configured output field. JSON metadata includes success, content type, byte size, source and target formats, detected profile when available, lost-element count and details, conversion tools, and output envelope. Empty input errors; with Continue On Fail enabled, an item instead contains an error in its JSON.

Links

Discussion