Ontario's RTA changes land September 21. Most of them are date arithmetic.

Ontario's RTA changes take effect September 21, 2026: a seven day N4, a conditional N12, and a prescribed test for persistent late payment.

Published: 2026-09-16 · Author: Ahmed Heshmat · 11 min read

In short: Ontario's RTA changes take effect on September 21, 2026, and the expensive ones are not the headlines. The N4 termination date drops to seven days. An N12 stops carrying the month of compensation, but only if three conditions all hold. And persistent late payment finally has a prescribed test, one that counts payment dates and what each payment was applied to. Whether you can use that last one at all comes down to what your rent ledger can tell you about dates.

Key takeaways

  • For an N4 given on or after September 21, the termination date can be the 7th day after the notice, for every tenancy rather than just daily and weekly ones (RTA s.59(1), as replaced by Schedule 12 of Bill 60).
  • The one month's compensation on an N12 under s.48 falls away only where all three conditions hold: the notice is given on or after September 21, the termination date is at least 120 days out, and that date is the end of a period of the tenancy or the end of the fixed term. Miss the third and you still owe the month.
  • Persistent late payment now has a prescribed test in O. Reg. 516/06 s.8.1: rent unpaid seven days past due, on at least three occasions in any six month period, with a carve out for occasions where the lateness was only the result of the landlord applying a payment to something else the tenant owed.
  • A tenant who wants to raise their own issues at a non payment hearing must first pay half the arrears claimed in the application as filed, no later than seven days before the hearing.
  • Two claims circulating in this month's roundups are not in the statute. Fixed term leases still roll to month to month, and the qualified report for a renovation N13 is still waiting on a proclamation.

We are not lawyers and this is not legal advice. It is an operator's reading of the consolidated statute and regulation, done on September 16, 2026, and every claim below links to the source so you can check it against your own counsel.

What actually changes on September 21

Two bills are landing at once. Bill 60, the Fighting Delays, Building Faster Act, 2025, and Bill 97, the Helping Homebuyers, Protecting Tenants Act, 2023. Both got Royal Assent long ago and have been sitting in pieces waiting to be switched on. The LTB said in June that one set came into force July 1 and another was coming in September, without saying which. The answer is in the e-Laws consolidation, where twenty eight separate notes now read "On September 21, 2026, the day named by order of the Lieutenant Governor in Council."

Here is what those notes do.

The N4 gets shorter. Section 59(1) is repealed and replaced. The new wording is flat: notice of termination "effective not earlier than the 7th day after the notice is given." The old split, seven days for daily and weekly tenancies and fourteen for everything else, is gone. If you run monthly tenancies, your non payment clock halves.

The N12 compensation becomes conditional. New s.48.1(2) removes the requirement to pay a month's rent or offer another unit, but it is a three part test, and the third part is the one that will catch people. The termination date has to be at least 120 days after the notice, and it has to fall on the day a period of the tenancy ends, or at the end of a fixed term. A notice that is 130 days out but lands mid month buys you nothing.

Persistent late payment gets a number. For twenty years the N8 ground has been argued case by case, because nothing in the Act defined "persistent." New s.58(1.1) sends it to the regulations, and O. Reg. 241/26 fills it in. Three occasions in any six month period where rent went unpaid more than seven days past due. The regulation also says the list is not exhaustive, so this is a floor the Board can go beyond, not a ceiling.

Non payment hearings get a toll gate. Section 82, the provision that lets a tenant raise maintenance and other issues at your arrears hearing, is rewritten. The "explanation satisfactory to the Board" escape hatch in s.82(1)(b) is deleted outright. And two new requirements arrive: the tenant has to pay half of the rent arrears claimed in the application when it was filed, to you or into the Board, and under the new regulation that payment is due no later than seven days before the hearing.

Renovation files pick up a notification chain. If a tenant gives you notice preserving their right of first refusal, new s.53(2.1) makes you write to them three times: without delay after you receive their notice, telling them the estimated date the unit will be ready; without delay after that estimate changes; and without delay after the unit is actually ready. Then s.53(2.2) gives them at least 60 days from the ready date to take the unit back. Under new s.57.1(1.1), missing any of that is deemed a failure to afford the right of first refusal, and the limitation period for their application now runs to the later of two years after they vacated and six months after the work is done.

Eviction enforcement gets harder to postpone. Section 83(1)(b) is now subject to prescribed conditions, and s.8.4 of the regulation sets them. The Board may postpone enforcement only with your consent, or where it would not be unfair to you and the other tenants, and for anything other than an s.48, 49 or 50 notice, only where there are also compelling grounds.

