Property Management in Germany: A Software Guide for Hausverwaltungen

Property Management in Germany: A Software Guide for Hausverwaltungen

I remember the first time I tried to explain Wohnungseigentumsgemeinschaft to a Latvian colleague. "Think of it as an OSMD," I said, "but with a lawyer attached, a court-enforced repair process, and a yearly owners' meeting that follows parliamentary procedure."

She looked at me like I was making it up. I wasn't.

German property management — Hausverwaltung — operates under the Wohnungseigentümergesetz (WEG, the Condominium Act) in a way that's fundamentally different from the Baltic OSMD model. The legal framework is more prescriptive. The financial controls are stricter. The documentation requirements would make a Latvian apartment association board member weep. And the software you use to manage all of it needs to understand these structures natively, not just bolt them onto a generic property management template.

This guide is for property managers operating in Germany — or planning to expand into the German market from the Baltics or elsewhere — who need to evaluate software that actually fits the Hausverwaltung workflow. Not a generic "10 best property management tools" list. The specific features, integrations, and compliance hooks that matter when your clients are German Wohnungseigentümergemeinschaften (WEGs).

The WEG structure: why your software needs to understand it

A WEG (Wohnungseigentümergemeinschaft) is the legal entity formed by the owners of units in a German residential building under the Condominium Act. It's not a company. It's not an association in the Latvian sense. It's a special legal construct where each owner owns their individual unit (Sondereigentum) plus a co-ownership share of the common areas (Gemeinschaftseigentum).

