Sage 50 and Stedi integration

What moves between them

Purchase orders and invoices created in Sage 50 are polled and sent to Stedi via REST API, where they are translated to X12 format and routed to your trading partners via SFTP, AS2, or webhooks, using your configured partnerships and connections. Inbound purchase order acknowledgments, invoices, and order changes arrive at Stedi as EDI, are parsed to JSON, and pushed via webhook to ml-connector, which posts them back into Sage 50's accounts payable and general ledger. The sync runs on a schedule you define; typical intervals are 5-15 minutes for near-real-time processing or hourly for most ERP use cases.

How ml-connector handles it

ml-connector runs a Windows polling process with local SDK access to Sage 50 on the same machine. It reads purchase orders and sales invoices by querying modified records by TransactionDate, constructs JSON payloads matching Stedi's required format, and sends them via REST to Stedi's API with an Idempotency-Key header to prevent duplicate shipments. On the inbound side, ml-connector registers a webhook endpoint with Stedi and receives transaction.processed webhooks for parsed inbound EDI. Each webhook is validated via eventId deduplication and transformed back into Sage 50 transaction format using the partnership mapping established at setup. Vendor and partner master records in both systems are matched by DUNS or account number to ensure invoices post to the correct vendor. Retry logic handles transient SDK failures and HTTP 429 rate limits from Stedi with exponential backoff. Because Sage 50 has no interactive session tolerance for concurrent SDK access, the polling process coordinates exclusive use of the SDK session.

A real-world example

A mid-sized distributor uses Sage 50 Accounts for order-to-cash and procure-to-pay, and trades with 40+ suppliers and customers via EDI. Before Stedi, the EDI team hand-keyed inbound invoices into Sage 50 and manually translated outbound purchase orders to X12, a process taking 2-3 hours per day and prone to transcription errors. With Sage 50 and Stedi connected, outbound purchase orders flow automatically to trading partners within minutes of creation, inbound vendor invoices arrive as JSON webhooks and post directly to AP, and the EDI team focuses on partnership setup and exception handling instead of re-keying. Month-end close is faster because all invoices are already recorded in Sage 50.

What you can do

• •Translate Sage 50 purchase orders and invoices to X12 EDI format and route them to trading partners via Stedi using SFTP, AS2, or webhooks.
• •Receive inbound vendor purchase order acknowledgments and invoices from Stedi as JSON webhooks and post them directly into Sage 50 accounts payable.
• •Match vendor and partner master records in Sage 50 and Stedi by account number or DUNS code so invoices post to the correct vendor.
• •Handle Windows SDK exclusive session access and coordinate polling intervals from 5 minutes to hourly based on your trading partner SLAs.
• •Provide a full audit trail of all EDI transactions and Sage 50 postings, with retry logic and deduplication for idempotent inbound processing.

Questions

How does ml-connector handle Sage 50's lack of cloud API and webhooks?

ml-connector runs a local Windows polling process on the same machine as Sage 50, accessing the company data files via the local SDK (US .NET SDK or UK SDO COM layer). It queries purchase orders and invoices by TransactionDate on a schedule you define, typically 5-15 minutes for near-real-time or hourly for most ERP workflows. Inbound EDI from Stedi arrives via webhook directly to ml-connector, eliminating the need for Sage 50 to initiate outbound connections.

What authentication does ml-connector use for each system?

Sage 50 uses Windows-local username and password credentials stored encrypted in ml-connector's configuration. Stedi uses an API key stored in the Authorization header; the key does not expire and can be revoked manually via the Stedi portal. All credentials are encrypted at rest and all API calls to Stedi include the required Idempotency-Key header for deduplication.

What records flow between Sage 50 and Stedi?

Outbound: purchase orders and invoices created in Sage 50 are read by ml-connector and sent to Stedi, where they are translated to X12 EDI. Inbound: vendor invoices, purchase order acknowledgments, and order changes arrive from Stedi as JSON webhooks and are posted into Sage 50's accounts payable and general ledger, matched to the correct vendor by account number or DUNS code.