How to split trip expenses fairly when not everyone goes to everything

A group of five hires a holiday cottage. Two of them skip the Saturday boat trip because of seasickness. Three of them want a wood-fired pizza place that two others find too expensive. By Sunday lunch, “we’ll just split everything five ways at the end” has stopped being the obvious answer.

The right way to handle this isn’t a mathematical trick — it’s picking the right kind of split for each expense, and accepting the small imprecisions that keep the maths simple. This guide walks through the four splitting modes most apps offer (equal, shares, exact, percentage), when each one is fair, and the rules of thumb that keep settling up tractable when life gets messier than the spreadsheet expected.

Equal split — the default for a reason

Everyone pays the same fraction. Five people, £100 dinner, £20 each.

This is the right answer for anything the whole group consumed together: a hire car shared by everyone, a Friday-night dinner everyone attended, a cottage everyone slept in. It’s also the right answer for anything where the variation isn’t worth the bookkeeping — a £15 pack of beers, a £6 coffee round. Tracking who had two pints and who had one quietly poisons a trip; just split.

Equal-split also handles the “not everyone went” case perfectly well — as long as you only put the people who went on the split. The boat trip the seasick two skipped is still equal-split: £60 boat, three attendees, £20 each. The trick isn’t a different split mode; it’s picking the right participant list for that expense.

The next three modes earn their keep in a different situation: when the people on the split consumed the same expense in materially different amounts.

Shares — when “everyone pays a bit, but not the same bit”

Shares splits an expense by a count, not a percentage. The same dinner, but one person had two mains and a starter while everyone else had one main. You give them two shares, the others one share each, and the bill divides into the right number of slices.

The classic uses are:

• Accommodation where someone has a private room and the others share. Private-room people take two shares, shared-room people take one each.
• Drinks rounds where one person genuinely drank twice as much as everyone else. They take two shares.
• Restaurant bills you don’t have a receipt for where one person had the £35 prix fixe with the wine pairing and three had the £20 set menu — two shares for the pairing, one share for everyone else, near enough.

Shares is what you reach for when the ratio is obvious but the absolute amount per person isn’t. You don’t have to do the maths. You just point at people and say “you, two; you, one; you, one” and the tool figures out the £-per-share number.

Everyone on a shares-split takes at least one share. To exclude someone entirely — they didn’t take part at all — remove them from the expense’s participant list rather than setting their share to zero.

Exact — when you know the line item

Sometimes you have the receipt and you know who ordered what. Person A had the lamb at £24, Person B had the cod at £18, Person C had the soup and a salad at £14. Service is split equally on top.

This is the right answer when the cost gap matters and the data exists. A nine-course tasting menu where two people had the wine pairing and three didn’t; a hotel bill where one person added a spa treatment to their room. The split isn’t a percentage or a count — it’s a list of specific amounts that have to add up to the total.

The pitfall is using exact-split for expenses where the data doesn’t exist. If five people grabbed a takeaway and you can vaguely remember three pizzas, two sides, and a shared garlic bread, don’t try to reconstruct it line by line. You’ll get it wrong, you’ll spend twenty minutes on a £40 bill, and you’ll generate friction over rounding errors. Either equal-split or shares-split that one. Save exact-split for the moments where the receipt is in someone’s hand and the gaps are real.

Percentage — for asymmetric arrangements

Two couples, one solo traveller. The two couples agreed to take 35% each of the cottage; the solo takes 30%. That’s not equal (not 33% each), it’s not shares-by-people (the couples would otherwise pay 40% each), and it’s not exact (no per-line itemisation). It’s a deal the group made up front, expressed as percentages.

Percentage is the rarest of the four modes, and the one most prone to misuse. Most things you’d reach for it for are actually cleaner as shares (a single room counts as two shares of a four-room cottage; you don’t need to translate that into 33% / 22% / 22% / 22%). Save percentage for the cases where the group has explicitly agreed the proportions up front — accommodation deals between couples and singles, group gifts where contribution levels were negotiated, anything where the percentage is the agreement.

Patterns for “not everyone goes to everything”

The hardest splits aren’t the algorithmic ones. They’re the social ones — the moments where part of the group does something the rest doesn’t, and the expense reflects that.

A few rules of thumb that hold up:

Default to equal, opt out by exception. Most expenses on a trip are genuinely group expenses. When someone didn’t take part in a particular thing, just leave them off that expense’s participant list and equal-split among the people who did go. Reach for shares or exact only when the attendees themselves consumed the same expense in different amounts (one had the private room, one had the wine pairing).

Per-night, not per-trip, for accommodation. If one person joins on day three of a five-night cottage stay, splitting the whole booking equally over-charges them and under-charges everyone else. Compute their share as nights_attended / total_nights × total_cost — most splitting tools express this as one share per night attended. The same logic applies when someone leaves early.

Group activities with non-attenders are a separate expense. If the museum cost £80 for the four who went, that’s an £80 expense split among those four. Don’t try to fold it into a single “Saturday entertainment” line that some people contributed to and others didn’t — keep each activity discrete.

The “host pays” instinct usually works. When the group is staying at one person’s friend’s flat and they offer to cover a thank-you bottle of wine, let them. Tracking every gesture as a split-eligible line item makes a trip feel transactional. The amounts are small; the social signal is the whole point.

The bigger rule: fair means “obvious and acceptable”, not “optimal”

Most splitting apps give you the tools to make every expense exact to the penny. That capability is a trap. The goal of a trip’s accounts isn’t perfect equity — it’s everyone leaving the trip without resentment, and being able to settle up in five minutes once it’s done.

That means:

• Don’t track to the penny on small things. A £4 coffee round equally-split when one person had a tea is fine. Reaching for shares-mode here is overkill.
• Settle once at the end, not after every meal. Running balances during a trip create more friction than they remove. Log expenses as they happen; let the tool compute who-owes-whom on the final morning.
• When the maths gets weird, ask the group. “Should this be split between everyone or just the four who went?” takes ten seconds and produces the actually-fair answer. The app doesn’t have to guess.

Putting it together

For most trips, the split mostly looks like: equal-split everything, with the two or three expenses where someone obviously opted out simply leaving those people off that expense’s participant list. One or two shares-splits when the attendees consumed unequally (a private room, a wine pairing). One or two exact-splits when there’s a hotel bill or restaurant tab where the data is on the receipt. Percentage shows up rarely, mostly for accommodation deals decided in advance.

The hardest part isn’t picking the mode — it’s having the conversation early. Agree, in the first day or two, that “we’ll equal-split unless someone calls it out” is the default. From there, every later expense either follows the default or gets a five-second decision. The trips where this conversation never happens are the ones where the post-trip reconciliation gets weird.