> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pdf.co/llms.txt
> Use this file to discover all available pages before exploring further.
# AI Invoice Parser
> Enhance your Zapier workflow by integrating this step to automatically detect invoice and structurally extract data with our advanced AI. The AI Invoice parser automatically detects invoice layouts without the manual effort previously required to supply document parsing templates for reference.
**Important**
* **Only invoices will be parsed**. For all other documents, please use our existing [**Document Parser**](/integrations/zapier/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 [Split PDF](/integrations/zapier/split-pdf) operation in your Zap.
* 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.
## Input
| Name | Description | Required |
| --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
| **Source PDF URL** | Provide the URL to the source PDF document, or a `filetoken://` link from [PDF.co Built-In Files Storage](https://app.pdf.co/files). If you use another cloud service such as **Google Drive** or **Dropbox** ensure the link is publicly accessible. Leave this field empty to generate blank PDF files containing barcodes. | Yes |
| **customField** | Comma-separated list of [custom field](/integrations/zapier/ai-invoice-parser#custom-fields) names to extract. Use `camelCase` for field names (e.g., `storeNumber`, `deliveryDate`). | No |
| **lineItemStructure** | A JSON object that defines a [custom structure](/integrations/zapier/ai-invoice-parser#line-item-structure) for line items. Each key is a field name (in `camelCase`) and each value is `"string"` or `"number"`. | No |
### Source PDF URL & Google
When using **Google Drive**, it’s typically recommended to choose the **File** option. For more advanced file integration techniques, see [Integrating File Sources with pdf.co](/integrations/zapier/input-file-sources).
### 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](https://pdf.co/support/request?subject=ai-invoice-parser%20-%20custom%20fields) 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
| Name | Description |
| ------------------ | ---------------------------------------------------------------------------------------- |
| `body` | An object array containing the all invoice parsing result. |
| `error` | Details of any errors (if any). |
| `status` | The [response status](/api-reference/introduction) 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. |
| `pageCount` | 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 (Українська)**