StUF-ZKN & StUF-BG SOAP / XML Digikoppeling

Custom StUF integration development

Appfront builds custom StUF integrations for the municipal application landscape. We connect case management systems, BRP services, tax applications and mid-office via StUF-ZKN and StUF-BG: XML messages over SOAP and Digikoppeling, secured with PKIoverheid. And because StUF is migrating towards the ZGW APIs and Common Ground, we also integrate with or migrate to that modern successor.

What is a StUF integration?

StUF, short for Standaard Uitwisseling Formaat (Standard Exchange Format), is the messaging standard maintained by VNG Realisatie (formerly KING) for data exchange within the municipal application landscape. It describes how applications exchange structured XML messages, usually via SOAP on top of Digikoppeling. StUF is a mature standard that is still widely used by municipalities and the suppliers of their core applications.

StUF has sector models for different domains. StUF-ZKN handles case and document services between, for example, a case management system and task-specific applications (cases, statuses, decisions, documents). StUF-BG handles basic data: querying and synchronising persons, addresses and companies from a BRP service or data warehouse. A StUF integration can be a simple request/response query, or an asynchronous stream of notifications to which consumers are subscribed.

Appfront builds in line with the official GEMMA/VNG StUF documentation and the OWASP ASVS security standard. It's important to be upfront: StUF is now a legacy standard, and its successor is the ZGW APIs within Common Ground. That's why we don't just build new StUF integrations, but also advise on the migration path and can run StUF and ZGW side by side.

StUF-ZKN: case and document services

The sector model for case-oriented working: creating and updating cases, passing on statuses and decisions, and exchanging documents between the case system and task-specific applications. The foundation for an integrated case landscape within the municipality.

StUF-BG: basic data

Querying and synchronising basic data such as persons, addresses and companies from a BRP (personal records database) facility or data warehouse. With subscriber indications and notifications, connected applications stay up to date automatically.

Migration to ZGW / Common Ground

StUF is legacy; the future is the ZGW APIs. We run StUF and ZGW side by side, or translate StUF-ZKN to the ZGW APIs via a case bridge, so you can migrate step by step without breaking your current integrations.

Our development process for StUF integrations

We work to a proven method that removes uncertainty early and delivers a stable integration. From an initial analysis of your application landscape, sector models and Digikoppeling connection through to go-live and ongoing maintenance, every step is aimed at an integration that your organisation can understand and trust itself.

1
Analysis & scope

We map out which applications need to be integrated, which sector model (StUF-ZKN, StUF-BG or both) and which message types are required, and whether a migration path to ZGW is relevant.

2
Architecture

We design the integration architecture, choose the right Digikoppeling profile with PKIoverheid, and define the message mapping and error-handling strategy.

3
Development

Implementation with XML schema validation, automated tests against the supplier's test environment, structured logging and monitoring. You see working builds along the way.

4
Go-live & maintenance

A controlled go-live with message validation and a safety net, followed by ongoing management, monitoring and, if needed, further migration to ZGW.

What a StUF integration delivers in practice

Every StUF integration is set up specifically for your application landscape, sector models and adjacent systems. Below are the features we deliver most often for municipalities and suppliers who use StUF and want to move to ZGW step by step.

Request/response queries (Lv01/La01)

Synchronous queries where your application sends an Lv01 request and receives an La01 response, for example looking up a person or address in a StUF-BG facility, or retrieving case data via StUF-ZKN. With correct selection and scope parameters.

Notifications & subscriptions (Lk01)

Asynchronous mutation messages (Lk01) that automatically pass changes on to subscribers. With subscriber indications and subscriptions, connected applications stay up to date without having to query repeatedly, including the corresponding Bv03 confirmations.

Document exchange (StUF-ZKN)

Exchanging documents as attachments to cases between the case system and task applications, including large files via MTOM/XOP. Metadata, status and decisions travel along so the case file in the case system stays complete and up to date.

Digikoppeling & PKIoverheid

