Infor CloudSuite and TrueCommerce integration

What moves between them

Purchase orders created in Infor CloudSuite are transformed into X12 850 EDI documents and delivered to TrueCommerce for transmission to suppliers. Advance ship notices (X12 856) and invoices (X12 810) received from suppliers through TrueCommerce are transformed back into Infor CloudSuite purchase order receipts and AP invoices on a daily schedule, matched to the original purchase order by supplier and line item. Supplier master data and GL account references are kept synchronized in both directions so documents land on valid dimensions in Infor CloudSuite.

How ml-connector handles it

ml-connector stores Infor CloudSuite OAuth credentials encrypted, parses the customer-specific base URL from the .ionapi file, and obtains a bearer token on a schedule before expiry (token lifetime is configurable per tenant, typically 1 to 24 hours). It polls Infor CloudSuite for new and modified purchase orders, transforms each into an X12 850 document with the correct supplier identification, and uploads the file to TrueCommerce SFTP with the file naming convention established during onboarding. On the return path, ml-connector polls TrueCommerce SFTP for advance ship notices and invoices, parses the X12 856 and 810 documents, matches them back to the originating purchase order in Infor CloudSuite using supplier code and line-item detail, and creates goods receipt and AP invoice records in Infor CloudSuite via the ION API. Infor CloudSuite requires the CONO (company number) parameter on most M3 operations, so ml-connector includes this from the customer configuration. Both systems enforce rate limits (Infor CloudSuite typically 100-500 requests per minute; TrueCommerce throughput controlled by the managed service), so ml-connector backs off on 429 responses and retries with exponential jitter. Every record carries a full audit trail and can be replayed if downstream processing fails.

A real-world example

A mid-market food distributor runs Infor CloudSuite M3 for procurement and inventory management, and uses TrueCommerce to connect with a network of specialty suppliers who operate on EDI 850/856/810. Before the integration, the procurement team manually extracted purchase orders from Infor CloudSuite, formatted them as X12 850 documents, uploaded them to TrueCommerce SFTP, and then manually keyed received quantity and supplier invoices back into Infor CloudSuite after receiving email confirmations from TrueCommerce. With Infor CloudSuite and TrueCommerce integrated, each purchase order is automatically transformed and delivered, acknowledgments and ship notices are matched back to the purchase order, and goods receipts are created without manual intervention. The procurement team now focuses on supplier management instead of file handling, and cycle time from order to receipt is reduced by 2-3 days.

What you can do

• •Automatically transform Infor CloudSuite purchase orders into X12 850 EDI documents and deliver them to TrueCommerce for supplier transmission.
• •Receive X12 856 advance ship notices and X12 810 invoices from TrueCommerce and create goods receipts and AP invoices in Infor CloudSuite, matched to the originating purchase order.
• •Handle Infor CloudSuite's per-customer OAuth endpoints, tenant URLs, and CONO company number requirements without manual URL configuration per customer.
• •Authenticate TrueCommerce via SFTP credentials provisioned during account setup, and parse customer-specific file naming conventions from the onboarding handoff.
• •Poll on a daily or hourly schedule with automatic token refresh, rate-limit backoff, a full audit trail on every record, and error replay.

Questions

How does ml-connector handle Infor CloudSuite's per-customer OAuth endpoints and base URLs?

Each Infor CloudSuite customer provides a .ionapi credentials file containing the OAuth endpoints and base URL specific to their tenant and region. ml-connector parses this file during setup, stores the endpoints encrypted, and uses them to obtain a fresh bearer token before expiry. Token lifetime is configurable per tenant, so ml-connector refreshes proactively to avoid outages.

What EDI documents are transformed and in which direction?

Purchase orders in Infor CloudSuite are transformed into X12 850 documents and sent to TrueCommerce for supplier transmission. Advance ship notices (X12 856) and invoices (X12 810) received from suppliers through TrueCommerce are parsed, matched back to the originating purchase order, and created as goods receipts and AP invoices in Infor CloudSuite via the ION API.

How does ml-connector match received EDI documents back to purchase orders in Infor CloudSuite?

ml-connector matches advance ship notices and invoices to the original purchase order using supplier code and line-item detail from the X12 documents. Once matched, it creates goods receipt and AP invoice records in Infor CloudSuite with the same GL accounts and dimensions, so the procurement cycle is closed automatically.