Reference
Supported target systems and connectors
Which target systems FlowEngine serves, which operations and sign-in methods exist and what state each connector is in.
Last reviewed October 30, 2026 · Version 2026.10
This overview shows which target systems FlowEngine can transfer data to, which operations exist and what state each connector is in. All connectors transfer exclusively out of FlowEngine; none reads data from the target system into FlowEngine.
Levels in the interface#
| Label | Meaning |
|---|---|
| no label | supported: executable and covered by automated tests that replicate the vendor's published interface. This is not a certification and not a test against your system. |
| Experimental | executable but less thoroughly tested. Use productively only after your own tests. |
| Planned | visible only, cannot be selected or executed |
Target systems at a glance#
| Target system | Operation | Interface | Authentication | State | Enablement required |
|---|---|---|---|---|---|
| SAP S/4HANA | Create supplier invoice (invoice, credit note) | OData V2, Supplier Invoice API (API_SUPPLIERINVOICE_PROCESS_SRV) | username and password, OAuth 2.0 (client credentials), client certificate (mTLS) | supported for S/4HANA Cloud Public Edition; Experimental for Private Edition and on-premise | yes |
| Odoo | Create vendor bill (invoice, credit note) | External JSON-2 API (Odoo 19 and later) | API key | supported | yes |
| Odoo | Create record in any model | External JSON-2 API | API key | Experimental | yes |
| DATEV | Posting batch (DATEV format) | file in the DATEV EXTF format | none, as it is a file | supported | yes |
| REST API | Send document as JSON (all document types) | JSON over HTTPS; structure defined freely or from OpenAPI 3 (JSON) | none, bearer token, API key, username and password, OAuth 2.0 (client credentials), client certificate (mTLS) | supported | no |
| OData service | Create entity | OData V2 or V4, fields from $metadata | as for REST API | Experimental | no |
| CSV, Excel (XLSX), JSON | Export documents | file for download or in a server folder | none | supported | no |
Currently planned and not usable:
- SAP: post journal entry (SOAP), create supplier (business partner), incoming invoice via IDoc and via BAPI/RFC, uploading the original document to SAP.
- Odoo: XML-RPC/JSON-RPC for versions before Odoo 19.
- DATEV: document image service, booking data service, invoice data service and sign-in with a DATEV account. For DATEV, FlowEngine only produces files and has no connection to DATEV online services.
- Microsoft Dynamics 365 Business Central and a general SOAP service.
What "available" to "released" means#
The following levels do not automatically build on each other. An available connector or a passed automated test is not yet a release for productive use.
| Level | SAP S/4HANA | Odoo | DATEV | REST API | OData service | CSV, Excel, JSON |
|---|---|---|---|---|---|---|
| Connector available | yes | yes | yes | yes | yes | yes |
| Connection configurable | yes | yes | not applicable (file) | yes | yes | not applicable (file) |
| Operation implemented | Create supplier invoice | Create vendor bill; any model experimental | EXTF posting batch | Send document as JSON | Create entity | Export documents |
| Tested automatically | against a test server with a replicated SAP interface description, incl. CSRF token | against a test server that replicates the JSON-2 API | header line, column order, character set and posting rules of the generated file | against a test server, incl. OpenAPI import | against a test server with $metadata | structure of the file formats |
| Checked against a real target system | not documented | not documented | column layout compared with a real DATEV file; an import into DATEV is not documented | not documented; the target system is always your own | not documented | not applicable |
| Released for customers | supported for S/4HANA Cloud Public Edition, otherwise experimental; usable only after enablement by your FlowEngine operator | supported, any model experimental; usable only after enablement | supported; usable only after enablement | supported, usable without enablement | experimental, usable without enablement | supported, usable without enablement |
"Released for customers" describes the status in the product. It does not mean that the connector has been tried with your system. A test against your specific target system is never part of the product. Before productive use, always run a connection test, a dry run and a first controlled transfer; for DATEV, also a trial import by your accountant.
Avoiding duplicate records#
| Target system | Duplicate check before creating |
|---|---|
| SAP S/4HANA, Odoo | yes, can be switched on under Behaviour |
| REST API, OData service | no; if the outcome is unclear, the transfer waits for your review |
| File exports | not applicable |
Details are described in Retries, idempotency and unresolved outcomes.