IT-Landschap Notariaat 2026

What does the whitepaper cover?

IT-Landschap Notariaat 2026 analyses why the structural workload in the notarial profession is not just a labour market problem but, above all, an IT architecture problem. Across nine chapters the whitepaper charts the route from closed legacy systems to a modular Best-of-Breed architecture with orchestrating AI, with the notary always in final control. Below you will find the essence of each chapter; the full argument is in the PDF, which is in Dutch.

Introduction: The Need for Fundamental Innovation

The workload in the notarial profession is not caused by the tight labour market alone. An ageing profession, the outflow of qualified staff and health-related absence put every signal on red, while the sector simultaneously performs at record level: in 2025 over two million deeds were executed, a historic record. Modern notary-entrepreneurs respond with four-day working weeks and restricted opening hours; that benefits their staff, but has direct commercial consequences for the notarial office.

The old reflex of absorbing more work by simply hiring more people leads, the whitepaper argues, to a rat race to the bottom: the work is taken on, but the organisation cannot actually handle it. What is strikingly often missing is a critical, holistic look at the underlying IT architecture and the design of the office's processes. That, according to the author, is where the real room for innovation lies.

H1. The Historical IT Architecture

The notarial software market has been served for decades by a select group of trusted vendors; some relationships date back to the 1990s. These systems grew into the operational backbone of the notarial office and served the sector well for years. They were, however, designed for one primary purpose: an immutable, highly secure digital filing cabinet, a System of Record. That makes them inherently reactive, passive and linear: the system waits until a staff member logs in and enters data.

To safeguard the duty of confidentiality under the Wna, this software often runs in heavily shielded virtual environments such as Citrix or Remote Desktop: what the employee sees on screen is effectively a secured video connection to a central server. Cloud-native architecture, open APIs and proactive AI demand open, flexible communication instead, and in practice that proves hard to reconcile with these security walls.

H2. The Cloud in Perspective

Under pressure from KNB chain partners such as the Kadaster and the Chamber of Commerce, cloud migration in the notarial sector is slowly gathering pace, and vendors like to present that step as groundbreaking innovation. The whitepaper counters with a sober observation: the wider business world set this transition in motion back in 2008. The belated move to the cloud therefore no longer equals fundamental innovation or data sovereignty; it is primarily the closing of a historical IT gap.

An office migrating to the SaaS version of its trusted package is, moreover, renting a shielded room in the vendor's own house: legally the office remains the owner of its data, but operationally it becomes more dependent on the vendor's willingness and roadmaps. And because lift-and-shift does not change the software's reactive, linear nature, proactive orchestrating AI requires an AI-first architecture. The cloud alone does not unlock that intelligence.

H3. Cooperation and Interests in the IT Chain

How fast a notarial office can innovate is closely tied to two external players: the software vendor and the IT administrator (MSP), both acting on entirely valid commercial interests. Vendors generally have APIs, but weigh strategically how far to open them up to independent AI platforms. An office that opts for the all-in-one environment sees its pace of innovation capped directly by that one vendor's development capacity and willingness.

IT administrators carry the heavy responsibility for continuity, security and compliance, with a business model historically interwoven with on-premise infrastructure: servers, firewalls and workplace security. As cloud-native AI runs from the browser and reduces the need for that heavy infrastructure, this explains why MSPs can respond hesitantly to independent AI systems and prefer to steer towards the software vendors' familiar roadmap.

H4. The Five Levels of AI Maturity

Every vendor currently claims to be AI-driven. To separate marketing from reality, the whitepaper divides the use of AI in the notarial profession into five levels. Level 1, public chatbots such as ChatGPT, lacks the notarial context and a data shield and is, for client dossiers, irresponsible under disciplinary law. Level 2 is the isolated smart button where the employee remains the glue; level 3 is AI built into the closed system that stays linear and reactive. Precisely levels 2 and 3 are the hardest to recognise behind the marketing.

Level 4 is orchestrating AI with a continuous Human-in-the-Loop, which the whitepaper compares to a philharmonic orchestra: a conductor that springs into action on a trigger and coordinates specialised sub-agents, while essential actions are only executed after the notary's explicit approval. Level 5, fully autonomous AI, is excluded by law and by disciplinary rules: an algorithm has no Belehrungspflicht and cannot verify a client's true intent. Level 4 is therefore the highest achievable foundation.

H5. Labels, Barcodes and Dependency

Why do many systems never get beyond level 2 or 3? The whitepaper uses the metaphor of the label and the barcode: every digital dossier carries a readable label (the content) and a barcode (hard metadata such as exact IDs, timestamps and version numbers). AI reads the label with ease, but as soon as a vendor restricts access to that metadata or omits it from the API, the AI loses deterministic certainty, has to guess, and the risk of hallucinations rises considerably. Level 4 can only orchestrate flawlessly when no metadata is held hostage.

