Real estate portfolio management software is the system of record for a company that owns, develops or manages property. It holds every property, the projects that create them, the units and leases inside them, and the listings that market them, on one record per building. Everything else in the business, from cost control to Nebenkostenabrechnung to the ImmobilienScout24 listing, reads from that record and writes back to it.
That definition matters because the category is easy to confuse with three neighbours. A broker CRM (Maklersoftware such as onOffice) tracks prospects and listings and stops at the signature. Landlord software (objego, immocloud, Vermietet.de) manages leases and charges for small portfolios and has no concept of a development project. Accounting or ERP books the money but does not know that a cost line belongs to KG 300 of a specific building phase. Portfolio management software sits across all three: it is where the building lives for its whole life, and the other tools attach to it.
What the property record actually holds
The word "record" hides a lot of structure. In practice a portfolio system carries a hierarchy and a set of attached objects, and the quality of the software is mostly the quality of those links.
| On the record | What it contains | Who works in it |
|---|---|---|
| Master data | Address, geocode, land register reference, areas, year built, energy certificate, media | Everyone |
| Hierarchy | Portfolio, project, construction phase, building, unit; in German development typically Quartier, Bauabschnitt, Haus, Wohnung | Development, asset management |
| Cost model | Plan and actual per DIN 276 cost group, KG 100 to KG 800, with plan versions and variance | Development controlling |
| Cash flow and metrics | Time-phased cash flow, IRR, MOIC, cap rate, DSCR per cost plan version | Finance, investors |
| Units and leases | Rentable units, tenants, leases with terms, indexation, deposits, break options | Property management |
| Operations | Maintenance requests, inspections, vendors, CapEx items, service charges | Property management |
| Marketing | Listings, portal publications, web exposés, inquiries and search profiles | Sales, letting |
If any of those lives in a separate tool with its own copy of the address, you do not have a system of record. You have four systems and a reconciliation job.
The three jobs it has to do
1. Develop
A development team needs the building to exist in the system before it exists on the ground: as a project with phases, a budget by cost group and a cash-flow forecast. The controlling question is always the same, which cost group is running over plan and by how much, and it has to be answerable per phase and per building, not just per project. DIN 276 is the German structure for that; US teams use their own cost codes, but the shape of the problem is identical. When the building is handed over, the same record should turn into a managed asset without an export.
2. Manage
Once a building is standing, the record carries units, tenants and leases. The operational work is repetitive and rule-bound: index-linked rent adjustments against the VPI, the annual Nebenkostenabrechnung with its twelve-month deadline under § 556 BGB, deposits held to the three-month cap, maintenance requests routed to vendors, CapEx items planned by year. Software earns its keep here by knowing the rules, so that an Indexmiete adjustment is a calculation the system runs rather than a spreadsheet someone maintains.
3. Market
Between development and management sits selling or letting. The record has to publish itself: to ImmobilienScout24 through the portal's REST API, to Immowelt and the long tail through an OpenImmo export, to your own website. Then the inquiries have to come back to the same record, matched to the unit and deduplicated, with consent logged. A portfolio system that treats marketing as somebody else's tool loses exactly the leads the portfolio was built to attract.
How it differs from the tools next to it
| Category | Built around | Where it stops |
|---|---|---|
| Broker CRM (Maklersoftware) | Prospects and listings | The signature. No development, no leases, no cost model. |
| Landlord software | Leases and charges for a few dozen units | Multi-entity portfolios, development projects, syndication beyond one portal. |
| Accounting / ERP | Ledger entries | Does not model the building: no phases, no units, no listings. |
| Spreadsheets | Whatever the last person built | Two people editing, one audit question, or the first version conflict. |
| Portfolio management software | The property record across its life | It is not a general ledger and should not try to be one. |
What to check before you buy
- One record, no exports. Ask to see a building go from a development project to a managed asset in the demo. If the answer involves a CSV, that is the answer.
- A real cost model. DIN 276 cost groups with plan versions and variance per group, not a single budget field.
- Lease rules that are rules. Indexation, Nebenkosten, deposits and notice periods calculated by the system, with the legal parameters visible.
- Syndication built in. Publish, update and withdraw on ImmobilienScout24 and an OpenImmo export for the rest, with the inquiries returning to the record.
- Your data stays yours. A documented API and a full export. Ask what leaving looks like before you arrive.
- Audit trail and permissions. Who changed the rent, when, and who is allowed to see the cost plan. Field-level security is not exotic; expect it.
- Multi-entity and multi-currency. Several owning companies, EUR and USD, without a second instance.
- A platform you can extend. A new field, report or workflow should be something your own team can add, not a change request into a vendor backlog.
Who needs it, and who does not
A private landlord with fifteen units is well served by landlord software and does not need a portfolio system. A pure brokerage that never owns what it sells needs a broker CRM. Portfolio management software is for the organisation that holds property through more than one stage of its life: developers who keep what they build, housing companies, family offices and funds, corporate real estate teams with owner-occupied sites, and asset managers who report to investors on buildings they also run. The common thread is that the building outlives any single tool, so the record has to.
Where REPM fits
REPM is real estate portfolio management software built on Microsoft Dataverse. It covers the three jobs above on one property record: development controlling with DIN 276, units, leases, charges and maintenance, and syndication to ImmobilienScout24 via the official API plus OpenImmo 1.2.7 export. Because it runs on Dataverse, security roles, the audit log and the API are the platform's, and your own team can extend the model. It is the right fit for organisations already on Microsoft 365; if you run on another stack, that is a second platform to license and administer, and we say so up front. You can try it on your own portfolio.