Construction Payroll in Canada: Understanding Hours, Overtime, CPP, EI and Payroll Workflow

Canadian construction payroll follows a structure that every employer needs to understand, even if a payroll system does the arithmetic. The structure is: recorded hours, regular and overtime classification, gross pay, statutory deductions, and net pay, wrapped in a workflow of review, approval, and payment.

This article walks through that structure in practical terms, explains where the numbers come from, and is deliberately careful about one thing: the statutory rates and thresholds change, so this article explains concepts and workflow rather than publishing current figures. Employers should verify current requirements with the Canada Revenue Agency, provincial authorities, and qualified professionals.

A worked example shows how the structure operates. A biweekly pay period runs from a Monday to the Sunday two weeks later. A worker's sessions across the period add up to 76 hours: 70 regular and 6 overtime after the company's thresholds are applied. The worker's rate is $30 per hour and the overtime multiplier is 1.5. Regular pay is 70 multiplied by 30, or $2,100. Overtime pay is 6 multiplied by 30 multiplied by 1.5, or $270. Gross pay is $2,370 before vacation and holiday components. From there, the tax engine applies the configured brackets and claim codes to compute federal tax, provincial tax, CPP, and EI, and net pay is what remains. Every number in that chain can be traced back to a session in the attendance record.

The same example exposes the common failure mode: if the 6 overtime hours had been absorbed into the regular total by rounding or by weekly reconstruction, the gross pay would be $2,280 instead of $2,370, and the worker would be underpaid by $90 without any record showing why. Structure is not bureaucracy; it is how the numbers stay honest.

Step one: hours

Every construction payroll period starts with hours. For hourly workers, the hours are the raw material of the entire calculation. If the hours are wrong, nothing downstream can be right.

The quality of the hours depends on how they were recorded. Paper timesheets reconstructed at the end of the week produce approximate hours. Digital check-in at the site produces timestamped hours. The difference matters at payroll time, because the pay period is only as accurate as its inputs.

In a site-based attendance system, the hours arrive organized by employee and site, with each session carrying a start time, end time, and duration. The payroll calculation does not need to guess or reconcile; it reads the sessions in the period.

The session is the unit of truth for hours. A session is the record of one check-in to check-out at a site. Sessions aggregate into daily hours, daily hours into weekly hours, and weekly hours into the pay period. When the aggregation is automatic, the payroll inputs are the same numbers the supervisors saw during the week.

The reverse is also true: when hours are reconstructed at the end of the period, the aggregation is done by memory, and every remembered number is a potential error. The first discipline of construction payroll is therefore not in the payroll office at all; it is at the site gate, where the session starts.

Step two: regular and overtime hours

The next step is classification. Hours are split into regular hours and overtime hours because they are paid at different rates.

Overtime rules in Canada are set by the provinces and vary between them. The common pattern involves a daily threshold and a weekly threshold: hours beyond the daily threshold are overtime, and hours beyond the weekly threshold are also overtime. Some provinces add double-time rules beyond a higher threshold.

Because the rules vary and change, a company should configure its overtime rules from its province's current requirements. In FastBuild, the company settings hold the daily threshold, weekly threshold, and overtime rate multiplier, and the same rules apply across all sites.

The classification itself comes from the attendance data. Daily hours are summed per worker per day, weekly hours per worker per week, and the thresholds are applied to produce the overtime totals.

A concrete example clarifies the daily and weekly interaction. A worker logs 10 hours on Monday and 7 hours on each of Tuesday through Friday, for 31 hours in the week. With a daily threshold of 8, Monday produces 2 daily overtime hours. With a weekly threshold of 40, the 31-hour week produces no weekly overtime. The overtime total for the week is 2 hours. If the same worker logs 9 hours on each of five days, the daily view produces 5 overtime hours, and the weekly view produces 5 overtime hours as well; the two views agree because the totals happen to line up. When they disagree, the weekly view is usually the more protective one, because it captures the pattern where no single day is long but the week is long.

The lesson for employers is to configure both thresholds deliberately and to verify them against the province's current employment standards, because the thresholds are legal parameters, not accounting preferences.

