Introduction
On a Thursday afternoon in the middle of a building addition, the awarding agency’s compliance officer emails your payroll administrator. She needs the certified payroll for weeks nine through nineteen, the fringe benefit calculation for two apprentices who moved between classifications partway through, and the backup showing which hours were charged to the covered project rather than to the private work the same crew ran on Fridays. Nothing in that request is unreasonable. The difficulty is where the answer lives: payroll in one system, job costs in another, signed timesheets in a shared drive, and the classification call in a foreman’s memory.
That is the shape of most compliance trouble in construction. It looks like paperwork, but underneath it is a labour-data problem. Certified payroll, prevailing wage, union reporting, and audit requests are all variations on a single question, asked in different formats by different parties. When the record needed to answer it has to be reassembled after the fact from systems that do not share it, reporting gets slow and the proof gets fragile. Accordingly, the contractors who find compliance manageable are rarely the ones with the most disciplined filing habits. They are the ones whose payroll, job costing, and general ledger already hold the same labour records.
This guide is written for the CFO, controller, payroll administrator, and owner at a mechanical, electrical, plumbing, fire and sprinkler, roofing, concrete, or civil contractor doing public, prevailing-wage, or union work in North America. It covers labour compliance specifically: certified payroll and prevailing wage, union and multi-agreement payroll, payroll audit readiness, and multi-entity obligations. To be clear about what it does not cover, jobsite safety and OSHA compliance is a separate discipline with its own tools, and subcontractor compliance documents such as insurance certificates and lien waivers belong to subcontractor management rather than payroll.
If you are evaluating your accounting platform more broadly, the Construction Accounting Guide covers the wider system requirements that this guide assumes.
The Problem: Compliance Proven After the Fact
Compliance rarely fails because a contractor decided to underpay somebody. It fails on proof and on timing. The obligations themselves are stable and reasonably well understood: pay the right rate for the right classification, report on schedule, and be able to show your work afterward. The last part is what breaks. When the records that would prove compliance sit in systems that were never designed to agree with each other, every filing turns into a small assembly project and every records request turns into an interruption nobody can plan around.
🚩 The certified payroll that does not agree with the job cost report
Hours are entered once for payroll and again, often by someone else, for job costing. Over eleven weeks the two records drift. The certified payroll shows a labourer at thirty-eight hours on the covered project while the job cost report shows forty-two, because four hours were recoded to a different job after payroll had already run. Neither number is fraudulent. Nevertheless, a reviewer looking at both now has a discrepancy to work through, and you have no clean explanation for it.
🚩 The classification decided at the payroll deadline
A worker spends part of the week on covered work at one classification and part on something that pays differently. The foreman knows what happened. His notes are on a paper timesheet in a truck. Payroll closes Tuesday, so the administrator makes the most reasonable call she can and moves on. Multiply that across a crew of twenty and several months, and the classification history on the project is a series of reasonable calls nobody documented.
🚩 The audit request that turns into a scavenger hunt
An external auditor, a lender, or a bonding company asks for support behind a labour figure. Producing it means an export from the payroll service, a spreadsheet a controller built to allocate burden, PDF timesheets in an email folder, and a manual tie-out to the general ledger. The answer is usually correct. However, it takes days, it consumes the people you can least spare, and every reassembly step is a place where the number could have been massaged, which is precisely what an auditor is trained to notice.
🚩 The compliance process that is really just one employee
One person knows how to pull the reports, which agency wants which format, and which quirks each union has. That knowledge is not written down anywhere. In other words, your compliance function has a single point of failure, and it takes vacations.
Put these together and the pattern generalizes: the contractor is not out of compliance, but cannot prove compliance quickly or cheaply. That distinction gets expensive at exactly the wrong moments, during a bid protest, a bonding review, or an agency records request with a short deadline.
Is Your Current Process Working?
A quick self-assessment reveals whether your compliance process is controlled or merely coping. Answer the following eight questions based on how things actually work today rather than how the process was designed to work.
Evaluation:
- Can you produce certified payroll for a specific project and week without exporting data into a spreadsheet first?
- Do the labour hours on your certified payroll reconcile to your job cost report without a manual tie-out?
- Is the classification and pay rate recorded on the original time entry, rather than applied later by the payroll administrator?
- Can you run one payroll covering project crews and service technicians across multiple union agreements?
- When a rate or fringe schedule changes mid-project, does the change apply going forward without breaking the historical record?
- Can you trace any line on a compliance report back to the individual time entry that produced it?
- Could someone other than your most experienced payroll person produce a full audit package next week?
- Does each legal entity in your structure report on its own obligations from the same underlying labour data?
If you answered no to three or more of these questions, your compliance work depends on reassembly rather than on records.
What Good Compliance Looks Like
The ideal state is not a better reporting tool bolted onto the same fragmented data. It is a labour record complete enough at the moment of capture that compliance reporting becomes a query rather than a project. In practice, that ideal shows up in six specific ways.
Payroll, job costing, and the general ledger draw on the same labour records
A single time entry carries the employee, the classification, the rate, the job, the cost code, and the entity. Payroll processes from it, job costs post from it as part of the same entry, and the ledger reflects it without a reconciliation between systems afterward.
Classification and rate live on the time entry, not in someone’s memory
The person closest to the work records what the work was, at the time it happened, on a mobile device. Furthermore, the prevailing wage or union rate attaches from the setup rather than from a clerk’s interpretation on Tuesday afternoon.
One payroll run covers project crews and service technicians
An employee is one employee, and a single time entry records whether the hour went to a project cost code or a service work order, then drives the pay, the cost, and the compliance report from that one record.
Audit support is a query against the ledger rather than a reassembly project
Dispatch details, customer history and equipment history go out to the field; hours, parts, notes, photos and signatures come back and attach to the work order.
Each legal entity reports on its own obligations from shared data
Entity-level compliance and consolidated visibility are not in tension when the entities sit in one database. Intercompany labour charges create their own entries as the work is processed, so entity filings do not wait on a month-end allocation exercise.
Access control and retention are properties of the system
Payroll data is sensitive, and it has to survive for years after a project closes. Consequently, the ideal state includes role-based access, multi-factor authentication and single sign-on, and hosted infrastructure that keeps records intact and retrievable for the full statutory retention period.
The Jonas Approach
Jonas is one construction ERP on one database rather than a set of products joined by a sync. That distinction matters more for compliance than for almost any other discipline, because compliance is a question about whether two records agree. When payroll and job costing are separate systems, agreement is something you verify. When they read the same labour records, agreement is a property of the architecture.
In practice, field time entry, payroll, job costing, the general ledger, and multi-company accounting all work from the same entries. Jonas payroll handles American and Canadian payroll from one data source, whether certified, unionized, or non-unionized, with multi-union and multi-trade reporting (Jonas payroll capabilities). Those same records feed real-time job costing, so a compliance report and a job cost report have one origin, reporting gives a controller drillable access from a summary figure down to the underlying transactions, and multi-factor authentication and single sign-on cover the access-control question auditors now ask.
By comparison, a payroll service plus an accounting package plus a compliance add-on can produce every one of those reports. What that stack cannot do is guarantee they agree, because they come from different copies of the same hours.
"Setting up union codes ahead of time became a breeze with Jonas, saving us 4 to 5 hours per week on union reporting."
Next steps
Moving compliance onto a single dataset is real work. Somebody has to map your pay classes, union agreements, fringe schedules, cost codes, and entity structure, and mapping those up front is what separates a clean go-live from a frustrating one. Our onboarding team handles the heavy lifting of that reconfiguration so it does not land entirely on you, but your payroll team will be instrumental to those efforts.
Those efforts, however, are a one-time cost. The compliance friction you carry today is recurring: the hours before every filing deadline, the days lost to every records request, the exposure you cannot quantify because the proof is scattered. The switch is not adding friction, it is trading recurring hidden friction for a one-time supported transition.
Book a demo with a Jonas specialist and bring your most recent certified payroll submission alongside the job cost report for the same week. If those two documents do not agree without a spreadsheet in between, that gap is the one worth testing.
Frequently asked questions
What is certified payroll and which contractors have to file it?
Certified payroll is a payroll report submitted on a set schedule for work on publicly funded construction projects, along with a signed statement confirming that every worker on the project was paid at least the prevailing wage for the classification of work they performed, including fringe benefits. It generally applies to contractors and subcontractors on federally funded or federally assisted work, and many states apply comparable prevailing-wage rules to state-funded projects. Forms, filing schedules, and submission portals vary by jurisdiction and by awarding agency, so confirm the specific requirements attached to each contract you bid.
How do union contractors handle multiple collective agreements in one payroll run?
The workable approach is to configure each agreement once, with its own classifications, rates, fringe contributions, dues, and effective dates, and then attach the agreement to the employee and the work rather than to a separate payroll run. Hours captured in the field carry the classification, so the correct rate and fringe apply from the setup instead of from a manual lookup. Contractors who instead maintain rates in spreadsheets outside the payroll system tend to find the historical record breaks the first time a rate changes mid-project.
Can construction accounting software produce certified payroll reports?
Some can, some cannot, and the more useful question is where the reporting data comes from. The table below summarizes the differences between three common setups.
| Capability | Generic payroll service | Accounting package plus compliance add-on | Unified construction ERP |
|---|---|---|---|
| Certified payroll produced from the same records that feed job costs | No | Partial (depends on the integration between payroll and job costing) | Yes |
| Multiple union agreements and fringe schedules in one payroll run | Partial (usually requires manual rate handling) | Partial (varies by package) | Yes |
| Project crews and service technicians in a single payroll run | No | No | Yes |
| Entity-level compliance reporting across multiple legal entities | No | Partial (often one company file per entity) | Yes |
| Drill down from a compliance report to the original time entry | No | Partial (breaks at the system boundary) | Yes |
| Direct native submission to every state and agency portal | No | Partial (depends on the add-on) | Partial (export to a dedicated compliance platform; portal-specific formats vary) |
What payroll records should a contractor have ready for an audit?
At minimum: payroll registers with classification and rate history by employee and by project, the time records those registers were built from, union and fringe benefit remittance detail, the labour hours supporting each contract’s job costs, and an audit trail running from any summary figure back to the individual time entry. Records also have to remain available for years after a project closes, since retention periods on public work extend well past final billing, so retention is part of readiness rather than a filing afterthought. The practical test is whether you can produce that package from your system of record instead of assembling it from exports. Broader financial audit preparation, including work-in-progress schedules and vendor documentation, is covered in the Construction Accounting Guide.
How long does it take to implement a construction ERP for payroll and compliance?
It depends, and any vendor quoting a single number without knowing your union structure is guessing. Realistic timelines vary with the complexity and cleanliness of your existing payroll data, the number of trades, divisions, and legal entities you run, how many collective agreements you carry, and how much time your team can commit alongside their day jobs. Union and certified payroll configuration is usually the longest build, because it is the part that has to be exactly right before the first live run.
