Practical guide
Change tracking and access logs in your software
Change tracking is the ability of software to record who performed a given operation, when and on which piece of data. Every time an accounting transaction is entered, an allocation modified or a login made, the system keeps a trace. These records, often called logs, are not there to monitor people invasively, but to guarantee transparency towards owners and to protect the manager in case of a dispute. An archive that keeps a memory of its own changes is harder to alter covertly and easier to defend, because every operation leaves a verifiable mark over time.
What tracking records and why it matters
Software with change tracking keeps a memory of relevant operations: entering or modifying a transaction, changing an allocation, sending a communication, a user's login. For each operation it typically records the author, the moment and the object of the change. This turns the archive from a static snapshot into a consultable history.
The difference from an Excel file is stark. A spreadsheet can be modified by anyone with access without leaving a trace of who and when: an amount changed yesterday is indistinguishable from one entered months ago. In software that records changes, by contrast, the sequence of events stays reconstructable, and this is a safeguard of correctness for the whole management.
Concrete help in case of a dispute
The condominium statement can be challenged by owners, and the manager must be able to demonstrate its correctness. Being able to trace when a transaction was recorded and by whom helps to respond in a documented way, reducing the room for generic accusations of tampering or negligence. Tracking is therefore also a tool that protects the manager.
The same applies to operations performed by staff. In a practice with several people, knowing who acted on a given condominium allows any errors to be clarified without approximate attributions. This is not about surveillance but about having a verifiable base of facts when it is necessary to reconstruct how a certain figure was reached.
Logs and security: spotting anomalous access
Access logs also serve a security function. Access at an unusual time, from a workstation never seen before or right after a password compromise can be a warning sign. Keeping a record of who logs in and when helps recognise anomalous behaviour and react, for example by resetting credentials or enabling two-factor authentication.
This dimension connects to Article 32 of the GDPR, which calls for measures appropriate to ensure the security of processing. The ability to verify access to owners' personal data is among the elements the manager, as data controller, can document among their organisational and technical measures.
Tracking and privacy: a balance to respect
Recording operations does not mean processing the data of those who perform them without limits. Logs themselves contain personal information, for example the identity of staff, and must be managed in line with the minimisation principle and with retention periods proportionate to their purpose. The goal is the security and transparency of the management, not pervasive monitoring for its own sake.
In a practice with several staff members it is appropriate for people to know that the software keeps a record of operations and for what purpose. Clear communication about the purposes of the logs avoids misunderstandings and correctly frames tracking as a tool of shared correctness, not surveillance.
What to check in a software's tracking
A software like AmministraPro records relevant operations and access events, so the manager has a verifiable base to protect themselves and owners. Anyone who wants to understand how tracking and access security are handled can review the capabilities on the features page and compare the plans on the pricing page.
- Whether the system records author, moment and object of relevant operations.
- Whether accounting changes stay reconstructable over time.
- Whether there is an access log useful for spotting anomalies.
- How logs are retained and for how long.
- Whether the logs respect the minimisation of personal data.
- Whether the tracked information is consultable in an understandable way by the manager.
Frequently asked questions
What does change tracking record in software?
Generally the author, the moment and the object of relevant operations: entering or modifying an accounting transaction, changing an allocation, sending communications, user logins. This allows the sequence of events to be reconstructed and turns the archive from a static snapshot into a consultable history, far harder to alter covertly than a spreadsheet.
Does tracking protect the manager or expose them?
It protects them. Being able to demonstrate when a transaction was recorded and by whom helps defend the correctness of the statement in case of a dispute, reducing the room for generic accusations of tampering. An archive that keeps a memory of its own changes is easier to defend than a file that can be modified without leaving a trace.
Are logs also useful for security?
Yes. The access log helps spot anomalous behaviour, such as a login at an unusual time or from a workstation never seen before, which can signal a password compromise. This capability connects to Article 32 of the GDPR, which calls for measures appropriate to ensure the security of the processing of personal data.
Does tracking violate staff privacy?
Not if managed correctly. Logs contain personal information, for example the identity of staff, and must be processed in line with the minimisation principle, with legitimate purposes such as the security and transparency of the management, and proportionate retention periods. It is appropriate for people in the practice to know that the system keeps a record of operations and for what purpose.
Does a spreadsheet offer the same tracking?
No. A spreadsheet can be modified by anyone with access without leaving a reliable trace of who and when. An amount changed recently is indistinguishable from one entered months earlier. Software designed to record changes, by contrast, keeps the sequence of events reconstructable, with a clear advantage in terms of correctness and security.
Try AmministraPro
Accounting, thousandths-based cost splitting, meetings, communications and artificial intelligence in a single Italian software, compliant with UNI 10801 and GDPR.