Who Can Edit or Delete a Shared Group Expense?

The trust problem every shared tab runs into#

Someone adds a hotel split at midnight from the lobby wifi. Someone else fixes a typo in the amount the next morning. A third person realizes the dinner expense was actually paid by a different card and edits the payer. All of that is normal in a trip where five or six people are logging costs in real time — but it raises an obvious question: if anyone can touch a shared expense, what stops someone from quietly deleting a charge you added, or changing a number right before you settle up?

That worry is exactly why some people fall back to a WhatsApp group and a spreadsheet instead of a dedicated app — at least there's a message history. The irony is that a spreadsheet has zero access control either; anyone with the link can edit any cell, with no record of who touched what. The real fix isn't locking expenses to their creator (that just creates a bottleneck when the one person who added a charge is asleep or offline when a correction is needed). The real fix is making sure that when someone other than the creator does something consequential — delete it, or quietly turn a settled charge back into an unresolved one — everyone affected finds out, with a reason attached.

How Lumela actually handles it#

Here's the exact permission model in Lumela's shared trip ledger, as it's enforced in the app today — not a planned feature, not a setting that needs turning on:

Editing is open to the whole group. Any member can correct the title, amount, currency, or how an expense is split, regardless of who originally logged it. If you can see the expense, you can fix it. This is deliberate: in a group of friends covering a shared trip, requiring the original adder to be available for every typo fix would slow everyone down for no real security benefit — the risk isn't editing, it's silent editing.

Deleting someone else's expense requires a reason — and the app enforces it, not just a guideline. If you're the one who added an expense, you can delete it with a tap. If you didn't add it, the delete button in Lumela stays disabled until you type something into a reason field. There's no way to submit an empty reason and have the server quietly accept it anyway — the check happens on both ends.

Everyone connected to that expense is told, with the reason included. The moment a non-owner delete goes through, Lumela sends a push notification to the person who paid, the person who created it, and everyone who was splitting it (minus whoever just deleted it) — and the reason you typed is right there in the notification body. Nobody finds out about a missing charge by noticing the total looks off three days later.

Nothing is actually gone. A deleted expense becomes a tombstone, not a hole. It shows up in a dedicated Deleted list with who deleted it, when, and the reason given, and it can be restored from there if it turns out to be a mistake — a fat-fingered swipe, or a dispute that gets resolved after the fact.

Reopening a settled expense has its own guardrail, for a different reason. Marking a completed expense back to "amount pending" isn't cosmetic — it immediately pulls that amount out of the group's balance calculations. Lumela lets the expense's creator, its payer, or a group admin do that freely, since they have the context to know why. Anyone else has to supply a reason, which gets written into the expense's activity log alongside the change itself.

Step by step: deleting an expense you didn't add#

1. Open the expense from the group's expense list.
2. Tap delete.
3. Since you're not the one who logged it, a reason field appears — the delete button won't activate until you fill it in.
4. Type a short reason ("duplicate," "wrong group," "refunded by the venue" — whatever's true) and confirm.
5. The payer, the original creator, and everyone in the split get a notification naming you and your reason.
6. If anyone disagrees, the expense is still sitting in the group's Deleted list and can be restored — nothing has to be re-typed from scratch.

The actual difference this makes#

This isn't about preventing mistakes — people will still delete the wrong thing sometimes. It's about making sure a shared trip ledger never has a silent edit that only one person knows about. Every deletion by someone other than the owner carries a reason and an audience; every reopened expense that pulls money back out of the balances carries the same. For a feature people only think about when something goes wrong, that's exactly the point: by the time it matters, the record is already there.

If you're still figuring out how splitting and settling up works day to day, see how Lumela splits trip expenses and who owes who when it's time to settle up.