Back to resources

Guide

Payment reminders and arrears collection

Collect common expenses on a schedule, not from memory. This guide sets out the reminder cycle, the fallback for owners without an account, the confirmations that stop the follow-up calls, and one escalation procedure for the whole portfolio. It applies to co-owned buildings across Europe; the legal route is illustrated with Cyprus, Spain and Germany.

The problem

Why manual collection breaks down

Most management companies chase overdue common expenses by hand. Four things go wrong, in every country.

Late payments compound quietly

Without a reminder at the right moment, a missed month becomes three. By the time the manager notices, the owner is facing a demand for a sum they did not see coming, and the conversation starts badly.

Manual follow-up does not scale

Calling or emailing each owner by hand takes hours every month and depends on someone remembering. As the portfolio grows, follow-up becomes irregular, and irregular follow-up is what owners learn to ignore.

Owners without an account hear nothing

An owner who never created a portal account receives no in-app notification. Without an email fallback they learn about a balance only when someone contacts them, or when the unit is sold.

Uneven communication is read as unfair

When some owners receive reminders and others do not, or tone and timing differ between buildings, owners question whether the process is fair. A collection procedure that cannot be described cannot be defended at the AGM.

Collection framework

Five steps that put collection on a schedule

Replace remembered follow-up with a cycle that runs whether or not anyone is at their desk. Each step below names the mechanism.

  1. 01

    Send reminders on a fixed weekly schedule

    Run one reminder job for the whole portfolio. Every Monday morning it reads each owner's latest final statement, takes the amount billed less every payment received against it, and notifies each owner with a balance through the in-app inbox and by email, naming the building and the amount. Nobody has to remember who owes what; the job reports how many reminders went out and to whom.

  2. 02

    Reach owners who have no account

    Not every owner creates an account when they are added. When a statement is issued, a payment is recorded or a reminder is due and the owner has no portal account, a short branded email goes to the address on file instead. It says what changed and for which building, and carries a link to create the account. Nothing is lost while the owner decides.

  3. 03

    Confirm every payment at once

    The moment a payment is posted, the owner is told through the inbox and by email. The confirmation closes the loop: the owner sees the money was received and applied, and the 'did you get my transfer?' call does not happen. Payments settle the oldest open charges first, so the confirmation also shows what the payment cleared.

  4. 04

    Let the statement do the asking

    The statement is the natural moment to prompt payment. When a statement is finalised the owner is notified straight away, and the notification shows the closing balance, so an owner who wants to settle can do so before the reminder cycle begins. Owners with portal access see the same balance on their dashboard.

  5. 05

    Write one escalation procedure and apply it everywhere

    Decide the steps in advance: reminder at day 0, a second at day 14, a personal call at day 30, a formal letter at day 60, and the legal route after that. Adopt the procedure at the AGM so it is the owners' policy, not the manager's mood. In Cyprus the management committee may pursue unpaid common expenses through the courts under Cap. 224; in Spain the community uses the monitorio procedure under article 21 of the Ley de Propiedad Horizontal; in Germany the Verwalter pursues Hausgeld arrears through the Mahnverfahren. The intervals above are illustrative; whether interest or a fixed charge may be added to overdue common expenses is a matter of national law and the building's regulations, so confirm before adding one.

A worked example

An owner in Paphos receives a June statement on 1 July with a closing balance of €186.40: €161.40 of common expenses and a €25.00 reserve fund levy. The statement notification shows the balance. No payment arrives. On Monday 6 July the reminder job finds the balance still open and sends a reminder by inbox and email. The owner pays €186.40 on 9 July; the confirmation goes out the same day and shows both balances at €0.00. Had the owner never created an account, the same three messages would have arrived as branded emails with a link to sign up.

Figures and dates are illustrative. The escalation beyond the reminder is the committee's written procedure; the reminder itself is the same for every owner in the portfolio.

What arrears do to the building

Common expenses are shared by definition. When one owner does not pay, the invoice is still paid, out of the building's cash or, if that runs dry, from the paying owners in the form of a higher levy or a deferred repair. That is why most European regimes give the community a privileged route to recover the debt, and why the Cyprus reform now under discussion proposes restricting a unit's transfer until its common expenses are settled. A reminder cycle that runs without fail is the cheapest part of that chain, and the one entirely in the manager's hands. See payment reconciliation for how payments are matched and ownership transfer controls for the transfer block.

Implementation

Collection checklist

  • Reminders run on a fixed weekly schedule for every building, based on the latest final statement.
  • Owners without an account receive a branded email with a link to create one, for statements, payments and reminders alike.
  • Payment confirmations are sent the moment a payment is recorded.
  • Statement notifications show the closing balance so owners can settle before the reminder cycle.
  • All notification templates carry the same branding and tone, with the building named.
  • The escalation procedure is written down, adopted at the general meeting and applied to every owner in the same way.
  • The in-app inbox is available in both the management dashboard and the owner portal.
  • Every notification sent is logged, with the recipient and the timestamp, for the audit trail and for disputes.

Sources

Sources and further reading

The instruments this guide relies on. Recovery procedures and any interest on arrears are national; confirm them with a local lawyer.

  • Immovable Property (Tenure, Registration and Valuation) Law, Cap. 224, Part IIA (Cyprus) — the owners' obligation to contribute to common expenses and the management committee's standing to recover them.
  • Regulation (EU) 2016/679 (GDPR), Articles 5, 6(1)(c) and 6(1)(f) — the lawful basis for processing owners' contact and balance data when chasing arrears, and the duty to keep it accurate.
  • Ley 49/1960 de Propiedad Horizontal, Spain, article 21 — the monitorio procedure for unpaid community charges.
  • Wohnungseigentumsgesetz (WEG), Germany, and the Zivilprozessordnung (Mahnverfahren) — recovery of Hausgeld arrears by the community.
  • National civil-procedure and interest legislation, as applicable — whether interest or a fixed charge may be added to overdue common expenses is set nationally and in the building's regulations.

Nothing on this page is legal advice. For the wider approach to arrears, read collecting overdue common expenses without losing the community.

Start with one building

Put the reminder cycle on a schedule

Start a free trial: 14 days, no card. Import one building, finalise a statement and watch the first Monday reminder go out.

  • 14-day free trial
  • No credit card required
  • Cancel any time