Skip to main content

Create ZUGFeRD Invoice (Zapier)

With PDF4me on Zapier you can turn CSV, JSON, or XML invoice data into ZUGFeRD output (often paired with Factur‑X naming). Pick XmlWithPdf when you need one file that people can open as a PDF while machines still read the embedded XML. Pick XmlOnly when the next system only wants the invoice XML.

What are you building?

The Create ZUGFeRD Invoice action combines your template PDF (for hybrid output) with invoice data from an earlier trigger or step. You choose Input Format, Output Mode, then Conformance, version, optional render on PDF, and language. Teams in Germany, the wider EU, and anywhere buyers ask for structured e‑invoices use this pattern; requirements often line up with EN 16931 style content even though your exact profile is agreed with the buyer or ERP.

Who is this page for?

If your customer or regulator expects ZUGFeRD or Factur‑X, or you already trade B2B in Germany, Austria, France, Benelux, or other EU markets moving toward structured invoicing, this Zap action is the right place to generate the file in Zapier. Replace our screenshots with your own Zap editor captures when you publish internally so people recognize their layout.

Connect PDF4me

Sign in to PDF4me when Zapier asks, or paste an API key from your PDF4me dashboard. Run Test on the step once fields are filled so you know calls succeed before you turn the Zap live.

One data format per run

Fill either Invoice Csv Data or Invoice Xml Data or Invoice Json Data, and make sure Input Format matches. Stuffing two formats “just in case” usually breaks the step or validation!

Configure the PDF4me step

Zapier usually moves you through connection, field mapping, then testing. After you rename earlier steps, hit Refresh fields so dropdowns show the right samples.

The images here show CSV plus XmlWithPdf and the conformance block. Swap them for screenshots from your Zap so new hires see the same buttons they use in production.

Template PDF plus CSV (XmlWithPdf)

Use one step for the PDF shell (often File and File Name) and another for the CSV file. Set Input Format to CSV and Output Mode to XmlWithPdf to get a hybrid ZUGFeRD PDF.

Zapier PDF4me Create ZUGFeRD Invoice action showing File and File Name from prior steps, Input Format CSV, Output Mode XmlWithPdf, Invoice Csv Data mapped from earlier Dropbox file, Invoice Xml and Json empty

Point File and File Name at your layout PDF (for example SimplePdf.pdf). Point Invoice Csv Data at the CSV coming from your download step. Leave the XML and JSON invoice fields blank when you stay on CSV.

Conformance, version, render, language

Pick Conformance Level (many teams start at BASIC), Zugferd Version (often 1.0), whether to Render Invoice on PDF, and Language if labels must follow a locale.

Zapier Create ZUGFeRD Invoice showing Invoice Csv Data from prior step, empty Xml and Json fields, Conformance BASIC, Zugferd Version 1.0, Render Invoice on PDF True, Language field

Conformance Level and Zugferd Version are normally required. Render Invoice on PDF matters when you stay on the hybrid PDF path.

Quick reminders

Hybrid PDF vs XML only

XmlWithPdf gives you a PDF people can open, with XML tucked inside for systems. XmlOnly skips the PDF wrapper when the receiver only ingests XML.

Where CSV lands

Pipe the actual file from Dropbox, Drive, or HTTP into Invoice Csv Data the way your PDF4me action expects (binary vs plain text). If the test fails, compare against a known good CSV first.

Conformance levels

Stay on BASIC until your buyer asks for COMFORT or EXTENDED. Those jumps change how much detail must sit in the payload, so confirm with whoever receives the file.

Field reference

ParameterUsuallyPurposeExample map
FileOften requiredTemplate PDF used when you output XmlWithPdf.`3. File`
File NameOften requiredFilename for that PDF including extension.`3. File Name` plus extension
Input FormatRequiredWhether payload is CSV, JSON, or XML.`CSV`
Output ModeRequiredXmlWithPdf for hybrid file, XmlOnly for XML alone.`XmlWithPdf`
Invoice Csv DataIf CSVCSV payload when Input Format is CSV.`2. File`
Invoice Xml DataIf XMLXML payload when Input Format is XML.n/a
Invoice Json DataIf JSONJSON payload when Input Format is JSON.n/a
Conformance LevelRequiredProfile such as BASIC, COMFORT, EXTENDED.`BASIC`
Zugferd VersionRequiredVersion exposed in the action.`1.0`
Render Invoice on PDFOptionalDraw invoice detail on the PDF when using XmlWithPdf.`True`
LanguageOptionalLabels such as German or English.`de`

Note: For XmlOnly, Zapier may hide or relax the template PDF fields. Trust the required markers on the live action after you choose the output mode.

First Zap checklist

  1. Add PDF4me and pick Create ZUGFeRD Invoice (label may vary slightly by app version).
  2. Connect your account and map File and File Name from the step that holds your layout PDF.
  3. Set Input Format, then map only the matching invoice field (CSV, XML, or JSON).
  4. Set Output Mode to XmlWithPdf or XmlOnly.
  5. Set conformance, version, render, and language as needed.
  6. Test the step, fix any red errors, turn the Zap on, then send the output wherever your process needs it (Drive, email, webhook)!
Which invoice field goes where?Open if you use CSV, JSON, or XML.
CSV

Set Input Format to CSV. Map Invoice Csv Data. Leave XML and JSON empty.

JSON

Set Input Format to JSON. Map Invoice Json Data. Leave CSV and XML empty.

XML

Set Input Format to XML. Map Invoice Xml Data with valid invoice or ZUGFeRD XML per connector rules.

Ideas for real Zaps

Patterns that come up a lotExamples only; adapt paths and apps to your stack.
Dropbox CSV plus layout PDF
  1. Pull the CSV and the base PDF from Dropbox (or your storage).
  2. Run Create ZUGFeRD Invoice with XmlWithPdf and BASIC unless your buyer asked for more.
  3. Save or email the PDF from the next Zap step.
Webhook JSON from your app
  1. Catch JSON with Webhooks by Zapier or your SaaS trigger.
  2. Set Input Format to JSON and map Invoice Json Data.
  3. Ship the hybrid PDF to SFTP, Drive, or your ERP handoff.
Archive rules
  1. After you have the PDF, optionally run Create PDF/A if records policy demands it.
  2. Notify finance or drop the file into long term storage.
Where do teams use this?Typical contexts, not legal advice.
Manufacturing and B2B

Supplier invoices where the buyer wants one PDF plus embedded XML for AP portals.

Finance ops

Closing batches driven by CSV or JSON exports from the ERP.

SaaS billing

Push JSON out of your product and let Zapier package ZUGFeRD for enterprise buyers who ask for it.

Same task on other platforms

Power Automate: Create ZUGFeRD Invoice. n8n: Create Zugferd Invoice (Latest).

Get help