The WEG is managed by a Verwalter (property manager — that's you) who is appointed by the owners' meeting (Eigentümerversammlung). The Verwalter has specific legal duties defined in § 27 WEG: maintaining the common areas, collecting the house fund contributions (Hausgeld), keeping the accounts, preparing the annual utility settlement (Wirtschaftsplan and Jahresabrechnung), and representing the WEG externally.

Here's why this matters for software: a WEG is not a tenant-landlord relationship. It's a co-ownership management relationship. The "tenants" are actually owners. The "rent" is actually a house fund contribution (Hausgeld) that's pre-budgeted in an annual plan (Wirtschaftsplan) and settled against actual costs at year-end. The financial flow is:

1. Wirtschaftsplan (annual budget) is approved at the owners' meeting.
2. Hausgeld (monthly contributions) are collected from each owner based on their ownership share (Miteigentumsanteil).
3. Jahresabrechnung (annual settlement) reconciles actual costs against collected Hausgeld and either bills or refunds each owner.

Generic property management software built for the tenant-landlord model breaks at step 1. It doesn't have the concept of an ownership-share-weighted budget. It can't generate a Wirtschaftsplan. And without that, you can't produce a valid Jahresabrechnung — which is a legal requirement under § 28 WEG.

The ownership share problem

Each unit in a WEG has a Miteigentumsanteil (MEA) — a fractional ownership share expressed as a fraction of the whole building (e.g., 122/1000). Every financial allocation in the WEG — from Hausgeld to utility settlements to reserve fund contributions — is weighted by this share. An owner with 122/1000 pays 12.2% of the total building costs. An owner with 85/1000 pays 8.5%.

But it's not that simple (it never is in Germany). Some costs are allocated by MEA. Others are allocated by a different key — number of persons (Kopfteile), living area (Wohnfläche), or consumption (Verbrauch). The allocation key is specified in the Teilungserklärung (declaration of division) and can be modified by the owners' meeting.

Your software needs to:

• Store the MEA for every unit.
• Store alternative allocation keys and when each applies.
• Calculate every line item in the Wirtschaftsplan and Jahresabrechnung using the correct key for that cost type.
• Show each owner their individual share of every cost, not just a building total.

If the software only does "split by area" or "split evenly," it can't manage a WEG. Period. The allocation key logic is non-negotiable, and it's the first thing I check when evaluating a German property management platform.

The Wirtschaftsplan and Jahresabrechnung: the core financial cycle

This is the heart of Hausverwaltung accounting, and it's where software choice matters most.

Wirtschaftsplan (annual budget)

The Wirtschaftsplan is the annual budget for the WEG. It projects all expected costs for the coming year — maintenance, insurance, utilities, management fee, reserve fund contribution (Instandhaltungsrückstellung) — and divides them into monthly Hausgeld amounts per owner based on the allocation keys.

Under § 28 Abs. 2 WEG (reformed in 2020), the Wirtschaftsplan must include:

• Expected income and expenditure for the common areas
• The reserve fund contribution (Instandhaltungsrückstellung), broken down by the three statutory categories: maintenance (Erhaltung), repair (Instandsetzung), and modernization (verbessernde Maßnahmen)
• The monthly house money (Hausgeld) each owner must pay, calculated by their MEA

The 2020 WEG reform (WEG-Reformgesetz) tightened the reserve fund requirements significantly. The reserve fund must now be "angemessen" (adequate) — a deliberately vague term that courts interpret based on building age, condition, and expected maintenance needs. In practice, Steuerberater and auditors now expect 0.5-1% of the building's replacement value annually as a minimum reserve contribution. For a building worth €3 million, that's €15,000-30,000 per year into reserves.

Your software needs to model the reserve fund as a separate three-category line item in the Wirtschaftsplan, not lump it into "general expenses." The 2020 reform made this a compliance issue, not a preference.

Jahresabrechnung (annual settlement)

The Jahresabrechnung reconciles actual costs against the Hausgeld collected. For each cost category:

• Actual cost is totaled for the year.
• The cost is allocated to each owner by the correct key (MEA, area, persons, or consumption).
• Each owner's share is compared to the Hausgeld they paid.
• The difference is billed or refunded.

This is functionally similar to the Latvian utility settlement (Nebenkostenabrechnung) but operates at the building level, covers all WEG costs (not just utilities), and must be delivered to each owner individually with a right to audit (Einsichtsrecht, § 29 WEG).

The document itself is legally prescribed. Each owner's settlement must show: their MEA, their share of each cost line, the allocation key used, the total Hausgeld paid, and the final balance. The software must generate this document per owner, not as a building summary.

The utility sub-settlement (Nebenkostenabrechnung within the WEG)

Within the Jahresabrechnung, there's a nested settlement for utility costs that follow German tenancy law (Betriebskostenverordnung — BetrKV). Even though WEG owners aren't tenants, the utility allocation often follows BetrKV principles because individual metering is common.

This is the same 12-line-item-per-unit problem I described in our DATEV integration guide. Heating allocated by consumption (if heat cost allocators are installed). Water allocated by persons if no individual meter, by consumption if metered. Insurance by area. Management fee by MEA. Each line needs its own allocation key, its own result per owner, and its own entry in the settlement document.

If your software handles the utility settlement as a single lump sum per owner, you're doing manual calculation in Excel for every unit, every year. That's not scalable past 20-30 units.

The owners' meeting: documentation and voting

The Eigentümerversammlung (owners' meeting) is where WEG decisions happen. Your software needs to support the full workflow:

Pre-meeting: - Invitation with agenda (Beschlusssammlung items) sent 3 weeks in advance (§ 24 Abs. 4 WEG — the formal invitation period) - Attendance confirmation and proxy collection (Vollmacht — owners can delegate their vote)

During meeting: - Recording each resolution (Beschluss) with exact wording, vote tally (yes/no/abstain by MEA percentage, not head count), and result - The 2020 WEG reform requires that votes be weighted by MEA — an owner with 200/1000 has more voting weight than one with 50/1000

Post-meeting: - Beschlusssammlung (resolution collection) — a legally required ongoing record of all WEG resolutions, maintained by the Verwalter since the 2020 reform - Each owner has the right to inspect the Beschlusssammlung at any time (§ 24 Abs. 6 WEG)

Most generic property management tools treat "meetings" as calendar events with notes. That doesn't work for WEG. The Beschluss recording — with exact wording, MEA-weighted vote tallies, and a permanent, inspectable record — is a specific compliance requirement. Software that can't generate a Beschlusssammlung document on demand is non-compliant with the 2020 reform.

DATEV and accounting integration

I covered DATEV integration in detail in a separate guide, so I'll keep this section to the Germany-specific angle.

German Hausverwaltungen almost universally work with a Steuerberater (tax advisor) who uses DATEV. Your software must export accounting data in DATEV format — specifically:

• SKR03 or SKR49 chart of accounts (SKR49 is the DATEV chart specifically designed for WEG accounting — it includes accounts for the Hausgeld, reserve fund, and WEG-specific cost categories that SKR03 doesn't have natively)
• Cost center per WEG (one WEG = one cost center, or sub-cost-centers per building if you manage multi-building WEGs)
• Line-by-line utility settlement export (not a lump sum — each Nebenkosten line item as a separate booking)

SKR49 is the differentiator. If your software only supports SKR03 (the general German chart of accounts), it can work — but your Steuerberater will need to manually map WEG-specific accounts, which defeats the integration. SKR49 has accounts like 0720 (Instandhaltungsrückstellung — reserve fund), 8200 (Hausgeldforderungen — house money receivables), and 9800 (Wohnungseigentümergemeinschaft — WEG clearing account) that exist specifically for WEG accounting.

Ask your Steuerberater which chart they use. If they say SKR49, your software must support it. If they say SKR03, ask why — and whether they'd switch to SKR49 if your software supported it (many would, because it's cleaner for WEG work).

Multi-currency: when your WEG has international owners

This is an edge case that's becoming more common: a WEG in Berlin or Hamburg where some owners are based outside the eurozone. British owners post-Brexit, Swiss owners, American investors buying Berlin apartments.

The WEG's accounts are in EUR — that's not optional. But individual owners may need Hausgeld statements and Jahresabrechnung in their home currency for their own tax reporting. This doesn't mean the WEG books in two currencies. It means the software should be able to generate owner-facing documents with a reference currency conversion (using the ECB reference rate or a monthly average) alongside the EUR figures.

More practically: if you manage WEGs and also manage properties in Latvia or Estonia (as Urbaneta clients do), you need a platform that handles EUR-to-EUR (trivially) but also EUR-to-CHF or EUR-to-GBP for owner reporting without maintaining a parallel accounting system. Multi-currency reporting is a nice-to-have for single-country operations, a must-have for cross-border property managers.

Data security and GDPR: the German-specific angle

German data protection law is stricter than the EU GDPR baseline. The Bundesdatenschutzgesetz (BDSG) layers additional requirements on top of GDPR — particularly around the storage of personal data, the right to information, and the processing of sensitive financial data.

For Hausverwaltung software, this means:

• Server location. Many German WEGs and their Steuerberater require data to be stored on servers located in Germany or the EU. A platform hosted on US-based AWS instances may not pass procurement requirements, even if it's GDPR-compliant technically. Check where the data physically resides.
• Access logging. Who accessed which owner's financial data, when, and why. This is a BDSG requirement that goes beyond GDPR's "appropriate technical measures."
• Owner data export. An owner can request all data the Verwalter holds about them (GDPR Article 15 — right of access). Your software must be able to produce this export per owner, including their Hausgeld history, settlement records, meeting votes, and correspondence.
• Deletion after handover. When you're replaced as Verwalter (and you will be, eventually), you must hand over all WEG documents and then delete your copies within a reasonable period. The software should support a clean export-and-delete workflow, not just "close the account."

What to look for: a practical evaluation checklist

When evaluating Hausverwaltung software, run through this list in order. Each item is a gate — if it fails, the software probably can't manage a German WEG properly.

1. WEG-native or WEG-bolted-on? Does the software treat WEGs as a first-class entity (with MEA, Wirtschaftsplan, Beschlusssammlung) or as a "property" with some German labels added? Look at the data model, not the marketing page. If the Wirtschaftsplan is a "budget template" and the Jahresabrechnung is a "report," it's bolted-on.

2. Allocation keys. Can it handle MEA, Wohnfläche, Kopfteile, and Verbrauch as allocation keys, with per-cost-type assignment? Can you override the default key for a specific cost line in a specific year?

3. Wirtschaftsplan generation. Does it produce a Wirtschaftsplan document that includes the three-category reserve fund breakdown required by the 2020 WEG reform? Can it carry forward last year's actuals as next year's budget baseline?

4. Jahresabrechnung per owner. Does it generate a per-owner settlement document with all required fields (MEA, allocation key per line, Hausgeld comparison, balance)? Or does it produce a building summary and leave you to calculate individual owner shares in Excel?

5. Beschlusssammlung. Does it maintain a permanent, inspectable record of all WEG resolutions with MEA-weighted vote tallies? Can it export this record as a single document for owner inspection?

6. DATEV export — SKR49. Does it export in DATEV format using SKR49 (not just SKR03)? Does the export include line-by-line utility settlement bookings, not lump sums?

7. Peppol / e-invoicing. Does it support Peppol BIS Billing 3.0 for e-invoicing to B2B clients and government entities? (See our Peppol e-invoicing guide for the full context.)

8. Data residency. Where does the data physically reside? Is it EU/Germany-hosted? Can it provide a DPA (Data Processing Agreement) that satisfies BDSG requirements?

9. Owner portal. Can owners view their own Hausgeld, settlement, and Beschlusssammlung online? This isn't legally required, but it reduces the Einsichtsrecht (inspection right) requests you handle manually by 80%+.

10. Multi-property, multi-WEG. If you manage 50+ WEGs, can the software handle that scale? Separate cost centers per WEG, consolidated reporting, batch Jahresabrechnung generation? Or does it cap at "one property per account"?

The market reality

Most software sold as "property management" in Germany falls into two camps: generic tools (buildable for WEG but requiring heavy customization) and specialist Hausverwaltung software (expensive, often desktop-based, with dated UX). The middle ground — modern, cloud-based, WEG-native, with DATEV and Peppol support — is thin. That's the gap Urbaneta targets.

If you're currently using a generic tool and bolting WEG logic onto it with spreadsheets, you already know the pain. The Wirtschaftsplan takes a week to build. The Jahresabrechnung takes a month. A Beschluss is challenged because the record is incomplete. The Steuerberater rejects the DATEV file because the cost centers don't match.

The fix isn't more spreadsheets. It's software that understands the WEG as a legal construct, not just a property with owners. That means MEA-weighted calculations, a proper Wirtschaftsplan, per-owner Jahresabrechnung, a Beschlusssammlung that would satisfy a notary, and DATEV export that the Steuerberater imports without a single correction.

That's the bar. Anything less is a tool pretending to manage German property.

Urbaneta supports WEG-native management with Wirtschaftsplan, MEA-weighted Jahresabrechnung, Beschlusssammlung, DATEV SKR49 export, and Peppol e-invoicing. Try it free for 14 days — no credit card required.