Date: 2026-05-13 Status: Research complete Related: Tangro analysis — Tangro was acquired by xSuite and merged 1 Jan 2025
xSuite Group is a German SAP-focused AP / invoice / document automation vendor. Headquartered near Hamburg, ~1,600 customers, 300k+ users, 80M docs/yr. Reference customers include BMW, Bell Food Group, BARMER, Boralex, Dole, Brüggen, Bruker. Acquired Tangro in 2024 (merged 1 Jan 2025).
xSuite has a real REST API surface — but it is partner-gated, not publicly discoverable:
aservice.xsuite.com/api/v1, confirmed via a SAP cloud-sdk GitHub issue)What is missing publicly: no developer portal, no OpenAPI/Swagger, no Postman collection, no GitHub SDK, no iPaaS connectors (zero on Celigo, Workato, Zapier, Make, n8n, Mulesoft, Boomi, Power Automate, Logic Apps), no SAP API Business Hub content, no documented webhooks. Every integration requires a paid xSuite partner engagement with NDA-protected endpoint specs.
Strategic verdict: xSuite is primarily a competitor, with narrow complement scenarios at joint SAP customers in adjacent scope (FP&A, close orchestration, expense, contracts).
| Capability | xSuite REST | iPaaS | SAP CPI iFlow | PEPPOL / e-invoice | Verdict |
|---|---|---|---|---|---|
| Push invoice (PDF + data) to xSuite | YES (partner-gated, undocumented) | NO | YES (custom) | YES (eDNA via Storecove) | Proven feasible (Hypatos OEM) — needs partner access |
| Read invoice status | LIKELY (REST) + Reporting API for BI | NO | YES (custom) | n/a | Poll-based; no webhooks |
| Trigger / manage approvals | UNCLEAR | NO | maybe | n/a | Closed workflow, partner-only access |
| Write master data | NOT POSSIBLE (wrong target) | NO | n/a | n/a | Master data lives in SAP, not xSuite |
| Webhooks / events | NONE documented | NO | n/a | n/a | Polling required |
| Read posted data | Not via xSuite — read from SAP directly | n/a | n/a | n/a | Bypass xSuite |
| Layer | Status | Evidence |
|---|---|---|
| Developer portal | None public | xsuite.com / docs.xsuite.com / developer.xsuite.com — all 404 or gated |
| OpenAPI / Swagger | None public | |
| Postman collection | None | |
| GitHub SDK | None | github.com/xsuite is CERN particle physics, unrelated |
| Authentication | OAuth 2.0 + Azure AD (eDNA), OAuth 2.0 client credentials (Helix at aservice.xsuite.com/api/v1) |
eDNA product page; leaked via SAP cloud-sdk GitHub issue |
| Named REST endpoints | Reporting API (Power BI) — separately licensed; eDNA inbound/outbound; Helix capture/archive | xSuite release 5.2.10 notes; eDNA + Helix product pages |
| Partner-academy integration components | xSuite Interface Prism, xSuite Helix — paid Academy training | shop.xsuite.com |
| SAP API Business Hub presence | None — notable gap for a BTP-certified vendor | api.sap.com |
| Webhook / event subscription | None documented | No "webhook" or "event subscription" terminology anywhere |
xSuite Invoice on BTP is API-first by design — a genuine architectural shift compared to Tangro's "no interfaces" ABAP-only stance.
Confirmed inbound write paths into xSuite:
aservice.xsuite.com/api/v1 — capture + archiveStrongest proof of feasibility: Hypatos uses xSuite's API for invoice extraction in an OEM arrangement (March 2025). A third party pushing extracted invoice data into xSuite via REST — the exact pattern Orcha would replicate.
Exact endpoint URLs, request schemas, attachment handling, and authentication scopes are not in public docs. Every integration requires NDA + partner engagement.
| Platform | Status |
|---|---|
| Celigo, Workato, Zapier, Make.com, n8n, Tray.io, Mulesoft, Boomi, Azure Logic Apps, Power Automate | None have an xSuite connector |
| SAP BTP / SAP Integration Suite | Confirmed (primary path) — Clean Core BTP-EXT-CC + GROW with SAP certifications; xSuite Invoice ships as a native BTP side-by-side extension |
| SAP API Business Hub | No public iflow/API listing — unusual for a BTP-certified vendor |
SAP BTP itself acts as the iPaaS layer for xSuite. Customers running Integration Suite can wire xSuite into S/4 via custom CPI iflows — that's the canonical path, not Zapier/Make.
| Channel | Status | Notes |
|---|---|---|
| PEPPOL via Storecove | Confirmed | Bidirectional, format conversion |
| ZUGFeRD / XRechnung | Confirmed (in + out) | Native to eDNA |
| Italian SDI / FatturaPA | Confirmed | Via eDNA |
| Email ingestion (SMTP) | Confirmed | eDNA accepts ZUGFeRD/XRechnung/BIS 3.0 by email |
| SFTP | Not advertised | Likely available, not public |
| Webhooks / events | None documented | Polling required |
| IDoc INVOIC02 | Inferred via SAP-native | Standard SAP path for on-prem variants |
| Microsoft Dynamics 365 connector | None | Despite Azure-hosted eDNA |
| Ariba Network | None directly | Routes via SAP, not xSuite |
| Hypatos OEM integration | Confirmed (Mar 2025) | Strongest evidence inbound REST is real and partner-usable |
| Item | Detail |
|---|---|
| Pricing model | Subscription (document volume + user seats); ~80% of customers cloud/subscription |
| Public pricing | None — sales/partner quote-only |
| Modules | xSuite Invoice (Basis + Premium-with-BTP), xSuite E-Invoice, xSuite Procurement, xSuite Orders, xSuite Archive (+ Archive Helix), Business Partner Portal, xSuite eDNA, xSuite Helix |
| API access SKU | Likely sold as separate modules; Reporting API is explicitly separately licensed; integration API access requires partner/PS engagement |
| SAP support | ECC, S/4HANA on-prem (ABAP add-on), S/4HANA Cloud Private Edition (RISE), S/4HANA Cloud Public Edition (GROW with SAP via BTP) — full coverage |
| Non-SAP ERPs | Helix + eDNA only, positioned as ERP-agnostic via REST. Core Invoice/Procurement is SAP-only |
| Customer prerequisites (cloud) | BTP subaccount, Azure AD integration, OAuth scopes |
| Implementation | Partner-led; xSuite ACADEMY certifies Cloud Partners (Basis/Archive/Capture levels); Partner Portal launches Jan 2026 |
| Reviews | Gartner Peer Insights positive but limited; SoftwareReviews 5.3/10 composite (OCR 46/100, compliance 51/100 — notable weak spots) |
| Orcha need | Verdict | Reasoning |
|---|---|---|
| Push parsed invoices into xSuite | LIKELY FEASIBLE via partner-gated REST | Hypatos OEM proves it works; requires xSuite partner agreement + NDA on endpoints |
| Receive invoices from xSuite into Orcha | LIKELY via SAP, not xSuite | More natural: Orcha reads from SAP after xSuite posts (BAPI/OData) |
| Attach PDF/image | Confirmed | Core eDNA capability |
| Trigger / manage approvals | Unclear — likely partner-only | xSuite has its own SAP-native workflow + Fiori UI; REST APIs claimed but no public spec |
| Read invoice status | LIKELY (polling) | REST claimed; no webhooks. Reporting API exists for BI |
| Read back master data | NOT POSSIBLE via xSuite | Master data lives in SAP — read from SAP directly |
| Write master data into xSuite | N/A — wrong target | xSuite reads SAP master data; no inbound master-data API |
SAP-shop customers running xSuite get Clean Core BTP architecture, GROW with SAP coverage, PEPPOL via Storecove, 1,600-customer track record, named SAP partner status. Orcha will lose head-to-head SAP AP deals against credible xSuite incumbents. Don't pursue.
xSuite's non-SAP story is weak: Helix and eDNA are positioned as ERP-agnostic via REST but the value chain (workflow, matching, posting) is SAP-anchored. Orcha's natural win is mid-market non-SAP: Dynamics 365 BC, NetSuite, Bexio, Abacus, Odoo. xSuite cannot credibly compete here.
At joint customers where xSuite owns SAP AP, Orcha owns adjacent finance functions xSuite doesn't do well:
Orcha consumes xSuite output (posted invoices) from SAP via standard BAPI/OData — no direct xSuite integration needed.
If a real joint customer requires Orcha ↔ xSuite data exchange:
xSuite product / architecture:
Certifications & partnerships:
Commercials & reviews: