Connect BambooHR and Miter for construction payroll

When a termination date is entered in BambooHR, that date syncs to Miter automatically. Miter uses the termination date to move the employee to dismissed status, removing them from active payroll. This means you don’t have to manually update Miter every time someone leaves, which reduces the risk of running payroll for a worker who is no longer active. Note that any final pay run will still need to be initiated separately by your payroll admin in Miter — termination sync does not automatically trigger a final paycheck.

Pay rate changes in BambooHR sync to Miter going forward. If a rate change comes in after a payroll run has already been submitted, it will apply to the next run. If your integration is configured to pull full pay rate history from BambooHR, you’ll have a record to reference if a retroactive correction is needed — confirm this setting with your implementation team, as it is a configurable option and not enabled by default. Always confirm your payroll cutoff timing with your Miter implementation contact to avoid mid-cycle rate discrepancies.

Multi-state payroll is supported, and home location data syncs from BambooHR to Miter as the employee’s address, which helps inform tax jurisdiction assignments. If your organization uses multiple legal entities or operates across multiple states, talk to your Miter implementation team before setup. Multi-entity configurations may require additional mapping to ensure employees from each entity sync to the correct payroll entity in Miter, and the right approach will depend on how your org is structured.

Miter uses employee identifiers — including employee number — to match existing records during the initial sync. If an employee already exists in Miter, the integration will map the BambooHR record to the existing profile rather than creating a duplicate. Your Miter implementation team will walk you through the matching logic during onboarding to make sure existing employee records are handled cleanly before the integration goes live.

The integration has two built-in configuration options: whether to auto-enroll employees in payroll when importing from BambooHR, and whether to pull full pay rate history from BambooHR to overwrite the pay rate history stored in Miter. Beyond those two settings, the standard integration syncs the full set of supported fields for all active employees. If you have specific employees or data types you need to exclude, contact your Miter implementation team to understand what options may be available — not all customization is supported out of the box, and some edge cases may require a workaround or manual handling.

Incomplete records in BambooHR can result in missing data in Miter. Fields like pay rate and employee number are essential for payroll to run correctly — if those are missing, payroll processing may be affected. Keep BambooHR records as complete as possible before activating the integration, and review your employee records in Miter after the initial sync to catch any gaps before your first payroll run.

Setup time varies depending on the size of your workforce and how your BambooHR data is structured. Most customers complete the integration setup during their standard Miter onboarding process. Your implementation team will handle the API connection, walk through the field mapping, and run a test sync to confirm data is flowing correctly before you go live. If you have complex org structures or multiple entities, plan for additional configuration time.