Ireland NLWT Rental Notification Guide

The Ireland NLWT Rental Notification workflow is role-based. When rent is paid to a non-resident landlord, 20% of that payment is withheld and remitted to Revenue through the Non-Resident Landlord Withholding Tax system. If a collection agent is handling the rent, that collection agent can submit a single RN, set up a repeat monthly RN, or upload RNs in bulk by CSV. If there is no collection agent, the tenant or other direct payer makes the RN instead. In both cases, the withheld amount is not the landlord's final tax bill. It becomes a credit the non-resident landlord later uses on Form 11 or CT1.

That role split matters more than most search results admit:

• Collection agent using NLWT: withholds 20%, files the RN, and remits the deduction through the system.
• Collection agent remaining chargeable: does not use the NLWT system and stays responsible for the landlord's rental-income tax position.
• Tenant or other direct payer: files the RN and remits the deduction where no collection agent is engaged.

The RN is therefore the operating record of who paid the rent, who made the deduction, which property the payment relates to, and which landlord should eventually get the credit.

The timing is also more specific than the older shorthand many practitioners still repeat. According to Revenue's NLWT Tax and Duty Manual, individual tenants should make the Rental Notification within 7 days of payment and deduction, while collection agents should make it on or before the 1st day of the following month. That is current Revenue guidance for the live system. It replaces the looser habit of describing every case as a 21-day filing obligation.

The system itself only came into operation on 1 July 2023, so a current rental notification ROS Ireland workflow is about electronic RNs, not the older paper route. That distinction matters because the RN now drives the later tax-credit trail. The non-resident landlord still files their own annual return under their own tax reference number, but the RN is what makes the withheld amount visible and usable in that process. If the RN is not made by the right person, or is made with the wrong identifiers, the annual credit problem starts long before Form 11 or CT1 is filed.

What changed on 1 July 2023 and why Form R185 is no longer the live workflow

Before 1 July 2023, the Irish withholding system for non-resident landlords worked very differently in practice. Where a tenant paid a non-resident landlord directly, the old paper route revolved around Form R185. Where a collection agent was appointed, that collection agent was generally the chargeable and assessable person for the landlord's rental income. In other words, the agent was not just passing along a withholding record. The agent sat inside the landlord's Irish income-tax compliance position.

The NLWT system changed that operating model. From 1 July 2023, the live process moved to electronic Rental Notifications made through Revenue's system. A collection agent who deducts 20% and submits the required RN information through NLWT is no longer treated as the chargeable person for that rental income. The non-resident landlord remains responsible for the annual return under their own TRN, whether that return is Form 11 for an individual or CT1 for a company. That is why current guidance treats the RN as the month-by-month compliance record and the annual return as the year-end tax settlement.

This is also why older articles can still mislead readers even when they are not completely wrong. They often describe the old paper evidence trail, or they explain the pre-2023 collection-agent position without making clear that the workflow has moved on. Form R185 still matters as historical context for work done before 1 July 2023, but it is not the live filing mechanism for current tenant or collection-agent withholding under NLWT.

There was a one-off 2023 transition issue because the system began mid-year. Revenue allowed a concessionary approach so non-resident landlords and collection agents were not forced into an unnecessarily messy two-return result for that year. For current operational work, though, the useful distinction is simpler: either the collection agent is engaging with NLWT and the RN system, or the collection agent is electing to remain chargeable and staying outside it.

That election still matters. A collection agent can choose not to make RNs and remain chargeable instead, but that choice keeps the tax risk with the agent and gives up the tools the NLWT system provides, including repeat RNs, bulk uploads, and landlord-side pre-population of withheld credits. For most readers, the practical question is not whether the law changed in theory. It is whether this month's rent is being handled in the current RN system or under a chargeable-agent alternative that carries very different consequences.

---

The information you need before you can file a correct RN

Most RN problems are data problems before they are tax problems. The system is straightforward once the filer has the right landlord record, the right property identifier, and the right filing path. Without that, the RN may still be submitted, but the withheld amount can end up hard to trace or hard for the landlord to claim later.

