Onventis — Integration Feasibility Analysis

Date: 2026-05-13 Status: Research complete


1. Executive Summary

Onventis is a German cloud source-to-pay platform (Stuttgart, founded 2000). ~1,000+ buying orgs, 1.2M users, ~$20B annual volume on platform. Mid-market DACH focus (€50M–€1B revenue). Top-5 in "Main Software 50" (Germany). Owned by Keensight Capital (PE) since Jan 2023, previously Main Capital Partners. Acquired WorkFlowWise (Dutch AP automation) in 2022 — that engine is now sold as Onventis AP Automation (AI extraction, 3-way match, approval workflow, posting proposals).

Onventis has a real REST API ("Onventis Buyer Public API") with token-based auth, real-time GET/POST against orders and invoices. Confirmed endpoint examples include GET /orders (with order-position receipt state). But the API surface is private and license-gated — no public OpenAPI/Swagger, no Postman collection, no public SDK, no self-serve developer portal. Docs live behind login at help.onventis.com and service.onventis.com.

Where Onventis shines is integration standards: native openTRANS (with Onventis extensions), cXML 1.2.014, OCI 4/5 PunchOut, EDIFACT (ORDERS, ORDRSP, DESADV, INVOIC, ORDCHG), xCBL, SAP iDoc, CSV — over HTTPS, SFTP, FTP, SMTP. PEPPOL-certified (the Onventis Network is itself a PEPPOL access point). ZUGFeRD / XRechnung natively supported. 40+ pre-built SAP interfaces ("over 100 customers"). SEEBURGER BIS ships a productized "Onventis xChange" connector.

Strategic verdict: Onventis is primarily a competitor on AP automation; complement only for procurement-only customers who haven't bought AP Automation. The decisive customer-discovery question is: "Do you use Onventis AP Automation?" If yes → no joint opportunity. If no → upstream/complement play where Onventis owns POs/contracts/supplier master and Orcha owns invoice extraction + finance/close.

Capability matrix

Capability REST API iPaaS Standards (openTRANS / cXML / EDIFACT) PEPPOL / e-invoice Verdict
Push invoice (PDF + data) to Onventis LIKELY (license-gated REST) NO YES (openTRANS INVOIC, EDIFACT) YES (Onventis Network) Realistic — but duplicates Onventis's own OCR if customer has AP Automation
Pull purchase orders out CONFIRMED (GET /orders) NO YES (openTRANS) n/a Clean play for 3-way match scenarios
Pull suppliers / contracts / categories CONFIRMED NO YES (iDoc, openTRANS) n/a Master data sync is a core Onventis ERP-integration use case
Trigger / manage approvals via API UNCLEAR NO NO n/a Onventis owns the workflow engine; programmatic decision-making not documented
Read invoice / order status LIKELY (REST polling) NO n/a n/a No webhooks documented
Webhook / event notifications NONE documented n/a n/a n/a Polling required
Write master data into Onventis CONFIRMED (iDoc supplier master) NO YES (iDoc, openTRANS) n/a Bidirectional supplier sync is a core capability

2. API Landscape

Layer Status Evidence
Developer portal None public No docs.onventis.com / developer.onventis.com / api.onventis.com; canonical docs at help.onventis.com are login-gated
OpenAPI / Swagger Not publicly indexed Spec almost certainly exists behind login; site:onventis.com swagger/openapi → 0 hits
Postman collection None
GitHub github.com/onventis has 1 public repo (wppt, a fork of redhat-performance Webhook Payload Proxy Transformer) — no SDK, no client lib
Authentication Token-based (Bearer/API token), per-tenant, scoped by license role IntegrityNext connector docs confirm "Authentication token" pattern provisioned in tenant UI under "Integration via API"
Versioning Implicit via yearly release tags (2024.x, 2025.x, 2026.x); no /v1///v2/ path versioning visible publicly
Named REST API "Onventis Buyer Public API" — confirmed via 2025.3 release notes (GET /orders, IsEndReceived boolean) help.onventis.com/content/onventis-2025-3
Cross-module REST Marketed as bidirectional with Invoice Processing module onventis.com/erp-systems/rest-api
Webhooks None documented The wppt GitHub fork is internal infra, not a customer-facing webhook product

3. Write Capability Verification

Confirmed writes into Onventis:

Confirmed reads:

Likely (advertised, not documented publicly):

Unknown:


