How does ml-connector handle the different authentication methods between Sage 300 and Deel?

Sage 300 uses HTTP Basic Auth with uppercase username and password; Deel uses bearer tokens or OAuth2. ml-connector maintains separate encrypted credential stores for each system and translates between them on every request. On the Sage 300 side it creates a dedicated web API user in Administrative Services; on the Deel side it refreshes OAuth2 tokens before they expire and handles bearer token rotation.

Which direction does data move between Sage 300 and Deel?

The main flow is Deel into Sage 300. Payroll invoices, employee cost allocations, and payslip data move from Deel into Sage 300 general ledger and vendor master. Sage 300 GL accounts and cost center dimensions are read-only to Deel, so ml-connector does not write financial entries back into the payroll system. Reference data such as cost centers can flow in both directions to keep the systems aligned.

How does ml-connector sync data if Sage 300 has no webhooks?

Sage 300 is pull-only, so ml-connector polls invoices, employee records, and cost data from Deel on a schedule tied to your payroll calendar. It can also receive real-time webhook events from Deel where enabled for critical events such as employee termination or invoice posting, combining webhooks with scheduled polling to balance latency and reliability.

Sage 300Deel

Sage 300 and Deel integration

Sage 300 runs accounting and procurement. Deel runs global payroll and HRIS. Connecting the two keeps your labor costs reconciled with your general ledger and eliminates manual re-entry of payroll expenses. Deel invoices and employee cost allocations post directly into Sage 300 on your payroll calendar, mapped to the correct GL accounts and vendors. Payroll changes in Deel stay synchronized with your Sage 300 vendor master and cost dimensions, so month-end close starts with labor accounts already balanced.

How Sage 300 works

Sage 300 is an on-premise Windows IIS-hosted ERP system that exposes accounts payable, accounts receivable, general ledger, purchase orders, and inventory through REST and OData endpoints. Authentication uses HTTP Basic Auth with uppercase username and password sent in every request. The API requires a dedicated web API user account created in Administrative Services with Web API security group privileges; the built-in Admin account cannot authenticate. Sage 300 has no webhooks or push notifications, so all data synchronization is pull-based via polling with OData filters and pagination parameters. Large volumes of API calls can trigger IIS AppPool timeouts, so polling must account for connection limits and batch sizes.

How Deel works

Deel is a cloud-hosted global payroll and workforce platform that exposes employee contracts, people records, invoices, payslips, and payroll inputs through a REST API authenticated with bearer tokens (Organization Token) or OAuth2 Authorization Code Grant. OAuth2 access tokens expire after 30 days and refresh tokens after 90 days. Deel supports both real-time webhooks for events such as contract.created and hris.employee.terminated, and direct API polling. The API enforces rate limits and returns HTTP 429 Too Many Requests with a Retry-After header; webhook payloads require HMAC-SHA256 signature verification before processing. Deel is payroll and HRIS only, with no vendor master or purchase order capability, so GL account codes must be embedded in invoice and cost allocation payloads.

What moves between them

The main flow runs from Deel into Sage 300. After each payroll run, ml-connector reads Deel invoices and employee cost allocations, maps them to Sage 300 GL accounts and vendor records, and posts labor cost journals into Sage 300's general ledger. Worker records from Deel flow one way into Sage 300 vendor master to keep headcount in sync. Reference data such as departments and cost centers is aligned so payroll expense allocations land on the correct GL accounts. Invoices are read-only in Deel, so ml-connector never writes payment confirmations back to the payroll system.

How ml-connector handles it

ml-connector stores both credential sets encrypted and translates between the two authentication schemes: Sage 300 Basic Auth (username and password, uppercase) and Deel bearer tokens (Organization Token or OAuth2 with 30-day expiry). On the Sage 300 side, it uses a dedicated web API user account created in Administrative Services and respects IIS AppPool connection limits by batching large polling cycles and retrying on timeout. On the Deel side, it polls invoices and cost allocations via REST, handles HTTP 429 rate limits with exponential backoff, and can also receive Deel webhook events where enabled for lower latency on critical payroll changes. GL accounts and vendor codes are validated first in Sage 300 before posting, so every labor cost journal lands on an existing account. Every record carries an audit trail and can be replayed if a posting fails, so payroll corrections and adjustments do not cause gaps in the ledger.

A real-world example

A mid-sized staffing company uses Sage 300 on-premise for accounting and procurement, and manages payroll and contractors globally through Deel. Before the integration, the finance team exported payroll registers and contractor invoices from Deel weekly and manually re-keyed the labor cost totals into Sage 300's general ledger, a process that took four to six hours and often resulted in posting errors and month-end reconciliation delays. With Sage 300 and Deel connected, contractor invoices and employee cost allocations post automatically into Sage 300 on the payroll calendar. The manual re-keying is eliminated, and the labor accounts are always reconciled, turning month-end close into a verification step instead of a fire-fighting session.

What you can do

Post Deel employee cost allocations into Sage 300 general ledger on your payroll calendar, mapped to the correct GL accounts and cost centers.
Sync Deel contractor and employee records into Sage 300 vendor master to keep headcount and contractor status aligned.
Authenticate Sage 300 with HTTP Basic Auth and Deel with bearer token or OAuth2, bridging the two authentication models.
Handle Sage 300 IIS AppPool timeouts and Deel rate limits with smart batching, exponential backoff, and transparent retries.
Track every payroll posting and invoice sync in a full audit trail with the ability to replay failed records without duplication.

Questions

How does ml-connector handle the different authentication methods between Sage 300 and Deel?: Sage 300 uses HTTP Basic Auth with uppercase username and password; Deel uses bearer tokens or OAuth2. ml-connector maintains separate encrypted credential stores for each system and translates between them on every request. On the Sage 300 side it creates a dedicated web API user in Administrative Services; on the Deel side it refreshes OAuth2 tokens before they expire and handles bearer token rotation.
Which direction does data move between Sage 300 and Deel?: The main flow is Deel into Sage 300. Payroll invoices, employee cost allocations, and payslip data move from Deel into Sage 300 general ledger and vendor master. Sage 300 GL accounts and cost center dimensions are read-only to Deel, so ml-connector does not write financial entries back into the payroll system. Reference data such as cost centers can flow in both directions to keep the systems aligned.
How does ml-connector sync data if Sage 300 has no webhooks?: Sage 300 is pull-only, so ml-connector polls invoices, employee records, and cost data from Deel on a schedule tied to your payroll calendar. It can also receive real-time webhook events from Deel where enabled for critical events such as employee termination or invoice posting, combining webhooks with scheduled polling to balance latency and reliability.

Connect Sage 300 and Deel

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started