Audit-proof documentation in property management: What really matters

Problem: Documents from everyday administrative operations do exist, but in the event of an audit, they lack evidentiary value because the creation time, editor, and modification history are missing.

Cause: Processes are managed in email inboxes, on local drives, and through verbal agreements—in other words, without timestamps, versioning, and immutability.

Thesis: Audit-proof documentation is not created through additional effort, but rather by consistently managing processes within a guided system that includes traceability as a standard feature.

What does audit-proof documentation mean in property management?

Direct Answer: Audit-proof documentation in property management fulfills three criteria: immutability (no subsequent modifications without an audit log entry), completeness (every relevant process is recorded), and temporal traceability (timestamps for creation, modification, access). GoBD and GDPR require documents that are machine-readable and retrievable throughout the entire retention period.

The Audit Case: What happens when proof is missing

An owner disputes damages to their apartment and claims they occurred during the previous tenancy. They demand the handover protocol from the move-out of the last tenant, which took place 18 months ago. The protocol exists, but was saved as a PDF on the local computer of an employee who has since left the company. The time of creation cannot be traced. Versioning does not exist. Who created the protocol cannot be identified from the document itself.

In this scenario, the document de facto lacks evidentiary value. In court or during mediation proceedings, it cannot be proven when the protocol was drafted, whether it was subsequently altered, or which person actually carried out the handover. This is the core problem of lacking audit-proof documentation: not the absence of the document, but the absence of its verifiability.

The Five Most Common Documentation Gaps in Practice

In the day-to-day operations of 450+ real estate companies, the same vulnerabilities emerge time and again.

2.1 Communication via email without system integration

Emails between property managers and tenants that remain solely in the email inbox are not audit-proof. They can be deleted, forwarded, or modified without generating a system log. If integration with a central system is lacking, the proof of who communicated what and when is also missing. In the event of a dispute: What is not in the system is considered not to have happened.

2.2 Inspection protocols on paper or saved locally

Paper protocols do not meet any of the GoBD requirements for machine-readability. Locally saved files without an automatic timestamp and without versioning are worthless in an audit, even if their content is accurate. A file’s creation date can be manually altered. A native system timestamp cannot.

2.3 Verbal agreements without written tracking

Agreements regarding rent adjustments, special uses, or maintenance responsibilities that are not documented in writing and with timestamps practically do not exist in legal disputes. This also applies to agreements made over the phone or in personal conversations, the content of which the parties remember differently later on.

2.4 Contract amendments without versioning

If a lease agreement is subsequently supplemented or amended, this must be recognizable as a new version with a date and editor. Overwriting the original document without a log entry contradicts the GoBD requirements for immutability and, in an audit, can be considered subsequent tampering.

2.5 Missing timestamps for decisions

When was a tenant selection made? When was a reported defect classified as resolved? Without native system timestamps, these decisions cannot be unequivocally proven in retrospect. The consequences range from an impeded defense in tenancy disputes to proof problems in operating cost billing.

What “audit-proof” legally means

The Principles for the Proper Management and Storage of Books, Records, and Documents in Electronic Form (GoBD, BMF circular of November 28, 2019) define four core requirements for business records.

Immutability: A document may no longer be altered after final processing without the system logging this event. Every change must remain traceable with a timestamp, user ID, and change content (GoBD, margin nos. 64 to 80).

Completeness: All business-relevant processes must be recorded. Gaps in documentation are considered grounds for suspicion in an audit and can shift the burden of proof.

Availability: Documents must be retrievable at all times during the entire statutory retention period. This also applies after staff turnover, system migrations, or corporate reorganizations.

Machine-readability: Documents must be available in a format that permits electronic auditing. Paper scans alone are insufficient if the original was created digitally (GoBD, margin no. 14).

In addition, the requirements of the GDPR apply to all personal data. Tenant data, applicant data, and communication content require clear purpose limitation and documented deletion routines. Missing or undocumented deletion processes constitute an independent compliance risk.

Overview of Retention Periods

Which documents must be retained for how long is determined by several legal bases:

Lease agreements, contractual documents

• Retention period: 6 years; if the contract also serves as an accounting voucher (e.g., as a recurring invoice), 8 years

• Legal basis: Section 257 (4) HGB (Commercial Code - commercial letters)

Accounting vouchers, operating cost statements

• Retention period: 8 years (since January 1, 2025)

• Legal basis: Section 257 (4) HGB, Section 147 (3) AO (Fiscal Code)

Tenancy correspondence

• Retention period: 6 years (commercial letters)

• Legal basis: Section 257 HGB

Rent claim records

• Retention period: 8 years (accounting vouchers)

• Legal basis: Section 257 (4) HGB, Section 147 (3) AO

Apartment handover protocol

