PSRA client accounts, demystified

Every euro of service-charge money an Irish managing agent collects on behalf of an Owners' Management Company belongs, legally, to that OMC — not to the agent. The agent is a custodian. And Irish law, through the Property Services Regulatory Authority, takes a very specific view of how custodians must handle money that is not theirs.

For many agents — particularly smaller practices that grew up running a handful of OMCs — the PSRA's client-account rules are a source of background anxiety rather than confident daily practice. The rules sound bureaucratic until you understand what they are designed to prevent: the thing that happens, in every profession that handles other people's money, when there is no mandatory segregation, no independent verification, and no consequences for commingling. That thing is embezzlement, sometimes accidental, sometimes deliberate, and always catastrophic for the people who trusted you with their money.

This guide explains the rules plainly, covers what the annual PSRA accountant's report actually involves, and sets out the one principle that technology vendors in this space must be held to: the software should never be in the flow of funds.

The PSRA D licence: what it is and who needs one

The Property Services (Regulation) Act 2011 established the PSRA as the statutory regulator for auctioneers, estate agents, letting agents, and property management agents in Ireland. The Act made it a criminal offence to provide a property service without holding the appropriate licence.

For managing agents — firms that manage multi-unit developments, commercial properties, or mixed-use schemes on behalf of owners — the relevant licence is the Class D licence: Property Management Services. The Principal of the practice (the individual who holds personal responsibility for the business's compliance) must hold a licence in their own name. Each employee providing property management services must also be licensed. The firm itself holds a separate licence, tied to the Principal.

The PSRA publishes a public register of licensed providers. Clients — OMC directors, owners, solicitors conducting due diligence on a transaction — can and do check it. An unlicensed agent managing an OMC is not just a regulatory problem; it is the kind of fact that surfaces in a sale-pack requisition or a Circuit Court hearing at the worst possible moment.

The client account obligation: segregation is not optional

The most important practical requirement of the PSRA regime is the mandatory separation of client money from the agent's own money. The Act requires that money received on behalf of clients — service charges, sinking fund contributions, insurance premiums collected for onward payment — must be held in a designated client account.

A client account is a bank account held in the agent's name but clearly designated as a client account. In practice, this typically means an account with "Client Account" in the account name or description, maintained at a recognised bank, separate from the agent's business current account. Many agents maintain a single pooled client account across all their OMCs; others maintain a dedicated account per OMC. Both approaches are permissible, but a pooled account requires particularly rigorous internal ledger accounting to ensure each OMC's balance can be identified and extracted at any time.

The prohibition on mixing — commingling client money with office money — is absolute. The agent's own fee income must be transferred out of the client account and into the operating account as soon as it is earned. Service charge money collected that is due to a contractor must be paid from the client account directly to the contractor, not routed through the office account and paid onward later. The moment office money and client money share a balance, the agent is in breach — even if the arithmetic happens to add up and nobody is out of pocket.

Commingling is a cardinal sin not because it always causes harm, but because it destroys the audit trail that proves harm did not occur. Once you cannot cleanly separate "my money" from "their money," you cannot prove you did not steal from them — and neither can anyone else.

The annual accountant's report: what it covers

The PSRA requires every licensed agent who holds client money to submit an annual Client Account Accountant's Report. This report is prepared by an independent qualified accountant — not the agent's own bookkeeper, and not the same person who manages the agency's statutory accounts unless they are sufficiently independent of the day-to-day client-account operation.

The accountant's work involves, at minimum:

• Confirming that the agent maintained one or more designated client accounts throughout the reporting period
• Reconciling the balance on the client account(s) against the agent's internal client ledger — that is, verifying that the total held in the bank accounts equals the total owed to all clients
• Verifying that there was no period during the year when the client account balance fell below the total amount owed to clients (a shortfall is a serious finding)
• Confirming that client money was not mixed with the agent's own funds
• Reviewing a sample of transactions to test that proper records were maintained and that receipts and payments are supported by appropriate documentation

The accountant does not audit every individual transaction. This is a targeted review, and its conclusions are only as reliable as the underlying records. An agent who maintains detailed, reconciled client ledgers — with every transaction referenced, dated, and matched to a bank statement line — will have a straightforward and relatively inexpensive accountant's report. An agent who maintains a spreadsheet of approximate balances and keeps invoices in a folder on the desktop will have a painful, expensive, and potentially inconclusive one.

The completed report is submitted to the PSRA along with the licence renewal application. A qualified report — one that raises exceptions or identifies deficiencies — is flagged by the PSRA and can trigger a formal investigation, a condition on the licence, or in serious cases a referral to the Complaints and Enforcement division.

Why reference-matching and reconciliation are compliance tools

Ask any accountant who has prepared PSRA reports for managing agents what makes the difference between an easy report and a difficult one, and the answer is almost always the same: whether the agent can match every euro coming in to the specific OMC and owner it belongs to, and every euro going out to the invoice or contractor it relates to.

This is the reference problem. When 400 owners in a portfolio send bank transfers each year — some using the reference on the invoice, some using their own naming convention, some sending nothing useful at all — and when GoCardless direct debits appear on a bank statement with the mandate reference rather than the owner's name, the job of reconciling the client account becomes a forensic exercise. Every unmatched transaction is a gap in the audit trail.

Good payment practice eliminates most of this friction at source:

• Every owner is assigned a unique payment reference that appears on every invoice and is pre-populated in any bank-transfer instruction
• Direct debit mandates are tagged to the owner and OMC at setup, so every collection automatically posts to the right ledger line without manual intervention
• Bank feeds are imported daily, and a reconciliation workspace allows transactions to be auto-matched, suggested-matched, or manually matched — with every unmatched item surfaced as a task, not buried in a statement
• Every disbursement from the client account carries a reference to the work order, invoice, or budget line it discharges, so the accountant can trace the full lifecycle of any euro

At year-end, the output of this process is not a spreadsheet with gaps — it is a fully reconciled ledger that the accountant can step through in hours rather than days, with exceptions already flagged and documented. That is the difference between a €600 report and a €3,000 one.

The cardinal rule for payment technology: never in the flow of funds

There is a version of "property management software with integrated payments" that is actually a platform that aggregates incoming payments into its own pooled account and then batches them out to agents on a settlement schedule. This model is common in e-commerce and hospitality technology. In Irish property management, it creates a serious regulatory problem.

If a technology platform holds service-charge money — even briefly, even as a pass-through — before settling it to the agent's client account, then the money is, at that moment, not in the client account. It is in the platform's account. The agent's client account balance is lower than the total owed to clients. That is the definition of a client-account shortfall. The accountant will find it. The PSRA will ask about it.

The platform, meanwhile, is almost certainly not a licensed payment institution under Irish or EU law — and if it is not, it should not be holding third-party funds at all. This is a regulatory exposure for the platform, but it becomes the agent's compliance problem, because it is the agent who holds the PSRA licence and the agent who submits the accountant's report.

The correct model is clean: payment rails (direct debit, card) are configured so that funds settle directly to the agent's client account. The software platform meters volume, generates references, manages mandates, and produces records — but it never holds money, never settles money on the agent's behalf, and never appears as an intermediary on a bank statement. The agent's client account is the first and only place the money lands before it is disbursed.

This distinction matters enormously when choosing a payment provider. Direct debit via GoCardless, for example, can be configured in two modes: a managed mode in which GoCardless holds and settles funds, and a partner mode in which GoCardless collects and settles directly to the merchant's (i.e. the agent's) own account. For PSRA compliance, only the direct-settlement model is appropriate. The same logic applies to card payments via Stripe: the agent should hold the Stripe account, and payouts should go directly to the client account — not to a platform intermediary.