Step three: gross pay

Gross pay is the amount earned before any deductions. For a construction worker, gross pay is built from four components: regular pay, overtime pay, holiday pay, and vacation pay.

Regular pay is regular hours multiplied by the hourly rate. Overtime pay is overtime hours multiplied by the hourly rate and the overtime multiplier. Holiday pay applies to hours worked on statutory holidays at the applicable holiday rate. Vacation pay is typically calculated as a percentage of earnings and is a provincial requirement in most of Canada, with the percentage varying by province.

The sum of these components is the gross pay for the period. Every pay stub should show the components so the gross total is auditable.

Vacation pay deserves a closer look because it is frequently misunderstood. In most provinces, vacation pay is not a deduction; it is an amount earned on top of the hours, calculated as a percentage of earnings, and it accrues or is paid out according to the province's rules. FastBuild applies the configured vacation pay percentage in the calculation, but the employer remains responsible for paying vacation pay in the manner the province requires, whether that is accrued or paid out per period.

Step four: statutory deductions

Statutory deductions are the layer that makes Canadian payroll different from payroll in most other countries. The main deductions are Canada Pension Plan (CPP) contributions, Employment Insurance (EI) premiums, and income tax.

CPP is a contributory pension program. Both the employee and the employer contribute, subject to an annual exemption and a maximum contribution set each year. EI is the employment insurance program, with employee and employer premiums subject to a maximum. Income tax is withheld on each payment, with federal tax and provincial tax calculated using the tax brackets and the employee's personal claim codes.

The rates, exemption amounts, and maximums are set by the federal and provincial governments and change regularly. This is exactly why this article does not state current figures: published numbers would go stale and could mislead. The right source is the official CRA tables for the current year, or a qualified payroll professional.

The claim code deserves an explanation because it directly affects withholding. When a new employee completes the federal TD1 form and the provincial equivalent, they declare claim codes that determine the basic personal amount used in the withholding calculation. A claim code of 1 typically reflects the basic personal amount; higher codes add credits for situations such as a second job or disability. The codes are recorded in the employee's tax profile, and keeping them current is part of onboarding.

A payroll system that follows this structure needs three layers of configuration: the tax brackets and claim codes per employee, the CPP and EI parameters for the year, and the frequency at which the annual amounts are prorated. When any layer is stale, every calculation that touches it is wrong, which is why reference data updates are a payroll ritual.

Step five: net pay

Net pay is gross pay minus total deductions. It is the amount that actually reaches the worker's bank account. The pay stub should present the full chain: hours, regular pay, overtime pay, gross pay, each deduction, and net pay, so the worker can see exactly what was earned and what was withheld.

The payroll workflow

Payroll is a workflow, not a single calculation. The discipline of separating the steps is what prevents errors from being paid.

The workflow in FastBuild is explicit. The manager generates a pay period for a date range. The system calculates the entries from the attendance data. The manager reviews the entries and the period totals. The manager approves the period. The period is marked as paid.

Each transition is a deliberate action, which means nothing gets paid by accident and every step can be revisited. An approved period that is discovered to be wrong is a review problem, not a silent correction.

The review step is where payroll errors are caught, and it deserves real time. The reviewer should check the obvious things: the period dates cover the right range, the overtime totals match the weekly reviews, the gross totals are in the expected band, and no employee is missing an entry. The discipline of reviewing before approving is what separates payroll that is run from payroll that is merely calculated.

Where the employee profile fits

The employee payroll profile holds the inputs that vary per worker: the hourly rate and the pay frequency. Keeping these current is an employer responsibility, and an outdated rate will quietly flow through every calculation.

Tax configuration holds the structural inputs: the tax brackets, personal claim codes, and CPP and EI parameters for the year. These are reference data, maintained separately from the employee records.

Common mistakes in construction payroll

The recurring mistakes are the same across companies. Running payroll from hours that were reconstructed rather than recorded. Applying overtime inconsistently between sites. Losing weekly overtime because only daily totals were tracked. Using stale rates, thresholds, or brackets. Paying from a record the supervisor never reviewed.

Each mistake is preventable with structure: recorded hours, configured rules, current reference data, and a review step.

