Acumatica and BambooHR integration

What moves between them

The main flow runs from BambooHR into Acumatica. ml-connector reads new hires, job and department changes, and terminations from BambooHR and writes them into Acumatica Employee records so ERP headcount reflects the HR system of record. BambooHR departments and divisions are mapped to Acumatica departments, and that org reference data is aligned so every synced employee lands on a valid Acumatica department code. Because BambooHR has no finance entities, no vendors, invoices, or GL data move on this connection. Acumatica employee writes are limited in scope, so the sync updates the supported employee fields and respects what the ERP allows.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the BambooHR side it runs the OAuth authorization code flow per customer subdomain, since the authorize and token URLs are subdomain-scoped rather than global, and it refreshes the one-hour access token using the offline_access refresh token. On the Acumatica side it accepts the full instance URL and pins the endpoint version so requests do not 404 on a version mismatch, and it wraps every field value in the value object that the Contract-Based REST API requires. Departments and divisions are mapped first, so each employee write references an Acumatica department that already exists. BambooHR can push employee.created, updated, and deleted webhooks, and ml-connector verifies the SHA-256 HMAC signature with a timing-safe compare, then calls GET on that employee to pull current fields, since the webhook body is intentionally lightweight. Where webhooks are not enabled, it polls BambooHR and reads Acumatica changes on the LastModifiedDateTime filter with a stored high-water mark. Acumatica returns HTTP 429 when the per-minute request count nears the license limit, so ml-connector backs off with jitter and retries, and BambooHR throttling returns 503 with a Retry-After header that it honors. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized professional services firm of about 400 staff runs Acumatica for finance and project accounting and uses BambooHR as its HR system of record. Before the integration, HR entered each new hire, transfer, and termination in BambooHR, then someone re-keyed the same changes into Acumatica so project costing and reporting used the right people and departments, and the two lists drifted apart between updates. With Acumatica and BambooHR connected, a new hire or department change in BambooHR flows into the matching Acumatica Employee record automatically, mapped to the correct department, and terminations are reflected promptly. The duplicate data entry is gone and the ERP headcount stays current with HR.

What you can do

• •Sync new hires from BambooHR into Acumatica Employee records so ERP headcount matches the HR system of record.
• •Push BambooHR role and department changes into Acumatica and reflect terminations promptly.
• •Map BambooHR departments and divisions to Acumatica departments so synced employees land on valid org codes.
• •Authenticate BambooHR with subdomain-scoped OAuth 2.0 and Acumatica with its tenant login and pinned endpoint version.
• •Verify BambooHR webhook signatures, poll where webhooks are off, and retry with a full audit trail on every record.

Questions

Which direction does data move between Acumatica and BambooHR?

The main flow is BambooHR into Acumatica. New hires, job and department changes, and terminations move from BambooHR into Acumatica Employee records, and departments and divisions are mapped so people land on valid Acumatica org codes. BambooHR has no vendors, invoices, or GL accounts, so no finance data moves on this connection.

Does the integration use BambooHR webhooks or polling?

It can use either. BambooHR signs employee.created, updated, and deleted webhooks with SHA-256 HMAC, which ml-connector verifies with a timing-safe compare before fetching the current employee with a follow-up GET, since the webhook body is intentionally lightweight. Where webhooks are not enabled, it polls BambooHR on a schedule and reads Acumatica changes on the LastModifiedDateTime filter.

How does ml-connector handle Acumatica's version-locked endpoints and tenant URL?

ml-connector accepts the full Acumatica instance URL per customer and pins the endpoint version, because a version that does not match the running ERP release returns HTTP 404 immediately. It also wraps every field value in the value object that the Contract-Based REST API requires, so writes are accepted rather than rejected as bad requests.