E-Invoice icon

E-Invoice

Handle E-Invoices (ZUGFeRD / XRechnung / Factur-X / EN-16931)

Overview

This node, named "E-Invoice," is designed to extract invoice data from electronic invoices embedded in PDF or XML files. It supports common e-invoice standards such as ZUGFeRD, XRechnung, Factur-X, and EN-16931. The primary use case is automating the extraction of structured invoice information (like invoice number, date, amounts, and line items) from documents that contain embedded XML invoice data.

A typical scenario would be processing incoming PDF invoices received via email or file upload, extracting their invoice details automatically for further processing in accounting or ERP systems. For example, a user can input a PDF containing an embedded XML invoice, and the node will parse and output the structured invoice data for downstream workflow steps.

Properties

Name Meaning
Input Binary Field The name of the binary input field containing the PDF file with embedded invoice XML data to extract.
Options A collection of additional options:
- Keep Source Choose what source data to keep in the output: JSON data only, binary data only, or both.
- Password Password to unlock the PDF if it is encrypted.
- Return Raw as JSON Whether to return the raw embedded XML invoice data converted into a JSON object.
- Return Raw as XML Whether to return the raw embedded XML invoice data as an XML string.

Output

The node outputs JSON data representing the extracted invoice information parsed from the embedded XML within the PDF. This typically includes structured fields such as invoice metadata, supplier and customer details, line items, totals, and tax information.

If configured, the node can also include the original input data in JSON and/or binary form depending on the "Keep Source" option.

Additionally, users can opt to receive the raw embedded XML invoice data either as a JSON object or as a raw XML string, useful for debugging or custom processing.

Dependencies

  • The node requires input PDF files that contain embedded XML invoice data compliant with supported e-invoice standards.
  • If PDFs are password-protected, the correct password must be provided.
  • No external API keys or services are explicitly required; all processing appears to be done internally.
  • The node depends on bundled internal modules for parsing and extraction logic.

Troubleshooting

  • Issue: Extraction returns empty or incomplete data.
    Cause: The PDF may not contain embedded XML invoice data or uses an unsupported format.
    Resolution: Verify the PDF contains valid embedded XML invoice data compliant with supported standards.

  • Issue: Node fails on encrypted PDFs without password.
    Cause: Encrypted PDF requires a password to access embedded data.
    Resolution: Provide the correct password in the "Password" option.

  • Issue: Raw XML or JSON output options are mutually exclusive.
    Cause: Both "Return Raw as JSON" and "Return Raw as XML" cannot be true simultaneously.
    Resolution: Enable only one of these options at a time.

  • Issue: Incorrect binary input field name causes failure.
    Cause: The specified binary property does not exist in the input data.
    Resolution: Ensure the "Input Binary Field" matches the actual binary field name containing the PDF file.

Links and References

Discussion