ZUGFeRD to XRechnung Converter

Convert supported ZUGFeRD or Factur-X CII content into a validated XRechnung UBL or CII target.

Outcome model

Every document ends in one explicit conversion state:

• CONVERTED: target XML was generated, parsed, validated by the pinned XRechnung rules, and found canonically equivalent after approved additions.
• NEEDS_INPUT: the source is usable, but mandatory target business terms are missing.
• UNSUPPORTED: the profile, version, target rule failure, or semantic gap is outside the automatic conversion matrix.
• NOT_EVALUATED: a required engine could not complete its assessment.

The Actor never emits a target artifact before target validation passes.

Supported matrix

• Input container: hybrid PDF or direct CII XML.
• Current D16B source profiles: BASIC, EN16931, and EXTENDED only when the canonical transfer to the target can be proven.
• ZUGFeRD 1.0 BASIC, COMFORT, and EXTENDED documents receive an automatic, fail-closed upgrade attempt. The original legacy XML must first pass the pinned Mustangproject 2.24.0 source validator. The same digest-pinned engine then upgrades it to CII D16B before normalization and conversion.
• MINIMUM and BASIC WL are explicitly rejected as semantically insufficient.
• Target syntax: UBL 2.1 or CII D16B.
• Target rules: XRechnung 3.0.2, configuration release 2026-01-31.

For ZUGFeRD 1.0, the canonical migration comparison starts at the upgraded D16B document. The result records

legacySourceToUpgradeIntegrity: NOT_PROVEN

Missing target data

KoSIT findings are translated into typed missingInputs. The safe override allowlist covers buyer reference, selected seller/buyer identifiers and addresses, seller contact data, and selected payment instruction terms.

Overrides:

• can add an absent allowlisted term only;
• can never replace an existing value;
• require a provenance reason;
• require a scheme identifier for electronic addresses;
• are validated by type and then by the target XRechnung engine;
• store the value as a SHA-256 in provenance, not as clear text.

If target validation exposes further missing terms, the result stays NEEDS_INPUT. Unsupported semantic differences stay UNSUPPORTED.

When requested, the key-value store can retain the original PDF-extracted legacy XML, the upgraded D16B intermediate, the validated target, and technical reports as separate artifacts. Dataset evidence includes their hashes without embedding invoice payloads.

Product boundary

This is an assisted, evidence-driven migration pipeline. It does not invent business data and does not make legal, tax, authenticity, signature, or recipient acceptance decisions.

Release state

The processing engine and Actor contract are feature-complete for the declared matrix. The source contains a fail-closed pay-per-event charge path for document-processed at exactly $0.01 per evaluated conversion. Local non-PPE results remain billable: false; a hosted run stops before processing unless the event and price contract are active. The synthetic apify-actor-start event is allowed, while apify-default-dataset-item must cost USD 0. Apify Console configuration, a Docker image build, and hosted lifecycle, charge-count, and budget-limit smoke tests remain before Store publication.