IFS Cloud and Wise integration

What moves between them

Supplier payment data flows from IFS Cloud to Wise. ml-connector reads payment proposals and pending vouchers in IFS, looks up or creates corresponding supplier recipient records in Wise, and creates payment transfers on a schedule you define. Once a transfer reaches completed status in Wise, ml-connector posts a voucher in IFS Cloud marking the payment as settled. Supplier master records are synchronized bidirectionally to keep vendor information aligned.

How ml-connector handles it

ml-connector stores both OAuth2 credentials encrypted and refreshes IFS tokens when they approach expiry. For each supplier in the payment batch, it queries or creates a Wise recipient keyed to the IFS supplier ID; recipient updates are handled by deleting the old record and creating a new one, since Wise recipients cannot be modified in place. Before creating a transfer, it fetches a fresh Wise quote (since quotes expire) and stores the quote ID as part of the transfer order. On the IFS side, every payment voucher read is captured with its ETag value; when the Wise transfer completes, ml-connector updates the IFS voucher with the transfer ID and marks it as paid, sending the ETag to enforce that no other process has changed the record. Wise transferstate-change webhooks are received and stored for audit, and failed transfers trigger alerts. IFS rate limits and Wise rate limits are respected with exponential backoff; transfers that hit rate limits are requeued. Every record move is logged with the original IFS payment proposal ID, the Wise transfer ID, and the final IFS voucher update, making replay and audit trivial.

A real-world example

A global manufacturing company with plants in three countries runs IFS Cloud for procurement and finance. Suppliers span multiple currencies and countries, requiring international payments through Wise. Before the integration, the accounts payable team extracted approved payment proposals from IFS weekly, manually looked up bank details in a shared vendor file, created transfers in Wise one by one, then returned to IFS to mark invoices as paid. With IFS Cloud and Wise connected, each approved payment proposal automatically becomes a Wise transfer to the correct recipient and supplier currency. Failed transfers alert the team immediately, and reconciliation is instant because IFS vouchers and Wise transfers are linked in the audit trail.

What you can do

• •Read payment proposals and pending vouchers from IFS Cloud and create corresponding transfers in Wise, keyed to supplier recipient records.
• •Automate the Wise transfer sequence including quote creation, recipient lookup-or-create, transfer order placement, and payment funding.
• •Keep IFS suppliers and Wise recipients aligned by syncing vendor master data and handling Wise recipient immutability by delete-and-recreate.
• •Update IFS Cloud vouchers with Wise transfer IDs and paid status after transfer completion, using ETag values to prevent concurrency conflicts.
• •Respect IFS OData and Wise API rate limits, retry failed transfers, track Wise quote expiry, and maintain a full audit trail of every payment move.

Questions

How does the integration handle Wise recipient immutability?

Wise recipients cannot be modified after creation. When a supplier record changes in IFS Cloud, ml-connector deletes the old Wise recipient record and creates a new one with the updated information. This ensures the recipient details (bank account, payout currency) always match the current IFS supplier record.

What happens if a Wise quote expires before a transfer is created?

Wise quotes expire after a time limit. ml-connector creates a fresh quote immediately before funding each transfer, so an expired quote does not block payment. If a quote expires between creation and transfer order, the integration detects the failure and requeues the payment with a new quote.

How is payment status reconciled between IFS Cloud and Wise?

When a Wise transfer reaches completed status, ml-connector reads the transfer ID and completed timestamp, then updates the matching IFS Cloud voucher using the ETag value to prevent conflicts. This marks the invoice as paid in IFS and creates a linked audit entry showing both the IFS voucher number and the Wise transfer ID for end-to-end traceability.