Create ZUGFeRD Invoice in Power Automate

What this action does

PDF4me Create ZUGFeRD Invoice builds hybrid e-invoices (human-readable PDF + machine-readable XML) aligned with ZUGFeRD / Factur-X conventions used in Germany and the EU. Use Pdf With Xml for a single file you can hand to customers and auditors, or Xml Only when your ERP or clearing platform consumes XML directly.

Authenticating Your API Request

To access the PDF4me Web API through Power Automate, every request must include proper authentication credentials. Authentication ensures secure communication and validates your identity as an authorized user, enabling seamless integration between your Power Automate flows and PDF4me document services.

Get your API Key

Power Automate configuration for Create ZUGFeRD Invoice.

Important Facts You Should Not Miss

Output mode controls the full behavior

In Pdf With Xml, map both invoice data and source PDF content. In Xml Only, invoice data is enough; PDF bytes are not required.

Map only one invoice data input

Pick one source format (XML, JSON, or CSV) and map only the matching field. Mixed mapping is the most common cause of validation failures.

Conformance and profile matter

Start with BASIC for broad compatibility. Move to COMFORT or EXTENDED when your buyer, ERP, or regulator requires richer invoice content (often discussed alongside EN 16931 semantic models).

Key Features

• Hybrid PDF output: One file with embedded invoice XML (Pdf With Xml) for customers and auditors
• XML-only path: Feed clearing houses or ERPs that ingest XML without a PDF shell
• Flexible input: Use existing XML, structured JSON, or CSV invoice data
• Conformance profiles: BASIC, COMFORT, EXTENDED to match receiver expectations
• Optional rendering: Control whether invoice data is drawn on the PDF visually
• Power Automate–native: Map SharePoint, OneDrive, Outlook, or Dataverse file content directly

Parameters

Required core settings: Input Format, Output Mode, Conformance Level, ZUGFeRD Version. Map PDF File Content when using Pdf With Xml.

Parameter	Required	Type	What it does	Example
File Name	Yes	String	Source PDF filename with extension (for Pdf With Xml).	Test.pdf
PDF File Content	Conditional	Binary	Required when Output Mode is Pdf With Xml. Map full file bytes.	Get file content
Output File Name	Recommended	String	Name of the generated file (Pdf With Xml output).	Zugferd-output.pdf
Input Format	Yes	Option	Invoice payload shape: XML, JSON, or CSV.	CSV
Output Mode	Yes	Option	Pdf With Xml = hybrid PDF; Xml Only = XML invoice.	Pdf With Xml
Invoice XML Data	Conditional	String	Use when Input Format = XML.	XML payload
Invoice JSON Data	Conditional	String	Use when Input Format = JSON.	JSON payload
Invoice CSV Data	Conditional	String	Use when Input Format = CSV.	CSV payload
Conformance Level	Yes	Option	Profile: BASIC, COMFORT, or EXTENDED.	BASIC
ZUGFeRD Version	Yes	Option	Specification version exposed in the connector.	1.0
Render Invoice on PDF	No	Boolean	Draw invoice data on PDF pages (Pdf With Xml).	Yes
Language	No	String	Optional locale for labels (e.g. de, en, fr).	de

Input and Output Decision Matrix

If you select	Then map	You get
Input Format = XML	Invoice XML Data	ZUGFeRD XML output path per Output Mode
Input Format = JSON	Invoice JSON Data	Same, from JSON source data
Input Format = CSV	Invoice CSV Data	Same, from CSV source data
Output Mode = Pdf With Xml	PDF File Content + File Name	PDF with embedded invoice XML
Output Mode = Xml Only	Invoice data only (no PDF bytes)	Standalone invoice XML

Quick Setup (Power Automate)

