E-Invoice icon

E-Invoice

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

Actions3

Overview

This node is designed to extract invoice data from electronic invoices provided in XML format. It supports extracting structured invoice information embedded within XML files, which is common in standardized e-invoice formats such as ZUGFeRD, XRechnung, Factur-X, or EN-16931. This node is beneficial for automating the processing of incoming invoices by converting raw XML invoice data into structured JSON objects that can be further used in workflows for accounting, auditing, or ERP integration.

Practical examples include:

  • Automatically extracting invoice details like supplier, buyer, line items, totals, and tax information from XML e-invoices received via email or API.
  • Feeding extracted invoice data into accounting software or databases without manual data entry.
  • Validating invoice contents against business rules or compliance requirements.

Properties

Name Meaning
Input Binary Field The name of the input binary field containing the file with embedded Invoice XML information to be extracted. Typically this would be the binary property holding the XML file data (e.g., "data").
Options A collection of additional options to customize extraction behavior:
- Keep Source Determines what source data to keep in the output alongside the extracted invoice data. Options are:
• JSON — Include JSON data of the input item
• Binary — Include binary data of the input item
• Both — Include both JSON and binary data
- Password Password string to provide if the PDF (if applicable) is encrypted. For XML extraction, this may be unused or ignored.
- Return Raw as JSON Whether to return the raw XML data of the e-invoice parsed as a JSON object instead of or alongside the extracted fields.
- Return Raw as XML Whether to return the raw XML data of the e-invoice as an XML string. Mutually exclusive with "Return Raw as JSON".

Output

The node outputs an array of JSON objects representing the extracted invoice data from the XML file. The structure typically includes key invoice elements such as:

  • Supplier information
  • Buyer information
  • Invoice number and date
  • Line items with descriptions, quantities, prices, and taxes
  • Totals and tax summaries

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

Additionally, if enabled, the raw XML content can be returned either as a JSON-parsed object or as a raw XML string under dedicated output fields.

Dependencies

  • The node requires the input XML file to be provided as binary data in a specified binary property.
  • No explicit external API keys or services are required; the extraction logic is bundled internally.
  • If dealing with encrypted PDFs (not relevant for XML resource), a password can be supplied.
  • Proper configuration of the input binary field name is necessary to locate the XML file data.

Troubleshooting

  • Common issues:

    • Incorrect binary property name: Ensure the "Input Binary Field" matches the actual binary property containing the XML file.
    • Malformed or unsupported XML: The node expects well-formed XML conforming to supported e-invoice standards.
    • Conflicting options: Enabling both "Return Raw as JSON" and "Return Raw as XML" simultaneously is not allowed.

  • Error messages:

    • Errors related to missing binary data usually indicate the specified binary property does not exist or is empty.
    • Parsing errors suggest invalid XML content or unsupported invoice format.

  • Resolutions:

    • Verify the binary property name and ensure the input contains valid XML data.
    • Validate the XML file externally to confirm it meets expected schema standards.
    • Use only one of the raw return options at a time.

Links and References

Discussion