Skip to main content
Use the Convert PDF to E-Invoice action to embed invoice XML into a PDF/A-3 document. The action validates the result with veraPDF and Mustang. Provide a PDF invoice and matching Factur-X or ZUGFeRD XML. This action does not generate invoice XML or compare the amounts in the XML with the visible PDF.
Zapier Convert PDF to E-Invoice action with the PDF mapped from a Google Drive trigger and the XML mapped from a Find a File step
The screenshot maps Source PDF URL from the Google Drive trigger and Invoice XML URL from the Find a File step, with ZUGFeRD selected as the profile.

Input

The supported conformance levels are MINIMUM, BASIC WL, BASIC, EN16931, and EXTENDED. Select the profile family that matches your invoice XML.

Getting both file URLs

The two URLs do not have to come from the same trigger. You can map Source PDF URL from one earlier step and Invoice XML URL from another. For example, if a new-file trigger provides only the PDF, add a search step before PDF.co to find the matching invoice record in your accounting system or a lookup table. Use a shared invoice ID, such as INV-1001, to retrieve that invoice’s XML URL. Map the PDF from the trigger and the XML URL from the search result into the PDF.co action.
Both files must be ready before the PDF.co step runs. If the matching XML is missing or the lookup is ambiguous, stop the workflow and resolve the match first. Each invoice needs its own matching XML; do not reuse the sample XML for other invoices.
The XML must already exist as a supported invoice XML document, and its URL must let PDF.co download the file. A link that opens a sign-in page or file-sharing preview is not a direct XML download. See Zapier field mapping and search steps for setup details.

Example: Create a Factur-X invoice

  1. Add a PDF.co action after the steps that provide your PDF and invoice XML.
  2. Select Convert PDF to E-Invoice and connect your PDF.co account. See Getting Started with Zapier for connection instructions.
  3. Map your PDF and XML links to the corresponding input fields. To try the action, use this matching sample pair:
  4. Test the action and review the validation result.
  5. Map url to your storage app’s upload step to save the validated invoice. You can also save the JSON report from validationReportUrl.
This action is available in PDF.co app version 4.1.0 and later. If it is missing from an existing Zap, select the current PDF.co app version for that step.

Output

Timeouts and validation

In the Zapier editor, Test step has a 30-second execution limit. An editor timeout does not cancel the PDF.co job, which can continue processing and incur charges. Check PDF.co API Logs before submitting it again.
Published Zaps receive the result through a callback and resume when processing finishes. A job that times out in the editor may still complete in a published Zap. If the e-invoice fails validation, the step fails and the conversion charge is refunded. The error includes a Validation report: link when a report is available. Open that report to review the failed checks, correct the input PDF or XML, and submit the corrected files. Save the validated invoice and report to your own storage before their temporary links expire. See the PDF to E-Invoice API reference for XML requirements, validation details, and file-retention limits. To archive a PDF without embedding invoice XML, use Convert PDF to PDF/A.