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.
| Name | Description | Required |
|---|
| Import Options | Choose the input source, either Upload a File or Import a file from URL. | Yes |
Upload a File
| Name | Description | Required |
|---|
| Data | Upload a file using raw binary data from another module. Note: This requires additional credits as it first uploads to PDF.co Temporary Files Storage. | Yes |
Import a file from URL
| Name | Description | Required |
|---|
| URL | Provide the URL to the source PDF document, or a filetoken:// link from PDF.co Built-In Files Storage. If you use another cloud service such as Google Drive or Dropbox ensure the link is publicly accessible. | Yes |
| Name | Description | Required |
|---|
| customField | Comma-separated list of custom field names to extract. Use camelCase for field names (e.g., storeNumber, deliveryDate). | No |
| lineItemStructure | A JSON object that defines a custom structure for line items. Each key is a field name (in camelCase) and each value is "string" or "number". | No |
| Webhook URL | The callback URL or Webhook used to receive the output data. | No |
| Export Type | Choose between Download a File or JSON Output. Default is Download a File. | No |
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
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
| Name | Description |
|---|
body | An object array containing the all invoice parsing result. |
error | Details of any errors (if any). |
status | The response status code. If all good this will be 200. |
credits | The credits spent on the process. |
remainingCredits | The credits left on your account. |
duration | The time it took for the process. |
Page Count | Total Page Count. |
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 (Українська)