Infor CloudSuite and Tradeshift integration

What moves between them

The main flow is bidirectional. Purchase orders created in Infor CloudSuite are translated to UBL format and published to Tradeshift so suppliers see them in the network. Supplier invoices received through Tradeshift are translated from UBL to CloudSuite AP format and polled into the system on a schedule you control. Receipts and acknowledgments flow the same direction, keeping both systems current without manual re-entry.

How ml-connector handles it

ml-connector stores both credential sets encrypted and manages the different auth schemes: OAuth 2.0 client credentials for CloudSuite (extracting the base URL and tenant ID from the .ionapi file) and OAuth 1.0a signature generation for Tradeshift calls (signing each request with the shared secret). Because both systems are pull-only, it polls CloudSuite for new purchase orders and Tradeshift for new invoices and receipts on your chosen schedule. Documents are translated between CloudSuite's MI-based purchase order and invoice schemas and Tradeshift's UBL XML structure, mapping supplier references, line items, quantities, and amounts. CloudSuite's OAuth token can have a 1-24 hour lifetime, so ml-connector proactively refreshes before expiry. Both systems return 429 when rate limits are hit, so ml-connector backs off and retries, and every record carries a full audit trail so failed translations can be replayed.

A real-world example

A mid-sized distributor runs Infor CloudSuite M3 for procurement, inventory, and finance, and trades with over 200 suppliers, many of them large manufacturers who require orders and invoices to flow through the Tradeshift network. Before the integration, the purchasing team manually entered purchase orders into Tradeshift after creating them in CloudSuite, and the accounts payable team spent the first week of each month reconciling supplier invoices received through Tradeshift back into CloudSuite by hand, matching line items and amounts, and calling suppliers to clarify discrepancies. With CloudSuite and Tradeshift connected, each PO created in CloudSuite automatically publishes to the network, suppliers acknowledge and ship from that single version of truth, and invoices flow directly into CloudSuite AP with line items already matched to the original PO. Invoice-to-PO matching becomes automatic, and the monthly reconciliation step is eliminated.

What you can do

• •Publish purchase orders from Infor CloudSuite to Tradeshift in UBL format so suppliers see a single version of truth.
• •Receive supplier invoices through Tradeshift and translate them into Infor CloudSuite AP transactions, matched to original purchase orders.
• •Sync receipts and delivery acknowledgments between CloudSuite and Tradeshift to keep both systems current.
• •Authenticate CloudSuite via OAuth 2.0 with tenant-specific ION Gateway endpoints and Tradeshift via OAuth 1.0a signing, managing token refresh and request signatures.
• •Poll both systems on your schedule with automatic retry, rate-limit backoff, and a full audit trail on every document.

Questions

How does the integration handle the different document formats between Infor CloudSuite and Tradeshift?

Infor CloudSuite stores purchase orders and invoices in its MI-based schema (PPS100MI for POs, APS100MI for AP). Tradeshift uses UBL 2.0/2.2 XML. ml-connector translates documents between the two formats, mapping supplier references, line items, quantities, and amounts so each system sees data it understands without manual re-keying or format conversion.

Does the integration support push notifications from either system, or does it rely only on polling?

Both Infor CloudSuite and Tradeshift are pull-only from an API perspective. CloudSuite supports ION Desk BOD document flows for push, but those require admin setup in ION Desk for each event type. Tradeshift offers an optional event stream for registered apps, but most integrations use polling with changedAfter filters for simplicity. ml-connector polls both systems on your schedule.

How does the integration handle authentication differences between the two systems?

Infor CloudSuite uses OAuth 2.0 Resource Owner Password Credentials Grant with a tenant-specific ION Gateway base URL and token endpoint extracted from the .ionapi file. Tradeshift uses OAuth 1.0a with a shared secret and requires the X-Tradeshift-TenantId header on every call. ml-connector manages both credential flows, refreshing CloudSuite tokens before expiry and signing every Tradeshift request with the OAuth 1.0a secret.