AI-drafted contracts and the notary requirement: where the SMB malpractice line sits

If you run an EU SMB and you have started using AI to draft commercial contracts, the question we keep getting is whether the AI draft is the final document or whether something else needs to happen before it is binding. The honest answer is jurisdiction-specific. In notary-required jurisdictions (most prominently the Netherlands and Germany, with similar rules in Austria, parts of Belgium, and Switzerland), a meaningful share of the contracts an SMB drafts (real-estate transfers, certain shareholder agreements, certain marriage and inheritance arrangements, some power-of-attorney instruments) require notarial attestation to be legally valid. AI tooling does not know which contracts are in scope; SMB owners assuming the AI draft is final are creating a class of legal-malpractice incidents that solo legal practitioners are seeing recurrently.

The structural reason the AI does not catch this: the tooling is trained on a global corpus that overweights common-law jurisdictions where notarial attestation is rare, and underweights the civil-law jurisdictions where it is routine. The AI’s default assumption is that a signed document with witnesses is binding. In the Netherlands and Germany, the signature is necessary but not sufficient for a category of instruments that the AI does not flag.

For a 1-to-25-employee SMB owner in NL, DE, AT, BE, or CH, the practical implication is that AI-drafted contracts need a quick jurisdiction-aware filter before they are treated as final. The filter is small. Skipping it produces incidents that are both expensive to remediate and personally consequential for the operator.

What the notary requirement actually applies to

Across NL and DE, the categories of instruments that require notarial attestation overlap substantially. The list below is illustrative, not exhaustive. The per-jurisdiction reading matters.

Real-estate transfers. Both NL (Burgerlijk Wetboek Boek 3, Article 89) and DE (Bürgerliches Gesetzbuch §311b) require notarial deed for the transfer of real property. An AI-drafted real-estate purchase agreement is not the operative instrument; the notarial deed (notariële akte / notarielle Urkunde) is.

Certain shareholder agreements. German GmbH share transfers require notarial attestation under GmbHG §15. Dutch BV share transfers require a notarial deed under the Dutch Civil Code. AI-drafted shareholder transfer language must be incorporated into a notarial deed to take effect.

Marriage and inheritance instruments. Prenuptial agreements, partnership agreements with property implications, and certain testamentary instruments require notarial attestation in NL and DE. AI-drafted versions are working drafts at best.

Some power-of-attorney instruments. Specifically those granting authority over real estate or company shares; the notarial form is required. General commercial powers of attorney typically are not.

Beyond these categories, ordinary commercial contracts (service agreements, supply contracts, employment contracts, NDAs) generally do not require notarial form. The AI draft is the operative document, signed by the parties, with the usual contract-law protections.

The trap is the boundary case: the SMB owner assumes “it is just a contract, the AI draft signed by both parties is binding,” when the underlying transaction is in one of the categories above and the document is not enough.

What the published professional bodies are saying

The Royal Dutch Notary Association (Koninklijke Notariële Beroepsorganisatie, KNB) publishes guidance for both notaries and the public on which transactions require notarial attestation. The 2024-2026 KNB commentary has explicitly addressed AI-drafted contracts, with the consistent position that AI tooling does not change what requires the notarial form; it only changes how the working draft is produced. The notary’s role of verifying identity, capacity, intent, and the legal validity of the instrument is unchanged.

The German Federal Chamber of Notaries (Bundesnotarkammer, BNotK) publishes equivalent guidance for the German market. The BNotK position is similar: AI tooling can produce drafts that the notary then reviews, attests, and registers; AI tooling cannot replace the notarial attestation. The BNotK commentary in 2025-2026 has emphasised that the notary’s review identifies AI-generated errors with some regularity, particularly around boilerplate clauses that the AI carried over from common-law templates and that do not function correctly under German civil law.

The pattern across both bodies is that the notary profession is comfortable with AI-assisted drafting and unhappy with AI-replaces-the-notary framing. The professional bodies are not opposed to the tooling; they are clear that the tooling does not address what notarial form addresses.

What the SMB owner is missing