In addition, many traditional vendors integrate third-party AI rather than building an AI-first infrastructure of their own, which creates extra chain dependency on someone else's roadmap, compliance and pricing. And there is a hard technological limit: even the most advanced AI is constrained by the software's own linear architecture to level 2 or 3 at most, forced into the role of a reactive helper rather than an orchestra leader.

H6. Security and Compliance through the Umbrella Architecture

Offices unwilling to wait for innovation inside their closed systems look at an independent umbrella architecture that works directly on their own office data. External AI operating in the central SharePoint environment, however, appears to collide with the Wna, the GDPR and the need-to-know principle. Professional level 4 platforms resolve this with local pseudonymisation: the Data Shield.

Before documents or queries reach the AI model, the Data Shield locally strips out all personal data, citizen service numbers, bank accounts and amounts, replaces them with abstract variables and then encrypts the data. The external AI reasons purely over anonymised logic; within the office's own IT walls the answer is reconnected to the real data. Privacy-sensitive data therefore never leaves the office's own environment. Combined with strict Data Retention agreements (the data sent is never used to train models), the notary keeps disciplinary control and the office complies with the strict KNB AI-Weegschaal.

H7. The KNB as Catalyst

The KNB plays a dual role: strict guardian of the profession's core values and, increasingly, advocate of the open infrastructure that breaks through the all-in-one silos. Through four pillars it steers the market towards Best-of-Breed and API architecture. European and national legislation, such as the digital incorporation of the B.V. and KIK, forces secure hubs and API standards into being: a vendor that cannot or will not build them in makes it impossible for the notary to perform their statutory duties.

At the same time, trust is shifting from the closed software package to the person of the notary, through personal professional certificates and strict authentication. As long as the AI orchestrator submits every action for approval, the KNB infrastructure no longer cares which system that action comes from. Paradoxically, the hard disciplinary line that excludes level 5 legitimises precisely level 4 and modular systems: the office must control its own source data to be able to carry that responsibility at all. The KNB also warns against lock-in and seeks to prevent it through its own Notarieel Netwerk.

H8. The Role of the Chain Partners

Where the KNB drives the transition top-down, chain partners such as the Kadaster, the Chamber of Commerce, the Tax Administration and the banks via ECH force the open architecture bottom-up. They have no direct interest in closed packages; their sole operational goal is secure, structured, real-time data exchange (Straight-Through Processing). When established vendors block or delay that data flow as gatekeepers, the chain simply builds roads around them.

The whitepaper describes four routes: sector-wide API hubs with openly published specifications that any qualified party may connect to; direct Microsoft integration, where official connectors pull source data straight into the office's own SharePoint environment; pilots with cloud-native challengers that build in weeks the API links traditional players sometimes take years to deliver; and identity shifting to the notary through eIDAS 2.0, eHerkenning and professional certificates. The question is no longer which IT system sends something, but which sworn notary does.

H9. Best-of-Breed and the Financial Impact

Workload is not solved durably by adding yet another loose button to the current software. Forward-looking offices therefore embrace the Best-of-Breed strategy: they place their active, daily workstreams in a modern cloud environment such as Microsoft Azure with SharePoint dossier folders, functioning entirely independently as the Source of Truth. On top of that own data layer sits the independent AI orchestrator, guiding processes from intake to deed.

The trusted packages need not disappear; they can regain their core role as the secure digital vault at the end of the process, for final archiving, complex KIK filings and management of the third-party funds account. The return: less error-prone copy-and-paste work, lower administrative pressure and, over time, winding down heavy local infrastructure and costly Citrix workplace licences, resulting in a markedly lighter, more flexible IT budget.

Conclusion: Control, Vision and Strategy

The answer to workload and staff shortage does not lie solely in chasing scarce personnel, nor in bolting reactive AI onto systems that were never architecturally designed for it. The transition is, moreover, no longer an optional internal choice but a hard external necessity: chain partners and the KNB are steering unmistakably towards open API standards, Straight-Through Processing and authentication based on the person of the notary. Whoever stays locked in closed all-in-one silos risks, in time, losing the connection to the notarial ecosystem.

Real relief comes from reclaiming control over the source data and the IT foundation: data sovereignty. Within an open, cloud-native Best-of-Breed environment, orchestrating AI can do its work, while the Data Shield, encryption and the Human-in-the-Loop principle keep the office within the strict requirements of the Wna and the GDPR. The whitepaper closes with five strategic considerations for the partnership and ten concrete questions for the conversation with your vendor.