For a collection agent, Revenue's starting set is broader than many landlord clients expect. The agent needs the landlord's name and address, the property's LPT ID, and the landlord's TRN plus tax type. The tax type matters because the RN has to point toward the correct annual-return path, Income Tax for an individual landlord or Corporation Tax for a company. A tenant paying directly does not need that full tax-identity set to get an RN made. The tenant instead needs the landlord's name and address, the property's LPT ID, and the landlord's email address or phone number. That lighter data requirement makes the tenant route workable, but it also means the landlord may need to claim the RN later if the filing did not include enough tax-reference detail to attach it automatically.

The property identifier is where operational files often go wrong. For standard residential property, the reference point is the LPT ID. But not every rental property fits that model. Revenue's manual makes clear that commercial property, agricultural land, and certain long leases where the tenant carries the Local Property Tax position do not use an LPT ID in the usual way. In those cases the non-resident landlord has to create a Commercial Premises or Land ID inside the NLWT system and pass that identifier to the tenant or collection agent. The filer cannot generate that substitute ID on the landlord's behalf.

That is why property onboarding matters. A collection agent managing mixed portfolios cannot assume every Irish rental is a standard residential unit with a ready LPT number. A landlord with retail or office property may need the same identifier discipline that sits behind related workflows such as Irish commercial rates bill extraction, where the property record has to match the obligation being reported. If the wrong identifier is used on an RN, the landlord-side credit trail becomes harder to reconcile even if the 20% deduction itself was correct.

Tax agents feel this problem at year end. Revenue allows tax agents linked to the client to access NLWT records and, if necessary, claim RNs when they know the relevant LPT ID or Commercial ID. That means the identifier is not just a filing-stage input. It is also the handle that lets advisers recover an RN when a tenant filed without the landlord's TRN or when a property had to be matched by property record rather than tax number. In practical terms, the RN is only as clean as the landlord and property master data supporting it.

Collection agent workflow: single RNs, repeat RNs, bulk CSVs, and audit trail

For a collection agent, the working sequence starts when rent is received, not when the annual return is being assembled. The agent identifies the gross rent for the tenancy, withholds 20%, submits the RN through the NLWT system, and remits the withheld amount to Revenue. That sounds simple when there is one landlord and one property. It becomes a real process problem when the same agency is running multiple non-resident landlords, multiple properties, and recurring monthly receipts that have to be matched accurately every time.

Revenue gives collection agents three ways to handle that filing load. A single RN works for one-off or first-time payments. A repeat RN is the practical tool for stable monthly arrangements because it creates an instruction to generate an RN at monthly intervals. A CSV upload is the scale option for agencies managing multiple landlords or larger rent books. The repeat route is especially useful because the system is built around recurring monthly filings, but it is not instant. Revenue says the first debit date for a repeat arrangement must be at least eight days in the future, so the first month is usually handled as a standard RN and later months move into repeat mode.

The CSV route is where process quality starts to matter more than tax knowledge. A bulk file saves time only if the landlord names, property IDs, and tax references are already clean. If a validation rule fails, the file does not quietly pass through with one bad row excluded. The filer has to correct the issue and re-submit the full file. That is why teams mapping NLWT into broader financial document automation workflows tend to treat rent receipts, landlord identifiers, and property references as one controlled dataset rather than as separate admin tasks.

The system also provides the controls collection agents need after filing. Search and report functions let the agent review what has been submitted in a period. An RN can be amended within Revenue's constraints, and if the practical need is to remove an RN, the deletion route is to amend the payment amount to zero. The system can also generate PDF acknowledgements for single RNs or grouped RNs, which gives the non-resident landlord a formal record of tax deducted. That audit trail becomes more valuable when the agency is also trying to keep its own client-money records straight, which is why a controls-oriented workflow often sits alongside related bookkeeping work such as letting agent client account reconciliation and an accountant-ready PSRA Section 35 reconciliation pack.

The alternative is to stay outside NLWT altogether by remaining chargeable. That may still suit a small number of collection agents, but it means giving up repeat RNs, bulk uploads, acknowledgement PDFs, and the landlord-side visibility created by proper RN filing. For most operational teams, the real question is not whether the system exists. It is whether the incoming rent data is organised well enough to use the system without generating a monthly correction cycle.

