Cases · Automation check
A shop's books in n8n built with AI, checked and fixed
A sample engagement: Nordaloom is a fictional shop, Stripe is in test mode and the books hold test data. The n8n workflows were built with Claude Code for this case; every finding, test and fix is a real run.
Goal
The owner wanted the paper and money side done in n8n: each payment booked with its country, currency, VAT from the owner's table, Stripe's fee and what is left; a PDF invoice whose number never skips or repeats; SEPA invoiced only once the money arrives; refunds as credit notes; disputes; payouts matched to the cent; euros, dollars and pounds booked in euros; a summary at 8:00 and the accountant's monthly CSV. Then the web shop was joined to the books. The question: are the books right where money and VAT get unusual, and is nothing lost or doubled when something fails?
Challenge
The books were handed over as built and tested, and on the usual path they were: a card sale in Latvia gave the right invoice, the same Stripe event sent again made nothing twice, invoice numbers had no gaps, and an outage of n8n, the database, email or the PDF converter lost nothing. The mistakes sat in rarer cases: business customers with EU VAT numbers, a refund that fails late, days with bank transfers, the shop's database not answering.
Solution
First the owner's rules for the books were written down, and the owner's requests went to the builder in plain words. Then each rule was tried on real Stripe test payments and real orders in a local copy of the shop, what should happen against what did. The fixes went back to the builder as the owner's messages; each round was checked again for what it fixed and what it broke, and on the final version every check ran again.
Outcome
6 problems: 4 medium, 2 low. An Austrian company with a German VAT number was charged Austrian VAT, €33.00 on €198.00, instead of reverse charge; a Latvian business with goods going to Berlin was charged German VAT instead of Latvian; a refund Stripe failed two hours later stayed in the books as paid back, and the customer kept a credit note for money they never got; while the shop's database was silent for 12 minutes nothing was booked, not even payments that had nothing to do with the shop, and no alert went out; on days with bank transfers the morning summary opened with "net €0.00"; the shop showed 21% VAT while the invoice charged the delivery country's. All six are fixed: the wrong invoices cancelled by credit notes and reissued, the owner alerted within a minute, the shop and the invoices on the same VAT. Of 133 checks, 9 failed as handed over and none on the final version. Payouts couldn't be seen in test mode; the report lists that and the other limits. Left to the owner: the fee Stripe takes on bank transfers, and a database login that can only read. One automation, built once: the numbers describe these books, not a rate.
From the case
The report, 8 pages (PDF)
Service
The same check for your automation
You send the workflows exported from n8n, not your passwords or keys. Every problem comes with an example in money, and every fix is checked again for what it broke.