Epicor Kinetic and Rippling integration

What moves between them

The main flow is Rippling into Epicor Kinetic. Employee records and department assignments flow from Rippling into Epicor Kinetic to keep the ERP headcount and cost center dimensions aligned. When an employee is hired, terminated, or moved to a different department in Rippling, ml-connector reads that change and updates or creates the corresponding employee record and cost center assignment in Epicor Kinetic. The sync runs on a schedule you define, such as daily or after each payroll run, to keep the two systems in agreement.

How ml-connector handles it

ml-connector stores both credential sets encrypted and uses OAuth2 on the Epicor Kinetic side, refreshing the bearer token before expiry (typically ~1 hour). On the Rippling side it uses either API Key or OAuth2 depending on your authentication method, and polls the employees endpoint with an updated_at filter to detect changes since the last run. Because neither system offers real-time webhooks for direct API-key integrations, ml-connector polls on a schedule and uses OData filters (UpdatedOn on Epicor Kinetic, updated_at on Rippling) to retrieve only records that have changed. Employee records are matched on unique identifiers and cost centers are validated in Epicor Kinetic before the update is written, so invalid dimension assignments are caught before they post. All records carry a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized contract manufacturer runs Epicor Kinetic ERP for finance and operations and uses Rippling for payroll and employee benefits across multiple locations. Before the integration, the finance team manually re-entered new hires and job transfers from Rippling into Epicor Kinetic each week, reconciling employee counts at month-end by hand. With Epicor Kinetic and Rippling connected, new hires and transfers flow automatically from Rippling into Epicor Kinetic, cost centers are validated and updated without re-keying, and the ERP headcount is always in sync with the payroll system. The manual reconciliation step at month-end is eliminated, and the finance team catches discrepancies in real time rather than at close.

What you can do

• •Sync employee records from Rippling into Epicor Kinetic, keeping headcount and employee master data aligned.
• •Map Rippling departments and cost centers to Epicor Kinetic GL dimensions so labor costs allocate to the correct accounts.
• •Authenticate Epicor Kinetic with OAuth2 or Basic Auth and Rippling with API Key or OAuth2.
• •Poll both systems on a schedule you define, with change detection on date fields and a full audit trail on every record.
• •Validate cost center dimensions in Epicor Kinetic before updating employee records to prevent invalid allocations.

Questions

Which direction does data move between Epicor Kinetic and Rippling?

The main flow is Rippling into Epicor Kinetic. Employee records, department assignments, and cost center dimensions flow from Rippling into Epicor Kinetic to keep the ERP headcount and labor costing aligned. Compensation and payroll data flow one direction only, so ml-connector does not write payroll entries back into Rippling.

How does the integration handle Epicor Kinetic's OAuth2 tokens and lack of webhooks?

ml-connector uses OAuth2 client credentials to authenticate to Epicor Kinetic and refreshes the bearer token before expiry (approximately 1 hour). Because Epicor Kinetic has no native webhooks, ml-connector polls the employee and cost center endpoints using OData filters on the UpdatedOn field to retrieve only records changed since the last sync, so the sync runs on a schedule rather than waiting for a push.

What happens if an employee record in Rippling maps to an invalid cost center in Epicor Kinetic?

ml-connector validates the cost center against Epicor Kinetic before updating the employee record. If the dimension does not exist or is inactive, the record is flagged in the audit trail and the update is not posted, so invalid allocations do not reach your general ledger. The record can be replayed once the cost center is corrected in Epicor Kinetic.