Messages that follow the sector standard Repairs, rentals and customer contact without retyping One language between housing association and supplier

Custom VERA integration development

Appfront builds integrations based on VERA, the data standard of the housing association sector, managed by Aedes Datastandaarden. VERA describes the data and messages that housing associations and their suppliers exchange, with interfaces specified in OpenAPI. We make sure your own system or app speaks those messages: repair requests to maintenance companies and the status back, data on tenants and homes to your customer portal, and integrations between the housing association's systems.

What is a VERA integration?

VERA is the data standard of the housing association sector. It includes a logical data model, reference data, process messages and interface specifications in OpenAPI, and is event-driven: when something happens in one process, the other process is notified. Since 2023, VERA has been managed by Aedes Datastandaarden. Housing associations and suppliers use the standard to describe and exchange data in the same way.

Without a shared standard, every housing association builds its own integration with every supplier. A tenant's repair request goes by email to the maintenance contractor, and the status comes back by phone. The customer portal shows data that doesn't match the primary system. And a contractor working for ten housing associations ends up with ten different ways of working.

We build custom because every situation is different: whether you are a housing association, supplier or software developer, which processes you want to integrate, which systems are already in place, and which version of the standard your partners use. What the standard prescribes, we follow from the Aedes Datastandaarden specifications; we make sure your system works with it.

According to the standard

Messages and interfaces following the VERA specifications, so partners understand them without translation.

Repairs without email

Repair requests and work orders sent to the maintenance contractor, with the status coming back automatically.

Consistent customer portal

Data on homes, tenants and contracts kept consistent across the primary system, portal and apps.

How we build your VERA integration

We start with your role and your processes: which data needs to move between which systems, and how it works today. It often starts with one process involving a lot of manual work, such as repairs, and one partner who already works with the standard. That way the first result is quickly visible.

1
Mapping processes and systems

Your role, processes, systems, partners and the version of the standard.

2
Messages and interfaces

The VERA messages and interfaces needed for your processes.

3
Building the integration

Your system connected according to the standard, with message validation.

4
Testing and maintenance

Testing with real partners, going live, and maintenance when new versions are released.

What a VERA integration actually does

The components below appear in almost every VERA integration. Which ones you need depends on your processes.

Repairs

Repair requests and work orders with the status returned.

Homes

Data on homes and units according to the standard.

Tenants and contracts

Tenants and contracts passed to the portal and apps.

Reference data

Codes and value lists according to the standard.

Validation

Messages validated against the specifications.

Log

Status and result per message.

Who we build a VERA integration for

The integration is intended for parties in the housing association sector that exchange data.

Housing associations

Your own systems and apps. Integrating according to the standard is the core.

Maintenance

Work for multiple housing associations. One way of working counts for the most.

Contractors

Planned maintenance and renovation. Getting the status back is what's needed.

Software suppliers

Software for the sector. The standard is the core.

Technology and integrations

This page is about integrations according to VERA. For housing associations in general, see our page on software for housing associations; for points scoring, our page on a calculation tool for the housing valuation system; and for allocation, our page on tenant selection with income testing. You can read about our approach on software development.

If you would first like to determine which integrations your processes need, take a look at our integrations according to CORA.

VERA Aedes Datastandaarden OpenAPI Process messages Event-driven exchange Reference data Repair requests Homes and tenants Message validation Log per message

Why choose Appfront for your VERA integration?

A repair request sent by email can get stuck, and then the tenant phones. That's what we build around: messages following the standard, status that comes back automatically, and data that is consistent everywhere.

One language

Partners understand the messages without translation.

Status updates automatically

A repair can be tracked without making a phone call.

Less custom work per partner

A new partner on the same standard can be connected faster.

Security and privacy in a VERA integration

The integration processes data on tenants and homes, personal data that must be handled with care. Partners receive only the data they need for their assignment, access credentials are stored encrypted, and every message is logged.

The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.

Frequently asked questions about a VERA integration

Questions that housing associations and suppliers ask before they get started.

VERA is the data standard of the Dutch housing association sector, with a logical data model, reference data, process messages and interface specifications in OpenAPI. Since 2023, the standard has been managed by Aedes Datastandaarden.

For processes the standard describes messages for, such as repair requests and maintenance, and for exchanging data about homes, tenants and contracts. We look at which messages are available for your processes in the first step. Where the standard does not yet describe a process, we build an integration that stays as close to it as possible.

With a dedicated integration, every housing association speaks its own language with every supplier. With the standard, a new partner is connected faster because both sides use the same messages. This saves time with every new connection, and reduces the risk of errors in translation.

If those associations use the same standard, largely yes. Differences per association, such as their own codes or versions, are recorded in the integration for each partner.

The standard continues to evolve. Through ongoing maintenance we adapt the integration, and we take partners still using an older version into account. That way, not everyone has to switch at the same time.

Yes. Every message is validated against the specifications before it is sent or processed, with clear notifications about what is wrong.

For housing associations with their own systems or apps, for maintenance companies and contractors working for multiple associations, and for software vendors who want to support VERA in their product.

Exchanging data in the language of the sector?

Tell us which processes you want to integrate, with which partners, and which systems you have. We will show you what the integration looks like.

Edit content