SYSPRO and Rippling integration

What moves between them

The main flow reads from Rippling into SYSPRO. Employee records, departments, and accounting dimensions from Rippling are mapped to SYSPRO's cost centers and GL dimensions so payroll can be allocated correctly. Cost center and department reference data is read from SYSPRO via OData polling and kept aligned in Rippling. Payroll GL postings calculated in Rippling are mapped and posted into SYSPRO's general ledger on a schedule tied to your payroll calendar. SYSPRO provides no push mechanism, so ml-connector polls OData tables for new GL accounts and cost centers every 10-15 minutes.

How ml-connector handles it

ml-connector accepts the SYSPRO server URL and login credentials for e.net and OData separately, since OData uses HTTP Basic Auth and e.net uses session tokens. It refreshes the e.net session token before expiry and maintains the OData HTTP Basic auth on each call. Rippling authentication uses OAuth2 bearer tokens or a stored API key depending on the integration mode. ml-connector polls SYSPRO's OData GenMaster and GenBalance tables with a $filter on PostDate to detect new GL accounts and balances, and polls Rippling's employee list with an updated_at filter to detect hires, terminations, and changes. Department and cost center mapping is stored encrypted per customer, so payroll lines post to valid SYSPRO dimensions. Because SYSPRO cloud prohibits direct database access, all reads go through OData or e.net REST, and large payloads use SOAP/NetTcp to avoid REST URL length limits. Every GL posting carries source data and timestamp for audit and replay if a downstream reference lookup fails.

A real-world example

A regional distributor with 200 employees runs SYSPRO for procurement, inventory, and general ledger, and Rippling for payroll across three regional warehouses and a head office. Previously, payroll was processed in Rippling but labor costs were re-entered into SYSPRO's GL by the accounting team every pay cycle, and warehouse cost centers had to be maintained manually in both systems. With SYSPRO and Rippling connected, Rippling feeds new hires, terminations, and department changes directly to SYSPRO, the payroll cost allocation posts to the correct SYSPRO cost center per warehouse without re-entry, and the accounting team no longer spends hours reconciling GL balances to payroll registers. Month-end close is faster because labor cost allocation is already correct.

What you can do

• •Sync Rippling employees, departments, and compensation into SYSPRO cost centers and GL dimensions on payroll cycles.
• •Poll SYSPRO OData for new GL accounts and cost centers every 10-15 minutes and keep Rippling accounting dimensions current.
• •Map Rippling payroll cost allocations to SYSPRO's general ledger accounts and post them on a schedule you control.
• •Handle SYSPRO's session token auth and OData Basic Auth simultaneously, plus Rippling OAuth2 or API Key Bearer Token.
• •Track all GL postings with full audit, timestamp, and source data for compliance and replay if a reference dimension is not found.

Questions

How does ml-connector handle SYSPRO's lack of native webhooks?

ml-connector polls SYSPRO's OData tables with timestamp filters on PostDate and InvoiceDate every 10-15 minutes for manufacturing and financial data. SYSPRO has no outbound webhook system, so polling is the supported method to detect changes. The interval is configurable based on your payroll calendar.

What authentication does ml-connector use for each system?

SYSPRO requires two auth paths: e.net Business Objects uses a session token obtained from login, and OData uses HTTP Basic Auth with operator code and OData password. Rippling uses either OAuth2 Bearer Token for App Shop integrations or an API Key Bearer Token for direct server-to-server connections. ml-connector stores all credentials encrypted and refreshes tokens before expiry.

Can ml-connector write payroll data back into SYSPRO's general ledger?

Yes. ml-connector reads payroll cost allocations from Rippling, maps them to SYSPRO cost centers and GL accounts via OData, and posts GL transactions using e.net Business Objects REST or SOAP depending on payload size. SYSPRO's cloud product prohibits direct database writes, so all updates go through the supported API layers.