Two things the roundups are getting wrong

We read the roundups first, the way anyone would, and two claims appear in several of them that the statute does not support.

The first is that fixed term leases will stop converting to month to month on September 21. Section 38 of the Act, which deems that renewal, carries no September note and no pending amendment. A fixed term that ends without being renewed or terminated still becomes a monthly tenancy on the same terms.

The second is that a renovation N13 will require a report from a qualified person confirming vacant possession is needed. That provision is real, it sits in Bill 97 Schedule 7, and it is still marked "On a day to be named by proclamation of the Lieutenant Governor." So is the regulation-making power that would define who counts as qualified, so neither arrives this month.

There is a third one worth flagging in the other direction. New s.57(6.1) creates a presumption of bad faith where nobody named in an N12 moved into the unit "within the prescribed period of time." The section switches on in September, but we could not find that period prescribed anywhere in O. Reg. 516/06 as it currently reads. A presumption with no trigger does nothing, which is the kind of gap that gets filled quietly by a regulation filed on a Friday.

Why three of these are ledger problems, not legal ones

Read the new persistent late payment test again as an operator rather than as a reader.

To count one occasion you need three facts about a single charge: the date the rent became due, the date the tenant actually paid it, and what that payment was applied to. Then you need to hold six month windows against a rolling calendar across every tenancy you manage, and you need to do it before the pattern lapses rather than after a tenant has stopped paying entirely.

The carve out is where this gets genuinely awkward. An occasion does not count if the lateness was "solely attributable to the landlord applying a rent payment made during that six month period to another amount owing by the tenant, including rent arrears." Most accounting systems apply an incoming payment to the oldest open balance by default. That default is exactly the fact pattern the regulation excludes. So a tenant who paid on time every month, into a system that quietly routed each payment at an old arrears balance, can look persistently late in your ledger and not be persistently late in law. Check how your system allocates before you count anything.

The other two are the same shape. The half arrears rule turns on a number frozen at filing and a date seven days before a hearing that moves when the hearing moves. The right of first refusal chain turns on three written notices triggered by events, one of which is "the unit is ready," which almost no property management system records as a date at all.

None of this is difficult work. It is detailed and dated, and it sits across systems that were never built to be asked these particular questions.

What AI is good for here, and what it is not

The honest division of labour, in the order we would build it.

Watching the sources. The e-Laws consolidation, the regulation, and the LTB's operational updates are all public pages that change without telling you. A scheduled job that fetches each one, diffs it against the last version, and flags what moved is a few hours of work and it is the difference between finding a prescribed period in week one and finding it in a hearing. The LTB also started publishing its final orders to Ontario's Open Data Catalogue in July, which makes the Board's own reasoning something you can read in bulk for the first time.

Doing the arithmetic against your own data. This is the part that pays. Pull the ledger, compute per charge lateness with the allocation carve out applied, hold the six month windows, and surface the tenancies that meet the test while there is still time to act. Same for the N1 calendar, the 120 day N12 dates that have to land on a period end, and the renovation notification chain. We do this work inside Buildium, AppFolio and Yardi rather than beside them, because a compliance list in a separate dashboard is a list nobody opens.

Drafting the paperwork, with a person signing it. A system can assemble the notice, fill the dates, and attach the ledger extract that supports it. A person reads it and serves it. We have written before about where AI actually lands in a property management operation, and this is the same boundary: the machine does the retrieval and the arithmetic, the human owns the decision that has consequences at a tribunal.

What AI should not do here is tell you what the law means. Ask a general purpose model about the September changes today and it will confidently repeat the fixed term lease claim, because that claim is all over the web and the statute is not. Retrieval against the primary source is the whole trick, and even then somebody who knows the file has to read the answer.

Before September 21

Four things, and none of them need a vendor.

First, pull the N1 calendar, because it carries the nearest deadline. The guideline for 2027 is 1.9%, notice is 90 days under s.116, and October 3 is the last day to serve for a January 1 increase, not the first. We wrote up what the 1.9% does to an operating budget separately.

Second, check how your system allocates a payment against an open balance. That single setting decides whether your persistent late payment counts mean anything.

Third, write down which of these dates you actually hold today and which ones you would have to go hunting for: due date, paid date, allocation, arrears as filed, hearing date, unit ready date.

Last, decide what happens on September 22, when the first N4 goes out on the new clock and somebody has to be sure the date on it is right.

If you run rental stock in Ontario and the fourth one is a person rather than a system, that is the conversation we have on a free call, and it is the same thing an AI audit is for.