FPRE — Fondation de placement Real Estate — is the Swiss benchmark and index provider for direct real estate investments. Its market reports and return indices are the reference standard used by institutional fund managers, pension funds and regulators to assess portfolio performance in the Swiss market.
For fund managers, FPRE compatibility is not optional. It's the language in which Swiss institutional real estate communicates. If your reporting cannot produce FPRE-aligned outputs, you face a permanent translation problem between your internal data and every external comparison, investor question and regulatory submission that references the benchmark.
This article explains what FPRE reporting actually requires, where the data problems typically arise, and how fund managers are solving this in 2026.
What FPRE reporting covers
FPRE publishes a set of performance indicators and benchmarks covering the Swiss direct real estate market. For fund managers, the most relevant elements are the return decomposition metrics — separating income return from capital return — and the standardised property-level KPIs used to contribute to and compare against the FPRE index.
At the property level, the key metrics are:
- Gross rental income — actual receipts from tenants, excluding service charges
- Net initial yield (rendement initial net) — net income as a percentage of market value
- Vacancy rate — by unit count and by revenue, separately
- WALT (weighted average lease term) — remaining lease duration weighted by income
- Capital expenditure — maintenance versus value-enhancing, separately classified
- Market value — appraised value at the reporting date
These metrics must be consistent at every level: property, sub-portfolio, total portfolio. An inconsistency at property level propagates to the fund level and creates errors that are difficult to trace after the fact.
Where the data pipeline breaks down
The challenge is that most of these metrics are not produced by a single system. They require data from at least three sources: the property manager (actual rents, vacancies, lease data), the accountant (income and expenditure in the correct classification), and the valuer (market values at the reporting date). Each of these parties may deliver data in different formats, at different times, and with different conventions for classification.
The most common failure points are:
Vacancy rate inconsistency. Property managers often report vacancy by unit count; FPRE requires vacancy by revenue. A property with one large vacant unit and five small occupied units has a very different vacancy picture depending on which measure you use. Translating between them requires unit-level rental data that not all régies provide automatically.
Capex classification mismatches. FPRE separates maintenance expenditure (which flows through the income statement) from value-enhancing expenditure (which is capitalised). Swiss property managers don't always use this classification consistently, which means the fund manager's team has to reclassify expenditure lines manually each period.
Lease data timing. WALT calculations depend on current lease start dates, end dates and contracted rent. This data lives in the property manager's system. If it's delivered via a quarterly PDF or a non-standard Excel extract, maintaining an accurate WALT figure in real time is essentially impossible.
Market value vintage. When does the FPRE-aligned reporting use the latest appraised value? If a revaluation happens mid-quarter, the treatment of the value change — whether it appears in capital return or creates a timing gap — must be handled consistently.
Why manual reconciliation doesn't scale
Many fund manager teams solve these problems manually: a senior analyst maintains the mapping between the régie's categories and the FPRE classifications, updates the WALT calculation each quarter, and reconciles the income and capital return components by hand.
This works — up to a point. The typical breaking point is around ten to fifteen properties, or when the team adds a second property manager with different data conventions. At that point, the reconciliation effort stops being a quarterly task that one person handles and becomes a week-long coordination exercise involving multiple people and multiple rounds of correction.
The risk also increases with scale. A manual reconciliation performed under deadline pressure, in a shared workbook with multiple contributors, is precisely the environment in which classification errors and formula mistakes accumulate undetected.
How FPRE-ready reporting software works
The purpose of dedicated portfolio management software in this context is to eliminate the manual reconciliation layer — not by replacing the property managers or the accountants, but by standardising the data they deliver into a single validated layer before the FPRE-compatible calculations run.
In practice, this means the software maintains a mapping between each property manager's data format and the standardised schema. When quarterly data arrives — whether via API integration, structured export or managed upload — it is validated against that schema before it enters the reporting layer. Validation controls flag classification mismatches, missing values and inter-period inconsistencies before they become report errors.
The FPRE-compatible outputs — vacancy by revenue, WALT, net initial yield, return decomposition — are then calculated from the validated dataset, not from a manually maintained spreadsheet. When a value changes, all dependent metrics update consistently.
The other consequence is the audit trail. Every figure in the FPRE output can be traced back to its source data point, the validation that approved it, and the timestamp of the import. For FINMA-regulated fund managers, this traceability is increasingly important: regulators expect to be able to follow the data lineage from raw régie inputs to published investor reports.
FPRE and the broader benchmarking picture
FPRE is the dominant benchmark for the Swiss market, but it exists alongside other standards that institutional managers need to engage with. INREV (the European Association for Investors in Non-Listed Real Estate Vehicles) publishes guidelines for pan-European fund performance reporting that apply to many Swiss managers with cross-border exposure. MSCI Real Estate provides comparable data for international benchmarking. SFAMA (the Swiss Fund and Asset Management Association) sets operational standards for Swiss collective investment schemes.
Producing reports that are simultaneously FPRE-compliant, INREV-compatible and FINMA-auditable from a single data source — rather than maintaining three parallel processes — is one of the main practical advantages of portfolio management software for Swiss institutional managers in 2026.
Practical steps for teams preparing for FPRE submission
If your team is preparing for its first structured FPRE submission, or looking to improve a process that's become unwieldy, the most important step is not technology — it's data standardisation. Before any software can help, you need a clear specification of what data each property manager should deliver, in what format, and on what schedule.
The second step is establishing a classification mapping: a documented translation between each régie's cost categories and the FPRE/INREV classification standards. This mapping rarely exists in written form in organisations that have been doing this manually — it lives in the head of the analyst who's done it for three years.
Once that documentation exists, the transition to structured software becomes a matter of configuration rather than reinvention. Most fund manager teams find that a six to eight week onboarding period is sufficient to go from existing Excel-based processes to a validated, FPRE-ready reporting pipeline — without disrupting the property managers or the underlying accounting systems.
STREETS supports FPRE-compatible reporting natively
STREETS is built for Swiss institutional real estate. FPRE-compatible outputs, FINMA-auditable data trails and multilingual reporting in English, French and German — from a single validated dataset. Typical onboarding: six to eight weeks.
Book a demo