Tenant-direct filings and how the landlord gets the Form 11 or CT1 credit

The tenant path only applies where there is no collection agent in the middle. If a non-resident landlord has engaged a collection agent and rent is paid to that agent, the tenant has no further NLWT role. That point sounds basic, but it removes a lot of confusion in mixed files where someone assumes the tenant should still withhold even though the collection agent is already operating the RN process.

Where the tenant pays the non-resident landlord directly, the tenant must use myAccount or ROS to make the RN and remit 20% of the rent to Revenue. The remaining 80% is then paid to the landlord. That is the practical meaning of NLWT tenant withholding in Ireland under the live system. The tenant is not filing the landlord's annual return and is not stepping into the wider chargeable-person role that a pre-2023 collection agent might have held. The tenant is creating the withholding record that lets Revenue and the landlord see what tax has already been remitted against that rental income.

Revenue gives tenants the same core RN options as collection agents: single input, repeat monthly RNs, and CSV upload. In most direct-tenancy situations, the useful distinction is between a one-off single RN and a repeat RN for ongoing monthly rent. Bulk upload exists, but it is more relevant where one payer is managing multiple properties or similar repeated payments. What matters operationally is that the tenant files promptly, uses the right property identifier, and understands that the RN is part of the landlord's later credit trail.

That credit trail is the landlord-side consequence many tenant-focused summaries leave thin. A landlord still has to file Form 11 or CT1 under their own TRN. If the tenant filed the RN without the landlord's TRN or PPSN and tax type, the landlord may need to claim the RN in the NLWT system using the property's LPT ID or Commercial ID before the record appears in search and before the withheld amount can flow properly into the annual-return process. Once associated correctly, the RN data can pre-populate the landlord's return with both the gross rental income and the withheld credit.

This is where tax advisers often enter the picture. A tax agent linked to the landlord can review the RN record and claim missing RNs where the property identifier is known. So the landlord-credit side of a Form 11 NLWT credit claim in Ireland is not a separate compliance universe. It depends directly on whether the tenant-created RN was made with enough clean data for Revenue's system to match it back to the right landlord and the right property.

---

Common mistakes, Irish edge cases, and the UK comparison that trips people up

One of the fastest ways to get Ireland wrong is to import UK assumptions into the file. Ireland's RN system is not the same as the UK NRLS quarterly-return pattern, and a reader who brings UK deadlines or UK forms into an Irish rent file can end up following the wrong timetable altogether. If that comparison needs a refresher point of reference, use the UK non-resident landlord scheme quarterly return guide as a separate regime, not as a model for Irish filing mechanics.

The most common Irish errors are more operational than conceptual. An RN is made against the wrong property identifier, the landlord's details are incomplete, or the filing is simply late because the payer assumed the withholding could be sorted out at year end. None of those mistakes changes the underlying obligation. They just turn a clean withholding record into a correction exercise. That matters because the RN is the record that supports the landlord's later credit claim. If the record is wrong, the year-end problem is not abstract. It is visible in missing search results, harder claims, and extra adviser work.

Some edge cases are easy to miss if the portfolio is not simple. Joint ownership is one. If only one owner is non-resident, the RN and deduction follow the amount paid to that non-resident owner. If jointly owned non-resident landlords are filing separate returns, separate RNs are needed so the credit can attach correctly to each landlord. Housing-support arrangements are another. In a HAP or RAS-style setup, the RN responsibility follows whoever is making each rent payment. If a local authority pays one portion, the authority makes the RN for that leg as tenant or other payer. If a tenant pays a top-up, that top-up needs its own RN through the tenant or collection-agent path.

The safest way to troubleshoot an Irish file is to work through the live payer path in order:

• Confirm who actually paid the rent, tenant, local authority, collection agent, or another direct payer.
• Confirm whether a collection agent is engaging with NLWT or has elected to remain chargeable outside the RN system.
• Confirm the property identifier that should be used, LPT ID for standard residential property or the landlord-generated Commercial Premises or Land ID where Revenue requires it.
• Confirm how the non-resident landlord will see and use the RN later, either by automatic linkage through tax identifiers or by claiming the RN through the property ID route.