Practical guide
How to link the bank account to the software
Property managers running Italian condominiums are required to keep a dedicated bank account for each building under Article 1129 of the civil code, and to report every transaction to unit owners in a traceable way. Linking that account to the management software is not a technology nicety: it turns hours of manual matching between bank statements and payment lists into a process that keeps itself up to date. This guide explains how transaction import works, how automatic reconciliation matches incoming payments to unit owner installments, how to check that cash balances before closing the financial statement, and what security precautions matter when handling sensitive banking data.
Why linking the bank account is worth it
The traditional approach has the property manager periodically download a bank statement and compare it by hand against the list of expected payments from each unit owner, line by line. In a building with twenty or thirty units and quarterly installments, the time spent on this reconciliation grows quickly and still leaves room for transcription errors: a misread bank transfer, an ambiguous payment reference, a transposed figure.
By linking the bank account to the software, transactions enter the system as structured data and are automatically compared against open installments. The property manager immediately sees which unit owners are up to date, which have paid only part of what is due, and which are still in arrears, without reopening online banking every time a unit owner asks a question or a financial statement needs to be prepared.
How transaction import works
Import can happen in two ways, depending on what the manager's or the condominium's bank makes available: uploading a bank statement file, typically in CSV or a standard banking format, or, where available, a direct connection that retrieves transactions at regular intervals without manual work. In AmministraPro both paths lead to the same result: every transaction is recorded with value date, amount, payment reference, and the sender's or beneficiary's IBAN, ready to be matched against the condominium's cash entries.
It is good practice to import transactions on a regular schedule, for example weekly, rather than letting months of statements pile up to be reconciled all at once just before the annual meeting. Frequent imports make it much easier to spot an unusual payment or an unrecognized charge right away, while the details of the operation are still fresh.
Automatic reconciliation: how payments get matched
The reconciliation engine compares every incoming transaction with the installments still open in the condominium's cost allocation plan, using amount, the unit owner's name or IBAN, and, when present, the payment reference as matching keys. Many property managers ask unit owners to include the unit number or installment reference in the transfer description, precisely to make this step easier.
When the match is unambiguous, the system automatically closes the installment and updates the unit owner's position. When the amount does not match exactly, for example a partial payment or a single transfer covering several installments, the transaction is flagged for manual confirmation: the manager decides how to split it, without having to rebuild the link between the statement and the allocation plan from scratch.
It is worth reminding unit owners, perhaps in a communication or at the annual meeting, to always include a clear payment reference: it is the single habit that reduces the number of cases requiring manual review the most.
Cash balancing: the check before closing the statement
Balancing means verifying that the cash balance shown in the software matches, on a chosen date, the actual balance of the bank account. It is the check a property manager must be able to demonstrate at any time to unit owners and, in case of a handover, to a successor, consistent with the transparent reporting duty set out in Article 1130 bis of the civil code.
With transactions imported and reconciled, balancing no longer requires a manual line by line comparison: it is enough to verify that the balance calculated by the software matches the bank statement on the same date. Any discrepancy, typically due to transactions not yet imported or operations still pending, shows up immediately as a difference to clarify, rather than as a surprise when the financial year closes.
Security of banking data
Bank transaction data contains information about identifiable unit owners and therefore falls within the scope of the General Data Protection Regulation (GDPR): the property manager, acting as data controller, must ensure access to this information is limited to those who genuinely need it and that the software provider offers adequate protection guarantees.
When linking a bank account, it is worth verifying that the software supports multi factor authentication for access and differentiated permissions, so that, for example, an office assistant can review transactions without being able to alter registry data or export sensitive information unchecked. AmministraPro is built for exactly this kind of professional use, with import and reconciliation integrated into day to day condominium management, so the property manager works on a single platform instead of switching between online banking, spreadsheets, and reporting software.
Frequently asked questions
Do I need a direct bank connection, or is uploading the statement enough?
A direct connection is not required: periodically uploading the statement file, for example in CSV format, is enough to feed reconciliation. A direct connection, where available, reduces manual work because it retrieves transactions automatically, but the outcome in terms of reconciliation and balancing is the same. What matters is how regularly you import, not the channel you use.
What happens if a unit owner pays several installments with a single transfer?
The system recognizes that the amount does not match a single open installment and flags the transaction for manual confirmation instead of closing it incorrectly on its own. The property manager then indicates how to split the amount across the owner's installments: this takes only a few seconds because the system has already identified the link between the transaction and the unit owner, leaving only the split to confirm.
What if a payment is not recognized automatically?
This happens when the payment reference is missing or unclear, when the transfer comes from an IBAN different from the one on file for the unit owner, for example a family member paying on their behalf, or when the amount does not match any open installment. In these cases the transaction stays pending in the reconciliation screen until the manager matches it manually to the correct unit: no data is lost, the automation simply asks for a human check.
Should cash balancing be done monthly or only at year end?
It is good practice to check it on a regular basis, for example monthly, rather than leaving everything until the annual statement is closed. Frequent balancing makes it possible to spot a missing transaction or a reconciliation error right away, while it is still easy to reconstruct what happened, instead of having to investigate months of activity just before the annual meeting.
Is the imported banking data secure?
The property manager remains the data controller for this information under the GDPR and must choose tools that limit access to those who genuinely need it, with adequate authentication and differentiated permissions among office staff. AmministraPro integrates transaction import and reconciliation into ordinary condominium management specifically to avoid banking data passing through multiple disconnected tools, reducing the points where it could be exposed.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.