Sage 100 and Deel integration

What moves between them

Employee cost data, contractor invoices, and payslips move from Deel into Sage 100. ml-connector polls Deel for contract and payroll-input records on a cadence aligned with your payroll runs and can also receive webhook events where they are enabled. GL postings for labor costs and contractor fees are read from Deel and mapped into corresponding GL accounts and cost centers in Sage 100. Worker and contractor reference data such as cost allocation and department keeps the two systems aligned. Data moves one direction: Deel is the source of payroll truth; Sage 100 receives the posted GL entries. Contractor invoices flow as separate AP records.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Sage 100 side it accepts your local agent URL and SOAP credentials, polling GL accounts and AP invoices on a schedule you define; on high-frequency writes it backs off on COM record-lock conflicts. On the Deel side it uses the bearer token or OAuth2 credentials you provide, refreshing the token when expiry approaches, and listens for webhook events where enabled so it can react immediately to employee or contractor changes. Cost centers and departments are mapped first so every payroll GL posting lands on a valid Sage 100 dimension. Idempotency keys are used on every write so a failed network call can be replayed without duplication. GL postings reference your existing GL accounts and are read-only from Deel, so ml-connector never writes financial entries back into payroll. Every record carries a full audit trail.

A real-world example

A mid-sized professional services firm runs Sage 100 on-premises for accounting and AP, and uses Deel for global payroll, contractors, and compliance across five countries. Before the integration, finance manually extracted payroll registers from Deel each month, allocated labor costs to projects and cost centers by hand, and entered the GL postings into Sage 100 by hand. They also received contractor invoices from Deel and re-keyed those into AP. With Sage 100 and Deel connected, labor cost postings flow automatically each payroll period, contractors invoices land directly in AP, and the chart of accounts stays current with actual headcount and cost allocations. Month-end GL reconciliation now starts with payroll costs already posted, and the re-keying step is gone.

What you can do

• •Read employee cost data, payslips, and contractor invoices from Deel and post labor GL entries into Sage 100, allocated to cost centers and GL accounts.
• •Map Deel contract and employee records to Sage 100 vendors and cost allocations so invoices and payroll postings land on valid dimensions.
• •Authenticate Sage 100 via stateless SOAP credentials and your local BOI agent, and Deel via bearer token or OAuth2, with token refresh and expiry tracking.
• •Poll Sage 100 AP invoices, GL accounts, and vendors on a schedule you control, with exponential backoff on COM record-locking conflicts.
• •Receive real-time webhook events from Deel for employee changes and contract events, and replay any failed GL posting or contractor invoice write with a full audit trail.

Questions

Does ml-connector work with Sage 100 SOAP Web Services or do I need the local BOI agent?

For full AP, GL, and vendor access, the local BOI agent is required since SOAP Web Services covers only AR and Sales Orders. The agent wraps the COM layer on your Sage 100 server and exposes it via API key or mTLS. ml-connector polls the agent endpoint you provide and handles the stateless username-password SOAP calls or agent-layer authentication.

How does ml-connector handle Sage 100 COM record locking on high-frequency writes?

Sage 100 COM enforces record-locking limits on concurrent writes. ml-connector detects lock conflicts and retries with exponential backoff and jitter so peak payroll periods do not trigger timeout failures. It tracks lock patterns in the audit log so you can see where contention occurs.

Can ml-connector receive Deel events in real-time or must it poll?

ml-connector can use Deel webhooks to react immediately to employee hires, terminations, and contractor contract changes. It also polls on a schedule you control as a fallback, so you get both real-time responsiveness and guaranteed catch-up if a webhook is missed.