Epicor Kinetic and Stedi integration

What moves between them

Purchase orders and customer records flow from Epicor Kinetic to Stedi. ml-connector polls Epicor for new or changed POs, translates them to Stedi 850 X12 transactions, and routes them to your trading partners. Inbound 810 invoices, 856 shipment notices, and 855 PO acknowledgments arrive at Stedi's webhook endpoint, parse to JSON, and ml-connector posts them into Epicor Kinetic's AP Invoices and POReceipts modules on the same schedule you define. Vendor master data is mapped once to align supplier names between the two systems, so every PO and invoice references a valid Epicor vendor.

How ml-connector handles it

ml-connector stores both Epicor and Stedi API credentials encrypted. For Epicor, it maintains the tenant URL (since Epicor publishes no shared base address) and handles OAuth2 token refresh when calls return 401. For Stedi, it presents the API Key on every request and generates Idempotency-Keys on outbound writes to prevent duplicate transactions in Stedi's system. Polling frequency follows your defined schedule; changes since the last sync are retrieved using OData date filters (e.g., UpdatedOn gt {timestamp}). Inbound EDI from Stedi arrives via webhook and must complete within 5 seconds, so ml-connector processes asynchronously and stores the event for replay if the downstream Epicor write fails. PO line items are validated against Epicor's parts master before transmission so EDI reaches Stedi with clean data. All records carry a full audit trail including the original EDI file, the JSON translation, and the Epicor posting result.

A real-world example

A mid-sized distributor runs Epicor Kinetic for procurement and order-to-cash. They maintain relationships with 40 suppliers, 20 of which expect EDI-formatted purchase orders and shipment confirmations via SFTP. Before the integration, the procurement team manually exported purchase orders from Epicor, reformatted them into X12 850 EDI files using a spreadsheet script, and uploaded them to each supplier's SFTP folder. Inbound 810 invoices arrived the same way and had to be manually entered into Epicor AP. With Epicor Kinetic and Stedi connected, every new PO in Epicor automatically translates to EDI and routes to the supplier, and supplier invoices arrive at Stedi's webhook, post to Epicor, and are ready for three-way matching. Manual file preparation is eliminated and invoices reach the system within minutes of transmission.

What you can do

• •Automatically translate Epicor Kinetic purchase orders to Stedi 850 EDI transactions and route them to trading partners via SFTP, FTPS, or AS2.
• •Receive inbound 810 invoices, 856 advance shipment notices, and 855 PO acknowledgments through Stedi webhooks and post them into Epicor Kinetic's AP module.
• •Map vendor names and codes between Epicor Kinetic and Stedi so every transaction references the correct supplier.
• •Handle Epicor's OAuth2 token refresh, Stedi's Idempotency-Key deduplication, and validate PO line items against Epicor's parts master before transmission.
• •Maintain a complete audit trail of every EDI file, JSON translation, and Epicor posting result for compliance and troubleshooting.

Questions

Which direction does data move between Epicor Kinetic and Stedi?

Purchase orders and customer data flow from Epicor Kinetic to Stedi, where they are translated to X12 EDI and routed to trading partners. Inbound 810 invoices, 856 shipment notices, and 855 acknowledgments flow from Stedi back into Epicor Kinetic's AP module. Vendor master data is aligned in both directions so every transaction references a valid supplier.

Does ml-connector handle the differences between Epicor Kinetic cloud and on-premises deployments?

Yes. Epicor Kinetic cloud uses tenant-specific URLs and OAuth2 or API Key authentication, while on-premises sites use the Token Resource Service to exchange Basic credentials for a bearer token. ml-connector accepts both configurations per customer and manages token refresh for both paths. All other features (polling, filtering, write operations) work identically across deployments.

How does ml-connector prevent duplicate EDI transactions in Stedi?

Stedi requires an Idempotency-Key header on every outbound write, valid for 24 hours. ml-connector generates a deterministic key based on the Epicor PO number and timestamp, and includes it on every request. If a network failure causes a retry, Stedi deduplicates the transaction using the same key, so your suppliers receive it exactly once.