Microsoft Dynamics GP and Deel integration

What moves between them

The main flows are Deel to GP for payroll and human resources. Payroll invoices and worker-invoice data flow from Deel into GP's payables and GL, mapped to vendor accounts and GL dimensions. Employee records and changes flow from Deel into GP to keep headcount and organizational structure aligned. Payroll inputs such as bonuses, deductions, and adjustments flow from GP into Deel via the API. GL postings from payroll are read-only in both directions. Reference data such as departments and cost centers is mapped in both directions so payroll allocations land on valid GP dimensions.

How ml-connector handles it

ml-connector stores Deel bearer tokens encrypted and presents them on every request to the Deel REST endpoint, handling OAuth2 token refresh at the 30-day expiry boundary. On the GP side it accepts the customer's on-premises SBA or SOAP URL and Windows domain credentials, using those credentials to authenticate each REST or SOAP call to poll for modified records. Because GP has no push mechanism, ml-connector polls on a schedule configured by the customer, typically aligned with the payroll calendar. Deel webhooks are also registered where available, allowing real-time employee status changes to trigger immediate pulls. When a GP posting is read-only or a GL entry conflicts with an existing account code, ml-connector logs the failure with full context so the records can be replayed after the downstream issue is fixed. Payroll adjustments destined for Deel are batched with idempotency keys to prevent duplicates across retries.

A real-world example

A mid-sized professional services firm runs Microsoft Dynamics GP on-premises for general ledger, payables, and payroll, and uses Deel to manage contractors and employees across five countries. Before the integration, the finance team exported payroll invoices from Deel each period and re-entered them into GP payables manually, then tracked employee data in a separate spreadsheet to reconcile headcount with GL salary accounts. With the integration, Deel invoices flow directly into GP payables mapped to the correct GL accounts, and employee records from Deel update automatically so the GL always reflects the current headcount and cost by department. The finance team no longer spends hours on manual reconciliation, and payroll-to-ledger tie-out happens on the day invoices are generated.

What you can do

• •Write payroll invoices and worker invoices from Deel into Microsoft Dynamics GP payables, mapped to the correct GL accounts.
• •Sync employee records, onboarding, and terminations from Deel into GP to keep headcount and organizational structure aligned.
• •Write payroll inputs such as bonuses and deductions from GP into Deel using the API with idempotency key deduplication.
• •Authenticate to GP using Windows Active Directory credentials via SBA REST or SOAP, and to Deel using bearer tokens with scope-based permissions.
• •Poll on a schedule tied to the payroll calendar with retries, webhook event ingestion, and a full audit trail on every record.

Questions

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

The main flows are Deel to GP. Payroll invoices, worker invoices, and employee records move from Deel into GP payables and HRIS. Payroll inputs such as bonuses and deductions move from GP into Deel. GL journal entries from payroll are read-only, so ml-connector does not write financial postings back into Deel.

How does ml-connector authenticate to GP when it runs on-premises with Windows authentication?

ml-connector accepts the customer's on-premises SBA or SOAP endpoint URL and a Windows domain account created by the customer with appropriate GP user roles. Each REST or SOAP call to GP presents those domain credentials through Windows Negotiate or NTLM authentication, encrypted in transit with the customer's SSL certificate. No cloud auth or API keys are required on the GP side.

Does the integration handle Deel webhooks, or does it only poll?

ml-connector supports both. It can receive Deel webhooks for real-time events such as employee creation, update, and termination, and verify webhook signatures using HMAC-SHA256. It also polls on a schedule for complete data syncs. Customers choose which approach fits their payroll calendar and operational needs.