How to track spending on a trip without ruining the trip
Multiple currencies, one person paying for everybody, cash again, and no appetite for admin. How to structure a holiday in your ledger so that one week does not destroy the readability of the month around it.
A household that has recorded reliably for months will often produce, for the week of its summer holiday, either nothing at all or a single entry saying "Italy" with a large number next to it. Then the month containing that week becomes unreadable, the year’s category totals inherit a lump nobody can decompose, and the following month’s grocery budget gets set from a baseline that includes seven days of restaurant meals.
This is not a discipline failure and treating it as one leads to the wrong fix. A trip breaks four assumptions your ordinary recording habit depends on: one currency, one person paying only for themselves, mostly card, and a few minutes of attention available in an ordinary day. It is worth deciding what to do about that before you leave, because it takes ten minutes at home and is nearly impossible to arrange on the second evening in an unfamiliar city.
Decide the structure before you go
There are two coherent approaches and the mistake is to end up between them.
One line in the annual budget
The trip has a total, that total is an irregular annual cost saved for in advance, and inside the trip nobody records anything. You come home, add up what left your accounts, enter one figure against "holiday", and you are done.
This is a completely legitimate choice and it is the right one for a lot of households. Its virtue is that it costs nothing during the trip, which is when your willingness to do admin is at its lowest. Its cost is that you learn nothing about the shape of the spending — you cannot tell next year whether it was the flights, the accommodation or the eating out, so you cannot make any decision about it except a total.
A tracked mini-budget of its own
The trip gets a rough allocation before departure, spending is recorded during it, and it is read as a separate unit rather than as part of the month. You find out what a week away actually costs you, broken down, and next year’s number is derived rather than guessed.
Its cost is real work while you are supposed to be relaxing. The way to make it survivable is to be much coarser than at home: three or four categories for the whole trip — travel, accommodation, food, everything else — rather than your usual scheme. Category detail is what makes recording slow, and slow recording on holiday does not happen.
What does not work is deciding nothing, recording enthusiastically for two days and stopping, which produces a partial record that looks like data and is not.
One payer of record, settled once
On any trip with more than one person, somebody ends up putting most things on their card because it is faster at the counter. Trying to split each meal, taxi and museum ticket at the moment of paying is the single most reliable way to make everyone hate the bookkeeping, and it is the reason most trip tracking collapses on day three.
Agree instead that one person is the payer of record. They pay for shared things, the entries are made once under their name, and there is exactly one settling-up at the end. Personal purchases stay with whoever made them and out of the shared total.
Two details make this work. The payer should be whoever is most likely to actually record things, since they are doing the data entry by default. And agree in advance what counts as shared — meals together, transport and accommodation obviously are; a jumper, a book or a round of drinks bought for someone else are where the awkward conversation at the end comes from.
Currencies: record in what you paid, convert once
The instinct is to convert at the moment of paying, using whatever rate the phone shows. Do not. That figure is not what you were charged, and the difference is not trivial.
The rate you actually pay is set when the transaction is processed, not when you tap, and it includes your card issuer’s margin and any foreign transaction fee. If the merchant offers to charge you in your home currency — dynamic currency conversion, the "would you like to pay in pounds?" question — the rate applied is theirs and is generally worse than your bank’s. Cash exchanged at an airport carries a different spread again. So one trip can easily contain three or four different effective rates, and none of them is the mid-market number your phone displays.
The workable method is to record the amount in the currency you actually handed over, keep the currency in the note if your ledger is single-currency, and convert once when you get home using a single rate derived from reality — total home-currency charged, divided by total foreign currency spent. That single blended rate is more accurate for the trip as a whole than a series of live guesses, and it takes five minutes rather than being a decision at every till.
So entries made during the trip are provisional in amount but correct in structure. Fixing the number afterwards is arithmetic; reconstructing the structure afterwards is not possible.
Mark the trip, or lose the month
This is the point that most affects the rest of your year, and it costs almost nothing to get right.
Without a marker, a week abroad merges into the surrounding month. Your food total for that month is now your normal food plus seven days of restaurants, your transport contains flights, and the month is not comparable to any other month. Worse, it is not comparable in an invisible way: nothing in the number says why it is high, so a year later you will see an expensive August and have no idea whether that was the holiday or a change in habits.
The fix is a single consistent marker on every trip entry — the same word in the note on all of them, or a dedicated category if you would rather. Consistency matters more than what you choose; "Lisbon" on some entries and "holiday" on others gives you nothing. With one marker you can pull the trip out as a unit, read it on its own, and read the month with it excluded.
In Fambook this is what the note field and the place field are for: entries carry a note, a place and the member who spent it, so a consistent trip word in the note gives you a way to find the whole trip afterwards, and the statistics screen breaks a period down per place and per member. Recording during the trip depends on entries saving without a network, since a phone abroad is frequently offline — entries are written to the phone first and pushed later, with anything still waiting shown as a count.
Getting the entries in at all
Fifteen seconds at the table, while the bill is in front of you, beats any amount of good intention on the flight home. This is the same recall problem that ordinary cash spending has, except worse: on a trip everything is unfamiliar, there are more transactions than usual, they are in a currency you do not have intuitions about, and the days blur together. Reconstruction four days later is not approximate, it is fiction with a plausible shape.
What actually works, in rough order of effectiveness:
- Enter at the table or immediately outside. The bill is in your hand and the amount is in front of you.
- If you cannot, photograph the receipt and enter it that evening — a photograph is a real record and your memory is not.
- A single fixed moment each evening, coarse categories, one entry per thing. Ten minutes before dinner rather than at midnight.
- For cash, do a wallet count every couple of days: record what you drew out, count what is left, book the difference as one lump. A correct total with no recall involved.
- Accept a lump "unaccounted" line rather than distributing it by guesswork. Six months later a guessed breakdown is indistinguishable from a recorded one, which is why it is dangerous.
Coming home
Three jobs, none of them long, all of them easier in the first two days than in the second week.
First, the settle-up. When the others repay the payer of record, that repayment is a transfer between people, not income and not a negative expense. Record it as a transfer, or leave it out of the ledger entirely and handle it between accounts — either is fine, but recording it as income means your household appears to have earned money it did not earn, and reducing the original expenses by the repayment means the trip total no longer reflects what the trip cost. The double-count is the most common error here and it goes unnoticed because the resulting numbers still look reasonable.
Second, the conversion: one blended rate applied once. Check the total against what your account actually shows, and if there is a gap, one line for foreign transaction charges is a more honest home for it than spreading it across the meals.
Third, and most valuable: exclude the trip when you set next month’s numbers. If you derive a grocery budget from a month containing a holiday, you will produce a figure that is wrong in both directions at once — inflated by restaurant meals, deflated by a week of not buying groceries at home — and then you will miss it and conclude that budgets do not work. Pull the marked trip entries out, read the remaining weeks, and set the number from those.
The broader point is that a trip is an irregular annual cost like insurance or a car service. The version of this that works long term is to know roughly what a trip costs you, set that aside monthly through the year, and record enough during the week away to make next year’s figure a derivation rather than a hope. None of that requires you to spend your holiday doing bookkeeping. It requires about ten minutes of decisions before you leave and about twenty after you get back.
Frequently asked questions
Should I track a holiday in detail or just record one total?
Either is defensible; drifting between them is not. One total is cheap and tells you nothing except the size, which is enough if your only decision is how much to save next year. A tracked trip with three or four coarse categories tells you whether the money went on flights, beds or restaurants, which is the only way next year’s figure becomes derived rather than guessed.
How should I handle foreign currency?
Record the amount in the currency you actually paid and convert once when you get home, using your total home-currency charge divided by the total foreign currency spent. A live rate at the till is not what you were charged — your issuer’s margin, any foreign transaction fee, and dynamic currency conversion at the merchant all change the real rate.
Should we split every meal as we go?
No, and this is where most trip tracking collapses. Nominate one payer of record for shared costs, keep personal purchases separate, and settle once at the end. Agree beforehand what counts as shared, because the ambiguous items — a round of drinks, a gift, a jumper — are what makes the final conversation awkward.
How do I record the settle-up without double counting?
Record it as a transfer between people, or keep it out of the ledger and handle it directly between accounts. Recording it as income makes your household look like it earned money it did not earn, and subtracting it from the original expenses means the trip total no longer reflects what the trip actually cost.
How do I stop the trip from wrecking my monthly numbers?
Put the same consistent marker on every trip entry — one word in the note, or a dedicated category — so you can read the trip as a unit and read the month with it excluded. Then set next month’s budgets from the non-trip weeks, since a month containing a holiday is inflated by restaurants and deflated by a week of not shopping at home.
What if my phone has no signal abroad?
The entry still has to save, which is why local-first storage matters more on a trip than anywhere else. Fambook writes entries to the phone first and uploads them when the network returns, retrying on launch and on recovery, and shows a count of anything still waiting rather than hiding it.
Try it for one month
Fambook gives a household one shared ledger: anyone can add an entry in seconds, every entry says who spent it, and the month adds up in one place instead of two. Records with no signal and syncs afterwards. Recording, categories, budgets, statistics, CSV import and export, sync and sharing for two people are free — the subscription only buys you less typing.