How Cuan is built around the client-account principle

Cuan's money architecture is designed specifically for PSRA compliance. When an agency onboards onto Cuan, the GoCardless sub-account and the Stripe account are established in the agency's name. The agency is the merchant of record. Payouts are configured to settle directly to the agency's PSRA client account — not to Cuan, not to a pooled account, and not on a weekly batch schedule. Cuan does not hold client funds. It never appears in the flow of money.

What Cuan does hold is the data: the reference that links every collection to the owner, OMC, and charge it relates to; the mandate database that tracks direct debit authorisations; the reconciliation workspace that matches every bank statement line to the internal ledger entry. Every euro that passes through the payment rails is referenced, categorised, and reportable — by OMC, by budget line, by owner, by date range — so that the year-end accountant's report is a matter of export and review, not reconstruction.

The Open Banking feed imports the client account statement daily. The reconciliation workspace auto-matches on reference, surfaces unmatched items, and allows manual or suggested matching. Nothing falls through the gap silently. Directors can see a live balance through the portal — drawn from the Open Banking feed, not from Cuan's internal ledger — so the figure they see is the figure in the bank, verified independently of the software.

For agents who want to understand how Cuan handles data security and access controls around financial records, our security page covers encryption, access roles, and the audit log in detail.

The PSRA regime is not a compliance burden bolted onto property management — it is the reason clients trust managing agents with their money in the first place. Agents who understand the rules, maintain clean records, and choose technology that respects the client-account principle do not just pass the annual accountant's report. They run a practice that directors are confident referring, that owners trust, and that withstands scrutiny in the rare but consequential moments when scrutiny arrives.