Date: 2026-05-13 Status: Research complete
IMPORTANT — read first
Tangro Software Components GmbH was acquired by xSuite Group in 2024 and legally merged on 1 January 2025. The Tangro brand and product line are being absorbed into the xSuite portfolio on a multi-year roadmap. For the parent entity's product strategy, cloud platform, and modern REST APIs, see the companion analysis: xSuite integration research.
This document is retained for the specific situation of customers still running the classic Tangro Inbound Suite as a SAP ABAP add-on. The architecture, integration surface, and Orcha sales motion are materially different from xSuite's modern cloud/BTP products — the classic Tangro stack has no public API, no iPaaS presence, and no path to S/4HANA Cloud Public Edition. Customers on this stack are at a forced migration point (either to xSuite's modern platform or off to a different vendor) which represents an unusually strong replacement opening for Orcha.
Tangro is structurally not an "integrate via API" target. The classic Tangro Inbound Suite is a closed SAP ABAP add-on that explicitly markets itself as "directly in SAP. Without any interfaces." No public REST API, no SDK, no developer portal, no Postman collection, zero iPaaS connectors. Its core data and workflow live inside the customer's SAP system, accessible only through standard SAP mechanisms (BAPI/RFC/IDoc/OData) — meaning you bypass Tangro entirely rather than integrate with it.
Tangro is a direct competitor, not a complement. It is itself an SAP-embedded AP automation suite — OCR, extraction, workflow, posting — exactly Orcha's value proposition.
| Capability | Public API | Via iPaaS | Via e-invoicing channel | Via SAP-direct | Verdict |
|---|---|---|---|---|---|
| Push invoice PDF + data to Tangro | NO | NO | YES (ZUGFeRD/XRechnung email or PEPPOL) | n/a | Realistic but wasteful — Tangro re-OCRs |
| Push structured invoice to SAP (bypass Tangro) | NO | NO | YES (PEPPOL/IDoc) | YES (BAPI_INCOMINGINVOICE_CREATE) | The clean play |
| Read invoice status from Tangro | NO | NO | NO | YES (read SAP tables/CDS views) | Custom ABAP/RFC |
| Trigger / approve in Tangro workflow | NO | NO | NO | LIKELY (custom RFC) | Closed product surface |
| Write master data (cost centers, GL, vendors) | NO | NO | NO | YES (SAP BAPI/OData) | Goes to SAP, not Tangro |
| Read master data | NO | NO | NO | YES (SAP BAPI/OData) | Goes to SAP, not Tangro |
| Webhook / event notifications | NO | NO | NO | Custom ABAP only | Not supported |
| Layer | Status | Evidence |
|---|---|---|
| Developer portal / OpenAPI / Swagger | None | No /developers, /api, no Swagger anywhere on tangro.de |
| Postman public collection | None | site:postman.com tangro → 0 hits |
| SDK / client library | None | github.com/tangro hosts only internal CI tooling (Jest runner, OTRS notifier, GH Actions wrappers) — zero integration libraries |
| "Tangro Connect" REST product | Does not exist | Search returns unrelated products |
| Tangro web services (SOAP/RFC) | Not publicly documented | Would require direct sales engagement |
| xSuite eDNA REST API (post-acquisition) | Exists, undocumented publicly | OAuth2 multi-tenant Azure — see xSuite analysis |
| Authentication | n/a (SAP user identity inside ABAP stack) | No OAuth/API key flow exists in classic Tangro |
Tangro's explicit positioning, repeated across their site: "Directly in SAP. Without any interfaces" — an anti-API design philosophy, not a documentation gap.
Confirmed write channels into Tangro (none are API):
No way to push pre-parsed JSON header+line data into Tangro. The product is fundamentally OCR-first; pre-extracted structured data has no documented intake. You can embed it as ZUGFeRD/Factur-X XML inside a hybrid PDF/A-3 and drop as email/PEPPOL — at which point Tangro's EDI Converter parses the XML and skips OCR. But Tangro still takes ownership of the workflow and visible UX.
| Platform | Tangro connector |
|---|---|
| Celigo, Workato, Zapier, Make.com, n8n, Tray.io, Boomi, Mulesoft, SAP Integration Suite | None of them have a Tangro connector |
Zero presence on every mainstream iPaaS. Consistent with Tangro's SAP-only, transport-delivered model — they have no need for cloud middleware because they live inside the SAP stack the customer already operates.
| Channel | Status | What it enables |
|---|---|---|
| Email (SMTP, PDF + e-invoice attachments) | Confirmed primary | Any SMTP sender drops to customer's Tangro inbox |
| ZUGFeRD / XRechnung (hybrid PDF/A-3) | Confirmed native | Cleanest German-market channel; mandated since 1 Jan 2025 |
| PEPPOL via xSuite eDNA → SAP | Confirmed | Standards-based pipeline using xSuite's Storecove access point |
| EDI / IDoc INVOIC01/02 | Confirmed primary B2B | Push structured IDocs to customer's SAP; Tangro consumes them |
| BAPI_INCOMINGINVOICE_CREATE (RFC) | SAP standard | Bypasses Tangro entirely — posts directly to MIRO |
| SFTP | Not advertised | Possible via SAP file ports + customer basis work; non-standard |
| Webhooks / event callbacks | None | Status sync requires custom SAP-side reads |
| SAP Ariba Network | Confirmed integration path | If joint customer uses Ariba |
| Unified APIs (Chift / Merge / Rutter / Finch) | None list Tangro | |
| "Tangro Box" appliance | Does not exist as a product | Tangro is software-only |
| Requirement | Detail |
|---|---|
| Pricing model | Sales-led, perpetual + annual maintenance (classic German SAP add-on model); xSuite is migrating to subscription post-acquisition |
| Public pricing | None disclosed |
| Modules sold separately | Invoice Mgmt (IM), Order Mgmt (OM), order confirmations, delivery notes, despatch advice, service orders, payment advice, debitor invoices, requisition notes, Business Workflow (BWF), EDI Converter, E-Invoicing |
| Supported SAP platforms | SAP ECC, S/4HANA on-prem, S/4HANA Cloud Private Edition (RISE). NOT supported on S/4HANA Cloud Public Edition — no ABAP extensibility there. xSuite Invoice on BTP is the separate product for that environment. |
| Customer prerequisites | SAP basis access to install transport requests; Tangro module licenses; optional Fiori launchpad for mobile approvers |
| API license? | N/A — there is no API product to license |
| Public reviews | None of substance — enterprise sales motion, not self-serve |
| Reference customers | Hager, ContiTech, Ricola, Ammann, Thüga (German DACH industrials) |
| Implementation | Consultancy-led; IA4SP partner network; "technical rollout in one day" marketing claim |
SAP S/4HANA Cloud Public Edition is SAP's multi-tenant SaaS:
| Constraint | Impact on Tangro |
|---|---|
| No customer ABAP transports | Tangro is delivered as Z-namespace ABAP transports — cannot be installed |
| Whitelisted APIs only | Internal function modules off-limits; only released OData / SOAP / Events |
| SAP-controlled release cycle | Quarterly upgrades pushed by SAP |
| Extensibility restricted to Key User / Developer Extensibility / Side-by-side on BTP | Classic Tangro ABAP architecture doesn't fit any of these |
xSuite's response is the separate xSuite Invoice on SAP BTP product, which runs side-by-side and integrates via OData — but it is a different product, not the classic Tangro codebase. Customers on classic Tangro who are migrating to S/4HANA Cloud Public Edition face a forced product change inside the xSuite portfolio, or a vendor change altogether.
| Orcha need | Verdict | Reasoning |
|---|---|---|
| Write reference data (cost centers, GL, vendors) | N/A — wrong target | Tangro reads master data from the customer's SAP; Orcha would push to SAP directly via BAPI/OData |
| Push parsed invoices into Tangro | Not via API. Workaround: ZUGFeRD-embedded XML in PDF/A-3 via email/PEPPOL | Tangro will re-parse; Orcha's extraction value is partially wasted |
| Receive invoices from Tangro into Orcha | Custom ABAP only | No outbound API/webhook; would require customer-side enhancement on Tangro tables |
| Attach documents via API | No API; ArchiveLink only via SAP | |
| Trigger / manage approvals | Not externally accessible | Tangro BWF approvals run via SAP GUI / Fiori / mobile SSO — no REST surface |
| Read invoice status | Yes, but via the SAP layer, not Tangro | Custom RFC/CDS view against Tangro's ABAP tables |
| Read chart of accounts / vendor master | Yes, via SAP directly | Bypass Tangro; standard BAPI/OData |
There is no "integrate with Tangro" play in the conventional sense.
Tangro customers are at a forced decision point: their ABAP add-on does not run on S/4HANA Cloud Public Edition, and ECC mainstream support ends in 2027 (extended maintenance to 2030 at cost). Migration is not optional. xSuite is pushing them onto the unified platform on its own timeline. Orcha's window: be the cloud-native alternative when the customer is already evaluating a change.
If a joint customer insists on keeping Tangro for SAP-anchored flows, scope Orcha to invoice-adjacent documents Tangro doesn't already own (expense reports, contracts, AR/debitor flows, FP&A) — explicitly not invoices, because that's a head-on collision.
Orcha drops enriched ZUGFeRD/XRechnung PDFs into the customer's Tangro email inbox. Works mechanically but wastes Orcha's extraction (Tangro re-parses) and gives Tangro the visible workflow. Transitional only.
Tangro product:
xSuite acquisition / post-merger:
Partner / ecosystem:
SAP technical reference: