Conformance Level dropdown shows different options than expected
You toggled between Versions. Version 1.0 has BASIC, COMFORT, EXTENDED. Version 2+ has Empty, MINIMUM, BASICWL, BASIC, EN16931, EXTENDED, XRECHNUNG. Pick the version first; conformance levels follow.
Second File picker did not appear when Input Format is XML
It only appears when File is set to Map. Click the File radio and choose Map; the second File picker (for the XML invoice) renders below.
Buyer ERP rejects the hybrid PDF as non-compliant
Mismatched Conformance Level. Check what the receiver expects (commonly EN16931 for B2B EU, XRECHNUNG for German B2G). Re-run with the right value.
Output is XML only when you wanted the hybrid PDF
Output Mode is set to XML Only. Switch to XML With PDF.
Rendered invoice on PDF is missing line items
Render Invoice on PDF is set to No or Empty, or Output Mode is XML Only. Set both: Output Mode = XML With PDF AND Render Invoice on PDF = Yes.
Want JSON or CSV instead of XML as the input
Change Input Format. The Invoice XML Data / second File picker is replaced by an Invoice JSON Data or Invoice CSV Data text field, which you map from a Google Sheets, HTTP, or file-download module.
What is ZUGFeRD 2.0+ and how does it differ from 1.0?+
ZUGFeRD 2.0+ aligns with the EU EN 16931 e-invoicing standard and supports the modern Conformance Level set (MINIMUM, BASICWL, BASIC, EN16931, EXTENDED, XRECHNUNG). ZUGFeRD 1.0 predates EN 16931 and uses BASIC / COMFORT / EXTENDED only. For any new integration in 2026 use 2+; 1.0 is kept for legacy buyer ERPs.
Is ZUGFeRD the same as Factur-X?+
Same technical format under different brand names. ZUGFeRD is the German designation; Factur-X is the French equivalent. Both align to EN 16931 and are cross-compatible: a ZUGFeRD 2.x invoice is accepted by Factur-X receivers and vice versa.
Which Conformance Level should I pick for a typical EU B2B invoice?+
EN16931 (also called Comfort). It is the German legal default and the safe choice for EU business-to-business invoicing. Use XRECHNUNG when invoicing German public authorities (B2G). Use BASIC only when a recipient ERP explicitly requires it.
Do I need to author the XML myself?+
No. The screenshots use an existing XML (Input Format = XML), but the module also accepts JSON or CSV. Choose Input Format = JSON or CSV and the XML is built for you. Sample JSON and CSV files are in the section above.
What if my buyer needs only the XML, no PDF?+
Set Output Mode to XML Only. The module returns just the XML invoice file without a PDF wrapper. Useful when the receiving ERP renders its own document and only consumes the structured data.
Can I render line items visually on the PDF page?+
Yes. Set Render Invoice on PDF = Yes (only effective when Output Mode is XML With PDF). The module draws the invoice items as a visual table on the PDF pages so human reviewers see the invoice content without opening the embedded XML.
Does this work in Power Automate, n8n, or Zapier?+
Yes. The PDF4me Create ZUGFeRD Invoice action is available on all four platforms with the same parameters. See the cross-platform comparison at the bottom of the Make action reference page.
Does the output PDF/A-3 work with every PDF viewer?+
Yes. PDF/A-3 is backward-compatible with all PDF readers. Human readers see the rendered invoice PDF; ZUGFeRD-aware ERPs extract the embedded XML automatically. Non-aware tools just see a normal PDF.
