Most Irish property managers treat RTB compliance as a legal problem. They consult a solicitor when a dispute arises, they try to remember the correct notice periods before sending a rent review, and they keep a folder somewhere with RTB correspondence. The problem is not ignorance of the rules — it is the absence of a system that enforces them automatically.
RTB compliance is a systems problem before it is a legal one. The failures that generate disputes and penalties are almost always operational: a notice issued on the wrong date, a tenancy registered late, a rent review calculated without the correct RPZ cap, a documentation trail that cannot be produced on request. These are not failures of legal knowledge. They are failures of process.
The 4 RTB workflows every property management system must handle
A properly configured property management system should make the following four RTB workflows automatic — not manual tasks that depend on someone remembering to do them.
1. Tenancy registration
Under the Residential Tenancies Act, landlords are required to register new tenancies with the RTB within one month of the commencement date. For most operators managing multiple properties, this is a recurring administrative task that gets missed — particularly when tenancies turn over quickly during peak letting seasons.
In a connected system, tenancy registration is triggered automatically when a new tenancy is created. The system generates the required details, flags the one-month deadline, and creates a task for the property manager. The registration date is recorded, and the tenancy record includes a complete RTB registration history.
2. RPZ rent review calculation
Rent Pressure Zones cover most of the major urban areas in Ireland, and within them, rent increases are capped at the lower of 2% per annum or the rate of inflation as measured by the HICP. The calculation is not complicated — but it needs to be done correctly every time, and it needs to be documented.
In a spreadsheet-based system, this calculation happens in whatever way the property manager remembers. In a connected system, the RPZ cap is applied automatically when a rent review is processed. The system calculates the maximum permitted increase, documents the basis for the calculation, and stores the result against the tenancy record.
3. Notice of rent review
A landlord must give at least 90 days’ written notice before a rent review takes effect. The notice must state the new proposed rent and the date from which it applies. Issuing the notice too late, or with incorrect information, makes the rent review procedurally invalid — even if the rent increase itself would be permissible under the RPZ rules.
In a connected system, rent review dates are tracked from the tenancy record. When a review date approaches — typically 120 days out, to give adequate preparation time — the system flags the upcoming review, generates a draft notice with the calculated new rent, and prompts the property manager to review and send. The notice issue date is recorded, and the correct effective date is calculated automatically.
4. Dispute documentation
If a tenant disputes a rent review or refers a tenancy matter to the RTB, the property manager needs to be able to produce a complete paper trail: the tenancy agreement, all correspondence, rent review notices, payment records, and any maintenance or repair communications relevant to the matter. In a system where this documentation is scattered across email folders and WhatsApp chats, producing it under pressure is a significant problem.
In a connected system, all tenancy documentation is stored against the property and tenancy record. Rent review notices, correspondence logs, maintenance job records, and payment histories are all retrievable from a single screen — and can be exported as a package if required for RTB proceedings.
How most Irish property managers handle this today — and why it fails
The most common approach is a combination of calendar reminders, spreadsheet tracking, and email folders. For a portfolio of fewer than 20 properties, this can work — with effort and attention. For a portfolio of 50 or more, it becomes a compliance risk.
The specific failure modes are predictable. Rent review dates get missed because the calendar reminder goes unnoticed during a busy period. RPZ calculations get done without proper documentation because there is no prompting to record the basis for the calculation. Tenancy registrations get delayed because the one-month window falls during a busy month-end period.
None of these failures are caused by bad intentions. They are caused by a system — the spreadsheet and email system — that is not designed to enforce process. It surfaces tasks only when someone actively checks, and provides no automatic escalation when deadlines are missed.
What a properly configured PropertyManagementOS does differently
PropertyManagementOS, as configured by Inovada, treats RTB compliance as a set of automated workflow rules rather than a checklist to be manually maintained. Tenancy records contain structured fields for commencement date, review dates, RPZ designation, and current rent. These fields drive automatic task creation, notice generation, and deadline tracking.
The result is not a system that makes compliance impossible to miss — it is a system that makes compliance the default outcome rather than something that requires active effort. The property manager’s job shifts from remembering compliance tasks to reviewing and approving outputs that the system has already generated.
If you are managing more than 30 properties in Ireland and RTB compliance is currently dependent on calendar reminders and spreadsheet tracking, the risk of a procedural failure — and the dispute that follows — is higher than it needs to be. The solution is not more careful attention. It is a system that enforces the process automatically.
To see how PropertyManagementOS handles RTB workflows in practice, book a discovery call and we’ll walk through your current setup and show you exactly what a connected system looks like.