Infor CloudSuite and Cleo integration

What moves between them

Purchase orders and supplier invoices flow from Infor CloudSuite into Cleo. ml-connector polls Infor CloudSuite via the ION API Gateway for suppliers, POs, and AP invoices at a cadence tied to your procurement cycle. Each record is mapped to Cleo EDI format (850 for POs, 810 for invoices) and written into Cleo via REST API calls. In the reverse direction, Cleo outbound EDI transactions (e.g., 810 invoices from suppliers) are polled from Cleo folders and can be parsed into Infor CloudSuite AP invoice records. GL accounts and customer master records flow in both directions to ensure Infor CloudSuite dimensions match Cleo trading partner attributes.

How ml-connector handles it

ml-connector stores both Infor CloudSuite and Cleo credentials encrypted, extracts the tenant-specific ION API Gateway URL and OAuth endpoints from the Infor .ionapi file, and manages token refresh for both systems independently. Because Infor CloudSuite offers no webhooks, ml-connector polls the REST API on a schedule you define, querying suppliers by modification date and invoices by status to avoid fetching the same record twice. Cleo's REST API also requires polling for outbound transactions, so ml-connector retrieves files from your outbound folders and parses EDI segments into supplier or invoice records. EDI documents are mapped to Infor CloudSuite M3 entities (CRS620MI for suppliers, APS100MI for invoices, PPS100MI for POs), and each call includes required parameters such as CONO (company number) for M3 operations. Token lifetime varies per tenant in Infor CloudSuite, so ml-connector proactively refreshes before expiry to avoid mid-flow failures. Cleo's REST API does not offer idempotency guarantees, so ml-connector deduplicates via external tracking of file IDs and transaction checksums. Rate limits at both systems are handled with exponential backoff and retry. Every record flows through a full audit trail, so any mapping failure or network error can be replayed once corrected.

A real-world example

A mid-sized distribution company runs Infor CloudSuite M3 for procurement, invoicing, and GL consolidation across four regional warehouses. They trade with 50+ suppliers via EDI, with POs and invoices flowing through a Cleo EDI hub. Before the integration, procurement staff manually exported PO data from Infor CloudSuite into a CSV, reformatted it into EDI 850 format, and uploaded it into Cleo for transmission to suppliers. Supplier invoices arrived in Cleo as EDI 810 documents, were downloaded as text files, and were manually re-entered into Infor CloudSuite AP by the accounts payable team. Month-end took three extra days to reconcile Cleo transaction counts against Infor CloudSuite ledger entries. With Infor CloudSuite and Cleo connected, POs are automatically formatted as EDI 850 and transmitted through Cleo as soon as they are approved in Infor CloudSuite. Supplier invoices flow back from Cleo as EDI 810 documents and are parsed into Infor CloudSuite AP invoices, allocated to the correct GL accounts and cost centers. Invoice matching completes in hours, and month-end close starts with supplier accounts already reconciled.

What you can do

• •Automatically format Infor CloudSuite purchase orders as EDI 850 documents and transmit them through Cleo to suppliers.
• •Parse EDI 810 invoices from Cleo and load them into Infor CloudSuite AP with GL accounts and cost center allocation.
• •Keep supplier master records synchronized between Infor CloudSuite and Cleo so trading partner attributes stay consistent.
• •Authenticate Infor CloudSuite with OAuth 2.0 and manage the tenant-specific ION API Gateway base URL and token lifecycle per customer region.
• •Poll both Infor CloudSuite and Cleo on a schedule defined by your procurement calendar, with retries, deduplication, and a full audit trail on every record.

Questions

How does ml-connector retrieve data from Infor CloudSuite if there are no webhooks?

Infor CloudSuite does not offer self-service webhooks. ml-connector polls the REST API endpoints on a schedule you define, querying suppliers and invoices by modification date or status to retrieve only new or updated records. This avoids redundant fetches and keeps your data fresh on your timeline, tied to your procurement cycle.

What is the .ionapi file and why does ml-connector need it?

The .ionapi file is a credentials bundle provided by Infor that contains the OAuth endpoint, client ID, secret, and the tenant-specific ION API Gateway base URL for your Infor CloudSuite instance. ml-connector extracts these values from the file to construct authenticated requests. The base URL varies by region and customer, so this file is the single source of truth for your instance location and credentials.

Can Infor CloudSuite invoices flow back out through Cleo to suppliers?

Yes. ml-connector can retrieve outbound EDI transactions (e.g., 810 invoices) from Cleo via polling, parse the EDI segments, and load them into Infor CloudSuite as AP invoices if you configure that direction. By default, the main flow is POs and invoices from Infor CloudSuite into Cleo, but the integration is bidirectional and can be tuned to your needs.