Plex and Cleo integration

What moves between them

Purchase orders and releases flow from Plex into Cleo daily (or on your configured interval). ml-connector fetches new and modified POs via Plex REST API, maps them to EDI 850 transactions with line-item detail, and submits them through Cleo's file API to your configured supplier folder. Supplier invoices received through Cleo (typically EDI 810 or API payloads) are parsed and mapped back to Plex invoice records, updating quantity received and GL account distributions. Payment acknowledgments flow one direction only: from Cleo into Plex GL to record supplier reconciliation.

How ml-connector handles it

ml-connector stores Plex OAuth 2.0 client credentials and Cleo username/password encrypted and refreshes both bearer tokens when they expire or when a 401 is returned. On the Plex side it polls the REST API on a configurable schedule (typically daily or per shift) filtering POs by modified_date and created_date to avoid duplicate submissions. On the Cleo side it reads from your configured supplier folder and parses inbound EDI 810s or API payloads into invoice structure, then submits outbound EDI 850 POs to the folder for transmission. Line items and GL account references from Plex are preserved in the EDI segment mappings so your supplier receives cost center and account distribution data. Because Plex has no webhooks, polling is used for both inbound and outbound flows. Supplier data (name, ship location, terms) is cached per customer and refreshed monthly. Every PO and invoice carries a Plex document number and Cleo transaction ID for audit and replay.

A real-world example

A mid-sized discrete manufacturer in automotive component supply uses Plex for purchasing, inventory, and supply chain management, and uses Cleo to exchange EDI documents with Tier 1 automotive OEMs and commodity suppliers. Before the integration, buyers exported purchase orders from Plex as spreadsheets, manually mapped them into EDI 850 format in Excel, and submitted them to suppliers via FTP or email. Received invoices arrived as EDI 810 files in a shared mailbox and were manually parsed back into Plex, a process that took days and introduced errors when PO structure changed. With Plex and Cleo connected, each PO created in Plex flows automatically to Cleo, mapped to EDI 850, and transmitted to the supplier within minutes. Supplier invoices received through Cleo are automatically matched to Plex POs and recorded as received. Procurement and payables cycles are shorter and manual re-keying is eliminated.

What you can do

• •Send Plex purchase orders to suppliers as EDI 850 transactions through Cleo daily or on your configured interval.
• •Receive supplier invoices and ASNs via Cleo as EDI 810/856 and record them as received in Plex without manual data entry.
• •Map Plex cost centers, GL accounts, and supplier terms into EDI segments so suppliers receive complete transaction context.
• •Authenticate both Plex (OAuth 2.0 client credentials) and Cleo (OAuth 2.0 password grant) and manage token expiry automatically.
• •Poll Plex on a schedule, track every PO and invoice with audit IDs, and replay any failed transaction from the queue.

Questions

What data moves between Plex and Cleo?

Purchase orders, releases, and line items flow from Plex to Cleo and are formatted as EDI 850 transactions. Supplier invoices and advance ship notices arrive at Cleo as EDI 810 or 856 and are recorded as received in Plex. Payment confirmations flow from Cleo into Plex GL for cash application and reconciliation. Data moves on a polling schedule you configure, typically daily.

Why does the integration use polling instead of webhooks?

Plex does not offer native webhooks, so polling the REST API on a configurable interval is the only reliable method. ml-connector filters by modified_date and created_date to avoid duplicate submissions and queries Cleo's file folder for inbound EDI so no data is missed between polls.

How does the integration handle Plex company codes and Cleo tenant isolation?

The Plex company code (PCN) is stored per customer and used to route API calls to the correct data partition. Cleo credentials are tenant-specific, so ml-connector authenticates to your Cleo host and folder. Each customer configuration is isolated and updated independently of others.