A lapsed clearance certificate stops a payment

The situation

A mechanical subcontractor had been on-site for five months on a mid-rise residential build, invoicing monthly against an approved schedule of values. Its WSIB clearance certificate, collected once at contract signing, had been sitting in the project file ever since, unquestioned on every progress payment approved so far.

At month-end, the general contractor’s accounts-payable process ran its standard pre-payment checklist, which included a step nobody had ever seen actually stop a payment before: confirm the clearance on file is still current before releasing funds.

The problem

A clearance certificate is not a document that simply sits valid until an expiry date passes. WSIB states plainly that “a clearance will automatically be created for your business as long as you are up-to-date on your WSIB payments and reporting” — and, separately, that “only registered businesses in good standing can obtain a clearance.” Both conditions have to hold, continuously, for a fresh clearance to exist at all; the number is not simply renewed on request the way a membership card is.

This is a different failure mode from a clearance that has merely gone stale on the calendar. A stale-but-otherwise-clean certificate can usually be refreshed with a routine request. A certificate that cannot be refreshed at all — because the underlying account is not currently in good standing — is a different and more serious problem, and it does not announce itself; it just quietly stops renewing.

The numbers

The AP check requested a current clearance number for the subcontractor and got back a status the project team had not seen before: not renewed. The subcontractor had missed a quarterly WSIB premium remittance roughly two months earlier — an internal cash-flow issue on its own books, unrelated to the work on this project — and its account had been out of good standing ever since, with no clearance issued in the interim.

The $46,000 progress payment due that month was the first payment cycle to actually hit that gap; the prior month’s payment had cleared before the remittance was missed. One payment cycle out of six on this contract ran into the problem — but it was the only one that needed to.

The rule that decided it

The general contractor’s exposure here is not abstract: releasing a progress payment to a subcontractor that is not currently in good standing with WSIB is exactly the situation the clearance requirement exists to prevent a contractor from walking into blind. Holding the payment until a fresh, current clearance exists is not a punitive step — it is the only way to confirm the condition the clearance certificate is supposed to certify actually still holds.

The stakes for skipping that check are statutory, not just procedural: under the Workplace Safety and Insurance Act, 1997, s.141.1(2), a general contractor that directly retains a subcontractor for construction work “is liable for those obligations, to the extent that the contractor or subcontractor does not comply with them” — joint exposure for the subcontractor’s own unpaid WSIB premiums. Section 141.2 lets a contractor avoid that liability only by obtaining a current certificate before the work begins and keeping it on file “for at least three years after the date it is obtained.”

The outcome

The subcontractor paid its outstanding WSIB remittance, and its account returned to good standing within four business days; a fresh clearance was issued two days after that. The $46,000 payment was released six business days after it was originally due, once the new clearance was confirmed and logged in the project file.

The project’s pre-payment checklist now runs the same clearance check every month for every subcontractor, not just at contract signing. That is a different gap from the one closed by tracking clearance status across an active vendor roster on a recurring calendar — see a property portfolio's own clearance-audit gap for that portfolio-level version — and a different gap again from clearance paperwork slowing down a bid cycle, covered in how one contractor cut its bid-prep time on the same paperwork. For how contractors are now tracking WSIB clearance status automatically across a project, see tracking WSIB clearance certificates across a project.

Takeaways

• • A WSIB clearance is not simply valid-until-expiry: it renews automatically only while the account stays current on both payments and reporting.
• • A business that falls out of good standing cannot obtain a fresh clearance at all until the underlying issue is fixed — that is a different, more serious gap than a merely stale certificate.
• • Check clearance status at every payment cycle, not once at contract signing — the gap in this case only existed for one of six payment cycles, and a monthly check was what caught it.
• • Holding a payment until a fresh clearance exists is not punitive; it is the only way to confirm the condition the certificate is meant to certify still holds.
• • This is a different mechanism from a portfolio-wide clearance audit or a bid-package paperwork delay — each is a different point where the same clearance requirement can bind.