Custom iZaaksuite integration
iZaaksuite is the case management system from PinkRoccade Local Government. Municipalities model their processes in it, receive requests through the web intake, show case information on the resident's personal web page and answer questions through the customer contact system. Appfront builds the connection to the systems that are not yet linked to it, so cases and documents no longer have to be transferred by hand.
What is an iZaaksuite integration?
iZaaksuite is a case management system for municipalities from PinkRoccade Local Government. Processes are modelled in it, residents and businesses submit requests through the web intake, the status of a case appears on the personal web page, and customer contact centre staff answer questions in the customer contact system. Documents are stored and archived.
Whatever is not in the suite often goes by hand. A line-of-business application makes a decision, but the case in iZaaksuite does not know about it. Requests from another channel are retyped. A partnership has its own system alongside those of the municipalities. And for management information, exports are merged in a spreadsheet. This creates duplicate work, and a file that is missing just the decision or the latest letter. That is awkward for the case handler, and even more so for the archivist.
We build custom integrations because every municipality has different systems alongside iZaaksuite. Which line-of-business applications, which channels, which archive and which figures need to go where determines how the integration works. Which interfaces your version offers, such as StUF-ZKN or the ZGW APIs, we review together with you and with PinkRoccade.
Complete cases
Including from other channels.
Line-of-business applications included
Decision stored with the case.
According to the standards
The interfaces of your version.
How we build your iZaaksuite integration
We start with your municipality: which systems run alongside iZaaksuite, which data currently moves by hand, and which integrations already exist. Then we look at which interfaces your version of iZaaksuite offers and which agreements you make with PinkRoccade. We often start with the line-of-business application with the most cases, because that is where most of the duplicate work sits. Other channels, the archive and management information follow once that runs well. After that, we maintain the integration when iZaaksuite or your other systems change.
Systems, processes and integrations.
What your version offers.
Cases, statuses and documents.
Go-live, monitoring, and maintenance when things change.
What an iZaaksuite integration actually does
The components below appear in almost every iZaaksuite integration. Which ones you need depends on your municipality and systems.
Creating a case
From every channel.
Line-of-business applications
Decisions with the case.
Statuses
To the resident.
Documents
To the file and archive.
Reporting
Turnaround times per case type.
Log
Every message recorded.
Who we build an iZaaksuite integration for
The integration is intended for municipalities that work with iZaaksuite alongside systems that are not linked to it. The more cases and the more systems, the more it delivers.
Municipalities
Cases from front desk to archive.
Partnerships
Multiple municipalities, one way of working.
Customer contact centre
Answers without searching.
Suppliers
A line-of-business application on iZaaksuite.
Technology and integrations
This page is about integrations with iZaaksuite. For the standards, see our page on the ZGW API integration and our page on the StUF integration; for the resident portal, our page on a citizen portal; and for the architecture, our page on GEMMA integration. You can read about our approach on building software.
Why Appfront for your iZaaksuite integration?
Decisions that stay in a line-of-business application, requests that are retyped and management information from separate exports cost a municipality time and leave the file incomplete. That is what we build on: every case complete, line-of-business applications integrated, and an integration through the interfaces your version offers.
Complete file
Decision and case together.
Less retyping
Every channel comes in.
As agreed
Via the interfaces.
Security and privacy in an iZaaksuite integration
The integration processes data about residents and businesses, sometimes including special category personal data. We use only what the case needs, access is set up per role, keys and certificates 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. We record the processing in a data processing agreement and align with the security requirements that apply to your municipality.
Frequently asked questions about an iZaaksuite integration
Questions municipalities ask before getting started.
iZaaksuite is a case management system for municipalities from PinkRoccade Local Government. It supports process modelling, web intake for residents and businesses, case information on the personal web page, the customer contact system for the contact centre, and document storage and archiving.
It does. iZaaksuite works with other PinkRoccade products, such as iFormulieren and the digital counter, and with systems that use the same standards. If your system already connects and does what you need, custom work is not necessary, and we will tell you so. A custom integration is for systems and channels that are not part of that.
Via the interfaces your version of iZaaksuite offers, such as StUF-ZKN or the ZGW APIs. In the first step we look at which messages and data are available, and which agreements you need to make with PinkRoccade, so you don't get stuck on a route that doesn't exist.
Yes. When the line-of-business application produces a decision or document, the integration attaches it to the right case in iZaaksuite and updates the status. The case handler and the contact centre then see the whole file in one place.
Yes. If several municipalities work together, for example in a shared implementation organisation, the integration can send cases to and from the right municipality, with agreements on who may see which data.
The integration reports it and records what went wrong. The message is retried or set aside for review, so no case is lost or ends up duplicated in iZaaksuite.
For municipalities and partnerships that work with iZaaksuite alongside line-of-business applications, channels and archives that are not tied to it, and for suppliers who want to connect their line-of-business application to iZaaksuite. If all your systems are already integrated and you are missing nothing, you don't need a custom integration.
iZaaksuite connected to the rest?
Tell us which systems you use alongside iZaaksuite and what is currently done by hand. We will show you how the integration works.