ZUGFeRD / Factur-X PDF Generator avatar

ZUGFeRD / Factur-X PDF Generator

Pricing

from $10.00 / 1,000 invoice generateds

Go to Apify Store
ZUGFeRD / Factur-X PDF Generator

ZUGFeRD / Factur-X PDF Generator

Generate a visible Factur-X 1.09 and ZUGFeRD 2.5 EN 16931 PDF/A-3 with pinned XML, container, and PDF/A validation evidence.

Pricing

from $10.00 / 1,000 invoice generateds

Rating

0.0

(0)

Developer

Kamer Ozkan

Kamer Ozkan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Strict JSON in. A generated and technically validated ZUGFeRD 2.5 / Factur-X 1.09 artifact out.

The Actor calculates totals with decimal arithmetic, generates the target invoice, runs an independent pinned validation stack, stores only accepted artifacts, and returns a SHA-256 evidence record. A rejected artifact is not delivered or charged under pay-per-event pricing.

Input

Use invoice for one document or invoices for a batch of up to 100. Amounts and quantities must be JSON strings such as "19.00", not floating-point numbers. The input schema exposes the complete production v1 canonical model and the strict product extension. Unknown fields are rejected instead of being silently ignored.

Production v1 capabilities

  • Generate Factur-X EN 16931 invoices, credit notes, and corrected invoices.
  • Render polished English, German, or French visible invoices with modern or classic layouts, logo, accent color, title, and footer options.
  • Accept an optional existing PDF/A-1 or PDF/A-3 visible document, then embed the generated CII XML.
  • Validate the CII rules, attachment relationship, metadata, and PDF/A-3.

Required product context

The production v1 profile is EN 16931. A user-supplied visible document must identify as PDF/A-1 or PDF/A-3 and is container-validated, but visual-to-XML semantic comparison is not performed.

Output

Each dataset row contains the technical assessment, artifact key, evidence key, hash, byte count, generator version, standard version, pinned ruleset, and bounded findings. The artifact and evidence JSON are private key-value store records.

For pay-per-event deployment, configure invoice-generated at exactly USD 0.01 and keep the synthetic apify-default-dataset-item event at USD 0. The synthetic apify-actor-start event may have any nonnegative configured price; every other event must remain free. The runtime refuses hosted non-PPE runs and unsafe event maps before reading input. Local non-PPE execution remains available for offline tests. A paid run charges only an artifact that was validated, stored, and delivered.

Operational boundary

This Actor generates and validates the document. It does not submit to Peppol, KSeF, SdI, or a French platform. It does not authenticate to an authority, create a qualified signature, perform legal archival, assign an official network identifier, or guarantee recipient or tax-authority acceptance. ACCEPTED means the generated artifact passed the documented pinned offline technical gate.