Ontario Construction Act Proper Invoice: The 28-Day Clock and Your Checklist.
What the Construction Act says about a proper invoice, the 28-day owner payment deadline, notices of non-payment and adjudication limits, read from e-Laws, with a checklist and an invoice-check automation where a person approves every date.
In Ontario, the date that starts the payment clock is not the date you finish the work or the date you send the bill. It is the date the owner receives a proper invoice. If the invoice is missing something the Construction Act requires, a dispute about whether the clock started at all can cost weeks. That is one small document with one very expensive job.
Devvista is a software development company that designs workflow automation for contractors, including invoice checking and deadline tracking around prompt payment. This page sets out what the Ontario Construction Act says about proper invoices, the 28-day owner payment deadline, notices of non-payment and adjudication, based on the e-Laws text we read, and then describes an automation that checks an invoice against the statutory contents, starts the deadline clocks and leaves every date for a person to approve. It is general information, not legal advice. To discuss it, describe how invoices move through your business.
Which Version of the Act We Read
Ontario has amended its Construction Act several times in recent years, and some online summaries disagree on dates. We therefore say exactly which text we read. We opened the Act on ontario.ca e-Laws on 11 November 2026. It was marked CURRENT, with a consolidation period of January 1, 2026 to the e-Laws currency date of November 5, 2026, and a last amendment of 2025, c. 14, Sched. 2 (Construction Act, R.S.O. 1990, c. C.30).
e-Laws marks provisions that are not yet in force with an editorial note. In the version we read, the only such notes concern the definition of "home buyer" in section 1(1) and a provision in section 39(1). Neither is part of what follows. We did not read the table of in-force dates for each amendment, so we do not state when individual changes started. If a date matters to your contract, check that table on e-Laws or ask a construction lawyer.
What Is a Proper Invoice in Ontario? A Seven-Item Checklist
Section 6.1(1) defines a proper invoice as a written bill or other request for payment for services or materials in respect of an improvement under a contract. It must contain the items below and, subject to section 6.3(2), meet any other requirements the contract specifies. We have turned the statutory list into a checklist you can use today.
| # | What the Act says the invoice must contain (s 6.1(1)) | Check on your invoice |
|---|---|---|
| 1 | The contractor's name and address | Is the legal name and address on the invoice? |
| 2 | The date of the invoice and the period, milestone or other contractual payment entitlement to which it relates | Is the date there, and is the billing period or milestone named? |
| 3 | Information identifying the contract or other authorization under which the services or materials were supplied, such as a contract number, line item number or purchase order number | Is the contract or purchase order number on the invoice? |
| 4 | A description, including quantity where appropriate, of the services or materials supplied | Is each item described, with quantities where they apply? |
| 5 | The amount payable for the services or materials supplied, and the payment terms | Is the amount clear, and are the terms stated? |
| 6 | The name, title, mailing address and telephone number of the person to whom payment is to be sent, or the name, mailing address and telephone number of the office or department | Is there a payee contact with those four details? |
| 6.1 | Any other information necessary for the proper functioning of the owner's accounts payable system that the owner reasonably requests | Has the owner asked for anything else, such as a vendor number or approval code? |
| 7 | Any other information that may be prescribed | Check the regulations for anything prescribed; we did not read them |
Two related rules change how strict this is in practice. Under section 6.1(2), an invoice that falls short still counts as proper unless the owner tells the contractor in writing, within seven days of receiving it, what is missing and what would fix it. Section 6.3(2) says a contract term that makes the giving of a proper invoice conditional on prior certification by a payment certifier or on the owner's prior approval has no force or effect.
The Prompt Payment Clocks: 7, 14, 28 and 35 Days
Once a proper invoice is received, the Act sets the clocks. We quote the sections we read. The Act says "days", and we did not read how days are counted, for instance across weekends, so confirm the counting method before relying on a computed date.
| Clock | What the Act says | Section |
|---|---|---|
| Invoice frequency | Proper invoices are to be given to an owner monthly, unless the contract provides otherwise | 6.3(1) |
| Owner deficiency notice | An invoice that falls short is deemed proper unless the owner notifies the contractor in writing within seven days of receiving it, stating the deficiency and what is required | 6.1(2) |
| Owner payment deadline | The owner shall pay the amount payable under a proper invoice no later than 28 days after receiving it, subject to a notice of non-payment | 6.4(1) |
| Owner notice of non-payment | To refuse all or part of the amount, the owner must give a notice of non-payment, in the prescribed form and manner, no later than 14 days after receiving the proper invoice, specifying the amount not paid and detailing all the reasons | 6.4(2) |
| Contractor pays subcontractors | After receiving full payment, the contractor shall pay each subcontractor whose work was in the invoice no later than seven days after receiving payment | 6.5(1) |
| Contractor, partial payment | Same seven days, from the amount paid, with rules for sharing it rateably between subcontractors | 6.5(2), (3) |
| Contractor, owner has not paid | Subject to a notice, the contractor shall pay the subcontractor no later than 35 days after giving the proper invoice to the owner | 6.5(4) |
| Contractor notice to subcontractor | To rely on the owner's non-payment, the contractor must give a notice of non-payment, with an undertaking to refer the matter to adjudication within 21 days, no later than seven days after receiving the owner's notice, or if there was none, before the 35 days expire | 6.5(5), (7) |
| Payment is subject to holdback | Any requirement to pay under this Part is subject to the holdback requirements in Part IV | 6.2 |
The text says the same pattern continues down the chain: section 6.6 applies timing rules to payments between subcontractors. We did not read it in detail for this page.
Adjudication Time Limits We Could Confirm
If a dispute about a proper invoice or a notice of non-payment cannot be settled, the Act has an adjudication process in Part II.1. We read two provisions that matter for deadline tracking and we leave out the rest of the procedure, which includes prescribed forms we did not read.
| Point | What the Act says | Section |
|---|---|---|
| Time limit to start an adjudication under a contract | An adjudication may not be commenced if the notice of adjudication is given more than 90 days after the contract is completed, abandoned or terminated, unless the parties agree otherwise | 13.5(3) |
| Time limit under a subcontract | More than 90 days after the earliest of: the contract date above, the date the subcontract is certified complete under section 33, and the date the subcontractor last supplied services or materials | 13.5(3.1) |
| Adjudicator's determination | No later than 30 days after receiving the documents required by section 13.11; this can be extended by up to 14 days with the parties' written consent, or by longer written agreement | 13.13(1), (2) |
| What can be adjudicated | Disputes on matters prescribed by regulation, or any matter the parties agree to | 13.5(1), (2) |
The regulations prescribe the matters. A search result pointed to Ontario Regulation 264/25 on adjudications, but we did not open it, so we do not list the prescribed matters here.
Annual Holdback Release in the Current Text
You may also have heard that holdback release changed. The text we read includes section 26, headed "Payment of basic holdback". It says that following each anniversary of the date the contract was entered into, the owner shall publish a notice of annual release of holdback no later than 14 days after the anniversary, then pay the accrued holdback for the preceding year at least 60 days but not later than 74 days after that notice is published, unless a lien has been preserved or perfected. The contractor must then pay a subcontractor its accrued holdback no later than 14 days after receiving payment (s 26(2) to (5)).
We did not read the transition rules that decide which contracts this applies to, and e-Laws attaches its in-force dates to a separate table. So we give you the clocks as written and we recommend your adviser confirms whether and how they apply to a given contract. For a tracker, the practical point is that holdback creates a second set of dates beside the invoice dates, tied to the contract anniversary.
Where Manual Invoicing Loses Money
Most of the cost of a proper-invoice dispute is lost time, not law. These are the places it goes missing.
| Where it leaks | What goes wrong | Why it costs money |
|---|---|---|
| Invoices are built from a template by hand | The contract or purchase order number, the billing period or the payee contact is left off | The owner can argue the invoice was not proper, and the 28 days is contested |
| The owner's accounts payable team asks for an extra field | The request is not seen or not met | Section 6.1(1) item 6.1 lets the owner reasonably ask for it |
| Nobody records when the owner received the invoice | The 28, 14 and 7 day dates are counted from the day it was sent | You chase on the wrong date, or the owner serves a notice you assume is late |
| A notice of non-payment arrives by email and is read days later | The seven day window for a contractor's notice to a subcontractor is already running | A missed notice can leave you carrying the owner's non-payment |
| Subcontractor payments tracked in a separate spreadsheet | The seven day and 35 day clocks are not linked to the owner invoice | You pay late, or pay before you know whether you were paid |
| Holdback anniversaries live in someone's head | The notice date and the 60 to 74 day payment window go unnoticed | Cash that was due is released late |
Notice how many are record-keeping problems. A system that stores the received date, the invoice contents and every notice in one place removes most of them.
A Proper-Invoice Tracker You Can Copy
You can start with a sheet. Use one row per invoice and add these columns.
| Column | What goes in it |
|---|---|
| Invoice number, contract and purchase order numbers | To match the statutory identification item |
| Billing period or milestone | To match the statutory period item |
| Checklist result for items 1 to 7 | Pass, or the missing item |
| Date sent, date received (with proof) | The date received starts the clocks |
| Owner deficiency window ends | Date received plus seven days |
| Owner notice of non-payment window ends | Date received plus 14 days |
| Owner payment due | Date received plus 28 days |
| Subcontractor payment due | Seven days after you are paid; and the 35-day outer date from the day you gave the invoice |
| Adjudication outer date | 90 days from the relevant completion, abandonment or termination date |
| Confirmed by (name, date) | The person who checked the dates |
Every date in the sheet is a candidate. The person who confirms it checks the contract and the Act, including how days are counted.
The Automation: Check Before You Send, Start the Clocks, a Person Approves
The automation has two jobs: stop a bad invoice leaving the building, and start the right clocks the moment one is received. We would build it in five stages.
| Stage | What the system does | Who decides |
|---|---|---|
| 1. Receive | Collects invoices from the sources you choose: email, a portal download or a folder. Stores the original and the date and time it was received or sent | Nobody: it is filing |
| 2. Read | Claude reads the invoice, extracts the fields in the statutory list and the amount, and shows each extracted value next to the original | A person checks anything marked uncertain |
| 3. Check | Compares the extracted fields with the seven items in s 6.1(1) and with the extra requirements in the contract that you have recorded. Lists what is missing, in plain words, before the invoice is sent | A person decides whether to send, fix or ask the owner |
| 4. Start the clocks | On confirmed receipt, proposes the seven, 14 and 28 day dates, the 35-day and seven-day subcontractor dates and, where relevant, the 90-day adjudication date | A person confirms each date |
| 5. Alert and record | Reminds the right people before each date, records any notice received or sent with its time, and keeps one timeline for the invoice | A person acts on every alert |
A second use is on the owner side. An owner or main contractor that receives invoices can have the system check them against the same list and flag, within the seven-day window in s 6.1(2), any deficiency a person may want to notify in writing. The decision to notify stays with a person.
For the build we would usually start with n8n or Make, which connect email, folders, spreadsheets and accounting systems quickly, and add custom code where a rule is particular to your contracts. This is a design description. We are not citing a client result for it, and we do not claim a construction case study.
Contracts, Invoices and Confidentiality
Contracts and invoices carry commercial terms and sometimes personal information. Before any AI model reads them, we would ask you to check the confidentiality terms of your contracts, decide which documents may be sent to a model, and record which model and where it runs. We would restrict who can see the documents, log who confirmed each date and agree how long records are kept. We are developers, not lawyers, and we do not make a statement here about privacy law. Ask your adviser about your obligations.
When Not to Automate
Not every Ontario contractor needs this. We would suggest something simpler if any of these is true.
| Your situation | What we would suggest |
|---|---|
| You send a few invoices a month on one or two contracts | The checklist above and a calendar. The system costs more than the problem |
| Your accounting package already produces invoices with all the required fields and you track dates there | Use it. Add only a received-date log |
| There is a live payment dispute or an adjudication notice has been given | Speak to a construction lawyer now. Software cannot repair a missed date |
| You want the system to decide whether an invoice is proper | We would not build that. We check against a list and a person decides |
| You also work in other provinces | The rules differ. We have not covered other provinces here, so we would research each first |
If a simpler option fits, we will say so on the first call. For the wider picture of what can be automated in a contractor's office, see our AI automation page and the US hub on AI automation for construction companies. The method carries across countries, but the rules do not.
How a Build Runs and What Moves the Quote
A first release is usually one contract type and one inbox. Here is how we would propose to run it.
- Walk through three real invoices. We look at what was sent, what was received and what the dates actually were.
- Write the checklist and rules with you. Statutory items, the contract extras and who confirms what, reviewed by your adviser.
- Test on past invoices. The system flags what was missing and proposes dates, and you compare them with history.
- Run beside your current routine. Alerts fire, a person confirms, nothing is relied on until it matches.
- Extend. Add subcontractor payments, holdback anniversaries or the owner side.
Prices vary with scope. What moves a quote is the number of contracts and invoice formats, how invoices reach you, whether you track subcontractor payments and holdback as well, and which accounting or project systems the alerts must reach. Calls, demos and releases are held on video. We begin with a short call about your budget range, then propose a scope that fits it. Our construction software and custom software development pages cover the wider systems.
Who This Suits and Your Next Step
This suits Ontario contractors and subcontractors who send several invoices a month, owners and main contractors who receive many, and anyone who has argued about whether a proper invoice was given. It does not suit a business that wants a verdict on its legal rights.
| A good fit | Probably not |
|---|---|
| Several contracts and invoices a month | A few invoices a year |
| Invoices arrive in different formats | A single template, always complete |
| A person will confirm every date | You want dates trusted blindly |
| You want one timeline per invoice, including notices | You want a legal opinion |
To start, use the contact form, tell us roughly how many invoices you send or receive in a month and the budget range you have in mind. We will come back after a short call with a written proposal. For a site-team tool that captures documents from the field, see our mobile app development page. Back to the Canada home page.
Straight Answers.
Tell us how invoices move through your business
Describe your contracts, how invoices are sent or received and what systems you use. Book a call and we will say what to automate, what to leave to a person and what the first release should contain.
- 30-minute online call
- Honest feedback on fit
- No obligation
- Book a call30 minutes online. Tell us what you want to build.
- Get a straight answerHonest feedback on fit and scope.
- DecideYou choose the next step once the scope is clear.