The directory, not the logo wall.
Thirteen connected systems, ordered by category, seven of them publicly documented. Anyone who does not find their own provider here finds the route it comes in on anyway.
By category, with its documentation state.
A directory is only useful if it says how deeply a connection is documented. "Guide" means publicly described in the integration portal, reviewable without a contract. "Connection" means present and in operation, but without a public walkthrough.
ERP 2
- SAP (ABAP) Guide
- SAP (OData) Guide
Accounting 2
- DATEV Guide
- FibuNet Guide
Credit insurer 3
- Allianz Trade Guide
- Atradius Connection
- Coface Connection
Credit agency 5
- Creditreform Guide
- Creditsafe Connection
- CRIF Connection
- Dun & Bradstreet Connection
- Bureau van Dijk Connection
A provider missing from this list is not an exclusion — over the REST API, batch and file handover, any system that releases its data can be connected.
Your system missing?
Tell us which one — we will check whether it can be connected over one of the generic routes, and what that means in practice.
Request an integrationAnd for everything else, four routes that always work.
Most system landscapes contain at least one program with no ready-made connector. These four are for those — with the same fields and the same validation as a named connector.
- REST API
- Read and write, authenticated by token, publicly documented.
- Batch interface
- Whole populations rather than single calls, at the source system's cadence.
- SFTP file handover
- Files into a directory, monitored and logged.
- Webhooks
- The other direction, so your systems do not have to ask.
Agencies and insurers are part of the same layer.
Reports, cover and limits do not come from a portal beside the product but through the same connections — and land on the debtor, where the credit decision reads them.
What gets asked about integrations.
Then it is connectable over one of the generic routes: REST API, batch interface, SFTP file handover. The only requirement is that your system releases its data. What takes time afterwards are the field mappings, not access.
That the connection is publicly documented in the integration portal — your IT can review it before anything is signed. Connections without a guide exist and run in production; they simply have no public walkthrough.
Yes, they are part of the same layer. Reports, cover and insured limits arrive through the existing connections and land on the debtor rather than sitting in a portal beside it.
Because they are two different connections: one over ABAP transports and one over OData. Which one fits depends on your SAP landscape — both are described in the integration portal, and for newer landscapes the SAP Business Technology Platform is added.
Yes, which is why there is a number here rather than a marketing phrase. What is added appears in the integration portal first — that is the source this page takes its list from.