Software choice
How to assess certified email (PEC) integration in condo software
Certified email, in Italy the PEC, is the tool the manager uses to send acts with legal value: owners' meeting notices under Article 66 of the implementing provisions of the Italian Civil Code, payment reminders, formal communications. Its value lies in the acceptance and delivery receipts, which prove the sending took place. Software that integrates the PEC lets you send to entitled recipients and keep those receipts linked to the individual owner, instead of hunting for them in an external mailbox years later. This guide explains what software should do on PEC integration and how to verify its real behaviour before choosing.
What to check on PEC integration
- Bulk sending to entitled recipients directly from the software
- Storage of acceptance and delivery receipts linked to the owner
- Handling of PEC addresses in owner and supplier records
- Clear separation between the legal PEC channel and ordinary communications
- Correct attachments, such as the meeting notice or the minutes in PDF
- Tracking of outcomes and handling of failed deliveries
- History of sendings viewable by condominium and by year
- Clarity on what is included in the plan and on the use of the PEC mailbox
Why integrated PEC matters when choosing
The PEC is not a simple email: the acceptance and delivery receipts have evidential value and serve to prove that an act was sent and received. For a meeting notice or a payment reminder, this can make the difference in any dispute. Handling the PEC outside the software, in a separate mailbox, means sending by hand and then having to search for the receipts when they are needed.
Software that integrates the PEC closes this gap: it sends to entitled recipients and archives the receipts, linking them to the owner and the act. Assessing this integration means understanding how much the software protects you legally and how much time it saves compared with manual handling.
Bulk sending and receipt storage
The first element to test is bulk sending. A meeting notice must be sent to all owners with a PEC address: good software lets you send it to everyone in a single operation, attaching the letter in PDF, instead of composing one message at a time. During the trial it is worth checking how simple it is to select the recipients and attach the correct document.
The core of the integration, however, is the storage of receipts. Every PEC sending generates an acceptance receipt and a delivery receipt: the software should archive them linked to the individual owner and the act sent, so they can be retrieved even years later. Software that sends but does not store the receipts in an orderly way leaves you exposed precisely when proof of sending matters most.
Addresses, distinct channels and outcomes
The quality of the integration also depends on handling the addresses. The software should keep each owner's PEC address in their record, distinguishing it from the ordinary email, so it knows who can be sent to with legal value and who cannot. Software that confuses the two addresses risks treating as served an act sent over a channel that is not certified.
It is essential to keep the PEC channel distinct from ordinary communications. Not everything goes by PEC: informal notices can pass by email or notice board, while meeting notices and reminders require the certified channel. Good software makes this distinction clear and tracks the outcomes of sendings, flagging failed deliveries, so you can act on a wrong address instead of assuming served what never arrived.
History and proof over time
The value of the PEC is measured over time. A dispute can arise months or years after the sending, and at that point you need to prove that the act was sent and to whom. Software that keeps a history of sendings by condominium and by year, with the receipts linked, makes this proof immediate, while rebuilding it from an external mailbox is slow and uncertain.
It is worth checking when choosing how easy it is to find the sending of a specific notice to a specific owner, with its receipts. It is the test that tells whether the PEC archive is really useful or just a disordered store of messages, because the difference only shows when the proof is truly needed.
How to test the integration before signing
To assess it well, simulate sending a meeting notice: select the owners with a PEC address, attach the letter in PDF, send and check that the receipts are archived and linked to the owner. Then try to find that sending in the history and check how the software flags a failed delivery.
The underlying question is whether the integration removes the manual mailbox handling and guarantees proof of sending over time. AmministraPro integrates the PEC with sending to entitled recipients and storage of receipts linked to the owner, keeping the legal channel distinct from ordinary communications; the features page and the pricing page show what is included at each level before you decide.
Frequently asked questions
Why is integrated PEC important in software?
Because the acceptance and delivery receipts of the PEC have evidential value and serve to prove that an act, such as a notice or a reminder, was sent and received. Software that integrates the PEC sends to entitled recipients and archives the receipts, linking them to the individual owner, instead of leaving you to search an external mailbox years later. Assessing this integration means understanding how much the software protects you legally.
Should the software store the PEC receipts?
Yes, it is the core of the integration. Every PEC sending generates an acceptance receipt and a delivery receipt that prove the sending took place. The software should archive them linked to the owner and the act sent, so they can be retrieved even years later. Software that sends but does not store the receipts in an orderly way leaves you exposed precisely when proof of sending matters most, for example in a dispute over the validity of a meeting notice.
Should all communications to owners be sent by PEC?
No, and it is important that the software distinguishes the channels. Informal notices can pass by email or notice board, while meeting notices and payment reminders require the certified channel for their legal value. Software that confuses PEC and ordinary communications risks treating as served an act sent over a channel that is not certified. The clear separation between the two channels is therefore a concrete assessment criterion.
How should the software handle a failed delivery?
It must track it and flag it clearly. If a PEC is not delivered, for example due to a wrong address or a full mailbox, the manager must know in order to act, instead of assuming served what never arrived. Good software tracks the outcomes of sendings and highlights failed deliveries, allowing you to correct the address in the records and repeat the sending to that owner.
Is a history of PEC sendings needed?
Yes, because the value of the PEC is measured over time. A dispute can arise months or years after the sending, and you need to prove that the act was sent and to whom. Software that keeps a history by condominium and by year, with the receipts linked, makes this proof immediate. When choosing, it is worth checking how easy it is to find the sending of a specific notice to a specific owner, with its receipts.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.