4. iPaaS / Middleware Findings

Platform Status Notes
Celigo, Workato, Zapier, Make.com, n8n, Tray.io, Mulesoft, Boomi, Power Automate, Logic Apps, Lobster_data No Onventis connector Same gap as xSuite/Tangro — Onventis is not in the cloud-iPaaS ecosystem
SEEBURGER BIS Confirmed (productized) "Onventis xChange" — bidirectional web-services interface, SAP RFC; marketed in SEEBURGER Integration Marketplace
ITARICON Managed Integration Confirmed (managed-service partner) Onventis ↔ SAP / Dynamics
ITscope Confirmed Packaged e-procurement connector (IT reseller catalogs)
Unite (formerly Mercateo) Confirmed Marketplace search + punchout integration

5. Alternative Channels

Channel Status What it enables
openTRANS (native, with Onventis extensions) Confirmed Orders, order changes, confirmations, delivery notes, invoices — bidirectional
cXML 1.2.014 PunchOut Confirmed Inbound + outbound; SAP-compatible
OCI 4/5 PunchOut Confirmed Standard supplier catalog punchout (incl. "Onventis OCI 5.0 JSON" custom mode)
EDIFACT Confirmed ORDERS, ORDCHG, ORDRSP, DESADV, INVOIC
xCBL, SAP iDoc, CSV Confirmed Conversion service from openTRANS
PEPPOL Confirmed (own access point) Onventis Network is PEPPOL-certified; customers receive e-invoices via Peppol
ZUGFeRD / XRechnung Confirmed All EN16931-compliant formats handled by Invoice Processing
SFTP / FTP / HTTPS / SMTP Confirmed Transport options for EDI / openTRANS exchange
SAP pre-built (iDoc, BC, PI/PO, S/4HANA) Confirmed 40+ pre-built interfaces, "over 100 customers", marketed openly
Dynamics NAV / 365 BC / F&O Partner-built Via Navision partners + ITARICON
Oracle, Infor, Sage, NetSuite Likely (via standards) Marketed as supported via openTRANS/EDIFACT but no productized connectors found
Unified APIs (Chift / Merge / Rutter / Finch) None Not listed
Webhooks None documented Polling required

6. Licensing & Access

Item Detail
Pricing model Subscription, modular SKUs (Buyer, AP Automation, Sourcing, Contract Mgmt, Supplier Mgmt, Network, Analytics). Likely user-tier + transaction/document volume for AP & Network
Public pricing None — sales-led, quote-based; Capterra/GetApp list "Contact vendor"
Modules Onventis Buyer; Onventis AP Automation (ex-WorkFlowWise); Onventis Sourcing; Onventis Contract Management; Onventis Supplier Management; Onventis Supplier Portal / Network (PEPPOL-certified, free for suppliers); Onventis Analytics; Network Collaboration; VMI add-on for SAP
API access SKU Likely included with Buyer / AP modules but enabled per-tenant by Onventis support — no self-serve, no public sandbox
ERPs supported SAP (deepest, partner-certified), Oracle, Microsoft Dynamics NAV / 365, Infor, Exact, "many more" via openTRANS / EDIFACT / xCBL / cXML / iDoc / CSV. NetSuite not explicitly listed
Customer prerequisites (1) License Onventis Buyer or AP Automation; (2) Request API access via Onventis support; (3) Provide tenant credentials
Implementation Hybrid: Onventis-direct + certified partners (Aneon, Kloepfel Consulting, KL-GROUP, ITARICON). SAP integrations typically partner-led
Reviews Capterra/GetApp profile exists, review volume thin; no G2 score surfaced; not in Gartner MQ for S2P Suites 2024-25 (sub-scale vs. SAP/Coupa/JAGGAER/GEP). FeaturedCustomers lists 173 references. Public refs: Schott AG, Remmers
Ownership Keensight Capital (PE) since Jan 2023, previously Main Capital Partners; earlier investors Sapphire Ventures, Cathay Capital
2022 acquisition WorkFlowWise (Dutch AP automation + e-invoicing specialist) — this is the engine behind today's Onventis AP Automation module

7. Orcha-Specific Deep Dive