• Retention period: at least 3 years after move-out

• Legal basis: Section 195, Section 548 BGB (Civil Code)

Applicant data

• Retention period: delete as soon as the purpose ceases to apply; if claims under Section 21 AGG (General Equal Treatment Act) are conceivable, generally no later than 6 months after rejection

• Legal basis: DSK Guidance V2, January 2026

The guidance from the German Data Protection Conference (DSK, Version 2, January 2026) requires deletion as soon as the collection purpose no longer applies, and specifies generally no later than six months for cases where claims under Section 21 AGG are conceivable. Anyone retaining applicant data longer must be able to demonstrate a documented purpose that justifies the extended storage under data protection law.

The period for handover protocols arises from the limitation period of claims for compensation after the end of a lease pursuant to Section 548 BGB: Landlords can only assert compensation within six months after the return of the leased property. The general 3-year period under Section 195 BGB applies to further claims. As a minimum retention period, the protocol should remain securely accessible for at least three years after move-out.

Have timestamps assigned automatically by the system

Every handover protocol carries an automatic timestamp that is assigned by the system and cannot be manually altered. This ensures the time of creation is verifiable, regardless of which device or employee was involved.

Assign communication to the process

All communication with a tenant is assigned to the respective process and cannot be removed from the system without creating a log entry. This ensures it remains traceable who communicated what and when, even months later.

Version contract amendments instead of overwriting

Contract amendments create a new document version without overwriting the earlier one. This satisfies the GoBD requirement for immutability, and every version remains identifiable with a date and editor.

Store decisions independently of individuals

Decisions made during the application process are recorded with a date and the person handling them, even if that employee has since left the company. Staff turnover therefore no longer leads to evidentiary gaps.

Allow documentation to emerge within a guided process

EverReal, as a guided workflow system for property managers, maps these processes in a structured manner. No step in the leasing process is completed without internal system logging. This does not mean that employees have to handle additional documentation duties manually: Documentation is generated within the process itself because the process is guided.

Conclusion

Audit-proof documentation is not an extra task that has to be handled alongside day-to-day business. It is created when operations are consistently managed within a system that includes timestamps, versioning, and immutability as standard features.

Anyone still working with local files, email inboxes, and verbal agreements is left without reliable proof in an audit. Not because there are no documents, but because their verifiability is missing.

Start the Self-Assessment “How audit-ready is your property management?” | Request a demo

How an audit trail closes these gaps

An audit trail is an automatically maintained log of all system-recorded events, featuring timestamps, user IDs, and document statuses. In contrast to manually maintained lists, a system-integrated audit trail is immutable because entries cannot be deleted or modified without generating a new log entry.

Learn more about building a complete audit-proof leasing process in the foundational article.

Further reading: Process standards in property management and GDPR in property management.

We do not provide legal advice. Property managers are advised to clarify individual legal questions with a specialized attorney or their professional association (VDIV, IVD).

Q: How long do I have to retain lease agreements?

A: Lease agreements and associated contractual documents are subject to a retention period of six years under Section 257 HGB. Statements and other documents of an accounting nature must be retained for eight years as accounting vouchers; the reduction from ten to eight years has been in effect since January 1, 2025. The period begins at the end of the calendar year in which the voucher was created or the commercial letter was received or dispatched (Section 257 (5) HGB). For as long as the tenancy is active, the documents are needed for the performance of the contract anyway and may be retained. Tenancy correspondence classified as commercial letters must be retained for 6 years.

Q: Is email correspondence with tenants audit-proof?

A: Emails alone are not audit-proof as long as they are merely stored in an email inbox. Audit-proof storage requires correspondence to be transferred into a system that ensures immutability, timestamps, and machine-readability. Every relevant email must be assigned to the applicable process or tenancy and stored in a system that guarantees GoBD-compliant archiving. Subsequent printing and scanning is insufficient if the original was created digitally.

Q: What is an audit trail and why do I need it as a property manager?

A: An audit trail is an automatically maintained log of all relevant system events. It records who performed which action in the system and when: whether a document was created, modified, retrieved, or assigned to another person. In day-to-day property management, an audit trail protects against the common problem of decisions, communication, or protocols no longer being traceable in retrospect. In an audit, such as during a tenancy dispute or an official inspection, it serves as reliable proof that an event took place at a specific point in time.

Q: Is a local drive sufficient for audit-proof archiving?

A: No. A local drive does not meet the GoBD requirements for immutability and availability. Files on local drives can be modified, deleted, or moved without a log entry. In the event of staff turnover or device failures, availability throughout the entire retention period is not guaranteed. Audit-proof archiving requires a system that stores documents immutably, automatically logs versioning, and ensures permanent, device-independent access for the entire statutory retention period.