IFS Cloud and PayPal integration

What moves between them

The main flow is PayPal into IFS Cloud. PayPal invoices and payment confirmations flow into IFS as supplier invoices and payment proposals, then mapped to IFS GL accounts and company codes. Payment and order events arrive via PayPal webhooks in real-time, triggering reconciliation of PayPal transactions against IFS vouchers and invoice status updates. Reference data such as customers and suppliers aligned across both systems so payment receipts land on valid IFS dimensions. PayPal transactions are read-only in ml-connector so no financial data flows back to PayPal.

How ml-connector handles it

ml-connector stores OAuth2 credentials for both systems and refreshes tokens when they expire, handling the 60-minute IFS token lifecycle and the 8-hour PayPal lifecycle. On the IFS side it uses the tenant-specific base URL per customer and polls OData with filters on modified timestamps to fetch new invoices and payment proposals. On the PayPal side it registers a webhook endpoint and listens for real-time payment and order events with RSA-SHA256 signature verification, while also polling the transaction search API for 31-day lookback reconciliation. It maps PayPal transaction IDs to IFS voucher reference fields and reconciles payment amounts against invoice totals, handling discrepancies with logged exceptions. Rate limits are managed with exponential backoff and jitter; 429 responses trigger exponential backoff on the IFS side, and PayPal webhook retries are automatic but monitored for failure patterns. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized online retailer operates IFS Cloud for procurement, inventory, and general ledger, and uses PayPal for customer order processing and payment collection. Before the integration, the accounting team downloaded PayPal transaction reports daily and manually created supplier and customer invoices in IFS, then spent the first week of month-end chasing discrepancies between PayPal settlements and the revenue and receivables accounts. With IFS Cloud and PayPal connected, each PayPal order flows into IFS automatically as a customer invoice, each settlement posts as a revenue journal entry allocated to the correct GL account, and the accounting team begins month-end close with reconciled payment records and no manual re-keying.

What you can do

• •Sync PayPal invoices and payment confirmations into IFS Cloud as supplier invoices and payment proposals, mapped to the correct GL accounts and company codes.
• •Receive PayPal webhook notifications in real-time for orders, payments, and refunds, triggering immediate updates to invoice status and payment reconciliation in IFS.
• •Authenticate both IFS Cloud and PayPal via OAuth2 Client Credentials, managing token refresh cycles on both sides and handling the different token lifetimes.
• •Reconcile PayPal transactions against IFS vouchers and invoices using transaction IDs, amounts, and timestamps, with logged exceptions for mismatches.
• •Poll the IFS OData API with modified timestamp filters and the PayPal transaction search API with 31-day lookback, backing off exponentially on rate limits.

Questions

Which direction does data move between IFS Cloud and PayPal?

The main flow is PayPal into IFS Cloud. Invoices, payments, and order events from PayPal flow into IFS as supplier invoices, payment proposals, and revenue journal entries. Reference data such as customers and suppliers are aligned in both directions so payments land on valid IFS GL accounts and company codes. PayPal transactions are read-only in ml-connector, so no financial data flows back to PayPal.

How does the integration handle PayPal's webhook signature verification and IFS's OData concurrency requirements?

ml-connector verifies PayPal webhook signatures using RSA-SHA256 via the paypal-transmission-sig header on every incoming notification. On the IFS side, it reads records first to capture their @odata.etag values, then includes that etag in PATCH or POST operations to enforce optimistic concurrency control. This ensures both systems are protected against tampering and concurrent edit conflicts.

What happens when PayPal's 31-day transaction search window doesn't cover all my pending reconciliation?

ml-connector uses both push webhooks for real-time PayPal events and polling of the PayPal transaction search API for 31-day lookback reconciliation. Within the window, it matches PayPal transaction IDs and amounts against IFS vouchers to reconcile payments automatically. Transactions older than 31 days are assumed already reconciled; if a discrepancy is discovered outside the window, it can be replayed manually via the audit trail.