Orcha need Verdict Reasoning
Push parsed invoices into Onventis UNCLEAR / LIKELY REST API advertised for Invoice Processing but no public schema. Risk: duplicates Onventis's own OCR/extraction (WorkFlowWise engine) for customers who have AP Automation
Pull purchase orders from Onventis (for 3-way match) CONFIRMED (GET /orders) Clean use case — Orcha reads POs to match against extracted invoice data
Pull suppliers / categories / contracts CONFIRMED Master data sync is a core Onventis ERP-integration use case
Receive approved invoices from Onventis to Orcha LIKELY Standard ERP-export path; same pipes (REST / iDoc / openTRANS) used to push to SAP can target Orcha
Attach documents via API LIKELY Invoice Processing handles PDF natively; attachment lifecycle confirmed; explicit binary-upload endpoint not publicly documented
Trigger / manage approvals via API UNCLEAR Onventis owns a configurable workflow engine (amount, cost center, GL rules). Programmatic decision-making not documented
Read invoice / order / approval status LIKELY (polling) REST API real-time bidirectional; no webhooks documented
Write master data into Onventis CONFIRMED (iDoc supplier master) Bidirectional sync is a core capability

8. Onventis Product Scope (excluding AP Automation)

This section documents what Onventis does outside the AP overlap with Orcha. It's the basis for the "complement" archetype — these are the modules a joint customer might run alongside Orcha rather than against it.

Onventis Buyer (operational procurement)

Onventis Sourcing (strategic sourcing)

Onventis Contract Management

Onventis Supplier Management

Onventis Supplier Network / Onventis Network

Onventis Analytics (spend analytics)

Onventis Hybrid Procurement

VMI add-on (for SAP customers)

Cross-cutting platform features

Where Onventis stops — the Orcha non-overlap

These finance/back-office functions Onventis explicitly does NOT cover, which defines the joint-customer complement scope for Orcha:


Primary verdict: COMPETITOR on AP, COMPLEMENT only for procurement-only customers.

A. Direct AP automation competition — narrow opportunity

Onventis AP Automation (the WorkFlowWise engine) does what Orcha does: AI extraction, 3-way match, approval workflow, posting proposals. For any customer who has bought this module, Orcha is largely redundant on AP. Walk away unless the customer is actively unhappy with extraction quality or workflow rigidity.

B. Procurement-only customers — the real opening

Customers who bought Onventis Buyer + Sourcing + Supplier Management but NOT AP Automation. Here:

This is a cleaner archetype than the xSuite/Tangro picture — Onventis genuinely has an integratable REST surface for this play.

C. AP automation replacement at unhappy Onventis customers

The WorkFlowWise engine is Dutch-origin from a 2022 acquisition — extraction quality is reportedly the weak link in mid-market AP tools generally. If a customer's pain is "too many manual corrections per invoice" — same playbook as for unhappy xSuite customers — propose Orcha as the AP layer while keeping Onventis Buyer for procurement.

D. PEPPOL channel coexistence (not an integration play per se)

Onventis Network is a PEPPOL access point. If a joint customer routes e-invoices through Onventis Network, Orcha can receive those via standard PEPPOL channels (Storecove etc.) — no Onventis-specific integration needed. This is plumbing-level coexistence, not a partnership.

Practical filter for sales

The decisive question early in any Onventis customer conversation:

"Are you using Onventis AP Automation, or just Onventis Buyer / Sourcing / Supplier Management?"

Answer Play
Buyer/Sourcing/Supplier only Complement (B) — pull POs/suppliers, become their AP layer
AP Automation + happy Walk away
AP Automation + unhappy (extraction quality, workflow rigidity, manual work) Replacement (C) — pitch Orcha as the AP layer, keep their Buyer module

Effort estimate for a Buyer + Orcha integration

Compared to S/4HANA Cloud Public Edition (~15 engineer-weeks for v1), an Onventis integration is smaller but partner-gated:

Workstream Effort
API access request + NDA + tenant credentials 4–8 weeks elapsed (Onventis-side, not engineering)
Token auth + REST client 0.5 week
GET /orders + supplier/contract pull 1 week
Schema mapping (Onventis PO ↔ Orcha invoice match) 1.5 weeks
Invoice push back (if scope) 1.5 weeks
Status polling + reconciliation 1 week
Testing in customer's tenant 1 week
Total ~6.5 engineer-weeks once API access is granted

The blocker is not engineering effort — it's getting API access granted by Onventis on a per-customer basis when you're a competing AP vendor. Expect friction.


10. Sources

Onventis product / API:

Partners / ecosystem:

Corporate / commercial: