Sync payroll and job costing with CMiC

Yes. The sync supports multi-entity setups, so contractors running several companies or divisions in CMiC can map jobs, GL accounts, and departments to the correct entity in Miter. This matters for contractors who separate union and open-shop work, or run distinct legal entities by region, since it keeps job costing and payroll segregated the same way CMiC already segregates them.

Updates to jobs, cost codes, or budgets in CMiC flow into Miter on the next sync, so changes made to a project’s structure carry through without someone manually editing the corresponding record in Miter. If a cost code gets closed out or a budget changes mid-project, that update reaches Miter the same way the original setup did.

The sync matches records using unique identifiers from CMiC, like job number and employee ID, so it updates existing records rather than creating duplicates. If a conflict comes up — such as a trade classification that doesn’t have a matching Miter trade code — the sync flags it so someone can resolve the mapping instead of guessing at a default.

No. Jobs, cost codes, phases, and budgets are set up once in CMiC and sync into Miter as activities and job records. Field teams clock time against the synced activities in Miter without anyone needing to duplicate that setup work in a second system.

Yes. Miter handles certified payroll, prevailing wage, and union rules on its own, using pay type, rate, trade classification, and union status data that syncs between Miter and CMiC. Payroll runs then post back to CMiC as JC transactions, so compliance calculations stay in Miter while the job costing output lands where CMiC finance teams expect it.