Real Estate Management

Immocloud runs the bookkeeping that comes before the accounting system.

Immocloud is a fast-growing SaaS from Düsseldorf that uses AI to help its users run the whole property management process efficiently. By the time a tax advisor is involved, the work is already done: rent matched, receipts sorted, creditors and debtors maintained. The integration exists so none of that is lost in the handover.

Book a demo Read the key facts

Key facts

Who Immocloud is, and where Maesn sits in it

Each fact with its source

Website: immocloud.de
About Immocloud: immocloud GmbH, based in Düsseldorf, describes itself as a leading provider of digital property management. Its own site publishes more than 18.000 landlords using it, and its 2025 market report draws on more than 400.000 managed apartments and active tenancies.Source: immocloud.de
Who uses it: Professional property managers, and owners with a manageable number of properties: private landlords and family offices.Source: Maesn
Use case: Handing a finished set of property books to the accounting system the business or its advisor already uses. The incoming side of that, independent of any one vendor, is on the accounts payable automation page.Source: Maesn
Accounting systems: DATEV Rechnungswesen, DATEV Unternehmen Online, sevdesk and Lexware Office, plus further DACH accounting systems on the same connectionSource: Maesn

The problem

The bookkeeping is finished before the accounting system

Most integrations exist because a product holds data somebody else needs. This one exists because Immocloud holds data that is already sorted, and a shallow handover would undo the sorting.

A property portfolio produces a particular kind of bookkeeping. Rent arrives against a unit and a billing period. A receipt is either apportionable to the tenants or borne by the owner. An incoming invoice is split into gross and net and booked against a creditor. A tenancy is private or commercial, and the two are treated differently. Immocloud does all of that, which means the reconciliation is complete before anybody outside the platform looks at it.

That is exactly what makes the next step risky. The users of Immocloud do not want that quality to be lost at the border between their platform and their tax advisor, and an export that flattens the detail loses precisely the part that took the effort. Depth in the handover therefore decides whether the end-to-end journey Immocloud sells actually ends well.

CommunicationBetween tenant and landlordThe correspondence a tenancy produces runs through the platform instead of through a private mailbox.

BankTransactions, assignedA bank connection pulls the transactions in, and each one is assigned to a unit and to a billing period, including mid-year service-charge statements.

ReceiptsApportionable or notReceipts are uploaded, marked as apportionable to tenants or not, split into gross and net, and booked to a creditor.

Person accountsCreditors and debtorsSuppliers on one side, tenants on the other, private and commercial tenancies handled differently, all maintained in the platform itself.

What Immocloud does before the accounting system is involved at all.

How Maesn solves it

Two ways into DATEV, and one connection to the rest

The handover has to fit the person doing the bookkeeping. Immocloud can write real journal entries, or booking proposals for an advisor to release, and the receipt image travels either way.

Buchungsdatenservice

The booking itself

Journal entries written straight into DATEV Rechnungswesen, for a business that keeps its own books. Supported on 10 of the 29 connected systems.

Rechnungsdatenservice

A proposal to release

Booking proposals in DATEV Unternehmen Online, the platform a company and its advisor share. The advisor checks, amends and releases, and no API removes that step.

In both cases the receipt image goes with it, which is supported on four of the 29 systems and on both DATEV products.

The person accounts are where one connection earns its keep, because the two sides do not agree on what to call them. DATEV Rechnungswesen keeps creditors and tenants as contacts and can have them written and updated directly. On sevdesk and Lexware Office the same records are customers and suppliers, with their own fields and their own rules. The common data model is what lets Immocloud write one shape and have it land correctly in either.

The other half is the tenant side, which behaves like a receivables ledger: rent due against a unit, matched against what actually arrived, apportioned across a billing period. Where that has to be reflected in the accounting system rather than only in the platform, it is the workflow on accounts receivable automation.

What changed

Nothing that was reconciled has to be reconciled again

Immocloud publishes no figure for this integration, and none is invented here. What changed is describable without one: the accounting side became a choice its customers make rather than a limit Immocloud has to explain.

For the userThe reconciliation done inside Immocloud arrives as bookings, not as a file somebody has to interpret.

For the advisorEntries or proposals, whichever the working relationship calls for, with the receipt attached to each.

For ImmocloudOne integration to operate instead of one deep accounting build per system, and the next system on the same connection.

The flexibility has a second use that only shows up in larger portfolios. A company whose activities reach beyond the buildings keeps its general accounting where it already is, and the property side arrives there properly instead of forcing a choice between a property tool that cannot book and an accounting system that has never heard of a unit or a billing period. Where several entities each keep their own books, that is the neighbouring workflow on company consolidation.

Immocloud case study FAQ

Common questions

What exactly goes into the accounting system?

Bookings, the receipt image behind each one, and the person accounts they post against. Which shape the bookings take depends on the route: through the Buchungsdatenservice they arrive in DATEV Rechnungswesen as journal entries, through the Rechnungsdatenservice they arrive in DATEV Unternehmen Online as booking proposals for the advisor to release.

Why does Immocloud offer two DATEV routes rather than one?

Because two different people do the bookkeeping. A company doing its own books wants the entry made; a company that has handed bookkeeping to an advisor wants a proposal the advisor reviews and releases. Measured across the connected systems, journal entries can be created on 10 of the 29 and booking proposals on 10, and DATEV is the vendor where the choice between them is a product decision rather than a limitation.

Do the receipt images really travel, or only the figures?

Both, and this is the unusual part. Writing a document file is supported on four of the 29 connected systems, and both DATEV products are among the four. For a property portfolio that matters more than it sounds: a service-charge statement that gets challenged is settled by the receipt, not by the entry.

What happens to creditors and tenants as records?

They are maintained in Immocloud and they arrive on the other side under whatever that system calls them. DATEV Rechnungswesen keeps person accounts as contacts and can have them written and updated; sevdesk and Lexware Office keep the same records as customers and suppliers. One connection writes both shapes, which is the point of a shared model.

Why not build the accounting integrations in-house?

Because depth is the requirement, not coverage. Immocloud's users have already reconciled everything before the handover, so a shallow export would throw away the work rather than pass it on. Building that depth once per accounting system, and keeping it through every change on the other side, is a different product from property management.

What if the company does more than hold property?

That is the case the combination is for. A company with activities outside the portfolio keeps its general accounting where it already is and lets the property side arrive there properly, rather than choosing between a property tool that cannot book and an accounting system that knows nothing about units and billing periods.

Other case studies

Automates the full accounts payable cycle and posts every payment back into the customer's ERP.Read the case study

Turns tracked project time into draft invoices inside the accounting system the customer already runs.Read the case study

Pulls overdue invoices out of the customer's ledger so collection can start without a manual upload.Read the case study

Syncs client data and invoices between the CRM and the DACH accounting systems its customers run.Read the case study

Ship your ERP and accounting integrations. Connect once.

Book a demo