StUF messages run over Digikoppeling: the WUS profile for synchronous queries and ebMS for reliable asynchronous messaging. We set up the PKIoverheid certificates, endpoints and routing in line with the applicable standards frameworks.

Message validation & mapping

Incoming and outgoing messages are validated against the StUF schemas (version 03.01) and the sector models. We build clear mappings between your internal data model and the StUF elements, with clean error handling via Fo0x error messages.

StUF to ZGW case bridge

A translation layer that converts StUF-ZKN messages to the ZGW APIs and vice versa. Existing StUF applications keep working while you connect new components to modern REST/JSON APIs, the practical route to Common Ground.

Typical use cases in practice

A StUF integration turns out very differently for every organisation. We see a number of patterns come up again and again in the public sector, and for each of them we have a working set-up that pays attention to the right sector models, Digikoppeling and the migration path to ZGW.

ZAAK

Case management system and task applications

Municipalities that link their case management system via StUF-ZKN to task-specific applications for permits, notifications or social services. Cases, statuses, decisions and documents flow back and forth so that the case file stays central and complete. See also our software for municipalities.

Basic data from the BRP

Applications that use StUF-BG to query or synchronise people, addresses and companies with a BRP (personal records database) facility or data warehouse. With subscriber indications and notifications, data stays up to date without duplicate registration, a core principle of collecting data once. Related: our BRP integration.

Midoffice, broker & taxes

A midoffice or broker acting as a central hub that routes StUF messages between core applications, and integrations with the tax application for assessments and objections. We set up reliable message exchange with clear routing, logging and monitoring across the entire landscape.

Migration to Common Ground

Organisations that want to move from StUF to the ZGW APIs without a big bang. With a case bridge, we run StUF and ZGW side by side and migrate applications in phases, so that your services keep working during the transition.

Technology we use

We build StUF integrations with the official StUF standard (version 03.01) and the sector models, combined with the backend stack that suits you. The exact choice depends on your application landscape, your Digikoppeling connection and the desired migration path to ZGW, so that your organisation can manage or further develop the integration.

If your municipality uses the Liber case management system, read more about our Liber integration.

StUF 03.01 StUF-ZKN (Case and Document Services) StUF-BG (Basic Data) SOAP / XML XML Schema validation (XSD) Digikoppeling WUS & ebMS PKIoverheid certificates Lv01 / La01 / Lk01 / Bv03 / Di01 / Du01 MTOM/XOP for documents Subscriber indications & subscriptions ZGW APIs (REST/JSON) StUF-ZGW case bridge Java / .NET / Node.js / Python BIO / government standards frameworks Logging & monitoring GitHub Actions

Why Appfront for your StUF integration?

Appfront has extensive experience building integrations for a wide range of organisations in the Netherlands, including the public sector. We always start with a thorough analysis of the existing systems and processes: a StUF integration must not only be technically correct, but also add practical value within your application landscape.

For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.

You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also see our broader services around software for municipalities, municipality websites, custom software and Digikoppeling integrations.

  • Experience with StUF-ZKN, StUF-BG and the StUF message types
  • Familiar with Digikoppeling (WUS/ebMS) and PKIoverheid
  • Builds both StUF and ZGW integrations, and migrates between them
  • Secure by default: separation of privileges, authorisation at message level
  • Structured error handling, validation and retry mechanisms
  • Extensive logging and monitoring from day one
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance and proactive further development
  • Approach tailored to your existing application landscape

Security and privacy for StUF integrations

StUF messages containing case and basic data almost always include personal data. Transport therefore runs over Digikoppeling with PKIoverheid certificates and encryption, with authorisation at message level so that a recipient only receives the data it is entitled to. Appfront builds in line with OWASP ASVS and the government standards frameworks (BIO), with separation of privileges and full logging.

We work from the principle of data minimisation: only the data a recipient needs is exchanged. We document the data flows, mappings and message definitions so that your record of processing activities is complete and you can demonstrably comply with the GDPR. Message-level logging makes traffic traceable and auditable.

