Custom SBR Wonen integration development
SBR-wonen is the partnership through which housing associations submit their annual forecast and accountability information digitally: the dPi and the dVi. The data goes to the Housing Associations Authority, the WSW and the ministry, and part of it goes to Aedes for the benchmark. Besides entering it in the portal, an association can submit system-to-system, directly from its source records. Appfront builds the integration that converts your data into a complete XBRL dataset according to the SBR-wonen taxonomy and checks it before submission.
What is an SBR Wonen integration?
An SBR Wonen integration ensures that your association's forecast and accountability information comes from your own systems instead of spreadsheets and manual work. SBR-wonen is a partnership of four organisations: the Housing Associations Authority, the Social Housing Guarantee Fund, the ministry and Aedes. Every year, associations submit their forecast information (dPi) and accountability information (dVi) through it, and Aedes uses part of that data for the benchmark. This way, an association does not have to supply the same data to each party separately.
According to SBR-wonen, you can submit in two ways: manually in the portal, with the option to import part of the data, or system-to-system from the source administration. The main message is XBRL; the WOZ property table may also be submitted as xBRL-csv. The SBR-wonen taxonomy determines the data model, the validation rules and the reporting rules, and reports are sent via Digipoort to the requesting parties. With system-to-system, a complete XBRL dataset must be in place at the end of the chain, because manual completion in the SBR-wonen or Logius systems is then no longer possible. The definitions are written according to the sector standards CORA and VERA; VERA has been managed by Aedes Datastandaarden since 1 April 2023.
We build custom solutions because the data for a dPi or dVi comes from multiple systems: property, finance, lettings and maintenance. In SBR-wonen, every element has its own definition and a unique number, and a performance indicator is built up from key figures with calculation rules and business rules. The integration records, for each key figure, which system and which field it comes from and how it is calculated. The data model can change every year; the model for the dPi2026 was published in the Staatscourant (the Dutch Government Gazette) on 2 July 2026. That is why we maintain the mapping per annual release, so you can see what has changed compared with last year.
From the source
Data from your own systems.
According to the taxonomy
XBRL as SBR-wonen requires.
Checked in advance
Validation rules before submission.
How we build your SBR Wonen integration
We start with your current submission process: which key figures you currently pull from which systems, where spreadsheets and manual edits come into play, and which checks your controller and auditor perform. We then create a mapping for each element of the SBR-wonen taxonomy to your source fields and calculation rules, which you and your auditor can review. We first build the part that takes the most manual work, often the property and asset data, and have the integration generate an XBRL dataset that we test against the validation rules before anything is submitted. The remaining components and the submission itself follow. With each new annual release of the data model, we update the mapping.
Key figures, sources, manual work.
Elements mapped to your source fields.
XBRL checked before submission.
Submission, monitoring and management per annual release.
What an SBR Wonen integration actually does
The components below feature in almost every SBR Wonen integration. Which ones you need depends on your systems and on what your software supplier already provides.
Mapping
Elements mapped to your source fields.
Calculation rules
Key figures calculated traceably.
XBRL
Dataset according to the taxonomy.
Validation
Rules checked before submission.
Annual releases
Changes visible per model.
Log
Every submission can be traced.
Who we build an SBR Wonen integration for
The integration is intended for housing associations that currently compile the dPi and dVi largely by hand, or that need to combine data from multiple systems. The more systems and manual steps involved, the greater the benefit.
Housing associations
Submission from your own source.
Controllers
Traceable key figures.
Information managers
One mapping per annual release.
Software builders
Your package ready for S2S.
Technology and integrations
This page is about submitting the dPi and dVi via SBR-wonen. For Standard Business Reporting in general, such as returns and reports to the Dutch Tax Authority or the KvK (Chamber of Commerce), see our page on SBR integration, and for the format itself our page on the XBRL integration. If you are looking for software for your housing association as a whole, see custom housing association software development. You can read about our approach at building software.
Why Appfront for your SBR Wonen integration?
Key figures compiled from spreadsheets every year, a validation error that only surfaces at submission, or a figure nobody remembers how it was calculated: these cost a housing association time around every deadline. That is what we build on: a mapping you can review, checks before submission and an integration that shows what has changed per reporting year.
Traceable
Every figure traced to its source.
Checked in advance
Errors caught before submission.
Per reporting year
Changes tracked.
Security and privacy in an SBR Wonen integration
The integration processes financial and property data from your housing association, which is commercially sensitive. It uses only the data the reporting requires, with a dedicated account that has exactly the permissions needed for it, and logs every dataset and submission with time and result. If the data includes information about tenants or individuals, the GDPR applies and we process no more than the reporting requires.
The integration runs in a European data centre, with encrypted connections and storage. Certificates and keys for submission are kept secured and are not visible to staff. We agree with you in advance who may compile, check and submit a dataset.
Frequently asked questions about an SBR Wonen integration
Questions that controllers, information managers and software suppliers in the housing association sector ask before getting started.
SBR-wonen is a collaboration between the Dutch Housing Associations Authority (Autoriteit woningcorporaties), the Social Housing Guarantee Fund (WSW), the ministry and Aedes. Through SBR-wonen, housing associations submit their forecast and accountability information digitally each year, so they do not have to provide the same data to each party separately.
The dPi is the forecast information and the dVi the accountability information that housing associations submit every year. Both go to the requesting parties; Aedes uses part of the accountability information for the benchmark.
It means the report is submitted directly from your source administration instead of being entered in the portal. According to SBR-wonen, a complete XBRL dataset must then be available at the end of the chain, because manual supplementing is no longer possible.
The main message is XBRL; the WOZ property table may also be submitted as xBRL-csv. The SBR-wonen taxonomy defines the data model, the validation rules and the reporting rules. The reports go via Digipoort to the Autoriteit woningcorporaties, the WSW and the ministry.
SBR is the framework of agreements for digital reporting, for example to the Dutch Tax Administration and the KvK (Chamber of Commerce). SBR-wonen uses that framework for the housing association sector, with its own taxonomy and definitions. This page covers only the dPi and dVi.
The SBR-wonen definitions are written according to the sector standards CORA and VERA. VERA is the data exchange standard in the housing association sector and has been managed by Aedes Datastandaarden since 1 April 2023. If your systems already use VERA, that makes the mapping easier.
For housing associations that need to combine data from several systems, or whose software supplier does not cover the entire submission. If your package already delivers a complete dataset that you only need to check, a custom integration is usually not necessary.
Your dPi and dVi from your own administration?
Tell us which systems you work with and how you currently compile the submission. We will show you how an integration takes that over.