Microsoft Dynamics GP and Cin7 integration

What moves between them

Master data flows from Microsoft Dynamics GP into Cin7 Core: GP vendors become Cin7 Core suppliers and GP inventory items become Cin7 Core products, on a polling schedule keyed to GP ModifiedDate. Transactions flow back the other way: when a Cin7 Core purchase reaches the INVOICE approach, ml-connector creates a matching payables invoice in GP against the right vendor and GL accounts, and goods receipts can post as well. GL account codes are mapped in both directions but never written into Cin7 Core, since its chart of accounts is read-only. GP remains the authority for posted financials.

How ml-connector handles it

ml-connector stores GP Windows credentials and the Cin7 Core account ID and application key encrypted, presenting Windows Negotiate or NTLM to the GP SBA or SOAP endpoint and the two key headers to Cin7 Core on every call. Because GP has no event stream, it polls GP vendor and item lists by ModifiedDate and pages SBA with top and skip, while subscribing to Cin7 Core Automation webhooks for purchase created and updated events; where the webhook payload lacks a signature it is treated as a trigger and the record is re-read over the API. GP vendor IDs map to Cin7 Core supplier names and item numbers map to product SKUs, and Cin7 Core line account codes map to GP segmented account numbers before any payables invoice is created. Writes target only unposted GP work transactions in an open fiscal period, and multicurrency documents carry CurrencyId and ExchangeRate. SBA POST bodies are wrapped in a Payload key. GP throughput is bounded by the customer SQL Server, so concurrency is held low; Cin7 Core 429 responses are retried using the Retry-After header. Every record carries a full audit trail and can be replayed if a call fails.

A real-world example

A mid-sized wholesale distributor with around 120 staff runs Microsoft Dynamics GP for financials and accounts payable and adopts Cin7 Core to manage warehouse stock and purchasing across several sales channels. Before the integration, buyers raised purchase orders in Cin7 Core while the finance team re-keyed every supplier bill into GP, and the vendor list and item catalog drifted apart between the two systems. With the connection in place, GP vendors and items populate Cin7 Core automatically, and each authorised Cin7 Core purchase invoice posts into GP as an unposted payables voucher ready for review. The duplicate data entry is gone and the two systems agree on suppliers and stock items.

What you can do

• •Push Microsoft Dynamics GP vendors and inventory items into Cin7 Core as suppliers and products.
• •Create GP payables invoices from authorised Cin7 Core purchases, on the correct vendor and GL accounts.
• •Map GP segmented account numbers to Cin7 Core line account codes so bills post to valid accounts.
• •Authenticate GP with Windows credentials and Cin7 Core with its account ID and application key headers.
• •Poll GP by ModifiedDate and consume Cin7 Core purchase webhooks, with retries and a full audit trail.

Questions

Which direction does data move between Microsoft Dynamics GP and Cin7?

Vendors and items move from Microsoft Dynamics GP into Cin7 Core, while purchase invoices and goods receipts move from Cin7 Core back into GP as payables transactions. GL account codes are mapped in both directions to keep postings valid. The Cin7 Core chart of accounts is read-only through its API, so GP stays the system of record for the general ledger.

How does the integration handle the fact that Dynamics GP has no webhooks?

Microsoft Dynamics GP has no webhook or event system, so ml-connector polls GP vendor and item list endpoints filtered on ModifiedDate on a schedule you set. On the Cin7 Core side it does subscribe to Automation webhooks for purchase events, which it uses as a trigger to re-read the record over the API. This keeps both systems aligned without depending on a push from GP.

What does ml-connector need to reach an on-premises GP server?

GP runs on the customer's own Windows Server with no cloud endpoint, so the SBA REST or SOAP Web Services port must be reachable over HTTPS, either through the firewall or via a local agent inside the network. ml-connector authenticates with a dedicated Windows domain account mapped to a GP user, since GP uses no OAuth or API keys. Writes target unposted work transactions in an open fiscal period, as posted records are read-only through the API.