Say you are a consultant. Four days in another city for a client workshop, leaving Tuesday, back Friday evening. By the time you are home you will have accumulated somewhere around twenty receipts, two of which will be thermal stubs already fading, one of which will be in a currency you did not plan for, and several of which will be ambiguous as to whether they were business or personal.
Eighteen months from now, somebody — your accountant, a tax authority, or you — may need to reconstruct what that trip cost and why each cost was legitimate. Almost everything that determines whether that reconstruction is possible happens during the four days, not afterwards.
This is that trip, stage by stage.
Before you leave: fix the trip identifier
Decide, before the first booking, what this trip is called. "LDN-MCR Hartley workshop Oct" or simply "TRIP-041". Write it somewhere you will see it — the top of your notes, a pinned message to yourself.
This sounds trivially small. It is the single highest-leverage thing in the whole process, because every subsequent record either carries that identifier or does not, and the ones that do can be pulled together with one filter later. The ones that do not have to be found by date-guessing through a year of rows.
Two things to capture at this stage:
- The booking confirmations, which are the only receipts generated before the trip and the ones most likely to be buried in email
- The business purpose, in one sentence, written now while it is obvious
The purpose sentence should name the counterparty and the reason: "Hartley Group — onboarding workshop for the Q4 migration." Not "client visit."
The outbound day: establishing the pattern
Your first two or three captures set the pattern for the rest of the trip. If you capture the train ticket properly on Tuesday morning, you will probably keep doing it. If you tell yourself you will sort it out later, you have set a different pattern and the trip is already compromised.
Tuesday's typical haul:
| Receipt | Capture risk | What to add beyond the image |
|---|---|---|
| Train ticket | Low — digital, in email | Trip ID, leg direction |
| Station coffee | High — small, thermal, feels trivial | Trip ID |
| Taxi to hotel | High — thermal, fades fastest | Trip ID, from/to |
| Hotel check-in | Low — invoiced at checkout | Defer; capture Friday |
| Dinner | Medium | Trip ID, attendees if any |
Note the pattern: the risky ones are the cheap ones. A £3.40 coffee feels beneath the effort of a capture, and across a four-day trip the sub-£10 items commonly total more than the hotel.
The taxi stub deserves specific attention. Thermal receipts from in-car printers are the worst-quality paper in the chain; left in a jacket pocket, they are frequently unreadable within a month. Photograph it in the car, before you put it anywhere.
During the trip: the ambiguity problem
Midweek is where travel records go wrong in a way that is invisible at the time.
Wednesday evening you eat dinner alone. Is that a business expense? In most jurisdictions, subsistence while travelling for work is treated differently from a meal you would have eaten anyway at home — and the treatment varies enough by country that the answer is genuinely "it depends".
What does not vary is this: the decision is easier to make and far easier to defend if the record says what happened. "Dinner, alone, hotel restaurant, travelling" is a fact. Your accountant can apply the right treatment to a fact. They cannot apply anything to "Dinner £31".
The same applies to the Thursday evening where two colleagues joined, and to the Friday lunch that was partly a client meeting and partly you being hungry. Record what occurred; classify later with advice.
The personal-day question. If you extended the trip by a day for your own reasons, that day's costs are generally not business costs, and the trip's travel costs may need apportioning. Mark the personal day in your records at the time. Discovering it later, from a hotel invoice that runs one night longer than the workshop, is the kind of discrepancy that attracts questions.
Currency, if you crossed a border
Two numbers exist for every foreign transaction: the amount printed on the receipt, and the amount your card issuer actually charged after conversion and any fee. They will not match, and the gap is sometimes several per cent.
Record both. The printed amount ties to the receipt image; the charged amount ties to your statement. If you only keep one, reconciliation at year end becomes an exercise in reverse-engineering exchange rates, which is slow and never quite exact.
A practical column layout for the mixed-currency trip:
- Amount (as printed)
- Currency (as printed)
- Amount charged (home currency, from the statement)
- Date charged, which may differ from the transaction date by a day or two
Check-out day: the invoice you have been waiting for
The hotel invoice is the one document on the trip worth reading rather than just photographing, because it is usually itemised and the items are often treated differently from each other: room, breakfast, bar, laundry, parking, city tax.
A single "Hotel — £642.00" row collapses all of that into one figure and guarantees someone reopens it later. Split it at least into room-and-tax versus everything else. If your category list separates accommodation from meals, breakfast belongs on the meals line even though it arrived on the hotel bill.
The same evening: close the trip
This is the step that converts a pile of captures into a record, and it should happen while you are on the train home, not next month.
- Filter your sheet to the trip identifier
- Compare the row count against your memory of the trip — missing days are obvious here and recoverable today
- Fill any empty purpose or attendee fields
- Add the trip's total to wherever you track client-recoverable costs
- Flag anything you are unsure about for your accountant, rather than guessing a category
Fifteen minutes, and the trip is done. Scan2Sheet helps for most of the mechanical part — each capture has already landed as a categorised row with the image linked, so closing the trip is a filter and a read-through rather than a data-entry session. The judgement calls in steps three and five remain yours, and they are the ones that make the record defensible.
The three documents that go missing most often
Across a lot of trips, the same three records are the ones absent when someone goes looking.
The flight or rail receipt, as opposed to the itinerary. Airlines and rail operators send a booking confirmation immediately and a receipt or invoice separately, sometimes only on request, sometimes only after travel. The confirmation shows an itinerary and a price; it is not always acceptable as proof of payment. Check, at booking, whether what you have in your inbox is a receipt or a schedule, because requesting one afterwards gets progressively harder.
The second night of a two-hotel trip. Trips with a hotel change mid-way reliably produce one invoice and one gap. The first hotel is captured at checkout; the second is captured while you are thinking about getting home.
Anything bought in cash. Cash spending leaves no statement line, which means it leaves no trace at all if the receipt is lost. There is no recovery path. For cash purchases the receipt is not supporting evidence — it is the only evidence.
If the client is reimbursing you
Trips billed on to a client have a second audience, and the requirements do not perfectly overlap with the tax ones.
Clients commonly want: the receipt itself, an agreed rate or cap applied, and costs presented per trip rather than per month. Some want their own project code on each line. Many will not pay for anything submitted after an agreed window, which is a shorter window than any tax deadline.
The practical consequence is that rebillable travel should be flagged at capture rather than identified later. A rebillable column on each row means the invoice preparation is a filter, and — more importantly — the gap between what a trip cost and what was invoiced becomes visible.
That gap is worth checking every time. Unbilled recoverable travel is one of the quietest ways for a consultancy to lose money, because an absence never shows up in any report that was not designed to look for it.
How long the trip file matters
Record retention requirements vary by jurisdiction, but the practical minimum in most places is several years after the relevant filing, and longer in specific circumstances.
That horizon has one design implication worth noting: whatever holds your receipt images needs to outlive the phone you took them on. Images in a camera roll are not a records system. Images in cloud storage, linked from the row that describes them, are — because the link is what preserves the connection between the evidence and the explanation.
A folder of 4,000 photographs with no index is, functionally, the same as no records at all. The work of matching them to transactions exceeds the value of the deductions.
Eighteen months later
The test of all this is a specific question asked cold: "What was this £642 hotel charge in October last year, and why was it a business cost?"
With the process above, the answer is a filter on the trip ID that returns the booking confirmation, a dated workshop purpose, an itemised invoice split into its components, and a coherent set of surrounding travel on the same dates. It takes two minutes and raises no further questions.
Without it, the answer is a bank statement line and a story. Those are the claims that get disallowed — not because they were illegitimate, but because nothing remained to show that they were not.
Pick your next trip, assign it an identifier before you book anything, and run it through this once. The habit transfers; the backlog does not have to.