XRechnung to JSON Parser

Parse XRechnung UBL 2.1 Invoice, UBL 2.1 CreditNote, or CII D16B XML into one stable EN 16931-oriented JSON contract.

Quick start

The following input uses an official XRechnung testsuite invoice pinned to an immutable source commit:

{
  "documents": [
    {
      "documentId": "official-ubl-smoke",
      "fileName": "01.01a-INVOICE_ubl.xml",
      "url": "https://raw.githubusercontent.com/itplr-kosit/xrechnung-testsuite/b3791d47a2e1446b1751a27cb732aac294231293/src/test/business-cases/standard/01.01a-INVOICE_ubl.xml"
    }
  ],
  "sourceSyntax": "UBL",
  "allowPartialNormalization": true,
  "storeTechnicalReports": false,
  "maxFindingsPerDocument": 100
}

Each submitted document produces one Dataset result with separate processing, technical conformance, normalization, billing, source-provenance, and invoice data fields.

What it does

• Accepts up to 100 XML documents by upload, inline XML, inline base64, HTTPS URL, or explicit key-value store record.
• Enforces a 5 MiB per-document and 100 MiB per-run limit.
• Detects UBL Invoice, UBL CreditNote, or CII and can enforce a caller-declared syntax.
• Runs KoSIT Validator 1.6.0 with the pinned XRechnung 3.0.2 configuration release 2026-01-31.
• Reports XML, XSD, Schematron, EN 16931, XRechnung, and mapping evidence separately.
• Maps the full declared EN 16931 syntax binding into the shared JSON model, with business-term trace entries and decimal strings.
• Can retain KoSIT XML and XHTML reports as opt-in KVS artifacts.

Invalid documents can still receive normalized data when XML parsing is safe. conformanceStatus and normalizationStatus are separate so a technically rejected document is never presented as conformant.

Product boundary

The result is integration-ready JSON, not a preconfigured connector for every ERP. Posting logic, chart-of-accounts rules, master-data resolution, duplicate handling, approval policy, and the final ERP field mapping remain system-specific.

The Actor does not make legal, tax, authenticity, signature, or recipient acceptance decisions.

Release state

The processing engine and Actor contract are feature-complete. The source contains a fail-closed pay-per-event charge path for document-processed at exactly $0.005 per evaluated document. 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 not create an additional charge.

The live Apify pricing contract uses document-processed as the primary event at $0.005 and retains the standard $0.00005 Actor Start event. A Store release is approved only after the selected hosted build passes an eligible document, a free source failure, and a free constrained-budget lifecycle smoke with exact charge-count and artifact checks.