BC pay transparency reports reach employers with 50 or more BC employees on 1 November 2026. What the report contains, where the data comes from, and how to produce it.
British Columbia's Pay Transparency Act phased reporting in by employer size, and the final step is the one that reaches ordinary mid-sized businesses. Reports are due by 1 November each year.
| From | Employers covered |
|---|---|
| 1 November 2024 | 1,000 or more employees |
| 1 November 2025 | 300 or more employees |
| 1 November 2026 | 50 or more employees |
If you have 50 or more BC employees, your first report is due by 1 November 2026, and then annually. Treat the date as a data deadline rather than a filing deadline: the figures come from a full reporting period, so a business that starts collecting in October is reporting on records it did not design to be reported on.
This is general information and not legal advice. Check the current requirements with the Province of British Columbia, because thresholds and report contents are set by regulation and can change.
The report sets out pay information for your employees broken down by gender and other diversity characteristics, showing the differences in pay between groups. It is a statistical picture of your payroll, not a narrative about your policies.
That shape has a consequence worth understanding before you start. The report is a calculation over your own records, so the quality of the output depends entirely on whether your payroll and HR data can be joined, cleanly, for the whole period. Most of the difficulty employers hit is not the arithmetic. It is that the two halves of the calculation live in different systems and do not agree about who worked there.
In most businesses this report needs three sources joined together: the payroll system, the HR record, and whatever you used to ask employees about demographics. They rarely share an identifier.
| Problem | How it shows up | What fixes it |
|---|---|---|
| No common key | Payroll uses an employee number, HR uses an email address | One identifier that both systems carry |
| Mid-year changes | A promotion looks like two different people | Effective-dated records, not overwritten ones |
| Leavers | Someone who left in June is missing from a year-end extract | Extract by period worked, not by current status |
| Overwritten history | Last year's figures change when you rerun the report | Keep the version you reported, as reported |
| Pay components | Bonus and commission sit outside the salary field | Map every component once and write the mapping down |
The fourth row is the one that causes real trouble. If your systems overwrite rather than keep history, rerunning last year's report can produce different numbers from the ones you filed, and you have no way to explain the difference. Keep a copy of each report and the extract it was built from.
Mid-sized employers often reach this point and find they have a payroll product that was never meant to answer this question. The honest options are a different payroll product, a reporting layer that sits over what you have, or an export and a defined calculation you can repeat. We look at the trade-offs in payroll software in Canada.
You cannot report on characteristics you never collected, and collecting them is not simply adding a field. Employees are being asked for personal information about themselves, and the way you ask changes both the response rate and your obligations.
Two practical points. First, a free-text field will produce data you cannot aggregate, so use defined options with a way to decline. Second, non-response is a result, not a gap to be filled; decide how you handle it before you run the numbers, and keep that decision written down so next year's report is comparable.
The first report is a project. The second should be a button. The difference is whether anybody wrote the calculation down in a form a computer can repeat.
Step six is the one worth doing early. A dry run in the spring is a to-do list. The same dry run in late October is a problem.
If you have 50 or more BC employees, do the dry run before anything else. Pull a period's payroll, try to join it to your HR records, and see whether you can produce counts and pay by group at all. Whatever breaks is your actual project.
Employers hiring in Ontario have a separate and earlier deadline, since job posting rules start on 1 January 2026. See Ontario pay transparency for that side.
We build the reporting layer that sits over payroll and HR systems and turns this into a repeatable extract, including the version history that lets you show what you filed and why. Send us the systems you are working with and we will tell you what the join looks like before you commit to anything.
The threshold reaches employers with 50 or more BC employees on 1 November 2026, following 1,000 or more in 2024 and 300 or more in 2025. Reports are due by 1 November each year. Confirm the current rules with the Province of British Columbia.
Pay information broken down by gender and other diversity characteristics, showing differences in pay between groups. It is a calculation over your own payroll and HR records rather than a description of your policies.
Responses should be voluntary, so non-response is normal. Decide in advance how your calculation handles it and write that decision down, so this year's report and next year's are comparable.
Some can and many cannot, because the report needs payroll joined to HR and demographic data on a common identifier. Do a dry run on real data well before the deadline; whatever fails to join is the work.
No. Ontario's rules starting 1 January 2026 are about what a job posting must contain. BC's reporting requirement is an annual statistical report about your existing workforce. An employer hiring in both provinces has to do both.