Parse Invoice
AI-generatedSummary
Parse an XML or PDF invoice into a structured invoice object. The operation detects UBL or CII syntax from the document; the Format setting does not change that behavior.
Inputs
- Input — Choose Binary (default) to read the document from the named binary field, or Text to provide the XML invoice as text.
- Input Binary Field (required) — Binary property containing the XML or PDF document; defaults to
dataand is used when Input is Binary. - Input Text (required) — XML invoice text; used when Input is Text.
- Input Content Type — Content type of the input. Auto-Detect (default) identifies PDF from its
%PDF-header and treats other input as XML; XML or PDF can also be selected explicitly. - Format — Auto-Detect by default, with CII and UBL options. The source says this hint has no effect: parsing detects the syntax and reads UBL and CII, including XML embedded in ZUGFeRD or Factur-X PDFs.
- Advanced (JSON) — Optional raw JSON deep-merged into the parse query string for additional query parameters. It cannot set request headers.
Output shape
A single JSON item per input item, containing the parsed invoice data.
The node uses the API response's
dataproperty when present; otherwise it returns the response object. Output items are paired with their input items. Empty documents fail; with Continue On Fail enabled, an error item is returned.
Examples
Example 1: Parse an XML invoice from an incoming binary field
Keep Input set to Binary, set Input Binary Field to the field holding the XML (default data), and leave Input Content Type on Auto-Detect.
Example 2: Parse XML invoice text
Set Input to Text, provide the XML in Input Text, and leave Input Content Type on Auto-Detect or select XML.
Example 3: Parse a Factur-X or ZUGFeRD PDF
Provide the PDF as binary and use Auto-Detect for Input Content Type; the parser reads its embedded XML when it is UBL or CII.