Skip to main content
Important
  • Only invoices will be parsed. For all other documents, please use our existing Document Parser.
  • To ensure accurate processing, each invoice must be clearly separated. If an invoice contains multiple pages, we recommend splitting it into individual PDFs using the PDF Split node in your workflow.
  • While AI Invoice Parser supports multi-page invoices, the total page count for a single PDF must not exceed 100 pages. Submitting large PDFs containing multiple invoices is not recommended.
Make Step

Input


Upload a File Import a file from URL

Integrating External File Sources

Streamline your Make workflows with external file sources like Google Drive and Dropbox using their unique actions. Discover efficient integration strategies in our guide: File Source Integrations in Make.

Custom Fields

AI Invoice Parser with custom fields support automatically detects invoice layouts and extracts both standard schema data and user-specified custom fields without requiring manual templates. The customField parameter allows you to specify additional fields to extract beyond the standard schema. Some examples include:
  • storeNumber - Store or branch identifier
  • deliveryDate - Expected delivery date
  • financialCharges - Additional financial charges
  • lineTotal - Total amount for line items
  • purchaseOrderRef - Purchase order reference number
  • customerReference - Customer reference number
  • departmentCode - Department or cost center code
If a custom field returns an empty value, please contact our support team to help improve the extraction accuracy.

Line Item Structure

The lineItemStructure parameter lets you define a custom schema for line items. Each key is a field name you choose (in camelCase) and each value is the expected data type — either "string" or "number". When provided, every object inside the lineItems array will contain exactly the fields you specified. If a value cannot be extracted from the invoice, the field will still be present with an empty or default value instead of being omitted.
Use camelCase for field names (e.g., unitPrice, totalPrice). The field names you define will be used as-is in the response, giving you full control over the output keys.

Output

Supported Languages

  • Albanian (Shqip)
  • Bosnian (Bosanski)
  • Bulgarian (Български)
  • Croatian (Hrvatski)
  • Czech (Čeština)
  • Danish (Dansk)
  • Dutch (Nederlands)
  • English
  • Estonian (Eesti)
  • Finnish (Suomi)
  • French (Français)
  • German (Deutsch)
  • Greek (Ελληνικά)
  • Hungarian (Magyar)
  • Icelandic (Íslenska)
  • Italian (Italiano)
  • Latvian (Latviešu)
  • Lithuanian (Lietuvių)
  • Norwegian (Norsk)
  • Polish (Polski)
  • Portuguese (Português)
  • Romanian (Română)
  • Russian (Русский)
  • Serbian (Српски)
  • Slovak (Slovenčina)
  • Slovenian (Slovenščina)
  • Spanish (Español)
  • Swedish (Svenska)
  • Turkish (Türkçe)
  • Ukrainian (Українська)