DATEV Integration for Property Managers: A Practical Setup Guide
If you manage properties in Germany — or you handle accounting for a German-speaking portfolio from Riga or Tallinn — you've probably hit the same wall I did. Your property management software spits out beautiful reports. Your accountant nods, opens DATEV, and then asks you to re-enter everything by hand.
I spent three months last year doing exactly that. Every month-end, I'd export a CSV from our platform, reformat it in Excel, and email it to our tax advisor in Hamburg. She'd manually post each line into DATEV Arbeitsplatz. We were paying for software on both ends, and still doing data entry twice.
Here's what I've learned about making DATEV integration actually work for property management — without the monthly copy-paste ritual.
What DATEV actually is (and what it isn't)
DATEV isn't accounting software in the way most people think about it. It's the backbone of German tax advisory. Over 40,000 tax advisors in Germany use it. When your Steuerberater says "send me the DATEV file," they mean a specific XML-based format — officially called DATEV-Format, or sometimes the newer DATEV XML-Format — that their DATEV installation can import directly.
The format covers booking data (Buchungsstapel), master data (Stammdaten), and increasingly, documents (Belege). For property management, the piece that matters most is the Buchungsstapel — the batch of accounting entries that represents your monthly rent, utility, and maintenance transactions.
What trips people up: DATEV expects data structured around German chart-of-accounts rules (SKR 03 or SKR 04), with specific cost-center (Kostenstelle) and cost-unit (Kostenträger) coding. If your property software doesn't map to those accounts, your accountant has to recode everything. That's the bottleneck.
The three integration paths (and which one I'd pick)
There are basically three ways to get data from a property management system into DATEV. I've tried all three.
Path 1: Manual CSV export and reformatting
This is where most people start, and it's where I started. You export transactions, clean up the columns to match what DATEV expects, and hand the file to your tax advisor.
It works. It's free. And it eats 4-6 hours every month if you have more than 30 units, because the account mappings never quite line up. One month I spent an entire afternoon tracking down why heating cost allocations were landing in the wrong Kostenstelle — turned out our software used a different numbering scheme for building cost centers than DATEV's SKR 03 expected.
Use this if you have under 15 units and your accountant is patient. Beyond that, the math stops working.
Path 2: DATEV format export from your property software
Some property management platforms can export directly to the DATEV-Format XML. This is the sweet spot for small-to-mid Hausverwaltungen — you configure your chart of accounts once, map each transaction type to the right SKR 03/04 account, and then monthly exports just work.
The setup is the hard part. You need to know your SKR (most residential property managers use SKR 03), and you need to map every transaction category:
- Rent income → account 8000 (SKR 03) or 0800 (SKR 04)
- Operating costs (Betriebskosten) → 4200-4290 range, split by cost type
- Maintenance/repairs → 4310-4320
- Property tax → 4400
- Insurance → 4430-4440
- Management fees → 4610
When I set this up for a 48-unit portfolio in Bremen, the initial mapping took about two hours. After that, monthly export was a 5-minute job. The key was sitting down with the Steuerberater first — she gave me her exact account list, and I mirrored it in the software.
Path 3: Direct API or DATEV-Online integration
The newest option. DATEV has opened up APIs — DATEV Online and the DATEV Schnittstellen — that allow direct data transfer without the file round-trip. Your property software pushes booking data via API, and it appears in your tax advisor's DATEV environment.
This is the cleanest path, but it comes with real prerequisites. You need DUALSHaftung registration (DATEV's partner program) or a direct arrangement with a DATEV-Online-enabled Steuerberater. Most small Hausverwaltungen aren't there yet. I'd hold off on this unless you're managing 200+ units and your tax advisor specifically requests it.
The account-mapping problem (the part nobody explains)
Here's the thing that caused me the most pain: the same transaction can map differently depending on your accounting framework. In Latvia, our software just tracks "utilities" as one bucket. In DATEV-land, utilities split into eight or more accounts based on the Nebenkostenabrechnung structure mandated by German law (Betriebskostenverordnung, § 556 BGB).
So when you set up the integration, you're not just connecting systems. You're translating between two different mental models of what "operating costs" means.
The way I handle it now: each cost type in the property software maps to a specific DATEV account with a Kostenstelle for the building and a Kostenträger for the unit. Heating goes to 4200 with Kostenstelle = building ID. Water goes to 4210. Building insurance to 4430. Property management fee to 4610. The mapping table lives in a config file that I can update when the Steuerberater changes an account.
If your property software can't do per-unit cost-träger coding, you'll lose granularity. For a 20-unit building that might be fine. For a 120-unit complex, your accountant will refuse to work without it.
What I'd do differently if starting today
I'd negotiate the DATEV export format with the tax advisor before choosing property management software. Seriously. If you know your Steuerberater uses DATEV (and in Germany, they almost certainly do), the DATEV-Format export capability is not a nice-to-have. It's a requirement that should sit right next to "can it handle German Nebenkostenabrechnung" and "does it support VAT at 19%."
The conversation I wish I'd had on day one: "Here's our SKR 03 account list. Can your software map each transaction type to these accounts and export a DATEV-Format XML file?" If the answer is yes, you're 80% of the way there. If it's no, you're signing up for monthly manual work.
A practical setup checklist
When you're ready to configure DATEV integration, here's the sequence that worked for me:
- Get your Steuerberater's account list (SKR 03 or SKR 04, with their specific sub-accounts and Kostenstelle numbering).
- In your property software, create a mapping for each transaction type — rent, each operating cost category, maintenance, insurance, management fees.
- Assign Kostenstelle (building-level) and Kostenträger (unit-level) codes to every unit.
- Do a test export with one month of data and send it to your Steuerberater for validation before going live.
- Once validated, automate the monthly export. Most software lets you schedule it for the 5th or 10th of the following month.
That validation step — step 4 — saved me from a messy first month. Our Steuerberater caught two account mappings I'd gotten backwards (insurance and property tax), and we fixed them before anything posted to the real DATEV environment.
VAT, currency, and the cross-border question
If you're reading this from Riga or Tallinn and managing German property, there's an extra layer. German VAT on property management fees is 19%, not Latvia's 21% or Estonia's 22%. If your software defaults to your home-country VAT rate, your DATEV exports will be wrong.
I handle this with per-portfolio VAT settings — German portfolio uses 19%, Latvian uses 21%. It sounds obvious, but I've seen invoices go out with the wrong rate because someone copied a template and didn't check.
On currency: if your German portfolio bills in EUR (and it will), but your home accounts are also in EUR, you're fine. If you're managing across EUR and non-EUR portfolios, DATEV expects EUR-denominated booking data. Non-EUR transactions need conversion before export. Most DATEV-format export tools handle this, but verify.
The cost of not integrating
I tracked this for six months at my previous job. Before integration: 22 hours/month on manual accounting data entry and reconciliation across a 70-unit German portfolio. After: 3 hours/month, mostly reviewing the automated export before sending it to the Steuerberater.
That's 19 hours saved every month. At a typical property manager's effective rate of €35-45/hour in the German market, integration pays for itself before the second month.
The bigger cost, though, is error rate. Manual re-entry means typos. Wrong account codes. Missed transactions. One month we posted €4,200 of heating costs to the wrong building's Kostenstelle, and it took three weeks to unwind it with the Steuerberater. Automated mapping eliminates that entire class of error.
What about Austria and Switzerland?
Quick note since this comes up. Austria has its own equivalent — most Austrian Steuerberater use DATEV Austria or BMD. The export format is similar but not identical. Switzerland is a different world entirely — DATEV has limited penetration; most Swiss fiduciaries use Abacus or Sasimea. If you're managing cross-DACH, you'll need export support for multiple formats, not just DATEV.
Making the jump
If you're still on the manual export path, the upgrade isn't as scary as it sounds. The hardest part is the one-time account mapping — everything after that is automated. And if you're evaluating property management software right now, put DATEV-Format export at the top of your checklist if you work with German portfolios.
When I finally got the mapping right and watched a clean DATEV file export for the first time, I genuinely felt a weight lift. No more Sunday-evening CSV cleanup. No more "did I miss a line" anxiety. Just a file that my Steuerberater could import without a single phone call.
Managing German properties from the Baltics? [Try Urbaneta free](https://urbaneta.com/en/auth/register) — 14-day trial, no credit card needed. Built-in DATEV-Format export, Nebenkostenabrechnung support, and multi-country VAT handling.