[Feature] Add ERP/finance connector #1

Open
opened 2026-07-10 22:09:38 +02:00 by zemion · 3 comments
Owner

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

Reason: ERP/finance connector work belongs to the ERP 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: 334
  • Source kind: product
  • Section: GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform

Imported item:

Add ERP/finance connector.
Moved from add-ideas/govoplan-core#129. Reason: ERP/finance connector work belongs to the ERP module. Original issue body: <!-- codex-generic-backlog-fingerprint:cbf5cb856349804db73b10b7 --> Imported from a backlog-like text file. - Source: `/mnt/DATA/Nextcloud/ADD ideas UG/Products/govoplan/split-concept-action-plan.md` - Line: `334` - Source kind: `product` - Section: `GovOPlaN Split Concept and Action Plan > Product Roadmap > Milestone C: Public-Sector Integration Platform` Imported item: ```text Add ERP/finance connector. ```
Author
Owner

A generic “ERP connector” cannot define safe finance semantics without a bounded target.

Decisions required:

  • first business slice (recommend approved payable/export plus booking-status reconciliation rather than a broad ERP mirror);
  • first ERP/product and API/file profile;
  • source of truth for vendor, account, cost centre, tax, booking, payment, and correction state;
  • approval threshold, duplicate/idempotency key, reversal, closed-period, and outcome-unknown rules.

Manual inputs required:

  • sandbox/test tenant, interface specification, credentials/certificates, chart-of-accounts and tax-code mappings using synthetic data, and expected acknowledgement/error fixtures.

After selection, the autonomous slice can expose a provider-neutral finance handoff contract and one adapter with dry-run mapping, immutable evidence, replay safety, and manual reconciliation.

A generic “ERP connector” cannot define safe finance semantics without a bounded target. Decisions required: - first business slice (recommend approved payable/export plus booking-status reconciliation rather than a broad ERP mirror); - first ERP/product and API/file profile; - source of truth for vendor, account, cost centre, tax, booking, payment, and correction state; - approval threshold, duplicate/idempotency key, reversal, closed-period, and outcome-unknown rules. Manual inputs required: - sandbox/test tenant, interface specification, credentials/certificates, chart-of-accounts and tax-code mappings using synthetic data, and expected acknowledgement/error fixtures. After selection, the autonomous slice can expose a provider-neutral finance handoff contract and one adapter with dry-run mapping, immutable evidence, replay safety, and manual reconciliation.
zemion added
status
needs-info
and removed
status
triage
labels 2026-08-21 14:20:49 +02:00
Author
Owner

Decision recorded 2026-08-23: the recommended first slice is approved—governed payable export plus booking-status reconciliation, with deterministic correlation, idempotency, reversal handling and no ERP-owned authority leaking into GovOPlaN. The provider-neutral contract can proceed autonomously. A target-tested adapter still needs a named ERP/product/version, export transport/schema, booking object/status API, credential model and test environment.

Decision recorded 2026-08-23: the recommended first slice is approved—governed payable export plus booking-status reconciliation, with deterministic correlation, idempotency, reversal handling and no ERP-owned authority leaking into GovOPlaN. The provider-neutral contract can proceed autonomously. A target-tested adapter still needs a named ERP/product/version, export transport/schema, booking object/status API, credential model and test environment.
Author
Owner

Autonomous foundation published in v0.1.19 (a12e096).

Implemented a provider-neutral, effect-free contract for payable export planning and booking reconciliation: exact payable/profile revisions, canonical payloads and idempotency keys, evidence digests, explicit provider status mapping, and fail-closed quarantine for mismatched or unknown observations. Added English/German user and administrator documentation, permissions/roles, manifest contributions, release packaging, and tests.

The planner never dispatches, persists, selects an ERP product, or activates an environment. The broader feature remains open for an approved target ERP, transport adapter, credentials, runtime persistence, and end-to-end verification.

Autonomous foundation published in v0.1.19 (a12e096). Implemented a provider-neutral, effect-free contract for payable export planning and booking reconciliation: exact payable/profile revisions, canonical payloads and idempotency keys, evidence digests, explicit provider status mapping, and fail-closed quarantine for mismatched or unknown observations. Added English/German user and administrator documentation, permissions/roles, manifest contributions, release packaging, and tests. The planner never dispatches, persists, selects an ERP product, or activates an environment. The broader feature remains open for an approved target ERP, transport adapter, credentials, runtime persistence, and end-to-end verification.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-erp#1