[Feature] Add XRechnung workflow #1

New Issue

2026-07-10T22:10:05+02:00

zemion commented

2026-07-10 22:10:05 +02:00

Moved from add-ideas/govoplan-core#130.

Reason: XRechnung workflow work belongs to the XRechnung module.

Original issue body:

Imported from a backlog-like text file.

Source: /mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md
Line: 335
Source kind: product
Section: GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform

Imported item:

Add XRechnung workflow.

Moved from add-ideas/govoplan-core#130. Reason: XRechnung workflow work belongs to the XRechnung module. Original issue body:  Imported from a backlog-like text file. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md` - Line: `335` - Source kind: `product` - Section: `GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform` Imported item: ```text Add XRechnung workflow. ```

zemion referenced this issue from GovOPlaN/govoplan-core

2026-07-10 22:10:11 +02:00

[Feature] Add XRechnung workflow #130

zemion added the area/api codex/needs-human module/xrechnung

priority

p2

source/backlog-import

labels 2026-07-29 14:15:09 +02:00

zemion commented

2026-08-21 14:20:19 +02:00

This scaffold needs a first workflow profile before code can be truthful.

Decisions required:

inbound invoice validation, outbound invoice creation, or both (recommend inbound validation and governed handoff first);
exact XRechnung/EN 16931 syntax and version profile to pin, accepted extensions, and the authoritative validator/rule set;
transport boundary: validation-only versus a selected Peppol/portal/provider handoff;
ownership of supplier matching, booking proposal, rejection, approval, retention, and correction.

Manual inputs required:

licensed/approved positive and negative fixtures, expected validator reports, Leitweg-ID/routing examples with synthetic data, and—if transport is in scope—a sandbox endpoint and credentials/certificates.

A provider-neutral parse/validate/result-evidence slice can start as soon as the profile/version and inbound/outbound choice are recorded.

This scaffold needs a first workflow profile before code can be truthful. Decisions required: - inbound invoice validation, outbound invoice creation, or both (recommend inbound validation and governed handoff first); - exact XRechnung/EN 16931 syntax and version profile to pin, accepted extensions, and the authoritative validator/rule set; - transport boundary: validation-only versus a selected Peppol/portal/provider handoff; - ownership of supplier matching, booking proposal, rejection, approval, retention, and correction. Manual inputs required: - licensed/approved positive and negative fixtures, expected validator reports, Leitweg-ID/routing examples with synthetic data, and—if transport is in scope—a sandbox endpoint and credentials/certificates. A provider-neutral parse/validate/result-evidence slice can start as soon as the profile/version and inbound/outbound choice are recorded.

zemion added

and removed

labels 2026-08-21 14:20:47 +02:00

zemion commented

2026-08-23 11:23:49 +02:00

Implementation update 2026-08-23: the approved first boundary is inbound validation plus governed handoff. Release v0.1.19 (commit 94bad1d) pins and verifies KoSIT validator/config artifacts, runs without shell/network access, independently checks technical completion, scenario/step execution, formal conformance and assessment, and emits a digest-bound handoff only after a fail-closed result. No XRechnung/config version is activated by default because that deployment choice remains open. This workflow issue remains open for an approved version allow-list, target regression corpus and downstream Procurement/Payments journey.

Implementation update 2026-08-23: the approved first boundary is inbound validation plus governed handoff. Release v0.1.19 (commit 94bad1d) pins and verifies KoSIT validator/config artifacts, runs without shell/network access, independently checks technical completion, scenario/step execution, formal conformance and assessment, and emits a digest-bound handoff only after a fail-closed result. No XRechnung/config version is activated by default because that deployment choice remains open. This workflow issue remains open for an approved version allow-list, target regression corpus and downstream Procurement/Payments journey.

zemion commented

2026-08-23 18:15:03 +02:00

Autonomous foundation published in v0.1.20 (b3ccc56).

Added explicit KoSIT validation-profile governance: an allow-list binds exact verified artifact digests, approval evidence, effective receive-time windows, and approved/suspended/retired state. Selection is deterministic by invoice receive time, never inferred, and unknown, invalid-window, suspended, retired, or digest-mismatched profiles fail closed. Documentation, manifest contributions, and tests were extended accordingly.

GovOPlaN still does not choose an XRechnung/KoSIT version. The broader workflow issue remains open for the deployment-specific version policy, production artifact supply, and complete journey verification.

Autonomous foundation published in v0.1.20 (b3ccc56). Added explicit KoSIT validation-profile governance: an allow-list binds exact verified artifact digests, approval evidence, effective receive-time windows, and approved/suspended/retired state. Selection is deterministic by invoice receive time, never inferred, and unknown, invalid-window, suspended, retired, or digest-mismatched profiles fail closed. Documentation, manifest contributions, and tests were extended accordingly. GovOPlaN still does not choose an XRechnung/KoSIT version. The broader workflow issue remains open for the deployment-specific version policy, production artifact supply, and complete journey verification.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-xrechnung#1