Microsoft Dynamics GP and TrueCommerce integration

What moves between them

The primary flow is outbound from Microsoft Dynamics GP to TrueCommerce. Purchase orders and payables invoices are read from Microsoft Dynamics GP via REST polling, transformed into EDI X12 format (850 for orders, 810 for invoices, 846 for inventory availability), and written to TrueCommerce SFTP or API on a customer-defined schedule. Inbound flows receive EDI documents from TrueCommerce: purchase order acknowledgments (855), advance ship notices (856), and functional acknowledgments (997) are downloaded, parsed, and used to update purchase order and inventory status in Microsoft Dynamics GP. Reference data such as vendors and item numbers are aligned in both directions.

How ml-connector handles it

ml-connector stores the Windows domain account and SFTP or API credentials encrypted. On the Microsoft Dynamics GP side, it connects via Windows Authentication using the domain account, polls REST SBA endpoints with ModifiedDate filters, and handles the Payload wrapper that SBA POST/PATCH bodies require. It respects Microsoft Dynamics GP's constraint that only unposted transactions can be modified and that fiscal periods must be open to create new records. On the TrueCommerce side, it presents SFTP or API credentials per customer configuration, polls for inbound EDI files on the customer's defined schedule, parses X12 documents, and extracts acknowledgment and shipment data. Because neither system supports native idempotency, ml-connector deduplicates outbound orders by document number and inbound acknowledgments by ISA control number. It handles the customer-specific file naming and directory structure that TrueCommerce requires during onboarding and backs off on rate-limit errors from either system.

A real-world example

A mid-sized discrete manufacturer runs Microsoft Dynamics GP on a Windows Server for financials and procurement, and uses TrueCommerce to connect with dozens of suppliers and logistics partners via EDI. Before the integration, the procurement team manually exported purchase orders from Microsoft Dynamics GP, formatted them as X12 EDI, uploaded them to TrueCommerce FTP by hand, and downloaded inbound acknowledgments and ship notices, then manually updated PO status and expected receipt dates back into Microsoft Dynamics GP. With Microsoft Dynamics GP and TrueCommerce connected, each purchase order in Microsoft Dynamics GP automatically flows to TrueCommerce as an EDI 850, and inbound 855 acknowledgments and 856 ship notices automatically update the PO status and inventory receipts in real time. The manual upload and download cycle is eliminated, and procurement staff can focus on exception handling instead of data re-entry.

What you can do

• •Export purchase orders from Microsoft Dynamics GP as EDI X12 850 documents to TrueCommerce on your defined schedule.
• •Export payables invoices from Microsoft Dynamics GP as EDI X12 810 documents to track freight and charges with trading partners.
• •Pull inbound EDI 855 purchase order acknowledgments from TrueCommerce and update PO status and accepted quantities in Microsoft Dynamics GP.
• •Pull inbound EDI 856 advance ship notices from TrueCommerce and update expected receipt dates and inventory receiving in Microsoft Dynamics GP.
• •Map vendors and item numbers between Microsoft Dynamics GP and TrueCommerce so orders reference the correct trading partner accounts and SKUs.

Questions

Which direction does data flow between Microsoft Dynamics GP and TrueCommerce?

The primary direction is outbound from Microsoft Dynamics GP to TrueCommerce. Purchase orders and invoices are exported as EDI X12 documents. Inbound flows receive acknowledgments, ship notices, and functional acknowledgments from TrueCommerce to update PO status and inventory in Microsoft Dynamics GP. Vendor and item master data can be aligned in both directions.

Does Microsoft Dynamics GP's Windows Authentication work with TrueCommerce's SFTP or API?

No, they use completely different auth systems. ml-connector handles the bridge by storing a Windows domain account for Microsoft Dynamics GP polling and separate SFTP or API credentials for TrueCommerce. The Windows domain account is used only for the Microsoft Dynamics GP REST API calls and does not expose credentials to TrueCommerce.

How does the integration handle Microsoft Dynamics GP's constraint that only unposted transactions can be modified?

ml-connector reads only posted purchase orders from Microsoft Dynamics GP for export to TrueCommerce, since a posted order is immutable. When inbound acknowledgments arrive, it updates only the received quantity and status fields on the PO, which are writable regardless of post state. If a PO is fully closed in Microsoft Dynamics GP, inbound updates are skipped with an audit log entry.