SYSPRO and BambooHR integration

What moves between them

The main flow moves from BambooHR into SYSPRO. Employee records, employment status, and compensation data flow from BambooHR into SYSPRO as new hires, status changes, and compensation updates occur. ml-connector polls BambooHR for changes on a regular schedule (typically 15-minute intervals) and writes employee master updates to SYSPRO using e.net Business Objects. BambooHR does not receive writes from SYSPRO in this direction. Reference data such as job codes, departments, and cost centers are mapped so that employee records in SYSPRO include the correct department and cost center for reporting and allocation.

How ml-connector handles it

ml-connector stores BambooHR OAuth credentials encrypted and uses the refresh token to obtain new access tokens when they expire. On the SYSPRO side it accepts the customer's server URL and operator credentials, logs in to obtain a session token, and uses that token on all e.net Business Objects calls. Because SYSPRO has no webhooks, ml-connector polls BambooHR for employee updates on a schedule tied to your hire/termination calendar rather than waiting for a push. It maps BambooHR job codes and departments to SYSPRO cost centers and department IDs before writing, so employee records land on valid SYSPRO dimensions. BambooHR rate limits are not published but return 503 Service Unavailable with an optional Retry-After header, so ml-connector backs off and retries. Session tokens expire on logoff or timeout, so ml-connector refreshes the SYSPRO session proactively before expiry. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized contract manufacturer runs SYSPRO for production, procurement, and cost tracking across three plants and a shared services office. They use BambooHR for payroll, benefits, and employee records. Before the integration, the operations team manually updated headcount and cost center assignments in SYSPRO when BambooHR reports showed new hires or job transfers, creating delays and mismatches in labor cost allocation. New hires sometimes assigned to wrong cost centers, and terminations stayed in SYSPRO until someone ran a report and cleaned them up manually. With SYSPRO and BambooHR connected, employee changes flow in automatically from BambooHR to SYSPRO. Headcount stays accurate, cost center assignments update when BambooHR job info changes, and labor cost reporting at month-end close reflects current staffing without rework.

What you can do

• •Sync new hires, terminations, and employment status changes from BambooHR into SYSPRO employee master records.
• •Map BambooHR job codes and departments to SYSPRO cost centers and department IDs automatically.
• •Refresh OAuth access tokens when they expire so polling runs continuously without manual intervention.
• •Handle SYSPRO session token expiry and re-authenticate proactively before tokens time out.
• •Poll BambooHR on a schedule tied to your hiring and payroll cycles, with retries and a full audit trail on every record.

Questions

Which direction does data move between SYSPRO and BambooHR?

The main flow is from BambooHR into SYSPRO. Employee records, employment status, compensation, and job information flow from BambooHR into SYSPRO. SYSPRO does not write employee data back to BambooHR, so it is a one-directional feed. Reference data such as job codes and departments are aligned so SYSPRO cost centers match BambooHR job assignments.

How does ml-connector handle the different authentication methods?

ml-connector stores BambooHR OAuth 2.0 credentials encrypted and uses the refresh token to renew access tokens when they expire. On the SYSPRO side, it uses operator credentials to log in and obtain a session token, then presents that token on every e.net Business Objects call. The session token is refreshed proactively before expiry to avoid logoff timeouts.

How does ml-connector work around SYSPRO's lack of webhooks?

ml-connector polls BambooHR on a schedule you control, typically every 15 minutes, to check for new hires, status changes, and compensation updates. It stores the timestamp of the last successful poll and requests only changes since that time, reducing API load. When SYSPRO receives employee updates, it validates that the job code and department map to existing cost centers before writing.