Office Lunch, Kitty, Cab Pool: How to Split Team Expenses at Work in India

Every Indian office runs an invisible economy: the team lunch someone fronts, the birthday-cake collection, the monthly kitty fund, the daily cab pool from the metro station, the chai run that one generous soul has been silently funding for a year. None of it is company money, so no reimbursement system touches it — and it all runs on memory and goodwill until one or both run out. Here is how office groups can put shared expenses on rails.

The Team Lunch Problem

One person pays the ₹4,300 bill because splitting at the counter holds everyone up. The right pattern: payer logs it in a shared group on the walk back, everyone's share is visible before they reach their desks, and UPI transfers happen in the elevator. For teams that eat together often, do not settle per meal — run a monthly balance and settle on salary day. Order-value fairness matters at office lunches more than among friends: use item-wise splits when the vegetarian who had a ₹180 thali should not fund the ₹600 biryani-and-dessert crowd.

The Kitty Fund, Done Right

Office kitties — monthly collections for celebrations, farewells, and festivals — fail from opacity: nobody knows the balance, who has paid, or where the money went. Fix it with three rules: one named keeper, one visible ledger (a shared expense group where contributions land as credits and spends as logged expenses), and a monthly balance announcement. When the ledger is visible to all members, contribution compliance goes up and the keeper stops absorbing suspicion along with the admin work.

Cab Pools and Daily Commutes

Cab and auto pools generate the highest transaction frequency of any office arrangement — twenty-plus rides a month with rotating payers and occasional absentees. Per-ride settlement is madness. Instead: log each ride against the people actually in the cab that day, let balances accumulate, settle monthly. The rotating-payer pattern roughly self-balances, and the ledger catches the drift that always exists (the person who "never has change" and the one who always pays).

Birthday Collections and Farewell Gifts

The collection problem is chasing: one organizer WhatsApp-messaging fifteen people individually, twice. Better: log the gift as an expense split across contributors in a group, and let app reminders do the chasing. The organizer fronts the money once and stops being a part-time collections agent. Etiquette guardrails that keep it clean: contributions are flat and modest, opting out is always allowed without commentary, and the birthday person is obviously excluded from their own collection.

Why Not Just Company Reimbursement?

Because none of this is reimbursable — it is personal money moving between colleagues, which makes it socially harder than friend money: you cannot nag your manager about ₹350, and junior team members will silently eat unfair splits rather than object. A neutral ledger removes exactly that hierarchy problem: the app states the balance, the app sends the reminder, and no one has to have a money conversation with someone who writes their appraisal.

Setting It Up

One group per arrangement — "Team Lunches", "Q3 Kitty", "Cab Pool" — not one mega-group, so balances stay interpretable. Use a free app like Lekhhaa: groups are quick to create, splits can be equal, exact, or item-wise per expense, balances are visible to everyone, and settlement is a UPI tap. The entire system costs each member ten seconds per expense, and buys back the small, constant social tax that unmanaged office money quietly levies on everyone.