XRechnung Invoice Generator

Strict JSON in. A generated and technically validated XRechnung 3.0.2 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

• Select UBL Invoice or UN/CEFACT CII syntax in the same product.
• Generate invoices, credit notes, and corrected invoices supported by the adapter.
• Map EN 16931 parties, delivery, references, periods, attachments, allowances, charges, payment data, tax groups, and monetary totals.
• Run the release-pinned KoSIT XRechnung validator and return its findings.

Required product context

buyer_reference, seller contact details, and seller/buyer electronic endpoint identifiers are required by the XRechnung path.

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.