Microsoft Dynamics GP and JAGGAER integration

What moves between them

The main flow runs bidirectionally. Vendors and purchase orders flow from Dynamics GP into JAGGAER so sourcing and supplier interactions happen in the cloud platform. Finalized invoices from JAGGAER flow back into Dynamics GP's payables ledger, matched to the original purchase orders and the vendor. Reference data such as GL accounts and supplier master records are synchronized in both directions. Dynamics GP invoices are read-only once posted, so ml-connector creates new invoices in Work status before GP's month-end posting step, and JAGGAER invoices are similarly pulled as finalized records ready to post.

How ml-connector handles it

ml-connector stores Windows domain credentials encrypted and uses them to authenticate against Dynamics GP's SBA or SOAP endpoints on the customer's network, working through firewalls where the customer has exposed the GP instance with a valid SSL certificate or local agent. For JAGGAER, it stores the OAuth2 client_id and client_secret encrypted and refreshes the bearer token when calls return 401. Vendor records are mapped bidirectionally by external ID so the same supplier appears in both systems with a linked relationship. Purchase orders flow GP to JAGGAER with line-item detail and GL account mapping, while JAGGAER invoices flow back matched to the original PO number and vendor. ml-connector respects Dynamics GP's fiscal period constraints, polling ModifiedDate filters at customer-defined intervals with delays to avoid overwhelming the on-premises SQL Server, and it validates GL accounts and cost centers before creating new payables entries in GP. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-market discrete manufacturer runs Microsoft Dynamics GP on-premises for accounting and purchasing, and has rolled out JAGGAER for supplier management and sourcing across three plants. Before the integration, the procurement team maintained vendor master records in both systems by hand, entering new suppliers into GP for invoice processing and then re-entering them into JAGGAER for sourcing events, leading to duplicates and mismatches. When an invoice arrived from a supplier, it was matched manually to the purchase order in JAGGAER, then re-keyed into Dynamics GP's payables system for posting. With GP and JAGGAER connected, new vendors approved in GP sync to JAGGAER automatically, purchase orders route through JAGGAER for sourcing, and finalized invoices flow back into GP's payables ledger already matched to the PO. The procurement team focuses on supplier relationships and negotiations, while the finance team receives invoices ready to post into the ledger.

What you can do

• •Sync vendors from Dynamics GP into JAGGAER for sourcing, with bidirectional master-record updates.
• •Move purchase orders from Dynamics GP to JAGGAER with full line-item detail and GL account mapping.
• •Pull finalized invoices from JAGGAER back into Dynamics GP payables, matched to the original purchase orders.
• •Authenticate Dynamics GP with Windows domain credentials and JAGGAER with OAuth2 client credentials, handling both on-premises and cloud environments.
• •Respect Dynamics GP fiscal period constraints and polling limits, with a full audit trail on every record.

Questions

How does ml-connector handle Dynamics GP's on-premises nature and Windows authentication?

ml-connector stores Windows domain credentials encrypted and presents them to the Dynamics GP SBA or SOAP endpoints on the customer's network. The customer must expose the GP instance through the firewall with a valid SSL certificate or via a local agent, and ml-connector works through that connection. Windows authentication is tied to an Active Directory account with the appropriate GP User role.

Which direction do vendor and invoice records move between Dynamics GP and JAGGAER?

Vendors sync bidirectionally with external ID mapping so the same supplier appears in both systems linked together. Purchase orders flow from Dynamics GP to JAGGAER for sourcing and supplier interaction. Invoices are pulled from JAGGAER back into Dynamics GP payables, matched to the original purchase order and vendor, and created in Work status before posting.

What happens when Dynamics GP's fiscal periods are closed or JAGGAER's OAuth2 token expires?

ml-connector validates that the target fiscal period is open in Dynamics GP before creating new payables entries, returning a clear error if it is closed. For JAGGAER, it refreshes the OAuth2 bearer token proactively and retries on 401 responses, tracking token expiry so a renewal does not cause an outage.