What AI doesn't know about your business
Operators edition. Three places where SMB AI tools produce visible work that fails because the tool doesn't know about the regulatory or algorithmic layer it's operating in. OPS-037: AI-drafted invoices fail EU VAT audits on cross-border treatment. OPS-039: AI-drafted contracts miss notarisation requirements in EU jurisdictions. OPS-041: AI-generated marketing content hits Google + LinkedIn + Etsy enforcement. The pattern is the same; the fix takes 30 seconds.
ABBY
This is Agent Mode AI. I'm Abby. Today we're doing the operators edition. Three claims from the OPS ledger, all describing the same pattern: SMB AI tools that produce visible, useful work that quietly fails because the tool doesn't know about the regulatory or algorithmic layer it's operating in.
AVERY
I'm Avery. Frame the pattern.
ABBY
AI handles the visible work. AI misses the regulatory-context work. The tool gives you an invoice, a contract, a marketing post. The tool does not know about the EU VAT scheme, the notarisation requirement, or the platform algorithm enforcement layer. The fix in all three cases is a 30-second pre-output check on the regulatory or algorithmic surface. None of the SMB tools currently ship that check by default.
AVERY
Start with OPS-037. The VAT one.
ABBY
OPS-037 is about AI-drafted invoices for EU SMB operators failing VAT audits at higher rates than human-drafted invoices, specifically on cross-border treatment. The failure modes cluster in three places. First, OSS scheme wording. The One-Stop-Shop scheme replaced the prior cross-border B2C VAT thresholds in 2021. Invoices for cross-border B2C sales must reference the OSS scheme correctly to be valid for the supplier. AI tools trained on pre-2021 corpora reproduce the old reverse-charge language, which is wrong for B2C since 2021.
AVERY
Second.
ABBY
Second, reverse-charge language. For B2B cross-border sales within the EU, the reverse-charge mechanism shifts VAT obligation from supplier to buyer. The invoice must include specific language signalling the reverse charge and must list the buyer's VAT number. AI tools generate plausible reverse-charge text but frequently omit the buyer-VAT-number requirement, which is a hard validation requirement.
AVERY
Third.
ABBY
Third, customer VAT-status verification. The reverse-charge mechanism only applies if the buyer is genuinely a VAT-registered business in another EU member state. The supplier is responsible for verifying that — the European Commission's VIES system is the canonical verification surface. AI tools generate the invoice without the verification step. If the buyer's VAT number is invalid, the supplier owes the VAT and the audit reads as fraud.
AVERY
What's the fix.
ABBY
A four-line VAT-compliance prompt prefix. Name the operator's VAT registration country and number. Name the buyer's status — B2B or B2C, in-country or cross-border, EU member state. Name the applicable scheme — domestic, OSS, reverse-charge. Name the VIES verification result. Most SMB invoicing tools do not ship this by default. Adding it is a copy-paste change to the prompt configuration.
AVERY
Now OPS-039. The contracts one.
ABBY
OPS-039 is about AI-drafted contracts in EU notary-required jurisdictions producing a class of legal-malpractice incidents. The pattern: SMB owner uses an AI tool to draft a contract, signs it as the final binding document, and discovers later that the contract type required notarisation to be enforceable.
AVERY
Which contract types.
ABBY
Three categories matter. Real-estate transfers in the Netherlands under Burgerlijk Wetboek Boek 3 Article 89, in Germany under Bürgerliches Gesetzbuch Section 311b, and similar provisions in Austria, Belgium, and Switzerland — all civil-law jurisdictions where land registry transfers require notarial deed. GmbH and BV share transfers in Germany under GmbHG Section 15 and the corresponding Dutch BV provisions — share transfers in private limited companies require notarial form. Marriage and inheritance instruments — prenuptials in many jurisdictions, certain wills, certain donations — require notarial form for validity.
AVERY
What does the AI tool actually output.
ABBY
A plausible-looking contract. The text reads correctly. The terms are coherent. The signatures are gathered. The document is filed. Six months later, the registry refuses to record the transfer because the form is wrong. The seller finds out their property never legally transferred. The new managing director finds out they don't actually hold the shares.
AVERY
The professional bodies have responded.
ABBY
The KNB — Koninklijke Notariële Beroepsorganisatie in the Netherlands — has published 2024-2026 guidance addressing AI-drafted contracts directly. The BNotK in Germany has done the same. Both publications name the specific transaction types where notarial form is required and the specific failure modes where AI tools produce documents that look final but are not.
AVERY
The fix.
ABBY
A 30-second pre-signing check. What is the transaction type? What jurisdiction? Does the law require notarial form for this transaction type in this jurisdiction? If yes, route to a notary before signing. AI contract tools do not flag this by default. The check is operator-side discipline, not vendor-side feature.
AVERY
Now OPS-041. The platform-algorithm one.
ABBY
OPS-041 is about SMB owners using AI to produce marketing content hitting platform algorithmic penalties at increasing rates. The platform-specific enforcement breaks into three patterns.
AVERY
Google.
ABBY
Google Helpful Content system plus the March 2024 spam policy update target what Google calls "scaled content abuse" — content produced at scale without sufficient expertise, experience, authoritativeness, or trustworthiness. AI-generated marketing content without human editing and human signature falls in scope. The penalty is a site-level visibility reduction.
AVERY
LinkedIn.
ABBY
LinkedIn's feed-distribution algorithm explicitly deprioritises fully-AI-generated content while tolerating AI-assist with human editing. The signal is in the engagement velocity in the first 30 to 60 minutes after posting. AI-generated posts without genuine human voice get suppressed in feed distribution by the algorithm before any human editorial review.
AVERY
Etsy.
ABBY
Etsy's listing-policy enforcement is heavier than either Google or LinkedIn. Etsy has category-specific AI prohibitions — handmade craft categories explicitly disallow AI-generated descriptions and AI-generated product imagery. Listing-policy violations result in listing removal and at scale shop suspension.
AVERY
The defensible posture.
ABBY
AI drafts plus human edits plus human signature, at sustainable cadence. The pattern works across all three platforms. Each platform's enforcement mechanism rewards genuine human involvement and penalises pure AI output. The operator who uses AI to draft and a human to edit and sign is in compliance with all three platforms' explicit rules.
AVERY
The pattern across all three claims.
ABBY
AI handles the visible work. The regulatory or algorithmic layer the AI doesn't know about is where it fails. The fix is operator-side discipline — a prompt prefix, a pre-signing check, a human edit pass. None of the AI tools ship the fix by default. The cost of skipping the fix is asymmetric: small upside on speed, large downside on penalties, audits, or invalidated documents.
AVERY
Verdicts.
ABBY
OPS-037 is Holding. The Belastingdienst, HMRC, and BZSt published guidance is consistent. The four-line prompt prefix fix is documented and works. Cadence is sixty days because EU VAT enforcement priorities shift on roughly that rhythm.
AVERY
OPS-039.
ABBY
OPS-039 is Holding. KNB and BNotK guidance is on the record. The statutory anchors — BW Boek 3 Article 89, BGB Section 311b, GmbHG Section 15 — are settled. Cadence is sixty days because the case law on AI-drafted contracts is what's emerging.
AVERY
OPS-041.
ABBY
OPS-041 is Holding. Google, LinkedIn, and Etsy all carry published 2024-2026 enforcement updates. The pattern is platform-specific, not generic AI-detection. The defensible cross-platform posture is documented and observable. Cadence is sixty days because platform algorithm changes ship on roughly that rhythm.
AVERY
What would change any of them.
ABBY
For OPS-037: a vendor-side standardisation on EU VAT-compliant AI invoicing. For OPS-039: a vendor-side jurisdictional-form check on AI contract tools. For OPS-041: a platform-side de-escalation on AI-content enforcement. None is currently in the visible pipeline.
AVERY
Final word.
ABBY
The three claims, the source guidance, and the fix patterns are at agentmodeai dot com slash holding. The Sunday brief ships every week with what moved on the ledger.
AVERY
Holding-up. See you next Sunday.