SYSPRO and TrueCommerce integration

What moves between them

SYSPRO purchase orders and invoice records flow outbound to TrueCommerce on a poll cycle, where they are transformed into EDI X12 format and routed to trading partners. Trading partner acknowledgments (855), advance ship notices (856), and invoices (810) arrive in TrueCommerce and are polled back into SYSPRO as received documents for matching and reconciliation. The integration runs bidirectional but the primary load moves outbound: new purchase orders in SYSPRO trigger outbound pushes to TrueCommerce immediately, while inbound documents are read on a schedule to avoid excessive polling.

How ml-connector handles it

ml-connector obtains and refreshes SYSPRO session tokens on every poll cycle and uses e.net Business Objects to read PorMasterHdr and PorMasterDetail records (purchase order headers and lines), transforming them to X12 850 format and uploading to TrueCommerce via SFTP. It respects TrueCommerce file naming conventions, which are customer-specific and confirmed during setup, and tracks which files have been processed so duplicate uploads do not occur. Inbound documents are downloaded from the TrueCommerce SFTP folder on a schedule, parsed from EDI format, and upserted into SYSPRO's supplier and inventory tables. TrueCommerce uses ISA control numbers for EDI deduplication (not application-level idempotency headers), so ml-connector preserves control numbers across the bridge. Because TrueCommerce has no published rate limits and throughput is managed on their side, ml-connector begins with conservative poll intervals and adjusts upward once confirmed safe by TrueCommerce.

A real-world example

A discrete manufacturer with 40 locations uses SYSPRO for procurement and inventory, and maintains relationships with 120 suppliers via TrueCommerce EDI. Before the integration, the procurement team exported purchase orders from SYSPRO daily, emailed them to TrueCommerce support to push via EDI, and manually logged into the TrueCommerce portal to download acknowledgments and advance ship notices each morning. Inbound documents were printed and routed to warehouse supervisors via email. With SYSPRO and TrueCommerce connected, each new PO in SYSPRO reaches suppliers the same day through the managed network, and incoming acknowledgments and shipment notices flow back into SYSPRO automatically where they can be matched against orders and trigger warehouse workflows.

What you can do

• •Export SYSPRO purchase orders and order changes to TrueCommerce in X12 850 format on demand or on schedule.
• •Retrieve purchase order acknowledgments, advance ship notices, and invoices from trading partners via TrueCommerce and load them into SYSPRO.
• •Maintain SYSPRO session tokens and handle TrueCommerce file naming conventions so both systems remain in sync.
• •Track processed files and control numbers to prevent duplicate uploads and support replay of failed records.
• •Poll SYSPRO and TrueCommerce on a schedule you define, with retries and a full audit trail on every record.

Questions

How does the integration handle SYSPRO session tokens and TrueCommerce file naming conventions?

ml-connector logs into SYSPRO via e.net Logon to obtain a session token on each poll cycle and refreshes it if a call returns an error. TrueCommerce file naming conventions are customer-specific and must be confirmed during setup with their team. ml-connector stores the agreed-upon convention and applies it to every outbound file so TrueCommerce recognizes and processes them correctly.

Can the integration push SYSPRO changes to TrueCommerce immediately, or does it only poll?

SYSPRO publishes no webhook system, so the integration is primarily polling-driven. However, ml-connector can be configured to check for new purchase orders immediately after they are created in SYSPRO, so outbound documents reach trading partners the same business day. Inbound documents are polled on a standard schedule.

What happens if a TrueCommerce trading partner returns an acknowledgment that conflicts with the SYSPRO purchase order?

The integration downloads the acknowledgment (X12 855) into SYSPRO's document tables for manual review and matching. SYSPRO's built-in PO matching logic flags discrepancies such as quantity or price differences, and the procurement team can approve the change or reject the acknowledgment via standard SYSPRO workflows. ml-connector does not auto-approve mismatched documents.