QuickBooks Certified Payroll: Setup and Review

Current QuickBooks Online Payroll guidance says the federal certified-payroll report in Intuit QuickBooks Workforce requires a project, a weekly pay schedule, and custom standard and overtime pay types for each job classification. Employees’ time should be assigned to the project through the supported weekly-timesheet workflow. QuickBooks can organize the data, but the contractor must confirm contract coverage, wage determination, classifications, prevailing rates, fringe benefits, apprentices, deductions, weekly pay, and the Statement of Compliance. The certifying official needs knowledge of the represented facts.

This guide is part of Steady’s Payroll, W-2 & 1099 library. It explains the federal workflow in practical terms, but the correct result still depends on the payment year, entity, worker relationship, filing method, and state rules.

The answer in context

Project setup identifies the contract

Use a distinct project with the correct contractor, location, contract number, and reporting period.

Weekly scheduling supports weekly reports

Certified payroll is generally reported by workweek even if accounting reports usually group labor differently.

Classifications need separate pay types

A worker performing different duties needs hours and rates recorded by the applicable classification.

Time entry must hit the project

Unassigned or incorrectly entered time can disappear from the certified report while remaining in payroll totals.

Fringe treatment is not automatic

Distinguish qualifying plan credit from cash paid in lieu and retain plan documentation.

The report follows paid payroll

Tie gross pay, deductions, and net wages to the completed payroll register.

Certification remains a human control

An authorized knowledgeable signer reviews and accepts responsibility for the statement.

Step-by-step workflow

1. Review the contract. Confirm federal, state, local, and project-specific prevailing-wage requirements.
2. Create the project. Enter consistent project identity and map time, payroll, and job-cost records.
3. Use a weekly pay schedule. Assign covered employees as required by the current QuickBooks certified-payroll workflow.
4. Create classification pay types. Set standard and overtime types for every labor classification used.
5. Configure rates and fringes. Document base rate, fringe obligation, plan credit, cash in lieu, overtime, and effective dates.
6. Enter weekly timesheets. Allocate daily hours by employee, project, classification, and overtime status.
7. Run and pay payroll. Review gross-to-net results, deductions, taxes, and payment completion.
8. Generate the report. Compare the QuickBooks output with WH-347 requirements and the agency format.
9. Certify and submit. Obtain a valid signature and submit through the required project portal.
10. Retain and correct. Archive setup, time, payroll, report, statement, receipt, and corrections.

Worked example

A contractor has an electrician who also performs laborer work on one covered project. It creates separate standard and overtime pay types for both classifications, records weekly timesheets by project and duty, and applies the current wage determination and fringe treatment. After payroll is paid, a reviewer ties the QuickBooks certified-payroll report to time and payroll. The authorized official signs the compliance statement only after the classification split is verified.

The example is intentionally a workflow illustration, not a conclusion for every taxpayer. A strong file connects each number on the return to a source report and records why an exception, exclusion, or classification was applied.

Records to keep

Keep the source form or worksheet, contracts or engagement records, payer and recipient identity support, the detailed payment or payroll ledger, bank and processor reconciliation, calculations, correspondence about corrections, filed copies, recipient-delivery evidence, and federal and state acceptance confirmations. Store the records by tax year and keep superseded versions when they explain a correction.

A reviewer should be able to begin with the final reported amount and trace it back to transactions without rebuilding the year. Add a short review memo for judgments such as worker status, corporate exemption, payment-method exclusion, state filing, or unusual timing. That memo is often more useful than another unlabeled spreadsheet.

Common mistakes

• Using one hourly item for every duty. Separate covered classifications and rates.
• Entering time outside the supported project workflow. Use the current QuickBooks weekly-timesheet method.
• Ignoring the weekly pay-schedule requirement. Configure covered employees for the report’s expected cadence.
• Treating job cost as prevailing wage. The contract wage determination and fringe rules control.
• Leaving fringe benefits unexplained. Support plan credits and cash-in-lieu amounts.
• Generating before payroll is paid. Certified payroll represents completed wage payment.
• Letting software certify. A knowledgeable authorized person must sign.
• Forgetting portal acceptance. Save submission and correction evidence.

Final review before filing

Confirm the form and revision year, taxpayer identities, dollar fields, payment categories, withholding, filing channel, recipient statement, state obligations, due dates, and approval. Compare the final output with the source reconciliation rather than reviewing the form in isolation. If software recalculates an amount after an edit, rerun the tie-out.

Keep preparation, filing, and acceptance as three separate statuses. A draft can be complete but unfiled; a transmission can be sent but rejected; a federal return can be accepted while a state return is still missing. This status discipline prevents a polished PDF from being mistaken for finished compliance work.

How to handle a discrepancy

When a source form, ledger, payroll report, or software preview disagrees with another record, stop before filing and identify which amount represents the underlying transactions. Trace the difference by vendor or employee, date, invoice or payroll run, payment channel, and account. Common causes include a payment posted to the wrong year, a void recorded after a report was generated, a card payment included with checks, a duplicate import, an incorrect taxpayer name, or a late adjustment. Record the explanation and the correcting entry or form request.

Do not erase the trail by overwriting the original report. Save the first version, the reconciliation, the corrected version, and the approval. If a third party supplied an incorrect information return, request a formal correction and retain the correspondence. If a return was already transmitted, use the current correction procedure for that form and channel. A corrected recipient copy without a corresponding agency correction can leave the records inconsistent.

Federal filing is only one layer

Federal acceptance does not settle state or local obligations. A state may use a different threshold, worker test, filing portal, account number, transmittal, or due date. Some states receive eligible information through a combined program, while others require a direct submission. Verify the jurisdictions connected with the payer, recipient, employee, work location, withholding, and business activity. Save state confirmations separately so they are not hidden behind the federal acceptance.

Make next year easier

Turn the year-end work into a monthly control. Collect identity forms during onboarding, code payment methods consistently, reconcile payroll and vendor activity each month, and flag vendors or income streams that need special treatment. Schedule a fall review of missing forms, classification questions, state registrations, and electronic-filing access. By year-end, the team should be validating a maintained file instead of reconstructing twelve months of transactions under a deadline.

Assign one owner and one reviewer to the calendar. The owner prepares the source schedule and resolves open items; the reviewer tests identities, totals, rule references, filing status, and evidence. Record the date of the official guidance used because form pages and software menus can change during the filing season. If a rule is uncertain, document the question and escalate it before the deadline rather than placing an unsupported assumption in the final file. This short control list protects both accuracy and continuity when another bookkeeper, payroll specialist, or tax preparer takes over the work. Save the checklist with the return so next year’s team can see which controls were completed and which exceptions required follow-up.

Practical implementation notes

Setup matrix

Track project, employee, classification, pay type, base rate, overtime, fringe, plan, effective date, and reviewer.

Weekly control

Tie timecard hours, payroll hours, rates, gross, deductions, net, report, and payment.

Fringe file

Preserve plan documents, eligibility, hourly credit calculation, cash in lieu, and funding evidence.

Signer packet

Provide the wage determination, report, exceptions, payroll proof, and certification checklist.

For the next layer of context, see this related guide, the companion reporting article, and the connected workflow.

If the form, books, and filing status do not agree, Steady can help reconcile the source data and prepare a clean filing package through its specialist service.