A small European consultancy that travels can flag out-of-policy expenses before month end with three checks built into the expense sheet: over the cap, no receipt, and spent on a weekend without a trip attached. Each check is a formula, and the flagged rows are reviewed every Monday morning. The caps and figures here are invented, so set caps that fit your own business.
Why travel costs slip past review
Consultants book flights early, pay for hotels in other currencies and eat out in cities with different price levels. The invoice may arrive after the trip. A single month can hold costs from three trips, and without a trip reference, nobody remembers which cost belonged to which client.
Columns to set up
- A: date. B: category. C: amount in €. D: trip or client reference. E: receipt Yes or No.
- F: over-cap check. G: weekend check. H: missing receipt check. I: reviewed, with initials.
The formulas
Assume a cap of €120 for meals and €180 for hotel nights, kept in a small table on another tab named Caps, with category in A2:A4 and cap in B2:B4.
- Over cap: =IF(C2>IFERROR(VLOOKUP(B2,Caps!$A$2:$B$4,2,FALSE),1E+9),"Over cap","")
- Weekend: =IF(AND(WEEKDAY(A2,2)>5,D2=""),"Weekend, no trip","")
- Missing receipt: =IF(E2="No","Receipt missing","")
In the first formula, IFERROR returns a huge number for categories not in the table, so unlisted categories are not flagged by mistake. WEEKDAY with 2 as the second argument numbers Monday as 1, so values above 5 are Saturday and Sunday.
A trip reviewed line by line
| Item | Amount | Flags |
|---|---|---|
| Train tickets | €96 | None |
| Hotel, 2 nights | €410 | Over cap if cap is per night: €205 a night against €180 |
| Client dinner | €148 | Over cap |
| Taxi, Sunday | €34 | Weekend, no trip if D is empty |
The hotel total of €410 is two nights at €205, so each night is €25 over a €180 cap, and the total is €50 over €360. Check the arithmetic whenever a cap is per night but the log holds a total.
What happens after a flag?
Add a short reason in column I: pre-approved by email, client request, or genuine overspend. A flag with a reason is closed; a flag with no reason is the one to follow up on. Do not delete flagged rows. Keeping them makes the next review quicker.
What about expenses paid in another currency?
Record the euro amount shown on the card statement, not a converted figure from memory. If a hotel in another country charged in its own currency, note the original amount in the trip column, so the caps check works on the euro cost you actually paid. A cap that was written in euros should be tested with euros, otherwise small rate moves will flag or miss items for reasons nobody can explain later.
Also decide who sets a trip budget before it starts. A one-line message, Berlin trip, two days, about €900 all in, gives the review something to compare against and makes the flags more meaningful than a general cap.
If two people travel together, enter each person's costs on their own rows even when one card paid for both. Otherwise per-person caps cannot be checked, and a shared dinner of €210 for two looks like one overspend instead of two ordinary meals.
Monday morning routine
- Filter column I for blanks.
- Read the flagged rows only.
- Message the traveller for each unexplained one.
- Close with initials, not deletion.
SpendixAI is built for India and INR and focuses on personal workspaces with budgets, so it is not the right tool for a European consultancy's expense policy.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


