Five steps. One validated Dutch BV resolution.
No blank generic AI prompt, no 2018 Word template. A deterministic pipeline where every step is auditable and the law is the final check.
From picking an entity to signed and archived.
Each step has one goal, one screen and one clear outcome. No unexpected fields, no creative AI side paths, only what the DCC requires.
01: Pick your BV
Enter the KvK number once per entity. We pull statutory name, RSIN, registered seat, legal form and directors live from the trade register; everything is then ready for every subsequent resolution.
Start with your first entity02: Fill in the numbers
The wizard asks exactly what this doc type needs, for a dividend resolution: distributable reserves, proposed distribution, 12-month liquidity forecast and short-term liabilities. All in euro cents, no floating-point.
See a dividend-resolution wizard03: AI drafts
Mistral La Plateforme (Paris, EU, data_retention=0) fills our version-pinned, lawyer-reviewed clauses. 14 locked slots per dividend resolution, exact DCC citations, no creative deviations.
How we prevent hallucinations04: Validator checks §2:216 DCC
TypeScript validator runs the balance test (§1) and liquidity test (§2) on euro cents, plus six semantic checks (date consistency, directors' declaration, dividend-tax substantiation). Failure = no export, with a Dutch error message.
Deep dive into the distribution test05: Sign & archive
PDF + DOCX with sequential numbering per entity (2026-BV-001), SHA-256 hash in the footer, eIDAS-AES signature and a 7-year evidence bucket. Ready for the tax authority, the KvK and your accountant.
Pay per documentAt every step, a generic AI is missing something.
The pipeline is the difference. A generic AI misses 5 of 5 steps, not one, not two, but the whole chain from entity to archive.
| Criterium | Generieke AI | Caproom Docs |
|---|---|---|
| Step 01, Auto-fill from the KvK trade register | Vraagt jou de KvK-data te kopiëren, typefouten landen in het besluit. | KvK Basisprofiel-API: statutaire naam, RSIN, zetel, bestuurders auto-ingevuld. |
| Step 02, Structured wizard per doc type | Begeleiding via open prompt, geen idee welke cijfers nodig zijn. | Wizard vraagt exact wat art. 2:216 BW nodig heeft, in de juiste volgorde. |
| Step 03, Version-pinned, reviewed clauses and prompts | Tekst wordt elke keer anders, geen versie- of prompt-historie. | Vaste, lawyer-reviewed clausules + prompts met versie + diff in admin. |
| Step 04, Deterministic §2:216 DCC validator | Validatie ontbreekt, model raadt, jij ondertekent. | Deterministische TypeScript-validator vóór render; faal blokkeert export. |
| Step 05, Sign, number, archive with audit log | Geen handtekening, geen nummering, geen archief, losse Word-output. | eIDAS-AES tekenflow, doorlopend nummer per entiteit, 7-jaar evidence-bucket. |