The quiet complexity of splitting a trip expense

Four friends share a bill. The interface asks for a title, amount, and who paid. It feels like a tiny form until the total does not divide evenly, one person paid for only three people, and someone adds a photo of the receipt. Now the app is making decisions about money, identity, and storage.

In a shared trip product, expenses can be split equally or with custom amounts. For an equal split, the code rounds each share down to the nearest cent and assigns the remaining cents to one participant. That is not the only possible rule, but it is a rule people can understand and one that makes the parts add back to the original total. A ledger that loses a cent on every awkward split eventually loses confidence too.

Who is allowed to change the record?

The expense action checks edit access to the trip before creating or deleting a record. Deletion is scoped by both expense ID and trip ID, so an ID from another trip cannot be used to remove the wrong row. Reading a receipt has its own check: the server loads the expense's trip and confirms that the viewer can see it before returning the image.

Those checks are easy to miss when a product begins as a personal utility. The moment other people are invited, the trust model changes. A receipt can contain names, addresses, and payment details. It should not be fetched as part of every list query or exposed because someone guessed a link.

Keep the main screen light

The receipt image is loaded only when requested, rather than carried with every expense in the list. That keeps the common view quick and makes the privacy boundary easier to inspect. The list needs enough context to answer “who paid, how much, and who owes?” It does not need to transport every photo at once.

The same thinking applies to features like notes, stops, and shared people in a trip. Each helps a real coordination problem, but each adds relationships that need access checks and clear ownership. The small form was never really just a form. It was the beginning of a shared record that several people have to trust.