Skip to main content
Important
  • Only invoice documents are supported for parsing.
  • 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 API.
  • 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.
Ai Invoice Parser Pn

​
Input

NameDescriptionRequired
Invoice File URLProvide 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
Custom FieldSpecify custom fields beyond the default list. Use comma-separated format for multiple custom fields extraction (e.g., storeNumber, lineTotal, financialCharges).No
Webhook URLThe callback URL or Webhook used to receive the output data.No

​
File Requirements and Limitations

The PDF.co AI Invoice Parser only supports files with up to 100 pages. Files exceeding this limit will not be processed, so please avoid uploading documents larger than 100 pages. If your file contains multiple invoices in a single PDF, use the Split PDF operation in n8n to separate each invoice before passing them to the AI Invoice Parser node.

​
Source PDF URLs

If your previous node or trigger outputs a binary file (e.g., from Gmail or other apps), you’ll need to upload the file first using the PDF.co Upload File operation to generate a valid URL. This URL is required as the input for the Source File URL field in all subsequent PDF.co actions. You can integrate with Google Drive, Dropbox, or other apps to trigger your automation and pass files into PDF.co.

​
Custom Field Extraction

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.

​
Output

NameDescription
PageCountTotal Page Count.
urlDirect URL to the final PDF file stored in S3.
bodyAn object array containing the all invoice parsing result.
durationThe time it took for the process.
errorDetails of any errors (if any).
statusThe response status code. If all good this will be 200.
jobIdUnique identifier for the background job.
creditsThe credits spent on the process.
remainingCreditsThe credits left on your account.

​
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 (Українська)