Minnesota Certified Payroll Requirements

Minnesota sits on a cadence of its own — not weekly like the federal system, not monthly like Illinois or Connecticut, but every two weeks. It also has a provision that's genuinely in the contractor's favor, and that most subs have never heard of: if the contracting authority failed to put the wage determination in your contract, the cost of that mistake can land on the authority rather than on you.

Who's covered: Minn. Stat. 177.41 to 177.44

Minnesota's prevailing wage law lives at Minnesota Statutes sections 177.41 through 177.44, administered by the Department of Labor and Industry (DLI). It requires that employees on state-funded construction projects, and other projects covered by the law, be paid wage rates comparable to those paid for similar work in the area where the project is located.

DLI publishes rates by region and by project type — and Minnesota separates these more explicitly than most states, with distinct commercial, residential, and highway/heavy schedules. Pulling a commercial rate for highway work, or the reverse, is a straightforward way to underpay without ever intending to. Rates and forms are published at dli.mn.gov; the prevailing wage unit can be reached at dli.prevwage@state.mn.us or 651-284-5091.

The filing: every two weeks, to two recipients

Certified payroll forms must be completed by every contractor and subcontractor on a project and submitted every two weeks — more precisely, no more than 14 days after the end of each pay period.

Note who receives them. Minnesota directs the submission to the contracting authority and the project owner. On many jobs those are the same entity, but on plenty they are not — and a contractor who files only to the general contractor's compliance inbox may not have satisfied the requirement. Confirm both recipients at the start of the project.

Every payroll must be certified by attaching a completed and executed Statement of Compliance to each report. An uncertified payroll is not a filing.

The provision worth knowing: who pays when the determination is missing

Minnesota requires the contracting authority to incorporate the applicable wage determinations — plus contract language provided by the commissioner of labor and industry — into its proposals and contracts, so that contractors and subcontractors are on notice that sections 177.41 to 177.44 apply.

And it attaches a consequence to skipping that step. Failure to incorporate the determination or the required contract language makes the contracting authority liable for making the contractor or subcontractor whole for any increases in wages paid — including employment taxes and reasonable administrative costs — based on the appropriate prevailing wage due to the laborers and mechanics on the project.

That is a meaningful protection, and it is worth knowing before you absorb a retroactive wage adjustment quietly. It is not a licence to stop checking: you still owe the correct rate, and the practical posture is to confirm the determination is in your contract before you bid. But if you discover mid-project that it was never there, the question of who bears the increase is not automatically answered against you. That is a conversation to have with the contracting authority, and if the amounts are significant, with counsel.

Record retention

Certified payroll records must be retained by the employer for a minimum of three years after the final payment is made on the project. As in Texas, the clock starts at the end of the job, not at the week the work was performed — so on a multi-year project your earliest records need to live considerably longer than three years.

Common Minnesota mistakes

• Filing to only one recipient. The submission goes to the contracting authority and the project owner.
• Drifting past the 14-day window. Two weeks is the outside limit after the pay period ends, not a target.
• Mixing the rate schedules. Commercial, residential, and highway/heavy are separate. Use the one matching the work.
• Submitting without the Statement of Compliance.An uncertified payroll doesn't count as filed.
• Eating a retroactive increase without asking. If the determination was never in your contract, the authority may be liable to make you whole.
• Shorting the fringe. Base plus fringe is the obligation; shortfalls become back wages on every hour worked.

Federal overlap

Minnesota projects carrying federal funds bring Davis-Bacon alongside the state law — a weekly WH-347to the contracting agency running against the state's two-week cycle. Workers are owed the higher of the applicable rates. The contract documents identify the funding sources; ask the contracting authority when it's unclear.

How Certiwage helps

Certiwage computes each week's payroll — gross, overtime at 1.5× the base rate plus straight-time fringe, deductions, net — and runs a fringe shortfall check before you certify. On the federal side of a Minnesota job it produces the WH-347and signed Statement of Compliance directly. For the state filing, its weekly records roll up cleanly into the two-week submission, with the per-worker classification, hours, rate, and deduction detail DLI's form asks for.

Certiwage is a document-preparation tool, not legal advice, and is not affiliated with Minnesota DLI or the U.S. Department of Labor. Confirm your project's rate schedule, recipients, and format with the contracting authority. Compare cadences in our Illinois (monthly) and Maryland (bi-weekly, electronic) guides.

Run one week through the free WH-347 builder to see the math checked — no signup.