The class of legal-malpractice incident that solo legal practitioners are reporting in 2025-2026 follows a recognisable shape.

A small business owner uses an AI tool to draft a contract for a transaction that requires notarial form (a property purchase, a share transfer, an inheritance arrangement). The AI produces a complete-looking draft with all the usual contract elements. The owner sends it to the counterparty, both parties sign, and the owner files the document as final. Months later, the validity of the transaction is challenged (by a tax authority, a creditor, a successor, or the counterparty themselves) and the document is found to be insufficient. The remediation requires going to a notary after the fact, often with the cooperation of all parties (which may no longer be available), and sometimes the transaction cannot be reconstructed at all.

The financial consequence varies. In a real-estate transaction, the buyer may not have valid title; the entire transaction may need to be redone. In a share transfer, the transfer may not be effective against third parties; tax assessments and corporate-record positions may be wrong. In an inheritance instrument, the testator’s intent may not be enforceable as written.

The reputational consequence for the operator is significant. The pattern is rarely framed as “the AI got it wrong” in the ensuing dispute; it is framed as “the operator was negligent in not knowing the requirement.”

The 30-second pre-signing check

For an SMB owner using AI to draft contracts in notary-required jurisdictions, a small workflow addition prevents the failure mode.

Before treating any AI-drafted contract as final, ask three questions in order.

What is the underlying transaction? If it involves real property, company shares (specifically GmbH or BV shares), inheritance, marriage property, or certain powers of attorney, the answer to the next two questions matters. For ordinary commercial contracts, you can stop here.

Does the jurisdiction require notarial form for this transaction type? Look up the transaction-type-and-jurisdiction in the KNB published guidance (NL), BNotK guidance (DE), or the equivalent national professional body. The lists are publicly maintained.

If notarial form is required, what is the actual workflow? Engage a notary, who will review the AI draft, identify any errors, attest the final form, and register the instrument with the appropriate registry. The notary cost is modest relative to the cost of remediation; the timeline is typically days to a few weeks.

The pre-signing check takes 30 seconds for the typical commercial contract (no notarial form required, AI draft can be the final). It takes a few minutes for the contracts that do require it (notary engagement scheduled, AI draft becomes the working version not the final). Either way, the check is cheaper than the malpractice incident that comes from skipping it.

Where this connects to the broader operator picture

This piece pairs naturally with the EU VAT compliance piece. Both are examples of AI tooling that handles the visible work well and misses the regulatory-context work that represents most of the legal risk. The VAT version is about invoicing; the notary version is about contracts. The structural pattern is the same.

It also pairs with the AI vendor due diligence framework at the procurement layer: when picking an AI contract-drafting tool, the question of whether the vendor has jurisdiction-aware notary-flagging is one of the questions the SMB should ask but rarely does.

What we are not claiming

We are not claiming that all AI-drafted contracts in NL or DE are at risk. The notary requirement applies to a defined list of transaction types; ordinary commercial contracts are out of scope. The risk concentrates in the specific categories above.

We are not claiming a specific incident frequency. The pattern is being discussed in published Dutch and German legal press; the per-incident data is private. The frequency is described as “recurrent” rather than “epidemic.”

We are not citing specific malpractice rulings because the cases are typically resolved through professional-liability insurance settlement rather than published judgement. The pattern is documented in the professional-body commentary; the per-case specifics are private.

What changes this read

Cadence on this piece is 60 days because the case law and the professional-body guidance evolve on multi-quarter timescales. The three things that would change the verdict:

A landmark Dutch or German court ruling on AI-drafted contracts and notarial form would crystallise the legal posture and shift the framing from “general doctrine applies” to “specific ruling applies.” A major SMB contract-drafting AI vendor shipping built-in jurisdiction-aware notary-flagging would close the gap structurally and reduce the operator-side burden. Updated KNB or BNotK guidance specifically addressing AI tooling at the SMB scale would standardise the compliance handling.

We will re-test against KNB, BNotK, and major SMB contract-drafting vendor product changes on or before 30 Jun 2026.