One Portfolio View From SAP for Embassy Group

The situation

Every portfolio report was reconciled from SAP by hand.

Embassy Group manages a large portfolio of commercial and residential property, and the operating record for it lives in SAP: leases, billing and collections, and the costs of projects under construction. Portfolio reporting meant pulling separate SAP extracts for each view and reconciling them by hand, so occupancy, rent roll, collections ageing and project spend were each reported a little differently, and each report took days to assemble.

What we built

One governed model of the portfolio, reconciled to SAP.

We brought the SAP data into one governed analytical model of the portfolio. Extraction pipelines land leasing, billing, collections and project-cost data on Microsoft Fabric, where it is modelled around the entities the business manages: property, unit, tenant, lease and project. Definitions for occupancy, rent roll, collections ageing and budget against actual were agreed once with the finance and asset teams and built into a single semantic model. Power BI reports on that model give leadership the portfolio view and give asset and project teams the detail behind it, all reconciled to SAP.

How it works

The architecture, stage by stage.

1. Source

   • SAP leasing, billing, collections and project-cost data

2. Land

   • Extraction pipelines onto Microsoft Fabric

3. Model

   • One governed model of property, unit, tenant, lease and project, with agreed definitions

4. Serve

   • Power BI portfolio and asset reports on a single semantic model, reconciled to SAP

What changed

What the team has now.

• Occupancy, rent roll, collections and project spend now come from one model, reconciled to SAP.
• Portfolio reports no longer have to be assembled from separate extracts by hand.
• Leadership sees the whole portfolio and the asset teams see the detail behind it, with the same definitions.
• New properties and projects join the model through the same pipelines.