Custom iBurgerzaken integration development
A house move, an extract or an application for a travel document often starts online and ends in iBurgerzaken. In between, many municipalities still rely on manual work: retyping data, forwarding requests, chasing status updates. Appfront builds integrations with iBurgerzaken so that applications, appointments and cases land in the right place automatically, and residents can see where their application stands.
What is an integration with iBurgerzaken?
iBurgerzaken is the civil affairs suite from PinkRoccade Local Government. Municipalities use it to maintain the Personal Records Database (BRP), process travel documents and driving licences, and handle house moves. In tenders, BRP distribution via StUF-BG 3.10 is a standard requirement, alongside integrations with, among others, the Makelaarsuite and the basic registers via Haal Centraal.
Civil affairs work touches many other systems. A resident reports a house move through an e-form, books a passport appointment in the appointment system, and then wants to know where their application stands. Without an integration, an employee retypes the house move, the front-desk employee looks up the appointment on a different screen, and the resident calls the customer contact centre. That costs time and introduces errors into a register that has to be correct.
We build custom integrations because no two municipalities have the same landscape. Which e-counter, which appointment system, which case management system and which interfaces are available in your environment determines what the integration needs to do. If PinkRoccade or your portal supplier already offers an integration that does what you need, custom development isn't necessary, and we will tell you so.
No retyping
Applications arrive instantly.
Status known
For residents and the KCC.
As agreed
Via the standards.
How we build your integration with iBurgerzaken
We start with your service delivery: which applications come in online, which systems you use alongside iBurgerzaken, which interfaces are available, and where work is still done by hand. Then we build a first integration for the flow with the biggest gain, often house moves or appointments for travel documents. You work with it for a while. Further flows, status messages and reports follow if that goes well. After that, we maintain the integration as your landscape changes.
Flows and interfaces.
The flow with the biggest gain.
Statuses and further flows.
Go-live, monitoring, and maintenance when things change.
What an integration with iBurgerzaken does in practice
The components below appear in almost every iBurgerzaken integration. Which ones you need depends on your service delivery and your systems.
Applications
From e-counter and forms.
Agreements
Front desk and civil affairs together.
Cases
To the case management system.
Status
For residents and the KCC.
Checks
Before anything is processed.
Log
Every message recorded.
Who we build an integration with iBurgerzaken for
The integration is intended for municipalities that work with iBurgerzaken and no longer want to update other systems by hand, and for suppliers that want to connect to it.
Municipalities
Large and small.
Collaborations
Shared civil affairs.
Services
Front desk and KCC.
Suppliers
Portals and line-of-business applications.
Technology and integrations
This page is about integrations with iBurgerzaken. For the national register, see our page on the BRP integration, for the messaging standard our page on the StUF integration, and for municipalities in general our page on software for municipalities. You can read about our approach on building custom software.
Why Appfront for your integration with iBurgerzaken?
A house move that gets retyped, an appointment that can't be found with the application, or a resident who has to call to find out where their passport is: all of these cost a municipality time and trust. That is what we build against: applications that arrive immediately, statuses that flow back, and integrations built on the standards your environment offers.
Fewer errors
No retyping in the BRP.
Fewer calls
Status for the resident.
As agreed
Via the standards.
Security and privacy for an integration with iBurgerzaken
Citizen services (burgerzaken) handles personal data from the BRP (the Dutch personal records database), which is subject to strict rules. The integration uses only what is needed for the request, does not store personal data in URLs or log files, has role-based access, and stores keys and certificates encrypted.
The part we build runs in your own environment or in a European data centre that meets your municipality's requirements, with encrypted storage and daily backups. We record the processing in a data processing agreement and align with the BIO (the Dutch government information security baseline) and your municipality's security policy.
Frequently asked questions about an iBurgerzaken integration
Questions municipalities ask before getting started.
iBurgerzaken is the citizen services suite from PinkRoccade Local Government. Municipalities use it for maintaining the BRP, processing travel documents and driving licences, and handling relocations and other changes.
Via the interfaces available in your environment, such as StUF-BG or the Haal Centraal APIs, and for cases via the ZGW APIs. Which interfaces are available and what arrangements you make with PinkRoccade for them is something we look at in the first step.
A BRP integration queries the national Personal Records Database (BRP). An iBurgerzaken integration connects the system your municipality uses to handle citizen services with your other systems, such as the online services portal, appointments and case management system. Sometimes you need both.
Yes, if your environment offers an interface for it. The integration prepares the relocation in citizen services, with the checks you want, so that an employee reviews it instead of retyping it. You decide what may happen automatically and what requires review.
Yes. The integration can pass the status of a request on to the case management system, the resident portal or MijnOverheid. That way residents don't have to call to find out where their request stands.
The integration reports it and records what went wrong, without personal data in the log. The message is retried or queued for review, so no request is lost or processed twice.
For municipalities that work with iBurgerzaken alongside an online services portal, appointment system or case management system that isn't tied to it, and for suppliers who want to connect to it. If all your systems are already integrated and you aren't missing anything, you don't need a custom integration.
Citizen services connected to everything else?
Tell us which systems you use alongside iBurgerzaken and what is currently done by hand. We'll show you how the integration works.