# 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

Claude Duet · Reddit · No income is disclosed. The author says it has already saved him thousands of euros; that is his own claim, with no calculation, no time period and no verification.

## Business summary

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.

## Business value

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.

## Preparation and limitations

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.

## Starter prompt

````text
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.
````

## 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.

## Source and attribution

floraldo（Reddit 用户 u/floraldo，原帖作者本人，自述有近两年的荷兰税务欠账） (u/floraldo)
https://www.reddit.com/r/vibecoding/comments/1spuwzd/i_was_2_years_behind_on_taxes_claude_fixed_it_for/
2026-04-19
Results come from the source author. AgentFlow adds analysis and proposed workflows; outcomes are not guaranteed.
