How does the integration identify which supplier to pay in PayPal when SAP has no supplier email addresses?

The supplier master record in SAP S/4HANA includes a Bank Details section that can store email addresses or phone numbers. ml-connector reads this field to identify the PayPal recipient. If the field is missing or invalid, the invoice is flagged and skipped until the supplier record is updated in SAP.

Does the integration handle multi-currency payments and exchange rates?

Yes. ml-connector reads the currency code from the supplier invoice in SAP and includes it in the payout instruction to PayPal. PayPal manages the foreign exchange rate at settlement time; ml-connector records the settled amount from the webhook confirmation back into SAP for reconciliation.

What happens if a PayPal payout fails or a refund is issued?

PayPal sends a webhook notification with the failure reason or refund details. ml-connector marks the invoice as Payment Failed or Refunded in SAP and can create a reversal journal entry in the general ledger to keep the accounts payable balance correct. The invoice remains open in SAP pending manual review or a retry.

SAP S/4HANAPayPal

SAP S/4HANA and PayPal integration

SAP S/4HANA runs your enterprise finance and procurement. PayPal processes payments and payouts to suppliers worldwide. Connecting the two keeps your supplier invoice records in agreement with actual payouts and closes paid invoices automatically. New supplier invoices in SAP S/4HANA flow to PayPal for payment, confirmations flow back, and the general ledger stays reconciled without manual intervention.

How SAP S/4HANA works

SAP S/4HANA exposes suppliers, purchase orders, supplier invoices, GL accounts, cost centers, journal entries, and GL line items through OData V2 and OData V4 REST APIs. The cloud and on-premise versions authenticate with OAuth 2.0 Client Credentials, using a tenant-specific token endpoint and scopes defined in the Communication Arrangement. SAP has no native webhooks for payables, so invoices and payments are read by polling against the LastChangeDateTime filter or delta tokens. On-premise requires the sap-client query parameter; cloud public does not.

How PayPal works

PayPal exposes orders, payments, captures, refunds, invoices, transactions, subscriptions, and payouts through REST APIs over HTTPS. Every call uses OAuth 2.0 Client Credentials with a Bearer token cached for approximately 8 hours. PayPal also supports webhooks with up to 10 URLs per app, with payload signature verification using RSA-SHA256. The transaction search API is limited to a 31-day window and returns a maximum of 10,000 results per request. PayPal tracks no native GL accounts or supplier registry, so payment targets are identified by email address or phone number.

What moves between them

Supplier invoices and payment instructions flow from SAP S/4HANA to PayPal. ml-connector reads open supplier invoices and their line items from SAP, builds payout instructions mapped to PayPal recipient email addresses, and submits them to PayPal on a schedule or on demand. Payment confirmations and refund data flow back from PayPal into SAP, closing paid invoices in the vendor master and posting reconciliation entries to the general ledger if configured. GL account and cost center mappings ensure payouts are allocated to the correct cost dimensions in SAP.

How ml-connector handles it

ml-connector stores OAuth credentials for both systems and manages token refresh independently on each side, since SAP token lifetimes vary and PayPal tokens expire around 8 hours. For each supplier invoice in SAP, it looks up the supplier master to extract the PayPal recipient identifier (email or phone), validates that the supplier exists in the payout recipient list, and constructs a payout instruction with the invoice amount and currency from SAP. PayPal assigns a payout batch ID; ml-connector tracks it and listens for webhook notifications of successful transfers, failed transfers, or refunds. When a payment is confirmed in PayPal, ml-connector updates the invoice status in SAP to Paid and optionally posts a reconciliation journal entry to the accounts payable and bank GL accounts using the cost center from the invoice. The integration handles the 31-day transaction search window by maintaining a high-water mark timestamp and re-requesting transaction details on 401 token refresh.

A real-world example

A mid-sized e-commerce company runs SAP S/4HANA for order-to-cash and vendor payables. They pay suppliers in multiple countries through PayPal for flexibility, but invoice payment and reconciliation are manual: the accounts payable team exports supplier invoices from SAP each week, enters them into PayPal by hand, tracks payment confirmations in a spreadsheet, and reconciles the ledger at month-end against PayPal transaction history. With SAP S/4HANA and PayPal connected, new supplier invoices are sent to PayPal automatically, payment confirmations are applied to the invoices the moment they settle, and the accounts payable ledger is reconciled daily without leaving SAP. The manual keying step and the spreadsheet are gone.

What you can do

Read open supplier invoices from SAP S/4HANA and send payout instructions to PayPal mapped to supplier email addresses.
Receive PayPal payment confirmations and refunds via webhook, update invoice status in SAP, and close paid records automatically.
Post reconciliation journal entries into SAP general ledger accounts when PayPal payments confirm, allocated to the correct cost center.
Authenticate SAP S/4HANA with OAuth 2.0 Client Credentials and refresh tokens within the scopes defined in the Communication Arrangement, and PayPal with its own Client Credentials and Bearer token.
Poll SAP on a regular schedule for new invoices and monitor PayPal webhook events with RSA-SHA256 signature verification on every notification.

Questions

How does the integration identify which supplier to pay in PayPal when SAP has no supplier email addresses?: The supplier master record in SAP S/4HANA includes a Bank Details section that can store email addresses or phone numbers. ml-connector reads this field to identify the PayPal recipient. If the field is missing or invalid, the invoice is flagged and skipped until the supplier record is updated in SAP.
Does the integration handle multi-currency payments and exchange rates?: Yes. ml-connector reads the currency code from the supplier invoice in SAP and includes it in the payout instruction to PayPal. PayPal manages the foreign exchange rate at settlement time; ml-connector records the settled amount from the webhook confirmation back into SAP for reconciliation.
What happens if a PayPal payout fails or a refund is issued?: PayPal sends a webhook notification with the failure reason or refund details. ml-connector marks the invoice as Payment Failed or Refunded in SAP and can create a reversal journal entry in the general ledger to keep the accounts payable balance correct. The invoice remains open in SAP pending manual review or a retry.

Connect SAP S/4HANA and PayPal

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started