Connecting SAP with eConnect

Connect SAP S4/HANA, F&O or Business One with eConnect via the PSB API for e-invoicing and Peppol.

Integration methodPSB REST API / XML via email or HTTPDirectionSend + ReceiveMinimum subscriptionProfessionalContract requiredYes (via sales)

You connect SAP in 2026 with eConnect via the PSB API or through XML exchange by email or HTTP endpoint. The exact integration path depends on your SAP variant. The integration requires a contract with the eConnect sales team, a subscription key and IP whitelisting. The technical configuration is performed by a SAP partner or the eConnect tech team.

SAP variants

eConnect supports multiple SAP variants. The integration path depends on the variant you use.

SAP S4/HANA. You build a connection with the PSB REST API yourself. This variant supports both incoming and outgoing invoices. The PSB API provides endpoints for sending, receiving and validating e-documents.

SAP F&O (Finance & Operations). Outgoing invoices are sent via XML by email or through an HTTP endpoint. The configuration is agreed upon during the intake meeting.

SAP Business One. eConnect has no specific experience with SAP Business One. The integration path is identical to the generic PSB API, so technically a connection is possible using the same methods as for S4/HANA.

Integration partner Avelon

For incoming invoice processing in SAP, eConnect works with partner Avelon. Avelon provides the connection that automatically books invoices in SAP and serves a large share of SAP customers.

Before you start
  • An active eConnect account
  • A contract with eConnect for SAP integration (via sales)
  • A subscription key that you receive after the contract
  • IP whitelisting: the IP addresses of your SAP environment must be registered with eConnect
  • A SAP partner, Avelon or internal SAP expertise for the configuration
Getting started

Want to connect SAP with eConnect? Contact [email protected] for an intake meeting. During this meeting, the SAP variant, expected volume, technical architecture and security requirements are discussed. After the contract, you receive a subscription key and support with the configuration.

Tip: The SAP integration is based on the eConnect PSB API. For technical details, consult the PSB API documentation, or build your own integration if you want to develop it yourself.

Frequently asked questions
Which SAP variant do I have and what is the integration path?

With SAP S4/HANA you build a connection with the PSB REST API yourself (incoming and outgoing). With SAP F&O (Finance & Operations) outgoing invoices are sent via XML by email or HTTP endpoint. For SAP Business One, eConnect has no specific experience, but the integration path is identical to the generic PSB API. Contact sales for an intake meeting where the right approach for your variant will be determined.

Can I set up the SAP integration myself?

The technical configuration is typically performed by a SAP partner, Avelon (for incoming invoice processing) or the eConnect tech team. It starts with an intake meeting through the eConnect sales department, where the SAP variant, expected volume, technical architecture and security requirements are discussed.

Why is IP whitelisting required for the SAP integration?

IP whitelisting is a security measure that only accepts traffic from registered IP addresses. The IP addresses of your SAP environment must be registered with eConnect to secure the connection.

Which subscription do I need for the SAP integration?

You need at least a Professional subscription with eConnect, plus a contract with the sales department for SAP integration. After the contract, you receive a subscription key and support with the configuration.


Need help? Contact sales.

Request an intake meeting