How We Automated Business Trip Reports with Claude
We used to dread the end of every business trip at Enty. Not the travel itself, but the closeout that came after it: an afternoon lost to a calculator, a spreadsheet of half-remembered card charges, and the quiet worry that one missing report would flip a clean expense into a tax bill. So we did what we now do with most repetitive back-office work — we built a Claude skill to handle it and packaged it into our free, open toolkit at github.com/entyteam/enty-skills. This article is the honest version: the pain we lived with, why a template was never going to fix it, exactly how the skill works, and how you can close out your next trip in about five minutes.
Why did closing out a trip cost us an entire afternoon?
Because a business trip report is deceptively small. It looks like a formality — a page of names and dates — but it is the one document that decides whether a whole trip is a clean, tax-free business expense or a taxed benefit with a shaky audit trail. Every founder on our team had the same routine after a conference: dig through email for the flight confirmation, find the hotel invoice, screenshot the Bolt rides, then squint at a bank statement trying to remember what the €174 dinner on Thursday actually was. None of it is hard. It is just fiddly, easy to get wrong, and it always landed at the worst possible time — the week you got back and had a hundred other things to catch up on.
The truly frustrating part is the counter-intuitive bit that most people miss: the receipts are the easy half. A plane ticket, a hotel invoice, a conference pass — on their own these are just payments, and nothing in a flight to Tallinn tells your accountant why the company paid for it. The report is what says “this was a business trip, here’s the reason, here’s the proof.” In Estonia, business trips are booked to a dedicated “Business travel” expense account, and every expense on that account has to be backed by a report. No report, no deduction. So the document we kept treating as afterthought paperwork was actually the thing that made the trip a business expense at all.
What actually goes wrong when you do it by hand?
Three specific things tripped us up over and over, and they are the same three that catch most founders. Once we named them, the case for automating became obvious — these are not judgment calls, they are rules you either apply correctly or you don’t.
Per-diem confusion
A per diem (daily allowance) is a flat, tax-free amount paid to the traveller to cover personal costs on the road — mainly food. The rules feel simple until you are actually mid-calculation. Per diems apply to foreign trips only — a country other than the traveller’s country of permanent residence — so a trip inside your home country doesn’t qualify for a tax-free allowance at all. You do not need receipts for the per diem; the only thing that justifies it is the trip report itself. And the tax-free rate steps down partway through a long trip, which is exactly the kind of edge case you forget at 6pm on a Friday.
Food that lands on the company card
This happened on almost every trip: someone paid for lunch or a team dinner with the corporate card. That payment is still personal in nature — it’s exactly what the per diem is meant to cover — so you don’t book it as a business expense. Instead you declare it against the daily allowance, line by line, with the note “use of daily allowances.” As long as the total of those card-paid personal items doesn’t exceed the traveller’s per-diem entitlement (days × rate), it all reconciles and no receipts are needed. Doing that reconciliation by hand, across three travellers and a shared dinner, is where the calculator time really went.
The tax risk hiding in a missing report
This is the one that actually keeps founders up at night. Without a report, a flight ticket looks like an unrelated, personal-looking expense your accountant can’t book to the company, per diems can’t be justified, and in an audit the whole trip can be reclassified as a private benefit — with tax on top. We had trips where the documents existed but were scattered across four inboxes and never assembled into anything. From the accountant’s chair, scattered documents and no report are the same as no documents at all.
Per diems: the numbers we kept getting wrong
Here are the current Estonian tax-free rates in 2026 — the ones the skill applies automatically so nobody has to remember them. The rate is higher at the start of a trip and steps down after the first 15 days, and there’s a monthly cap on how many top-rate days you can claim. These figures went up in recent years (the old numbers were €50 and €32), which is precisely why doing it from memory is risky.
When | Tax-free rate | Limit |
|---|---|---|
First 15 days of a foreign trip | €75 / day | Max 15 days per calendar month |
Each day after that | €40 / day | — |
A few rules sit around that table and matter just as much as the numbers themselves. Rates and rules are country-specific and change over time, so always confirm the current figure with your accountant or on the Estonian Tax and Customs Board site before you rely on it.
Foreign trips only. Domestic travel never qualifies for a tax-free per diem, no matter how far you drove.
No receipts required. The daily allowance is a fixed amount per day; the trip report is the only justification it needs.
The entitlement is a ceiling, not an obligation. Days × rate is the most you can pay out tax-free — you never have to pay it all, but you can’t exceed it either.
Trip length drives everything. Flight and hotel dates prove how long the trip lasted, and the per-diem calculation rests entirely on those dates.
The tax math that made automating this a no-brainer
When we sat down to justify building the skill, the math justified it in about a minute. The same meals can be taxed three completely different ways, and the only variable is the paperwork you do. Take €744 of food from a week of travel and watch what happens depending on how it’s documented.
What you do | How it’s treated | Tax |
|---|---|---|
Do a trip report — food declared as “use of daily allowances,” within the per-diem limit | Tax-free daily allowance | 0% |
Just send the receipts, no report | Meals aren’t a business expense on their own, so they’re booked as a representation / benefit expense | ~22% (sometimes + social tax) |
Send nothing | Unexplained company-card spend, treated as a private / non-business expense | ~22% (and the weakest audit position) |
Estonian income tax is 22% in 2026, and some benefit types also carry social tax, so the gap between the top and bottom rows is real money — confirm the exact treatment with your accountant, but the direction never changes. For a company that travels regularly, the difference across a year is not a rounding error. That single comparison is the whole business case for taking the report seriously, and for not leaving it to a tired human at the end of a long week.
The trip report is the piece of paper that converts a ~22%-taxed expense into a 0% one. Everything else in the process is just supporting evidence for that one move.
Why a template was never going to fix it
Our first instinct was the obvious one: make a really good template and tell everyone to fill it in. It didn’t work, and looking back it was never going to. A template still makes a human do all the actual thinking — reading the boarding pass for the dates, classifying each card charge as travel versus food, running the per-diem step-down, and reconciling the total so there’s no leftover balance. A blank form doesn’t remove any of that work; it just gives it a nicer border. What we actually needed was something that could read the raw inputs we already had — tickets, invoices, a card statement — and do the classification and math itself.
That is exactly the shape of problem Claude is good at: messy, semi-structured inputs, a clear set of rules, and a defined output. So we encoded the entire procedure above — the per-diem rates, the foreign-trip rule, the “use of daily allowances” reconciliation, the requirement to include flights and hotels even when they aren’t on the accountant’s missing-documents list — into a Claude skill, and shipped it as part of our open enty-toolkit. The rules live in the skill, not in someone’s memory, which means they’re applied the same way every single time.
How does the skill actually work?
You hand Claude a few trip details plus your raw documents, and it produces a finished, audit-ready trip report — the same one an accountant would want, without you touching a calculator. Under the hood it runs the steps we used to do by hand, in order.
Reads your inputs. It takes your tickets, hotel invoice, taxi receipts, and card statement, and pulls out the dates, route, amounts, and descriptions.
Establishes the trip. It sets the traveller, the from → to dates, the route, and the business purpose you gave it (the purpose is the thread that ties every euro to the company).
Calculates the per diem. It applies the correct foreign-trip rates automatically — €75/day for the first 15 days, €40/day after — and respects the monthly cap.
Classifies each expense. Flights, hotels, and event passes go in as attached travel costs; food on the company card is declared line by line as “use of daily allowances,” not as a separate expense.
Reconciles the allowance. It checks the total of card-paid personal spend against the entitlement so there’s no leftover balance dangling on the books, and sets the allowance to what was actually used when needed.
Outputs the report. You get the finished document ready to hand to your accountant — or a clean blank template if you just want the structure.
The interaction is plain language, which is the point. You don’t fill in fields or learn a syntax — you just describe the trip and attach the files. Something as simple as “Make a trip report for my Tallinn trip, 12–15 May — here are my tickets and card payments” is enough to get a complete report back.
How do you install it?
The skill is free and lives in our public repo at github.com/entyteam/enty-skills. Installing it takes a minute, and there are two paths depending on how you use Claude.
Claude desktop / Cowork: download the `enty-toolkit.plugin` file from the repo, then go to Settings → Plugins and import it.
Claude Code (CLI): run `/plugin marketplace add entyteam/enty-skills`, then `/plugin install enty-toolkit@enty`.
Once it’s in, you never think about installation again — the trip-report logic is just there whenever you ask for it. And because the toolkit is open, the rules are readable: you can see exactly which rates and treatments it applies, rather than trusting a black box with your tax position.
The outcome: a 5-minute report instead of a lost afternoon
The honest before-and-after is the whole reason we’re writing this. Closing a trip used to mean roughly two hours of assembling documents, remembering charges, and second-guessing the per-diem math — usually late, usually reluctantly. Now it’s a five-minute conversation: describe the trip, attach the files, get a finished report, hand it to the accountant. The math is right because the rates live in the skill, the food is reconciled because the skill does it every time, and nothing gets left out because “include the flight and hotel even if they’re not on the missing list” is baked into the process.
There’s a habit worth adopting alongside the skill, because it makes even the automated version cleaner: transfer the daily-allowance amount to yourself and pay for food from your personal account. No stray restaurant charges on the company card, no receipts to collect, nothing extra to reconcile — the per diem becomes a single clean, tax-free line and your personal spending stays personal. Pair that habit with the skill and closing a trip stops being a task you dread and becomes something you barely notice. That’s exactly the kind of quiet, repetitive back-office work we think founders should hand off — to a skill, or to us.
Frequently asked questions
Do I need receipts for per diems in Estonia?
No. The daily allowance is a flat, tax-free amount per day, and the only thing that justifies it is a proper trip report — traveller, dates, route, and business purpose. You keep receipts for flights, hotels, and event tickets, but not for the per diem itself. That’s the entire point of a fixed daily amount.
How much is the tax-free daily allowance in Estonia in 2026?
It’s €75 per day for the first 15 days of a foreign business trip (maximum 15 such days per calendar month), and €40 per day for each day after that. These are the income-tax- and social-tax-free ceilings, so anything paid above them is taxed. Rates change over time, so confirm the current figure with your accountant or the Estonian Tax and Customs Board before you rely on it.
Can I claim a per diem for a trip inside Estonia?
No. The tax-free daily allowance applies to foreign business trips only — meaning a country other than the traveller’s country of permanent residence. A trip inside your home country doesn’t qualify for a tax-free per diem at all, regardless of distance or duration.
Is restaurant food a deductible business-trip expense?
Generally no. Meals are personal in nature and are exactly what the per diem is meant to cover. If food was paid on the company card, you declare it against the daily allowance as “use of daily allowances” rather than booking it as a separate travel expense — as long as the total stays within the traveller’s entitlement, it reconciles with no receipts needed.
What happens if I don’t file a trip report?
The trip’s expenses lose their connection to the business. Meals and unexplained card spend get treated as a benefit or private expense — roughly 22% income tax, sometimes plus social tax — and in an audit the whole trip can be reclassified as a private benefit. The report is what keeps the treatment at 0%, which is why it matters far more than any single receipt.
Should the hotel invoice be in my name or the company’s?
The company’s — with the legal name, registry code, and VAT number. An invoice in your personal name is harder to book to the company and weaker in an audit. Ask for it in the company’s name at checkout, and keep those details in a phone note so you can paste them quickly.
Can the Claude skill really build the whole report automatically?
Yes. Our free Claude skill, part of the open enty-toolkit, turns your trip details, tickets, and card payments into a finished, audit-ready trip report — per diems calculated and reconciled, food declared correctly, flights and hotels included. You can install it and read exactly what it does at github.com/entyteam/enty-skills.
We’re not in Estonia yet — is this still relevant?
It’s especially relevant if you’re weighing a move. Estonia’s per-diem and business-travel rules are one small example of how clean and rules-based the system is, and it’s the kind of thing Enty handles end to end once you’re set up. If you’re considering it, we can open your Estonian company and take care of the back office — trip reports included.
