BC's Prompt Payment Act Is Coming. Your Billing Process Isn't Ready.

Ask anyone who runs billing at a BC contractor what month end looks like and you'll hear a version of the same story. The progress numbers come in from three project managers in three formats. Someone chases the missing insurance certificate and the sub's statutory declaration. The payment application goes out on whatever day the package finally comes together, sometimes the 3rd, sometimes the 9th. Then it sits with the owner's consultant for however long it sits, and the phone calls start in week four. The whole cycle runs on effort and follow-up, and the timeline belongs to whoever feels like moving.

That era is ending in this province, and most small and mid-size contractors haven't started preparing for what replaces it.

What the Act actually changes

Bill 20, the Construction Prompt Payment Act, received Royal Assent in December 2025. It isn't in force yet. The government spent the first half of 2026 consulting on the regulations, and the Act only takes effect on a date set by regulation, likely with a runway, and it won't apply to contracts that already exist. So nobody needs to panic this quarter. But the shape of the regime is already clear, and it's worth understanding now, because the fixes it demands are process fixes, and process fixes take months to become habits.

The core mechanism is the "proper invoice." Once you deliver one, a clock starts that nobody can pause. As the Act is written, an owner has 28 days from receiving a proper invoice to pay it or to issue a formal notice objecting to it. Once a contractor gets paid, payment has to flow down to subcontractors within 7 days. Disputes go to a rapid adjudication process: an adjudicator's decision comes within 30 days and is binding on an interim basis, with payment due shortly after. Certification and approval steps can't be used to delay the trigger. Alongside all this, the Builders Lien Act holdback period shortens from 55 days to 46.

Invoicing defaults to monthly, though parties can contract for milestones instead. The detailed content requirements for a proper invoice will come in the regulations. That detail matters less than the structure: fixed clocks, formal notices with deadlines, and a fast dispute process that runs on documentation.

This is an operations problem wearing a legal costume

When legislation like this lands, the instinct is to treat it as a legal matter. Your contracts will need updating, and that part genuinely belongs with your lawyer. We're not lawyers and this isn't legal advice.

But Ontario has been living under prompt payment since 2019, and the lesson from there is that the firms who struggled didn't struggle with the law. They struggled with their own back office. Every mechanism in this regime is a test of operational speed, in both directions:

Your invoice has to be proper, on time, every month. A proper invoice that starts a 28-day clock is only useful if you can produce one reliably. If your payment application depends on progress data that gets reconstructed from memory, or a supporting-document package that comes together differently every month, you'll either submit late (delaying your own clock) or submit incomplete (giving the payer a legitimate objection and restarting the cycle).

Objections come with deadlines, and so do your responses. Under the current informal system, a disputed line item is a phone call and a revised invoice whenever. Under the Act, an owner's objection is a formal notice on a statutory timeline, and if you're the general and your owner short-pays, passing that withholding down to your subs comes with its own notice obligations, including giving the sub a copy of the owner's notice. Miss the mechanics and you lose the protection.

Adjudication is fast, and fast favours the organized. A 30-day decision means the party who can produce clean records wins on evidence the other party is still hunting for. Daily logs, quantities against the schedule of values, the change order trail, delivery records: if those live in one place and agree with each other, adjudication is your friend. If they live in four spreadsheets and two inboxes, it isn't.

A 46-day holdback period gives you nine fewer days to have your lien position and release paperwork sorted at the back end of every project.

Where month-end processes will crack

Picture a hypothetical mid-size civil contractor, the kind of operation we see often. Progress claims are built in Excel from numbers the PMs email in. The schedule of values lives in one file, the change order log in another, and they're reconciled by hand. Sub payment tracking is the accountant's memory plus the accounting system. Nothing about this is broken today, exactly. It produces a payment application every month and the company gets paid, eventually.

Put that operation under the Act and the weak points light up. The invoice goes out on the 9th instead of the 1st: that's eight days of payment timeline given away every single month, forever. The package is missing one document: formal objection, cycle restarts. The owner short-pays a line item and the 7-day flow-down clock starts ticking against subs whose entitlements nobody can quickly calculate. A dispute goes to adjudication and the first week is spent assembling records instead of arguing the case.

None of these are failures of skill. They're failures of pipeline, and they're all fixable before the Act arrives.

What to fix during the runway

The good news is the preparation list is short, unglamorous, and valuable even if the regulations take another year.

Standardize the billing package. One checklist of every document a payment application needs, one owner of the package, one calendar date it goes out. When the regulations define proper invoice contents, you update the checklist. The habit is the hard part; build it now.

Make progress data flow instead of being reconstructed. Your monthly claim should roll up from field records you already collect, quantities in daily logs against the schedule of values, not from a fresh round of estimates. If you've read this blog before you'll recognize the theme: the same structured field data that fixes reporting also produces defensible invoices. Under a prompt payment regime, "defensible" stops being a nice-to-have.

Track the clocks. Invoice dates, payment due dates, notice deadlines, holdback release dates, per project, in one place someone owns. This is a spreadsheet and a routine before it's ever a software purchase. The transcription and assembly steps, pulling quantities into the claim format, compiling the document package, flagging approaching deadlines, are exactly the kind of mechanical work that's now cheap to automate on the systems you already run. But automate the working process, not the current mess.

Know your sub-payment position at all times. When money comes in, you'll have 7 days to move it down the chain correctly. That math needs to be ready before the cheque arrives, not after.

The honest tradeoff: this is real work, a few focused weeks of it, and the Act's start date is genuinely uncertain, so some firms will gamble on waiting. The counterargument is that every one of these fixes pays for itself today, in faster billing and fewer disputes, under the current system. The legislation just turns a good idea into a requirement.

If your month-end billing runs on heroics and you'd rather find the gaps now than during your first statutory dispute, that's a conversation worth having early. On a discovery call we map how a payment application actually gets built in your operation, where the data comes from, where it stalls, and what the smallest set of changes would be to make the process run on rails instead of memory.