Infor CloudSuite and Wise integration

What moves between them

The main flow moves outbound: supplier master records and unpaid invoices flow from Infor CloudSuite into Wise as recipients and transfer preparation documents. ml-connector reads the Infor supplier list and invoice list on a schedule, registers each supplier's banking details in Wise as a recipient, and generates a transfer quote for each open invoice amount and currency. When Wise initiates or completes a transfer via webhook, ml-connector posts the payout status and reconciliation reference back into Infor's payment transaction log so the cash position reflects actual outbound activity. Reference data such as GL accounts and currency codes is validated on both sides to prevent invalid transfer attempts.

How ml-connector handles it

ml-connector extracts the base URL and tenant credentials from your Infor CloudSuite .ionapi file, obtains OAuth 2.0 bearer tokens on-demand, and polls the supplier and invoice APIs on a cadence you define. For each supplier, it builds a Wise recipient record (immutable, so updates require delete and recreate) with bank account or email details parsed from Infor. It then generates a Wise transfer quote for each open invoice, using the invoice currency and amount. Wise bearer tokens refresh automatically at 12-hour boundaries. When Wise publishes a transfer state change via webhook (e.g. COMPLETED, FAILED, or PAYMENT_PENDING), ml-connector receives the signature-verified event, looks up the matching invoice in Infor by customer transaction ID, and posts the payout confirmation into the payment transaction log. Rate limits are respected on both sides: Infor typically allows 100-500 requests per minute per client, and Wise allows 100 requests per second with burst limits. ml-connector tracks token expiry so that a regional base URL change or credential rotation does not cause outages, and every record carries a full audit trail.

A real-world example

A mid-sized consulting firm operates Infor CloudSuite Financials for AP and GL, and manages global supplier payouts in 12 different currencies. Before Wise integration, the finance team exported the monthly invoice register from Infor, manually looked up each supplier's bank details in email and spreadsheets, entered them into Wise, generated quotes, and executed transfers one at a time. Reconciliation meant comparing Wise transaction IDs back to Infor's payment log, often weeks later. With Infor CloudSuite and Wise connected, the invoice export and recipient registration happen automatically each month, transfer quotes are pre-calculated, and payout confirmations flow back into Infor's cash accounting the same day. The manual data entry step is eliminated, and the payment log is always current.

What you can do

• •Read supplier master data and unpaid invoices from Infor CloudSuite on a schedule aligned with your payment cycle.
• •Register suppliers in Wise as recipients with bank account and email details parsed from Infor supplier records.
• •Generate Wise transfer quotes for open invoices using the correct currency, amount, and supplier banking method.
• •Receive Wise transfer state changes via webhook and post payment status into Infor's payment transaction log for reconciliation.
• •Track token expiry, respect rate limits on both sides, and maintain a full audit trail on every record and state change.

Questions

Which direction does data move between Infor CloudSuite and Wise?

The main flow is Infor CloudSuite into Wise. Supplier master records and open invoices flow from Infor into Wise to generate recipients and transfer quotes. When Wise completes or fails a transfer, the payout status flows back into Infor's payment log for reconciliation. Reference data such as currency codes is validated in both directions.

Does ml-connector handle the multi-step Wise transfer sequence automatically?

ml-connector automates steps 1 and 2: it creates and updates recipients in Wise, and it generates transfer quotes for each invoice. Steps 3 and 4 (transfer order and payment funding) require explicit user action via the Wise interface or a downstream approval workflow, since fund transfers are sensitive operations. The webhook receives the completion status after a human or payment processor executes the transfer.

How does ml-connector handle Infor CloudSuite regional URLs and token expiry?

ml-connector extracts the regional base URL and OAuth endpoints from your .ionapi credentials file and uses that URL for all API calls. It obtains bearer tokens on-demand, refreshes them automatically at the 12-hour boundary, and tracks expiry so credential rotation or regional changes do not cause outages. If Infor invalidates a token early, ml-connector detects the 401 response and re-authenticates immediately.