Skip to main content

2026.7.5 Audit trail logs reads

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZTCFixed silently skipped ZaakTypeBesluitType relation on PATCH zaaktypenPATCH /v1/zaaktypen/{id} (v1.3) used to skip creating a ZaakTypeBesluitType relation whenever the besluittype omschrijving didn't match an existing besluittype in the destination catalog, without surfacing an error to the caller. Since this relation is a soft reference on omschrijving (no FK), it is now always persisted, so it resolves automatically once a matching besluittype exists.Bij het bijwerken van een zaaktype wordt de koppeling met een besluittype nu altijd opgeslagen, ook als het besluittype nog niet bestaat. Zodra een besluittype met dezelfde omschrijving wordt aangemaakt, werkt de koppeling vanzelf.
DRC/ZRC/BRCAudit trail now logs readsRead (GET) requests on documents, zaken and besluiten are now recorded in the audit trail. Previously reads were not logged at all, due to the resulting audit log volume. This log is intended to support detection of data leaks by showing which client application read which records. To keep the log volume manageable, specific client_id's whose reads are not of interest can be excluded from read logging, either as an exact value (e.g. harvester-123456789) or a wildcard pattern (e.g. rx.Mission.*). Excluded client_id's will not appear in read audit entries.Van elke keer dat een document, zaak of besluit wordt opgevraagd (gelezen) door een applicatie, wordt dit nu vastgelegd. Dit helpt bij het opsporen van datalekken: er is nu zichtbaar welke applicatie welke gegevens heeft geraadpleegd.

2026.7.2 Better GET all documents query

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
DRCPerformance improvement GET ALL queryThe GET query without query parameters returns all documents of an organisation in pages. Organisations with millions of documents experienced time outs in this query. The query now is optimized so that it returns in a reasonable time with valid data.
NRCLocking of subscriptionsWhen all notifications of a subscription have failed for a week, the subscription is locked, meaning that notifications are not sent for this subscription anymore.Beheerders kunnen unlocken in ZCA -> Notificaties

2026.6.9: number generator fix for ZRC and BRC

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
NRCImproved Hangfire retry handling for webhook delivery failures.Webhook processing recovers automatically after transient failures, improving reliability of callback delivery.Notificaties bereiken eindgebruikers betrouwbaarder, met minder verstoringen na tijdelijke storingen.Achtergrondtaken herstellen zichzelf, minder handmatige interventie nodig.
ZRCRemoved legacy BSN column inpbsn from database.Deprecated internal field inpBSN removed.Minder risico op datalekken.
ZRC/BRCEnforced uniqueness: identificatie+owner combination now guaranteed unique.Geen dubbele zaak-/besluitnummers meer, ook niet als externe applicaties foutieve bronorganisaties invoeren.
ZSDMS/DRCAdded retries for token renewal Hangfire jobs.Document- en berichtverwerking stabieler na onderhoud of storingen. Hierdoor betere data consistentie.

2026.6.3: Improved security for filter queries

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZRCEnforced strict validation for query parameters.Integrations must only use supported query parameters; unknown parameters now return a 400 response instead of being ignored.Gebruikers krijgen geen onbedoelde resultaten meer bij foutieve filters, wat de kans op datalekken verkleint.
ZRCExpanded audit trail coverage for GET queries with filters rsin and vestigingsnummer.Beheerders krijgen uitgebreidere audittrail-informatie voor onderzoek en monitoring op organisatie-identificaties.

2026.5.9: Security and billing improvements

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZRCAudit trail now contains GET requests BSNZoekacties op basis van BSN worden gelogd in de audit log.
ZRCHMAC key rotation support was implemented for encrypted BSN, including versioned key usage and migration tooling.Beheerders kunnen sleutels gecontroleerd roteren met migratieondersteuning, wat security-beheer en operationele continuiteit verbetert.

2026.5.3: Audit trail optimization

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZGWAudittrail optimizations for improved efficiencyThe storage of the audit trail was optimized in order to decrease the enormous size of the audit trails. From now on changes are stored as delta's and snapshots (snapshots being created after 25 delta's.). Existing audit trails still are kept in the 'old' format. There is no change in the response on GET's of audit trails.

2026.4.13: BSN encrypted

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZRCBSNs in database table zaakrollen_natuurlijk_personen are now stored encrypted.

2026.4.2: UI problems in ZCA solved

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
ZCAIn the new UI for ZCA (task applications and ZSDMS), the plus button for adding ZSDMS case type configurations was greyed out, preventing new entries from being created. This has been resolved. Additionally, the sorting of the synchronisation overview now consistently shows the most recent entries at the top.In de nieuwe ZCA-interface (taakapplicaties en ZSDMS) was de plusknop voor het aanmaken van ZSDMS-zaaktypeconfiguraties niet meer beschikbaar. Dit is opgelost. Daarnaast worden in het synchronisatieoverzicht de meest recente items nu weer altijd bovenaan weergegeven.
DRCFetching all documents of an organization without any filtering caused errors for organizations with a large number of documents. The underlying database queries have been improved to reduce the frequency of these errors.API calls to retrieve all documents for an organization without filter parameters are now more reliable for organizations with large document volumes, as the underlying database queries have been optimized.Het ophalen van alle documenten van een organisatie zonder filtering leidde bij organisaties met veel documenten tot fouten. De onderliggende databasequery's zijn verbeterd, waardoor deze fouten minder vaak zouden moeten optreden.

2026.3.18: Various fixes

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
DRCOn all DRC operations the audittrail 'New' and 'Old' value are the same except for lock and unlock. This has been fixed.The audittrail for DRC operations now correctly shows the old and new values, which improves traceability of changes.De audittrail voor DRC operaties toont nu correct de oude en nieuwe waardes, wat de traceerbaarheid van wijzigingen verbetert.
DRCA recent fix to enforce unique document identification (identificatie) inadvertently prevented any updates to documents that shared the same identification number as another document. This has been corrected.Client applications can now correctly PATCH or PUT documents that before the previous fix shared an identificatie with other documents, as long as the versie is different, which was previously blocked.Het was onterecht niet mogelijk om een document te wijzigen als een ander document met hetzelfde nummer bestond (maar met een ander versienummer). Dit is hersteld.

2026.3.15: Document Identification unique

ComponentSummary (english)Relevance for consumers (English)Relevance for end users (Dutch)Relevance for system administration (Dutch)
DRCThe combination of identificatie, versie, and owner for a document is now correctly enforced as unique. The previous implementation incorrectly used bronorganisatie instead of owner, which could lead to duplicate document numbers for a single owner. The business rules for handling document identification on POST and PATCH/PUT requests have also been corrected to align with this change.Client applications may receive error responses if they attempt to create or update documents with non-unique identificatie and versie combinations for the same owner.Het is nu niet neer mogelijk om hetzelfde documentnummer twee maal op te voeren.
ZRCThe database schema has been updated to correctly support complex objects for zaakobject. objectIdentificatie. overigeData. The old column has been removed and the new one (added in the previous release) now is correctly named.Relevant for apps that rely on database exports like Data Export
NRCFiltering on kenmerk_bron in GET requests for cases is now case-insensitive, ensuring more consistent and predictable filter results.This improves the usability of the case filtering functionality, as queries will now return expected results regardless of casing.
GeneralThe Hangfire retry page, which was broken, has been repaired.Beheerders kunnen nu weer achtergrondtaken correct monitoren en beheren.