A system of record for real estate is the one place where a property, its units, its leases and its costs are created and changed. Every other tool reads from it. A reporting overlay sits on top of several systems and shows what they held at the last refresh, so it can point out that two numbers disagree but has no way to decide which one is right.
What makes a system the system of record
The term comes from enterprise IT, and the test behind it is short: when two tools disagree about a fact, which one wins? For the base rent of a lease, the area of a unit or the approved budget of a project there should be exactly one answer, and the system that holds it is the system of record. Three things follow from that.
- Changes are made there first. A rent increase, a new tenant or a revised cost plan is entered in that system. Other tools receive the change; they do not originate it.
- It keeps the history. It can tell you what a value was before it changed, who changed it and when.
- Other tools read from it. Reports, portals and spreadsheets take their numbers from it instead of keeping a private copy that drifts.
Most real estate companies already have several systems of record, each for its own slice. The property management tool owns the leases, the development tool owns the project costs, the CRM owns the listings. That works until the same building has to be described in all three, which happens to every building a developer completes and keeps.
What a reporting overlay is
An overlay is a BI layer, a data warehouse or a consolidated workbook that pulls data out of those systems, joins it and shows a portfolio view. Power BI is the usual example. In its documentation on data refresh in Power BI, Microsoft says you might consider a semantic model in Import mode "a point-in-time copy", one that has to be refreshed to pick up changes in the sources. On shared capacity Power BI allows eight scheduled refreshes a day; on Premium, PPU or Fabric capacity the limit is 48. DirectQuery mode skips the copy and queries the sources live, but it still only reads.
None of this is a flaw in Power BI. A dashboard is supposed to read. The trouble starts when the dashboard is the only place where the portfolio exists as a whole, because then the portfolio has no owner. It is assembled every night from parts that each belong to someone else, and the logic that matches a project in one tool to a building in another lives in a query that one analyst understands.
Where the overlay breaks
The same situations come up in almost every portfolio that is held together by reports.
| Situation | What the overlay shows | Where it has to be fixed |
|---|---|---|
| The development tool and the property management tool hold different areas for the same unit | Two numbers, or whichever one the join happens to pick | In one of the source systems, by hand |
| A project completes and becomes a building you operate | Two unrelated rows until someone maps the IDs | By re-keying the building into the operating system |
| A listing goes out with last year's rent | Nothing, because the portal export is not in the model | In the CRM, usually after the first inquiry arrives |
| An auditor asks who changed the budget and when | The current value | In the source system's history, if it keeps one |
| A refresh fails overnight | Yesterday's numbers, often with no warning on the page | Rerun the refresh, then check what changed in the meantime |
The pattern is the same in every row. The overlay can make a disagreement visible, but the fix always happens somewhere else, followed by an export, a comparison and another refresh. That reconciliation loop is the real running cost of an overlay, and it grows with every system you add underneath it.
The handover is where it costs the most
The weakest point is the moment a project becomes a building. The DIN 276 cost history, the warranties and defect deadlines, the decisions made in each phase, the areas and the energy data all sit in the development tool, while the property manager re-keys whatever survived into a second system. A dashboard can show the finished project and the new managed building side by side. It cannot make them the same property, so the operating team starts without the history it will need when the first warranty claim or the first capex question comes up.
How to tell which one you are looking at
Vendors use the phrase "single source of truth" for both. These questions separate them quickly in a demo:
- Where do I change the rent of a lease? If the answer is "in your other system, and it shows up here after the next refresh", you are looking at an overlay.
- Can I see the previous value of a field, who changed it and when?
- Does the property stay the same record from project to managed building to listing, or is there a mapping table between stages?
- What happens to the reports when an ID changes in one of the source systems?
- Can other tools read the records directly, or only an export of them?
An honest answer to the first question settles most of it. If changes are made somewhere else, the tool is a view, however good the view is.
Where REPM sits
REPM is built as the system of record underneath development, management and listings, which is the idea behind one record from land to lease. The same property record carries the project with its phase model and DIN 276 cost calculation, then the units, leases, tenants, maintenance, rent and indexation once it is operating, and then the listings that are published, updated and withdrawn on ImmobilienScout24 and your other channels, with inquiries coming back to that record. The project a team completes is already the property it manages, so nothing is re-keyed at handover.
REPM runs on Microsoft Power Platform and Dataverse, with EU and DACH data-residency options under Microsoft's EU Data Boundary, plus role-based access and audit trails. It is ready for Copilot Studio and Dataverse agents. Because it runs in your own Dataverse, Power BI, Excel and the Web API read straight from the records. On the platform side, Dataverse auditing logs create, update and delete operations and can show who changed a field, when, and what the previous value was.
That does not make Power BI redundant. It changes its job: pointed at a system of record, a dashboard is a view of one set of records, and the nightly matching logic disappears. The trade-off is real, too. REPM fits best where a company already works in Microsoft 365 and the Power Platform. An organisation with no Microsoft footprint takes on a platform along with the product, and that belongs in the decision.
Test it with one rent change
The quickest test of any tool that claims to be a system of record is to change one rent and watch where the change appears. Load a few properties with their units and leases into the free trial, change a lease, and see whether every view follows without an export. For the full lifecycle from project to listing on your own data, request a demo.