Run payroll on BuildOps timesheets.

Yes. Timesheets and jobs sync from BuildOps into Miter via API. When a timesheet pulls into Miter, Miter automatically creates or updates the associated job, project, and phase, so hours land tied to the right work. BuildOps projects come into Miter as parent jobs, and BuildOps phases come in as sub-jobs underneath, which keeps multi-phase commercial work organized for payroll and job costing. Cost codes are matched to existing Miter activities, so you set those up once and they apply on every sync going forward.

Miter uses a combination of codes, IDs, and names to match incoming BuildOps data to existing records in Miter. For jobs, Miter matches on job code. For team members, it matches by ID. For activities, it matches by cost code. When a match is found, Miter updates the existing record rather than creating a new one. To avoid duplicates, treat BuildOps as the single source of truth for job and timesheet data. Running multiple integrations that sync the same record types simultaneously can result in duplicate records that require manual cleanup.

Yes. The integration uses a direct API connection between BuildOps and Miter, so timesheets and jobs flow through automatically with no file imports, exports, or manual reformatting. Syncs run on a daily schedule or on demand from the Miter dashboard.

If a timesheet is updated in BuildOps after it’s already synced, trigger a manual re-sync from the Miter dashboard to pull the latest data. Miter updates the existing timesheet record. Timesheets already in processing or paid status are protected from overwrites, so changes upstream in BuildOps can’t silently alter what your team has already approved or paid.

Yes. Miter supports multiple integrations running simultaneously. Many commercial contractors use BuildOps, Miter, and Sage Intacct together as a connected back-office stack. BuildOps handles field operations, service management, and project management. Miter handles payroll, HR, and compliance. Sage Intacct captures GL entries and financial reporting. The integrations also work together where it counts: BuildOps Intacct Class data, for example, flows through each timesheet into Miter, so your financial reporting stays clean across the stack.

Yes. You’ll need active BuildOps and Miter accounts before connecting. Reach out to your BuildOps representative for API credentials (Client ID, Client Secret, and Tenant ID), make sure employee IDs match between systems, and set up your Miter activities with cost codes that match BuildOps. If you run prevailing wage work, you’ll also set a default CPR project number in your Miter BuildOps configuration, since BuildOps doesn’t pass CPR number.

Yes. Jobs marked prevailing wage in BuildOps carry that status into Miter, and BuildOps labor rates and labor types match to your Miter Pay Rate Groups, applying the right union classification and rate to each timesheet. Certified payroll reports run on the actual hours your field team logged in BuildOps. One configuration note: BuildOps doesn’t pass CPR project numbers in the sync, so you’ll set a default CPR project number in your Miter configuration and update individual job CPR numbers afterward.