Two years of Dutch taxes cleared in one afternoon: Claude ingests three accounts, matches receipts from email, outputs box-format reports - 19 questions still go to the accountant
floraldo(Reddit 用户 u/floraldo,原帖作者本人,自述有近两年的荷兰税务欠账)Reddit · 2026-04-19
Read originalSaved text / editorial summary
原帖正文(Reddit r/vibecoding,作者 u/floraldo,Atom 源 updated 字段 2026-04-19;本轮经 Reddit 公开 Atom feed 取得,以下为节选,英文部分逐字未改写): “Claude just did my taxes for me. In one afternoon. I was almost 2 years behind and absolutely dreading the unentangling of my expenses, looking up receipts and invoices, and having to navigate the most complex tax system in the world (the Dutch one). I genuinely hate doing taxes. But I love automation. So here`s what I built: An automated accounting system that: - ingests transactions from 3 different bank accounts (2yrs back) - scrapes my email to match receipts to transactions - categorises expenses using agentic judgment - calculates what I owe, to whom, and by when - generates reports ready to send to my accountant All fully automated and matching the tax agency box format. My next quarterly summary will require only a single CLI command and take only 5 minutes. No joke. On top of that, my accounting system also features a full knowledge base with all the relevant information around the Dutch tax system for my specific case. WBSO, innovatiebox, holding, etc. - and I can easily add more knowledge. How? I let Claude do a deep research around my specific context and compiled it into a wiki that I integrate into my accounting structure. It already helped me save 1000s of euros through its advice and diligence. It will also flag any edge cases and ambiguities and automatically extract them as questions for my accountant. 19 total in the e-mail I sent out. Let`s see what my accountant comes back with. We`ll simply ingest that too into my knowledge base. Feel free to copy my structure and give it a go yourself. It`ll be a fun weekend project.” 中文对照:作者说自己落后了将近两年,最怵的是理支出、翻收据发票,还得面对荷兰这套税制。他搭的自动记账系统会做五件事——汇入三个银行账户的两年交易、抓邮件把收据与交易匹配、用「agentic judgment」给支出分类、算出欠谁欠多少以及什么时候之前要交、生成可以直接发给会计师的报表,全部对齐税务局的 box 格式。他自称下一个季度汇总只要一条命令、五分钟。另外他让 Claude 针对自己的情况做深度检索,把 WBSO、创新盒、控股这些规则整理成 wiki 接进记账结构。他自述靠它的建议省下数千欧元,并把 19 个边界情况抽出来当成发给会计师的问题。
Business model
Reddit user u/floraldo wrote in r/vibecoding about how he used Claude to clear nearly two years of Dutch tax backlog. His list is specific: ingest two years of transactions from three bank accounts; scrape his email to match receipts and invoices to transactions; categorise expenses using what he calls agentic judgment; calculate what he owes, to whom and by when; and generate reports ready to send to his accountant, matching the Dutch tax agency's box format. He says the two-year backlog was cleared in one afternoon and that future quarterly summaries will take a single command and about five minutes. The second half is a knowledge base: he had Claude deep-research his own situation - WBSO, the innovation box, a holding structure - and compiled it into a wiki wired into the accounting setup, so he can ask strategy questions with both the rules and his actual finances in view. He also jokes that at this rate he may not need the accountant in a year - his speculation, not an outcome. He says it has already saved him thousands of euros, and that it surfaced 19 edge cases and ambiguities which he extracted and emailed to his accountant. No amounts, no calculation behind the savings, no accountant verdict, and no subscription or token cost is given. The savings figure is the author's own claim, not a verified result.
The durable idea here is that uncertainty is an output. The author's agent does not smooth over the ambiguous cases; it pulls them out - 19 of them - and hands them to the person who can actually decide. Most people automating books let the model quietly fill a plausible number instead. Copy that inversion first, then worry about the automation.
Workflow
- Fix the scope first: which accounts, which years, one tax year at a time.
- Ingest transactions first, then attach receipts - never the other way round. (Order follows the original post.)
- Keep categorisation as a suggestion with a stated reason; never let it set the tax treatment.
- Extract every edge case and ambiguity into a separate question list. (The author's own step: 19 questions for the accountant.)
- Keep the report a draft for the accountant; no filing, no email, no confirmed amount. (AgentFlow's boundary; the original post does not describe a confirmation step.)
- Feed the accountant's answers back into the knowledge base so the next round asks fewer of the same questions.
Adaptation plan
The post gives no amounts, no breakdown of the savings, no accountant verdict, and no subscription, API or token cost. It does not say which bank formats were parsed, how email scraping was authenticated, how many transactions failed to match a receipt, or whether the box-format output was ever accepted as filed. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run.
Prompt
AgentFlow draft · Untested.
You are my bookkeeping cleanup assistant. You may read and organise the material I give you, suggest categories, compute what is owed and when, and draft reports. You do not file anything, do not send email, and do not fill in ambiguous numbers on your own. [INPUT] - Accounts and years: [account list, e.g. Bank A / Bank B / Bank C], [start and end dates] - Transaction file: [path to CSV or export] - Receipt source: [email export / attachment folder / scans] - Tax categories: [your jurisdiction's categories, e.g. box 1 / box 3] - Report format I need: [format description] [STEPS] 1. Do one thing only: build the master transaction table (date / account / amount / counterparty / currency) and report how many rows came from each account and whether the date range is fully covered. 2. Search the receipt source and match receipts to transactions. Matched rows get a receipt reference; unmatched rows go to a missing-receipt list. Do not guess, do not round amounts to force a match. 3. Suggest a category for each expense with a one-line reason. Flag anything touching a relief or special regime separately. 4. Produce the what-I-owe / to-whom / by-when list, using only receipts and transactions you have actually seen. Where the evidence is missing, write pending and move it to step 5. 5. Extract every edge case and ambiguity into a question list: which entry, why it is uncertain, who needs to decide. 6. Draft the report in my required format, stating at the top that it is a draft. [OUTPUT] 1) master transaction table; 2) receipt matching result including the missing list; 3) category suggestions with reasons; 4) what-is-owed list; 5) question list; 6) report draft. [NEEDS MY CONFIRMATION] - Missing-receipt entries above my size threshold: ask me, do not estimate. - Any relief or special regime judgement: show the source and let me decide. - Filing, sending or confirming any amount: stop at the draft and wait. [IF MATERIAL IS MISSING OR A STEP FAILS] Unreadable file, mismatched fields, empty receipt folder, missing currency: say exactly what is missing and which step it blocks. Never substitute older data or a guess.
Running costs and pitfalls
The post gives no amounts, no breakdown of the savings, no accountant verdict, and no subscription, API or token cost. It does not say which bank formats were parsed, how email scraping was authenticated, how many transactions failed to match a receipt, or whether the box-format output was ever accepted as filed. The workflow, prompt, synthetic sample and pitfalls here are AgentFlow's proposals and have not been run. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.