Infor CloudSuite and Stedi integration

What moves between them

Purchase orders flow from Infor CloudSuite to Stedi. ml-connector polls the ION API Gateway for new or modified purchase orders, maps line items to the X12 850 format (quantities, part numbers, dates, ship-to addresses), writes the transaction to Stedi via the REST API with an Idempotency-Key, and Stedi routes the EDI file to the supplier via SFTP or AS2. Inbound 810 invoices from suppliers arrive at Stedi, which parses them and posts a webhook. ml-connector receives the webhook, maps invoice line items back to Infor CloudSuite GL account and supplier references, and writes the AP invoice into CloudSuite via the ION API. Reference data (suppliers, GL accounts, ship-to locations) is queried once per flow setup and cached to avoid repeated lookups.

How ml-connector handles it

ml-connector stores Infor CloudSuite and Stedi credentials encrypted and refreshes the Infor OAuth token before it expires (tracking the 1 to 24 hour lifetime per tenant). On outbound, it polls the ION API for purchase orders, builds the 850 EDI structure with line-item details (unit prices, delivery dates, UOM), and POSTs to Stedi with an Idempotency-Key header (required for deduplication across retries). Stedi handles the SFTP or AS2 transmission to the partner. On inbound, ml-connector registers a webhook endpoint with Stedi and decodes incoming transaction.processed.v2 events, mapping the parsed 810 invoice JSON to Infor CloudSuite supplier and GL account codes. Both Infor and Stedi rate-limit; ml-connector respects HTTP 429 and backs off exponentially. The Infor ION API Gateway does not support traditional webhooks, so polling cadence is driven by your business cycle (e.g., daily PO checks, continuous invoice checks). Stedi webhook endpoints must respond within 5 seconds, so ml-connector processes asynchronously and writes to Infor in the background.

A real-world example

A mid-sized discrete manufacturer uses Infor CloudSuite Industrial for production planning and procurement, and trades regularly with 15-20 contract suppliers. Before the integration, the procurement team exported purchase orders from Infor as CSV, manually formatted them into X12 850 EDI files, and uploaded them to an SFTP server for each supplier. When invoices arrived from suppliers as EDI files, the team parsed them manually and re-entered line items into Infor's AP module. With Infor CloudSuite and Stedi connected, each new purchase order is automatically formatted as X12 EDI and delivered to the supplier within minutes. Inbound invoices from Stedi are parsed and posted into AP automatically, mapped to the original PO lines, eliminating data re-entry and reducing invoice-to-cash cycle time from 2 weeks to 3 days.

What you can do

• •Transform Infor CloudSuite purchase orders into X12 850 EDI format and send them to trading partners via Stedi's SFTP or AS2 channels.
• •Receive inbound 810 supplier invoices from Stedi, parse them from X12 EDI into JSON, and post them into Infor CloudSuite's AP module.
• •Map supplier names, part numbers, and GL accounts between Infor's data model and X12 EDI segment structures automatically.
• •Authenticate Infor CloudSuite using OAuth 2.0 with the ION API Gateway and Stedi using API key, managing token refresh and credential encryption.
• •Poll Infor CloudSuite on a business cycle (daily PO sweep, continuous invoice polling) and deliver Idempotency-Key headers to Stedi for guaranteed transaction deduplication.

Questions

Which direction does data flow between Infor CloudSuite and Stedi?

Purchase orders flow from Infor CloudSuite into Stedi, where they are converted to X12 850 EDI and sent to suppliers. Inbound 810 invoices from suppliers arrive at Stedi, are parsed into JSON, and flow back into Infor CloudSuite's AP module. Suppliers and GL accounts are queried from Infor once per setup and used for mapping on both directions.

Does Infor CloudSuite support webhooks for real-time purchase order updates?

No. Infor CloudSuite has no self-service webhooks; ml-connector polls the ION API Gateway for new or modified purchase orders on a schedule you define (typically daily or continuous). This trade-off gives you full control over sync timing and avoids the infrastructure cost of ION BOD document subscriptions.

How does the integration handle Infor OAuth token expiry and Stedi's Idempotency-Key requirement?

ml-connector tracks the Infor token lifetime (1 to 24 hours per tenant) and refreshes it proactively before expiry to avoid mid-flow failures. For Stedi, every outbound transaction write includes an Idempotency-Key header for 24-hour deduplication, so retries and re-runs never create duplicate 850 or 810 records even if the same operation is processed twice.