Connect SAP S/4HANA, F&O or Business One with eConnect via the PSB API for e-invoicing and Peppol.
You connect SAP with eConnect in 2026 via the PSB API or via XML exchange by email or HTTP endpoint. The exact integration path differs per SAP variant. The integration requires a contract with the eConnect sales team, a subscription key and IP whitelisting. Technical configuration is carried out by a SAP partner or the eConnect tech team.
eConnect supports multiple SAP variants. The integration path depends on the variant you are using.
SAP S4/HANA. The customer builds the integration with the PSB REST API. 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 via an HTTP endpoint. Configuration is agreed 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 an integration is possible via the same methods as with S4/HANA.
For incoming invoice processing in SAP, eConnect works with partner Avelon. Avelon provides the integration that automatically books invoices in SAP and serves a large portion of SAP customers.
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 during 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 yourself.
With SAP S4/HANA you build the integration yourself with the PSB REST API (inbound and outbound). 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 in which the right approach for your variant is determined.
Technical configuration is typically carried out by a SAP partner, Avelon (for incoming invoice processing) or the eConnect tech team. It starts with an intake meeting via the eConnect sales team, where the SAP variant, expected volume, technical architecture and security requirements are discussed.
IP whitelisting is a security measure where only traffic from registered IP addresses is accepted. The IP addresses of your SAP environment must be registered with eConnect to secure the connection.
You need at least a Professional subscription with eConnect, plus a contract with the sales team for SAP integration. After the contract you receive a subscription key and support during configuration.
Need help? Contact sales.
Request an intake meeting