Sage 50 and Deel integration

What moves between them

Employee records flow from Deel into Sage 50 on hire and termination. When Deel generates payroll invoices for contractor or EOR services, ml-connector polls the Deel invoices endpoint and writes matching GL journal entries into Sage 50 allocated to the appropriate cost center or GL account. The integration polls Deel on a schedule independent of Sage 50 since the desktop system cannot receive inbound webhooks. Employee terminations trigger a pause in Deel invoice reads for that person to avoid stale postings after offboarding.

How ml-connector handles it

ml-connector runs a polling service that connects to Sage 50 using the Windows SDK with stored encrypted credentials (username, password, company path, and ApplicationID for the US edition or DataPath for the UK edition). It polls Deel's REST API using OAuth2 bearer tokens, refreshing when a 401 response is received. On each sync interval, it queries Deel for new contracts and updates, writes matching employee records into Sage 50 via the SDK, then reads Deel invoices and payroll costs and writes them as GL journal entries in Sage 50 with automatic GL account mapping. Since Sage 50 is Windows-local and cannot run webhooks, ml-connector relies on Deel's REST endpoints and does not consume Deel webhooks. The polling interval is configurable; most payroll use cases sync daily or on-demand after payroll runs. All synced records are tracked to prevent duplicate GL entries, and if a downstream GL write fails, the record is flagged for retry on the next sync cycle.

A real-world example

A mid-sized staffing and services firm uses Sage 50 on Windows for accounting and payroll processing, and Deel for managing a global contractor and EOR workforce across five countries. Before the integration, the finance team manually entered contractor names into Sage 50 after onboarding in Deel, then exported Deel invoices and re-keyed them into GL each month, creating delays and reconciliation friction. With Sage 50 and Deel connected, each new Deel contract syncs to Sage 50 automatically on hire, and monthly Deel invoices flow directly into GL allocated to the cost center for each country. Month-end close is faster, and duplicate entries are eliminated.

What you can do

• •Sync new Deel contracts and terminated employees into Sage 50 employee and vendor records on a schedule you control.
• •Write Deel payroll invoices and contractor costs as GL journal entries in Sage 50, mapped to the correct GL accounts and cost centers.
• •Store Deel OAuth bearer tokens securely and refresh automatically when access tokens expire without blocking downstream syncs.
• •Authenticate to the Sage 50 Windows SDK using stored credentials and handle both US .NET SDK and UK SDO COM editions.
• •Poll Deel on a fixed interval with tracking to prevent duplicate GL entries, and retry failed GL writes on the next sync cycle.

Questions

How does ml-connector authenticate to Sage 50 when it is desktop-only and requires a Windows SDK?

ml-connector stores the Windows SDK credentials encrypted (username, password, company path, and ApplicationID or DataPath depending on edition) and runs a polling service on the same Windows machine or LAN where Sage 50 data files live. It connects via the .NET SDK or SDO COM layer and writes records directly, just as if a local integration user were making the changes.

Since Deel sends webhooks in real time but Sage 50 cannot receive them, how does the sync work?

ml-connector polls Deel's REST API on a fixed schedule (commonly daily or after payroll runs) instead of consuming webhooks. This approach fits Sage 50's constraint that it is desktop-only and cannot accept inbound callbacks. The polling interval is configurable and does not require any setup on the Deel side beyond API token creation.

How are Deel invoices and contractor costs posted into Sage 50's general ledger?

ml-connector reads Deel payroll invoices and contractor costs via the REST API, maps them to GL accounts and cost centers based on rules you configure, and writes GL journal entries into Sage 50 using the SDK. Each entry is tracked to prevent duplicates, and if a GL write fails, the record is queued for retry on the next sync cycle.