More about our approach to security: information security policy and CVD policy.

  • GDPR-compliant data processing and minimisation
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least-privilege principles
  • Audit logs with traceable data flows
  • Automatic retry and dead-letter queues
  • Monitoring and alerting for anomalies
  • Secrets management following best practices
  • Documentation for your record of processing activities

Frequently asked questions about StUF integrations

Answers to the questions we get asked most often about StUF integrations.

StUF (Standaard Uitwisseling Formaat) is the messaging standard from VNG Realisatie (formerly KING) for exchanging data within the municipal application landscape. A StUF integration exchanges XML messages via SOAP, usually on top of Digikoppeling. The standard has sector models: StUF-ZKN for case and document services and StUF-BG for core data such as persons and addresses. An integration can range from simple (a request/response query) to complex (asynchronous notifications with subscriptions between several core applications).

StUF is a mature, widely used but now legacy standard. Its successor is the ZGW APIs (REST/JSON) within VNG's Common Ground movement. In practice the two often run side by side: many core applications and national services still speak StUF, while new components use ZGW. Appfront builds both StUF and ZGW integrations and can migrate a StUF landscape step by step towards ZGW/Common Ground, for example via a case bridge that translates StUF-ZKN to the ZGW APIs.

StUF-ZKN (Case and Document Services) handles the exchange of cases, statuses, decisions and documents between, for example, a case management system and task-specific applications. StUF-BG (Core Data) handles querying and synchronising core data such as persons, addresses and companies, often from a BRP (personal records database) service or data warehouse. Both build on the same StUF message structure (version 03.01) and transport layer, but cover a different functional domain. Which one you need depends on the applications and processes you want to integrate.

StUF messages are XML and are exchanged via SOAP, generally over the Digikoppeling WUS profile (and ebMS for certain notification traffic) with PKIoverheid certificates for authentication and security. We work with StUF message types such as Lv01/La01 (request/response), Lk01 (notification/mutation), Bv03 (confirmation) and the free-form messages Di01/Du01. On our side we build the adapter with the stack that suits you — Java/.NET, Node.js or Python — including XML validation against the schemas, logging and monitoring.

The cost depends on which sector model (StUF-ZKN, StUF-BG or both) and which message types are needed, the number of applications to integrate, whether it involves queries only or also mutations/subscriptions, and the requirements around Digikoppeling, PKIoverheid and the supplier's test environment. Any migration path to ZGW also counts. We always provide a clear quote after a no-obligation analysis of your application landscape.

Yes. StUF traffic containing core and case data includes personal data and falls under the GDPR. Transport runs via Digikoppeling with PKIoverheid certificates and encryption, with authorisation at message level so a consumer only receives the data it is entitled to. Appfront builds in line with OWASP ASVS and the government standards frameworks (BIO), with separation of privileges, full logging and a data minimisation approach. We document the data flows so your record of processing activities stays complete and you can demonstrably comply with the GDPR.

Yes. Appfront regularly takes over the management of existing StUF integrations, even if they were originally set up by another supplier. We review the message definitions, mappings, error handling and Digikoppeling configuration, document the current setup and draft improvement proposals. From that point on we handle changes, extensions and monitoring — and, where desired, we can migrate the integration to the ZGW APIs in phases.

StUF is the standard in the Dutch municipal domain. A StUF integration is therefore well suited to municipalities, municipal partnerships, regional environmental agencies and implementing organisations that need to connect core applications such as a case management system, a BRP (personal records database) service, a tax application or a midoffice/broker, or that need to connect to national services. We also help software vendors who want to make their application StUF-compliant or expose it towards ZGW.

Ready to build your StUF integration?

Tell us which applications you want to connect via StUF, which sector models are involved and whether a migration to the ZGW APIs is planned. We are happy to advise on StUF-ZKN, StUF-BG, Digikoppeling and the path towards Common Ground. A no-obligation first conversation will quickly give you a clear picture of the possibilities. Feel free to contact us.

Edit content