A checklist for the pay period close can prevent most of them. Verify the period dates. Confirm every active employee has a payroll profile with a current rate. Compare the period hours with the weekly attendance reviews. Spot-check the overtime totals against the thresholds. Confirm the tax year configuration matches the current year. Review the gross totals per employee before approving. Only then mark the period as paid.

The checklist looks administrative, and it is. That is the point: payroll errors are rarely caused by the arithmetic; they are caused by the inputs. The arithmetic is the same every period. The inputs, hours, rates, thresholds, and reference data, are where the mistakes hide. A checklist that inspects the inputs is a checklist that finds the mistakes before they become pay stubs.

Frequently asked questions

Is FastBuild a payroll compliance service? No. FastBuild calculates payroll using the structure of Canadian payroll and the configured tax data. Employers are responsible for verifying current requirements with official sources and for final compliance.

Where do the hours come from? From the attendance records: GPS check-in and check-out sessions within the pay period.

Who can run payroll? Payroll administration is limited to roles with payroll management permission, typically owners and managers.

What shows on the pay stub? Regular pay, overtime pay, holiday and vacation pay where applicable, gross pay, federal and provincial tax, CPP, EI, total deductions, and net pay.

Can payroll be corrected after approval? The workflow is review, approve, mark paid. Corrections are handled deliberately rather than silently edited.

What happens when an employee has no attendance in a period? The period calculation handles the employee according to the configured rules; zero hours produce zero pay, and the review step confirms the entry.

How do claim codes affect the calculation? Claim codes set the basic personal amount used in the tax withholding; they come from the employee's TD1 forms and are stored in the tax profile.

Key definitions

Canadian payroll uses a precise vocabulary, and each term maps to a step in the calculation. Gross pay is the total earned before deductions: regular pay, overtime pay, holiday pay, and vacation pay added together. Deductions are the amounts subtracted from gross pay, led by CPP, EI, and income tax. Net pay is gross pay minus total deductions, the amount that reaches the worker. The pay period is the date range of the calculation, and the pay frequency is how often periods occur. The payroll profile is the employee's configuration: hourly rate and pay frequency. The tax profile holds the claim codes and province of employment. Overtime hours are hours beyond the configured thresholds, and overtime pay applies the rate multiplier to them. When every term has a single meaning, the pay stub becomes a document that both sides can read the same way.

Two related concepts deserve emphasis because they are commonly confused. CPP is a contributory pension program funded by employer and employee contributions, not a tax; the contributions are recorded on the pay stub separately from income tax. EI is the employment insurance program funded by premiums, also separate from tax. Neither CPP nor EI is income tax, and lumping them together in conversation is how misunderstandings about take-home pay start. The pay stub that separates them is not just good formatting; it is the clearest explanation the worker will ever receive.

The week before the period closes

Payroll periods do not happen in isolation; they are the endpoint of a week-by-week rhythm that determines how smooth the close will be. The week before the period closes is where the discipline shows up.

Monday: the previous week's attendance is reviewed. GPS exceptions get explanations, and any corrected sessions are settled while the week is still concrete. Friday: the weekly hours view is checked against expectations, and the overtime totals are reviewed against the thresholds. If the weekly review disagrees with a supervisor's recollection, the sessions are the referee, and the discrepancy is resolved before it reaches the period.

The day before the close: the employee payroll profiles are checked. Rates that changed mid-period are confirmed, and new employees are verified to have profiles. The tax configuration is confirmed to match the current year. On close day, the period is generated, reviewed, approved, and marked paid, with the review taking far less time than it would have taken to reconstruct the hours.

The rhythm matters because it moves the verification work out of the pay period and into the weeks where the information is fresh. Payroll becomes the last step of a process the company has been doing all along, rather than a crash on its own.

Conclusion

Canadian construction payroll is a structure, not a mystery: recorded hours, classification, gross pay, statutory deductions, net pay, and a review workflow. The companies that run it well are the ones that keep the inputs current, the rules configured, and the steps deliberate. Verify the current rates and thresholds with official sources, and let the system do the arithmetic on a record you can defend.