Every group trip has the same arc. Someone overpays for the rental, someone else grabs the groceries, a third person covers the fuel, and for two days the chat handles it with a running tally of I paid for this and you owe me that. By the third day that thread has decayed into screenshots from a spreadsheet nobody updates, a few half remembrances, and quiet resentment about the one person everyone suspects underpaid. Nobody trusts the math anymore. Four people each paying four people makes a mess of transfers that mostly cancel out.
SplitTabsBot heads this off by keeping the ledger inside the group chat itself. It tracks numbers only, never real money, so there is no payment processing and no banking detail involved. The actual payment still happens the way your group already pays each other. What the bot removes is the memory problem and the trust problem at once. The shared chat becomes the record, and anyone can check it at any moment instead of asking a friend to recall what they paid three days ago. Nobody's app is the source of truth, because there is no app, only the chat everyone is already looking at.
Logging matches how you would say it out loud. Run /add 42.50 dinner @alice @bob to record a cost with an amount, a short description everyone will recognise, and the usernames sharing it. The payer is always included in the split automatically, so you never list yourself. The guide to splitting bills in a Telegram group walks through the whole flow, from adding the bot to how each group gets its own fresh ledger.
The clever part is the settlement math. A group expense calculator that nets debts across everyone at once turns a tangle into a short list. Four people on a weekend trip: Alice pays $120 for the rental, Bob pays $86 for groceries, Carol pays $40 for fuel, Dave pays $18 for parking. That is $264 total, so the fair share is $66 each. A naive approach would have Carol and Dave each writing several payments to everyone else. Running /settle instead gives the minimal settlement, so Carol and Dave each pay roughly $48, completed in a handful of transfers rather than everyone paying everyone.
That is the difference between a scoreboard and a fixture list. /balance shows each member's net position, who is owed money and who owes it. /settle proposes the fewest transfers that bring every balance to zero. Running /balance twice a day during a trip changes nothing and nudges no one, but it keeps the numbers public and honest. A wrong amount is fixed with /undo, and /clear starts the ledger over. The only discipline that matters is logging in the order things happen and fixing mistakes immediately, rather than three days later when the memory is gone and a quiet appeal to fairness turns into an argument.
Money never moves through the bot, and no banking or payment details are stored, only amounts, descriptions, and who was in each split. Each group keeps its own separate ledger, so a household tab and a trip tab never bleed together. Members who leave still show in the balances for expenses already logged against them, worth knowing before the last person checks out.
After the trip a group often wants the numbers outside the chat. CSV export of the ledger via /export is a Pro feature scoped to the whole group. Once one person upgrades, anyone in the chat can run it and get a plain CSV that opens in any spreadsheet app. Pro is a one-time 150 Stars, roughly three dollars, for the whole group, and it removes the free tier's 20 expense cap. Free groups can still check /balance and /settle all they want; they just cannot export a file or exceed the cap. Export before you run /clear, because clearing is not reversible.
SplitTabsBot sits alongside other quiet tools that make group life easier. A crypto price alert bot keeps a side channel informed during the trip, and a habit tracker bot keeps personal check-ins in the same app. The directory of these tools holds the rest of the collection.
The trip does not have to end in a resentful spreadsheet. Log as you go, run /settle when the group is ready to pay up, and export a clean CSV if you want a record. Because the math stays public, updatable, and trusted, the only argument left is who gets the window seat.
Top comments (0)