1. Add Create ZUGFeRD Invoice to your flow.
2. Map File Name and Output File Name for traceability.
3. Set Input Format to XML, JSON, or CSV.
4. Map only the matching invoice data field (XML, JSON, or CSV).
5. Set Output Mode — for Pdf With Xml, map PDF File Content; for Xml Only, skip PDF content.
6. Set Conformance Level and ZUGFeRD Version to match your receiver.
7. Store or email the result; optionally chain Validate PDF/A before archive.

Output

The action returns generated file content and metadata your flow can pass to SharePoint, Outlook, or ERP.

Output	Type	Description
File Content	Binary	Generated PDF (Pdf With Xml) or XML (Xml Only)
FileName (header)	String	Suggested output filename
PageCount (header)	String	Page count when PDF is returned

Output behavior

Pdf With Xml returns a PDF with embedded ZUGFeRD/Factur-X invoice XML. Xml Only returns invoice XML for systems that do not need a PDF.

Troubleshooting

Invoice data mapped to wrong format

If Input Format is CSV, map only Invoice CSV Data. Do not populate XML/JSON fields in the same run.

PDF output errors in Pdf With Xml

PDF File Content must come from a step that returns complete file bytes, not metadata-only references.

Profile and compatibility mismatch

Start with BASIC for compatibility tests. Upgrade to COMFORT or EXTENDED only when your receiving system confirms support.

Workflow Examples

Workflow ExamplesOpens by default — four ZUGFeRD patterns in a 2×2 grid. Collapse anytime.

ERP → hybrid PDF archive

1. Trigger when invoice is approved in ERP or Dataverse.
2. Get PDF layout and invoice JSON/XML/CSV from prior steps.
3. Run Create ZUGFeRD Invoice with Pdf With Xml.
4. Save to SharePoint records library; optionally run Validate PDF/A.

Impact: One file for humans and machines—strong fit for audit and long-term storage.

CSV batch from SharePoint

1. Trigger on new file in a “staging” folder.
2. Read CSV file content for invoice lines.
3. Set Input Format CSV and map Invoice CSV Data.
4. Output Pdf With Xml and route to “approved invoices” library.

Impact: Repeatable batch generation without manual desktop tools.

Xml Only → SAP / ERP

1. Upstream system produces invoice XML or JSON.
2. Set Xml Only and map the correct data field.
3. POST the returned XML to your ERP import or middleware.
4. Log correlation IDs for support traceability.

Impact: Clean handoff when the PDF shell is generated elsewhere.

Customer portal + email

1. Finalize invoice in your billing system.
2. Generate ZUGFeRD PDF with embedded XML.
3. Attach to Outlook or upload to customer portal.
4. Store metadata (invoice number, amount) in SharePoint columns.

Impact: Self-service download and fewer “wrong format” support tickets.

Industry Use Cases & Applications

Industry Use Cases & ApplicationsExpand to see manufacturing, finance, public sector, and SaaS scenarios.

Manufacturing & B2B

• Supplier invoices — hybrid PDF/XML for buyers with strict AP rules
• Order-to-cash — automate invoice packages from ERP events
• Audit trail — one artifact per shipment or milestone

Finance & Accounting

• Accounts receivable — compliant outbound e-invoices
• Month-end — batch XML or PDF+XML from consolidated data
• Archival — pair with PDF/A validation before records retention

Public sector & regulated

• Structured exchange — XML-only for mandated clearing
• Transparency — embedded XML supports verification workflows
• Retention — align with internal records policies

SaaS & platforms

• Billing exports — generate ZUGFeRD from JSON/CSV you already emit
• Multi-tenant — separate invoice JSON/XML/CSV or templates per customer in your flow
• Customer success — fewer manual “send invoice again” loops

Related Actions

Validate PDF/A

Verify archive compliance before storing generated invoice files.

Parse Document

Extract invoice data before mapping XML, JSON, or CSV into ZUGFeRD creation.

Generate EPC QR Code

Add SEPA-ready QR payment data in the same invoice automation flow.

Get Help

PDF4me ConnectGet your API KeyPower Automate Documentation