Toronto Airbnb record keeping is one short provision of Chapter 547 that almost nobody reads until the City asks. Every operator must keep a record of each concluded transaction for three years, and produce it within 30 days of a request from Municipal Licensing and Standards.
The rule is four lines long. The exposure is bigger than that, because the platform you booked on is separately required to keep the same data about you, and because these records are deemed to double as Municipal Accommodation Tax records.
The Three-Year Rule
Toronto Municipal Code Chapter 547 puts the record keeping duty squarely on the operator, not on the platform and not on your property manager:
"A. Every operator shall keep a record of each concluded transaction related to the operator's short-term rental for three years following the date of the transaction. A transaction is concluded on the last day of the rental period. The records retained shall include the following: (1) The number of nights the short-term rental was rented; (2) The nightly and total price charged for each rental; (3) Whether the rental was an entire-unit rental or partial-unit rental; and (4) Any other information required by the Executive Director." Toronto Municipal Code § 547-4.5.A
Two things carry weight here. The duty attaches to each transaction, so it is a per booking obligation and not a yearly summary. And the retention period is fixed at three years by the bylaw itself, which is a different number from the one that applies to your tax records. More on that below, because conflating the two is the most common mistake we see.
When the Clock Actually Starts
The bylaw defines the trigger in a single sentence: a transaction is concluded on the last day of the rental period. Not the booking date. Not the payment date. Not the payout date.
For a normal two night weekend that distinction is trivial. For a long stay it is not. Take a guest who books in November, pays in full immediately, checks in on December 28, and checks out on January 4. The transaction concludes on January 4, so the record must survive until January 4 three years later. If you purge by booking year, you would have thrown that record out a full year early.
The same stay is also the classic place where a host's own night tally goes wrong, because part of it falls in one calendar year and part in the next while the entire-unit cap of 180 nights is measured per calendar year. Log the check-in date and the check-out date as separate fields, not just a night count, so the split can be worked out later without guessing.
The Four Required Fields, and Why Four Is Not Enough
§ 547-4.5.A names exactly four things you must retain:
- Nights rented. The number of nights the short-term rental was rented.
- Price. The nightly and total price charged for each rental, so both figures, not just the payout.
- Rental type. Whether the rental was an entire-unit rental or a partial-unit rental. This one matters because the 180 night cap applies to entire-unit rentals.
- Anything else the Executive Director requires. Clause (4) is open ended by design.
Clause (4) is the reason a minimalist log is a bad idea. The bylaw lets the Executive Director require additional information, and § 547-5.1.A reaches even further, to any document that relates or may relate to information that is or should be in your books. Practically, the cheapest insurance is to log more than four fields from day one, because reconstructing a check-in date or a platform reference two years later is far harder than typing it at the time.
The 30-Day Demand
Subsection B is the part with the deadline attached:
"B. Every operator shall provide the information referred to in Subsection A to Municipal Licensing and Standards within 30 days of being requested to do so by Municipal Licensing and Standards." Toronto Municipal Code § 547-4.5.B
Thirty days sounds generous. It stops sounding generous when the request covers three years of stays spread across two booking platforms, a handful of direct bookings, a change of property manager, and an email account you no longer use. Reconstructing that from scratch inside a month is a genuinely bad month.
There is also a second, faster track. A records request under § 547-4.5.B carries the 30 days. A formal audit does not repeat that number:
"A. For the purpose of investigating compliance with this chapter, the Executive Director may audit or examine all books and records and any account, voucher, letter, facsimile, and electronic or other document held by a short-term rental company or operator that relates or may relate to information that is or should be in the person's books or records. B. A short-term rental company and operator shall comply with all audit directions given by the Executive Director within the time he or she specifies, including: (1) Giving the Executive Director all reasonable assistance with her or his audit or examination; (2) Answering all questions relating to the audit or examination either orally or, if the Executive Director requires, in writing, on oath, or by statutory declaration..." Toronto Municipal Code § 547-5.1
Read that carefully. Audit directions are due within the time the Executive Director specifies, which is not automatically 30 days. You also owe reasonable assistance and answers, potentially in writing, on oath, or by statutory declaration. A statutory declaration about numbers you are reconstructing from memory is a situation to avoid entirely, and the way to avoid it is a running export rather than a scramble.
The Platform Is Reporting the Same Data About You
This is the part hosts underestimate. Chapter 547 imposes a mirror obligation on the booking platform, and the platform's version includes your identity:
"Every short-term rental company shall keep a record of each concluded transaction in relation to a short-term rental listed or advertised on its platform for three years following the last day of the rental period. A transaction is concluded on the last day of the rental period. The records retained shall include the following: (1) The full name, address, and registration number of the operator, as listed on the corresponding operator's registration issued under this Chapter; (2) The number of nights the short-term rental was rented; (3) The nightly and total price charged for the short term rental; (4) Whether the rental was an entire-unit rental or partial-unit rental; and (5) Any other information required by the Executive Director." Toronto Municipal Code § 547-3.3.A
Your name, your address, your registration number, your nights, your prices, and your rental type, all held by the company and all subject to the same audit power under § 547-5.1.A. Meanwhile the City asks you to state your own number every year at renewal:
"An application for the renewal of an operator's registration shall be in the form approved by Municipal Licensing and Standards and shall require the applicant to specify the number of nights the property was used as a short-term rental in the previous year." Toronto Municipal Code § 547-4.1.C
Put those two provisions next to each other and the picture is obvious. The City has a platform sourced night count and a host declared night count for the same unit and the same year. Inconsistencies are visible without anyone knocking on your door. That is not a reason to panic, it is a reason to reconcile your own log against every platform export before you sign a renewal declaration.
Direct Bookings Are Exactly Where Hosts Lose Track
§ 547-4.5.A applies to each concluded transaction related to the operator's short-term rental. There is no exemption for bookings that never touched a platform. A repeat guest who texts you and pays by e-transfer is a transaction, and it belongs in your record with the same four fields as any Airbnb stay.
Those nights also count toward the 180 night entire-unit cap, and they count toward the number you declare at renewal under § 547-4.1.C. The asymmetry is worth noticing: the platform's report under § 547-3.3.A will only ever show the platform's own bookings, so a host who declares only what the platform shows will understate their year. Your log is the only place the full picture exists, which makes it the document that protects you rather than the chore that annoys you.
Your Chapter 547 Records Are Also Tax Records
The bylaw explicitly wires short-term rental records into Municipal Accommodation Tax enforcement:
"All records and information that must be maintained by a short-term rental company or operator or that may be audited, examined, or collected by Municipal Licensing and Standards under this chapter are deemed to be collected and properly used for the purposes of administering and enforcing Chapter 758, Taxation, Municipal Accommodation Tax." Toronto Municipal Code § 547-5.5.D
So the log you keep for licensing purposes can be used to test your MAT position. Toronto's MAT is currently 6 percent. A temporary rate of 8.5 percent ran from June 2025 to July 2026 and has now ended, which means bookings from that window sit at a different rate than bookings today. If your records do not carry the rental dates and the amounts charged, you cannot demonstrate which rate applied to which stay.
One point to be precise about, because getting it wrong is expensive. Chapter 547 sets three years and only three years. It says nothing about how long you must keep MAT records. MAT retention lives in the City's separate tax rules under Chapter 758, and tax record retention is commonly cited as seven years. Do not assume the three year rule in § 547-4.5.A discharges your tax obligation, and do not read a seven year figure into Chapter 547, because it is not there. Confirm the MAT retention requirement directly with the City and then keep your records for the longer of the two periods. In practice that means one archive, kept for the longer period, that satisfies both.
A Log That Actually Works
You do not need software for this. A single spreadsheet with one row per booking clears § 547-4.5.A with room to spare, provided it carries these columns:
- Check-in date and check-out date. Separate columns. This is what makes the retention clock and the calendar year split calculable later.
- Number of nights. Required by clause (1), and worth storing rather than recomputing.
- Nightly price and total price charged. Both, because clause (2) asks for both. Record the price charged to the guest, not just your net payout.
- Entire-unit or partial-unit. Required by clause (3), and the field that drives the 180 night cap.
- Platform or direct. Not required by the bylaw, but this is the column that lets you reconcile against a platform export and spot what is missing.
- Guest reference. The confirmation code or booking reference, so any single row can be traced back to a source document.
- MAT collected and remitted. Again not in § 547-4.5.A, but § 547-5.5.D means these records serve tax enforcement too.
Then two habits. Export from every platform on the same day each month and paste the rows in, rather than trusting that the data will still be downloadable in three years. And back the file up somewhere outside the platform account, because a suspended or closed account takes its booking history with it.
What to Do
- Start the log today, not at year end. § 547-4.5.A is a per transaction duty and it is already running on every stay you have hosted in the past three years. Backfill what you can while the platform exports still reach back.
- Export monthly from every platform. Same day each month. Toronto Airbnb record keeping fails most often because someone assumed the data would always be one click away, and then an account changed or a listing was archived.
- Capture direct bookings by hand. They are transactions under § 547-4.5.A, they count toward the 180 night cap, and no platform report will ever surface them for you.
- Reconcile against your MAT filings. § 547-5.5.D means the same records are deemed collected for MAT administration. If your log and your remittances disagree, find out why before the City does.
- Keep a running night total. You need it twice: for the entire-unit cap during the year, and for the declaration § 547-4.1.C forces you to make at renewal. A number you can defend beats a number you estimated in the renewal form.
- Get the history at manager handover. The obligation under § 547-4.5.B is yours, not your manager's. Ask for a full booking export in spreadsheet form on the way in and on the way out.
- Have someone keep it current for you. At Nurture, the booking record, the night count, and the MAT trail are maintained as part of managing the property, so a 30 day request from the City is a file you send rather than a month you lose.
Frequently Asked Questions
How long do Toronto Airbnb hosts have to keep records?
Three years. Toronto Municipal Code § 547-4.5.A says every operator shall keep a record of each concluded transaction related to the operator's short-term rental for three years following the date of the transaction. The same subsection defines when a transaction is concluded: the last day of the rental period. So the three year clock runs from checkout, not from the booking date and not from the date you were paid.
What records does the City require Toronto Airbnb hosts to keep?
§ 547-4.5.A lists four items: the number of nights the short-term rental was rented, the nightly and total price charged for each rental, whether the rental was an entire-unit rental or a partial-unit rental, and any other information required by the Executive Director. The fourth item is open ended, which is the practical reason to log more than the bare minimum.
When does the three year clock start on a Toronto Airbnb booking record?
On the last day of the rental period. § 547-4.5.A states that a transaction is concluded on the last day of the rental period. A stay that checks out on January 4 is retained until January 4 three years later, even if the guest booked and paid the previous November. For stays that straddle a year end, log both the check-in and the check-out date so the nights can be allocated correctly.
How fast do I have to hand over my records to the City of Toronto?
Within 30 days. § 547-4.5.B says every operator shall provide the information referred to in Subsection A to Municipal Licensing and Standards within 30 days of being requested to do so. Note that a formal audit runs on a different clock: § 547-5.1.B requires compliance with all audit directions within the time the Executive Director specifies.
Do direct bookings count toward Toronto Airbnb record keeping?
Yes. § 547-4.5.A applies to each concluded transaction related to the operator's short-term rental. It does not carve out bookings that never touched a platform. A direct booking, a repeat guest paying by e-transfer, and a stay sold on a smaller listing site all belong in your record, and they also count toward the 180 night entire-unit cap.
How is Chapter 547 record keeping different from MAT record keeping?
Chapter 547 sets one number: three years, in § 547-4.5.A. Municipal Accommodation Tax retention comes from the City's separate tax rules in Chapter 758, and tax record retention is commonly cited as seven years. Chapter 547 does not state a MAT retention period, so do not assume the three year rule covers your tax obligation. Confirm the MAT requirement directly with the City and keep to the longer of the two.
Does Airbnb report my Toronto booking data to the City?
The platform keeps and is required to retain the same data about you. § 547-3.3.A requires every short-term rental company to keep, for three years following the last day of the rental period, the operator's full name, address and registration number, the number of nights rented, the nightly and total price charged, whether the rental was entire-unit or partial-unit, and any other information required by the Executive Director.
What happens if my records do not match the platform's records?
The mismatch is visible to the City. The platform holds your night counts and prices under § 547-3.3.A, and § 547-4.1.C requires your renewal application to specify the number of nights the property was used as a short-term rental in the previous year. Those two numbers sit side by side. Reconcile your own log against every platform export before you file a renewal.
Can the City audit my Toronto short-term rental records?
Yes. § 547-5.1.A lets the Executive Director audit or examine all books and records and any account, voucher, letter, facsimile, and electronic or other document held by an operator that relates or may relate to information that is or should be in the person's books or records. § 547-5.1.B adds a duty to give all reasonable assistance and to answer questions orally or, if required, in writing, on oath, or by statutory declaration.
My property manager has my booking history, is that a problem?
It is a problem at handover. § 547-4.5.A puts the record keeping duty on the operator, and § 547-4.5.B puts the 30 day production duty on the operator too. If a manager leaves with the only copy of two years of stays, the obligation stays with you. Ask for a full booking export in a spreadsheet format at the start of any management change, not after.
This article is for informational purposes only and does not constitute legal, tax, or accounting advice. The three year retention period quoted here comes from Toronto Municipal Code Chapter 547. Municipal Accommodation Tax retention is governed by separate City rules under Chapter 758 and is not set by Chapter 547. Bylaw details and tax rates change. Always verify current requirements directly with the City of Toronto and Municipal Licensing and Standards before making hosting decisions. Rules quoted from Toronto Municipal Code Chapter 547, consolidated to January 1, 2025.
Would You Survive a 30-Day Records Request?
If reconstructing three years of bookings sounds like a bad month, we already do this for the properties we manage. Booking records, night counts, and the MAT trail stay current so a City request is a file you send. We manage Airbnb properties across Toronto and the GTA.
Get Your Free Estimate