Practical guide
Managing multiple condominiums from one practice
A property management practice handling ten, fifty or a hundred condominiums faces a different problem than a single independent administrator: managing one building well is not enough, the practice needs a method that holds up as the number of buildings grows. The real risk is fragmentation, inconsistent ledgers, communications handled in no particular order, tax and assembly deadlines overlapping without a shared calendar. This guide describes how to organize portfolio wide dashboards, differentiated staff permissions and repeatable reporting, so that managing more buildings does not translate into a proportional increase in administrative load, while still keeping the separate accounting per condominium that Italian law requires under article 1129 of the Civil Code.
The starting constraint: separate accounts, unified operations
Article 1129 of the Italian Civil Code requires the administrator to keep a distinct bank or postal account for each condominium under management and to route through it every sum received under any title. This constraint, designed to protect owners from commingled funds, is also the first organizational obstacle for a practice with many mandates: accounting separation must be respected to the letter, while day to day operational management can and should be unified.
The answer is not choosing between separation and unification but applying each at the right level: accounting stays strictly distinct building by building, while cross cutting activities, deadline tracking, monitoring overdue payments, scheduling assemblies, are observed through a portfolio view that aggregates data without mixing it. Practice management software such as AmministraPro is built for exactly this: separate ledgers for each condominium alongside a portfolio dashboard that shows the status of every managed building at a glance.
Portfolio dashboards: what actually needs to be visible at a glance
Once the number of managed buildings passes a dozen, the administrator can no longer open each file individually to know what needs attention. What is needed is an aggregated view that flags exceptions, not one that lists everything: which buildings have unpaid installments past a given threshold, which assemblies must be convened within statutory deadlines, which tax deadlines (property tax payments on common areas, filings tied to renovation tax credits) are approaching.
In practice, this view is built from a handful of recurring indicators: aggregated arrears per building, to catch delays early before they become a cash flow problem for the property; a single assembly calendar that cross references deadlines across all buildings (the ordinary assembly must be convened at least once a year under article 1130 bis) avoiding scheduling clashes; the status of ongoing extraordinary works, together with the related disclosure deadlines toward owners.
A view of this kind shifts the practice's work from reactive, chasing urgencies building by building, to proactive, with priorities visible before they turn into complaints or disputes.
- Aggregated arrears per building, to catch delays early
- A single assembly calendar cross referencing deadlines across all buildings
- Status of ongoing extraordinary works, with disclosure deadlines toward owners
Differentiated permissions: who sees what inside the practice
A practice with several staff members (the licensed administrator, trainees, bookkeepers, front office staff) needs a permission system that reflects actual responsibilities, not undifferentiated access to every building's data. A bookkeeper handling the cash ledger of one group of buildings has no reason to see the assembly minutes of a condominium they do not directly manage, and a trainee can be given read only access until ready to operate independently.
Granular permissions also serve the data minimization principle required by EU Regulation 2016/679 (GDPR): each staff member should only access the data of the buildings they actually work on, not the practice's entire portfolio. This reduces exposure in case of an error or when a staff member leaves the practice, and makes it easier to demonstrate, if ever checked, that data access is proportionate to the role performed.
Repeatable reporting: standardizing without flattening
Every condominium has its own particulars (number of buildings, presence of a supercondominium, type of shared systems), but the documents a practice must produce periodically are structurally recurring: the annual financial statement with expenses apportioned by share (article 1123 of the Civil Code), the assembly notice with its agenda, the updated condominium registry.
Standardizing the templates for these documents, while keeping each building's specific content, lets a practice cut the time spent on document production without sacrificing quality: a statement generated from a consistent template is also easier for owners to follow in assembly, because its structure stays recognizable building after building. On this front, a single system that links registry, accounting and reporting across the whole portfolio, as with AmministraPro's features for practices with multiple mandates, avoids the duplicated work of copying data from one system to another.
Frequently asked questions
Is it mandatory to keep separate bank accounts for every condominium the practice manages?
Yes. Article 1129 of the Italian Civil Code requires the administrator to open a postal or bank account in the condominium's name and to route through it every sum received from owners or third parties under any title. A single account pooling funds from several condominiums managed by the same practice does not comply and can amount to serious irregularity under article 1129, with possible judicial removal from office.
Does a practice with many condominiums still need to appoint a separate administrator for each one?
Yes, every condominium with more than eight owners must appoint an administrator under article 1129 of the Civil Code, but nothing prevents the same person or the same practice from holding the appointment for several condominiums at once. This is standard practice: the appointment remains a distinct assembly resolution for each condominium, with its own mandate, its own term and its own resolution granting it.
How is data kept from mixing between condominiums managed by the same practice?
It requires software that strictly separates registry, accounting and documents for each condominium at the database level, while still allowing a read only aggregated view for whoever supervises the whole portfolio. AmministraPro, for instance, keeps ledgers distinct building by building and supports differentiated permissions per staff member, so aggregation happens only in the summary dashboard and never in the official records.
Is it better to use separate spreadsheets rather than one management system for multiple condominiums?
With a handful of buildings a spreadsheet can be enough, but manual management does not scale: it increases the risk of transcription errors across different files, makes it hard to cross reference tax and assembly deadlines across buildings, and does not automatically produce the mandatory registers (condominium registry, accounting ledger) in the required form. Dedicated practice management software reduces these risks and lets the number of managed buildings grow without a proportional increase in time spent on repetitive tasks.
What kind of permissions should a bookkeeper have compared to the practice's licensed administrator?
A bookkeeper should be able to access the cash ledger, payments and reminders for the buildings they actually handle, without necessarily seeing assembly minutes or communications reserved to other buildings in the portfolio. This setup respects the data minimization principle under EU Regulation 2016/679 and limits exposure in case of an error or a staff change within the practice.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.