verfahrensdokumentation
Skill65 starsChanged 14 days agoMITView on GitHub
Help a German company with its GoBD Verfahrensdokumentation (process documentation). Use when the user asks for the Verfahrensdokumentation, a process documentation template, or what a tax audit expects about their process. Germany only.
In this repository28 other files it gives its agents.
- accounting-cutoverSkill
- calculators-and-formsSkill
- categorize-transactionsSkill
- company-incorporationSkill
- corporate-tax-registrationSkill
- create-invoiceSkill
- expense-reportSkill
- financial-overviewSkill
- find-receiptsSkill
- gewerbe-registrationSkill
- manage-clientsSkill
- manage-productsSkill
- manage-vendorsSkill
- monthly-reconciliationSkill
- overdue-remindersSkill
- pl-opening-balanceSkill
- pl-tax-settingsSkill
- run-payroll-monthSkill
- run-workflowSkill
- suggest-categorySkill
- ta-client-periodSkill
- ta-company-reviewSkill
- ta-datev-preparationSkill
- ta-missing-receiptsSkill
- ta-month-closeSkill
- ta-tax-complianceSkill
- tax-deduction-finderSkill
- tax-reportSkill
The file
Files
Help the user get their GoBD Verfahrensdokumentation.
What it is
- Norman creates a PDF with the four GoBD parts: general description, user documentation, technical system documentation and operating documentation.
- Norman creates it fresh at each download from the company's current data, and asks the user nothing. It shows per year how many documents were captured, in how many months and by which channel, and who finalized how many bookings. It is not a Word file, and it is free on every plan.
- It stays the customer's own document. Nobody at Norman reviews it, and Norman holds no GoBD attestation. Never call Norman or its bookings GoBD-certified or unchangeable.
Download
- The user downloads the PDF in the app: Export on the transactions page, turn on Download in GoBD format, then Verfahrensdokumentation. A GmbH or UG also finds it under Ledger, Export GoBD.
- There is no link to the PDF. Tell the user to keep each downloaded version as long as the records it explains.
What the user adds
- The PDF covers only the work in Norman. The user describes the rest in their own document and keeps it with the PDF: what happens to paper originals, which systems they use outside Norman, and who does which task.
- Help them word it if they ask. Use only what the user states. Never guess a process for them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

