Pull HCSS time cards into Miter to process payroll

Once a time card successfully syncs from HCSS into Miter, HCSS marks it as “set to payroll” and the integration filters it out of future syncs — you cannot re-sync it through the integration after that point. If a foreman corrects hours in HCSS after the time card has already synced, those changes will not automatically carry over to Miter and must be made manually. To avoid this situation, Miter offers a configuration setting that adds an extra approval step: you can require time cards to be both approved and accepted in HCSS before they become eligible to sync. This gives your team a window to review and revise time cards in HCSS before they lock in Miter. If you do need to re-pull a time card that was already synced, there is a setting to include time cards already sent to payroll in the sync, but it should be turned off immediately after use to avoid re-fetching all historical records.

Yes. HCSS uses Business Units to represent different legal entities, and Miter maps each HCSS Business Unit to a corresponding Miter company. If you operate multiple entities, each one gets its own integration connection in Miter, keeping payroll and field data separated by entity while flowing through the same integration. The HCSS Marketplace authorization only needs to happen once and applies to all entities — you do not need to re-authorize for each company. After that, you configure each Miter company individually by selecting the appropriate HCSS Business Unit during setup. Multi-entity support is available, though contractors with more complex entity structures may want to coordinate with Miter during initial setup to make sure each connection is configured correctly.

Yes. The integration is designed to carry classification data through the full workflow. Pay classes sync from Miter to HCSS, and when time cards sync from HCSS back into Miter, the pay class on the time card maps to a classification override on the Miter timesheet. This means whatever classification is assigned in HCSS is what Miter uses when processing payroll. For certified payroll reporting, the setup happens in Miter: you enable certified payroll on the job, assign prevailing wage classifications to your team members, and Miter handles the CPR generation from there. Best practice is to enable certified payroll on a job before processing any timesheets so all earnings are captured with the correct classifications from the start. If team members clock time before classifications are assigned, those timesheets will be paid without a classification and will not appear on certified payroll reports.

Setup requires steps in both HCSS and Miter. Start in the HCSS Marketplace: navigate to the Miter app and approve the permissions that allow Miter to retrieve data on your behalf. This authorization only needs to happen once and covers all entities. Next, go to Company > Integrations in Miter, find the HCSS integration, and click “Set Up.” This takes you to the HCSS login page, where you log in to your HCSS account and grant Miter permission to retrieve data on your behalf. Once connected, you select the HCSS Business Unit that corresponds to your Miter company. From there, you configure which data dimensions to sync and whether to enable daily syncs for each. The connection itself is self-serve and does not require Miter support involvement, though most teams work through initial sync configuration and testing with their Miter implementation contact.

When cost codes sync from HCSS into Miter, Miter first checks whether an activity with the same cost code already exists. If a match is found, Miter updates or reuses that activity rather than creating a duplicate. If no match is found, Miter creates a new activity. The key decision during setup is whether those activities come in as job-specific (available only on the job they belong to) or company-level (available across all jobs). HCSS treats cost codes as project-level entities, while Miter supports both job-specific and company-level activities. A config setting exists specifically for HCSS to force all cost codes to sync as job-specific activities — useful when the same cost code is reused across jobs with different meanings. Without that setting, Miter defaults to creating company-level activities when the same cost code appears on more than one job. If a time card references a cost code that has not been synced to Miter as an activity — or that exists in Miter but is not linked to the specific job on the time card — the timesheet sync will fail. Error messages identify the exact missing dependencies: the specific cost codes, team member IDs, and pay classes blocking the sync, so your team knows exactly what to resolve before payroll runs.