Pipedream

Generate, validate, parse, and convert e-invoices from a Pipedream workflow with the Beliq component.

Listing pending

A Pipedream component for Beliq: build event-driven workflows that generate, validate, parse and convert e-invoices. Every verdict carries the check depth the API states for it, or says that none was stated.

• Source: github.com/beliq-eu/pipedream-beliq

Connect a Beliq account with an API key from the Beliq dashboard (Integration → API Keys). The component reads api_key from the connected account and talks to https://api.beliq.eu.

• Generate Invoice: build an e-invoice (XML or PDF) from an EN 16931 invoice object, with the API’s verdict on its invoice XML and the check depth the API states. For a visualization PDF that is the XML it was rendered from, which is not returned.
• Validate Invoice: check an XML or PDF invoice against the rule packs and schemas Beliq lists for its format and return the API’s verdict, with the check depth the API states.
• Parse Invoice: extract a structured EN 16931 invoice object from an XML or PDF document.
• Convert Invoice: convert an invoice document from one EN 16931 format to another.
• Check Account: verify the connected API key and read its plan and quota. Does not consume quota.

• Input (Validate / Parse / Convert): paste the XML as text, or point the action at a file by a /tmp path (for example a file written by a previous step) or a public URL. Leave Content Type on auto-detect to let Beliq sniff XML versus PDF from the bytes.
• Output (Generate / Convert): the produced document is written to the step’s synced /tmp directory and the action returns the file path plus metadata (content type, size, Schematron version, source/target format). Downstream steps read the file by path. Generate also returns the document’s sha256 and the API’s verdict in validationResult. An XML source sent to Factur-X or ZUGFeRD comes back as CII XML. A PDF comes back only when a hybrid PDF source is converted to Factur-X or ZUGFeRD: the PDF as sent when its embedded XML already is the target, otherwise that PDF re-wrapped around the converted XML. A PDF answer of Convert carries pdfNote, which says what was checked.

Validate returns the API’s result as it came. Read valid together with verificationBadgeLabel, the check depth the API states for that result; a result without it states none. valid means the document passed the rule packs and schemas Beliq lists for its format, in the stated versions. It does not mean every recipient, validation tool or tax authority accepts it.

The step summary gives the verdict as VALID or INVALID with the check depth beside it, or check depth not stated, and the error count. A France CTC block (franceCtcBlockingRuleIds) ends a transmission even where valid is true, so the summary leads with the number of blocking rules and counts the document as failed; the API’s own message stays in the result’s warnings. Generate’s summary does the same for the document it produced. With Validate Result off nothing is checked, and the summary says NOT VALIDATED.

• Quickstart: the underlying API in five minutes.
• Authentication: keys, quotas, and rate limits.
• API reference: the operations this component calls.