Sage 50 and TrueCommerce integration

What moves between them

The main flow runs from Sage 50 outbound to trading partners. When a purchase order is created in Sage 50, ml-connector polls for new or modified POs, transforms them into EDI X12 850 format, and uploads them to the TrueCommerce SFTP gateway on a schedule (typically daily). Supplier invoices arrive at TrueCommerce as X12 810 EDI documents and are polled hourly or on demand; ml-connector transforms them back into Sage 50's vendor invoice format and creates or updates vendor invoice records. Purchase order acknowledgments (X12 855) and advance ship notices (X12 856) flow the same direction, enriching the Sage 50 PO record with supplier confirmation and shipment tracking. All records are keyed by the original Sage 50 purchase order number and vendor ID for reliable matching and deduplication.

How ml-connector handles it

ml-connector runs as a Windows service with direct access to Sage 50 company data files via the local SDK. Authentication to Sage 50 uses Windows-local credentials (ApplicationID, CompanyPath, Username, and Password for the US edition, or DataPath and credentials for the UK edition). On each polling cycle, it queries Sage 50 for modified purchase orders and invoices since the last run, using LastModifiedDate or TransactionDate as the cursor. Outbound POs are transformed into standard X12 850 EDI format and uploaded via SFTP to integrationftp.truecommerce.com using TrueCommerce-provisioned credentials. Inbound documents (supplier invoices, acknowledgments, ship notices) are downloaded from the TrueCommerce SFTP folder, validated against the original Sage 50 PO number and vendor, and inserted or updated as vendor invoices or PO records. EDI functional acknowledgments (X12 997) are generated by TrueCommerce and handled via ISA control number deduplication rather than application-level idempotency headers. Polling interval is configurable but typically hourly for inbound and daily for outbound. The service handles exclusive-access constraints (Sage 50's SDK requires no interactive user session while the integration user is active) by running on a dedicated Windows machine or with a dedicated local session. Every document transformation and record insert is logged with the source EDI control number, Sage 50 record ID, and transformation timestamp for full audit trail and replay on failure.

A real-world example

A regional machinery distributor maintains supplier relationships across North America and Europe via TrueCommerce EDI. The company runs Sage 50 on a Windows server for accounting and procurement. Before the integration, the procurement team exported purchase orders from Sage 50, manually formatted them as EDI X12, and uploaded them to TrueCommerce weekly. Supplier invoices arrived at TrueCommerce as EDI 810s and had to be downloaded, parsed, and re-entered into Sage 50 by hand, a task that took several hours each week and introduced typos and duplicate invoice records. With Sage 50 and TrueCommerce connected, each new purchase order is automatically transformed and sent to suppliers within minutes, and inbound invoices and acknowledgments flow directly into Sage 50 with full audit trail. The procurement team now focuses on supplier relationships and exception handling rather than data re-entry.

What you can do

• •Transform purchase orders from Sage 50 into EDI X12 850 format and upload them to TrueCommerce SFTP on a configurable schedule.
• •Receive supplier invoices as X12 810 EDI documents from TrueCommerce and create or update vendor invoice records in Sage 50 with full line-item mapping.
• •Match inbound documents to source purchase orders using order number and vendor ID, with deduplication via EDI ISA control number.
• •Bridge Sage 50 local SDK authentication and exclusive-access constraints to TrueCommerce cloud-based SFTP and managed APIs with reliable polling and retry logic.
• •Maintain a complete audit trail of every EDI transformation, SFTP upload and download, and Sage 50 record insert or update for compliance and troubleshooting.

Questions

How does ml-connector handle Sage 50's requirement that the integration user cannot be logged in interactively while the SDK session is active?

ml-connector runs as a Windows service on a dedicated machine or user session where the integration user is not logged in interactively. The Windows service account has direct access to the Sage 50 company data files via file-system path and SDK, and uses application-level credentials (ApplicationID and CompanyPath for US edition, or DataPath for UK edition) to open the company data, avoiding session conflicts. For on-site deployments, a separate integration user account is created with no interactive login rights.

Which direction does EDI data flow between Sage 50 and TrueCommerce, and what document types are supported?

Outbound (Sage 50 to trading partners via TrueCommerce): Purchase orders in X12 850 format are polled from Sage 50 and uploaded to TrueCommerce SFTP on a daily or custom schedule. Inbound (trading partners via TrueCommerce to Sage 50): Supplier invoices (X12 810), purchase order acknowledgments (X12 855), and advance ship notices (X12 856) are polled from TrueCommerce and inserted as vendor invoices or PO enhancements in Sage 50. The flow is one-directional per document type; invoices and acknowledgments do not flow back out to trading partners.

How are TrueCommerce credentials and file paths managed, and are there test or sandbox modes?

All TrueCommerce credentials (SFTP username and password, or API keys for the managed Exchange API) are provisioned by TrueCommerce during account setup and stored encrypted in ml-connector configuration. File naming conventions and integration paths are customer-specific and confirmed during onboarding with TrueCommerce. Test mode is available via the TrueCommerce Transaction Manager UI flag (ISA15 field set to T for test, P for production) rather than a separate sandbox FTP host. ml-connector respects this flag and applies test or production mode on each SFTP cycle.