QuickBooks Online and BambooHR integration

What moves between them

Employee records and job information flow from BambooHR into QuickBooks Online on a webhook-driven schedule. When an employee is created, updated, or terminated in BambooHR, ml-connector receives the webhook event, fetches the full employee record, maps BambooHR fields to QB Employee entity attributes, and creates or updates the corresponding QB employee record. Compensation rates, job titles, and employment status flow the same direction so QB payroll records reflect the current state in BambooHR. Data does not flow back to BambooHR.

How ml-connector handles it

ml-connector stores OAuth2 credentials encrypted for both platforms and maintains a per-customer subdomain for BambooHR since the API requires a unique URL per company instance. It listens for BambooHR webhook events signed with SHA-256 HMAC and verifies the signature before processing. On Employee events, ml-connector fetches the full employee record from BambooHR, maps the job information and compensation data to QB Employee attributes, and posts the result to QB's REST API. If either OAuth token expires (QB at 1 hour, BambooHR at 1 hour), ml-connector refreshes the token transparently. When BambooHR returns 503 Service Unavailable (rate limiting), ml-connector backs off and retries. QB webhook payloads require a full entity fetch, so the integration also polls QB's CDC endpoint to detect any employee changes made outside the BambooHR flow, ensuring QB remains the source of truth for payroll-specific fields not managed by HR.

A real-world example

A mid-sized services firm runs QuickBooks Online for accounting and payroll, and BambooHR for employee records and benefits administration. Before the integration, HR completed each new hire in BambooHR, then notified the accounting team to manually create the employee record in QB and set payroll rates. Job title changes and terminations required back-and-forth emails and manual updates. With BambooHR and QB connected, each new hire created in BambooHR automatically appears in QB with job title and compensation already filled in, ready for the first payroll run. Terminations in BambooHR flag the QB employee for immediate deactivation, and title or rate changes sync without manual rework.

What you can do

• •Sync new employees from BambooHR into QuickBooks Online with job title and compensation pre-filled.
• •Automatically update QB employee records when job information or compensation changes in BambooHR.
• •Keep QB payroll employee roster in sync with BambooHR hires, terminations, and rehires.
• •Handle OAuth2 refresh for both platforms and verify BambooHR webhook signatures with SHA-256 HMAC.
• •Detect and retry on BambooHR rate-limiting 503 responses and poll QB's change data capture endpoint for payroll-specific changes.

Questions

What employee fields from BambooHR sync into QuickBooks Online?

Employee name, email, job title, department, employment status, and compensation rates (salary or hourly wage) flow from BambooHR to QB. BambooHR compensation is stored as versioned history, so ml-connector captures the current rate and maps it to QB's payroll field. QB employee records also include payroll-specific fields like tax W-4 data and direct deposit that remain QB-only and are not managed by the integration.

Does QuickBooks Online pull employee data back into BambooHR?

No. The integration is unidirectional: BambooHR is the source of truth for employee records and HR data. QB remains the source of truth for payroll-specific attributes and GL postings. Changes made directly in QB's employee records are not synced back to BambooHR.

How does the integration handle BambooHR's per-customer subdomain requirement and webhook signatures?

ml-connector stores the customer's BambooHR subdomain in the connection configuration and uses it to build the correct per-company API endpoint. BambooHR webhooks are signed with SHA-256 HMAC; ml-connector verifies the X-BambooHR-Signature header before processing any event to ensure the payload came from BambooHR.