A group per trip, flat or family
Keep the Karachi weekend separate from the flat's electricity bill. Each group has its own members, currency, expenses and balances.
Group expenses
Shared money goes wrong in a predictable way. Everybody pays for something, nobody writes it down, and a week later the group is reconstructing a restaurant bill from three different memories and one blurry photo.
An expense group fixes the record, not the friendship. Log each cost once, split it however it was actually shared, and let the running balance say who owes whom. Then settle up and let the ledger close it out.
Keep the Karachi weekend separate from the flat's electricity bill. Each group has its own members, currency, expenses and balances.
Equal when everyone shared it, percentage when the shares are uneven but proportional, and exact amounts when one person only had the coffee.
Splits are calculated in whole paisa and the leftover is assigned to someone explicitly, so a bill of 100 split three ways never comes to 99.99.
Record a payment in cash, JazzCash, Easypaisa or bank transfer. The balance moves and the settlement stays in the history as proof it happened.
Add a photo of the bill to a shared expense so a question three weeks later has an answer that is not somebody's recollection.
Send a link that shows totals only, the expenses, or the full ledger. It opens in a browser with no signup, for the person who will never install an app.
Almost nobody actually disagrees about how to divide a restaurant bill. What they disagree about is who paid for the taxi on the second day, and whether the hotel deposit was ever paid back. Those arguments are about recall, and they get worse with every day between the spend and the reckoning.
One shared list, written at the time, removes the whole category of dispute. Not because it is more precise, but because there is nothing left to reconstruct from memory.
That is why logging an expense in a group takes about as long as logging a personal one. If it took longer, it would happen at the end of the trip, from a bank statement, which is exactly the situation we are trying to avoid.
Raw balances between four people can imply six separate payments, half of which cancel each other out. Casshi nets each member's position across every expense, advance and settlement, then simplifies the result into the smallest set of transfers that clears everybody.
In practice that turns a tangle into one or two payments. It is less to explain in a group chat, and far less likely to end with one person having paid twice.
Advances are part of that calculation. When somebody books the hotel three months ahead, recording it as an advance means their contribution is counted from the start rather than appearing as an unexplained debt later.
Splitting a hundred rupees three ways in decimals gives you three shares of 33.33 and a bill that does not add up to itself. Repeat that across a weekend and the group ends up with a balance nobody can reconcile against the actual money that moved.
Every split in Casshi is calculated in integer paisa, and the leftover unit is assigned to a specific person rather than dropped. The shares always sum to the expense, exactly, every time.
The same arithmetic runs in the browser and in the database. The browser copy exists so the shares update as you type; the database is the one that decides, so a bad request cannot write a split that does not balance.
A group is shared, your own finances are not. Group expenses live in their own tables with their own membership rules, and joining a trip fund never exposes your personal transactions, budgets or savings goals to anybody in it.
Share links are deliberately scoped for the same reason. Totals-only is often all an outside party needs, and the link cannot be widened by whoever receives it. Those pages are also kept out of search results, so a link that ends up somewhere public does not become an indexed page of your group's balances.
Getting started
Set it up on day one and there is nothing to reconstruct on the last day.
Name it, pick the currency, and add the people in it. One group per trip, flat or shared arrangement.
Record who paid and how it was shared. Equal, percentage or exact amounts, whichever matches what actually occurred.
The group shows each person's net position and the simplest set of payments that would clear it.
Record the payment and its method. The balance updates and the settlement stays in the history.
Questions
Short, direct answers, and none of them promise anything the app does not already do.
Log each shared cost once, as it happens, with whoever paid recorded properly. Fairness is rarely an arithmetic problem. It is a memory problem, and it goes away the moment there is one list everybody can see.
Yes. Choose an equal split, a percentage split, or exact custom amounts per person. Exact amounts are what you want when three people shared a meal and one of them only had a coffee.
It works out each member's net position across every expense and settlement, then simplifies the debts into the smallest set of payments that clears them. Four people with tangled balances usually end up with two transfers instead of six.
Record it as an advance to the group. It counts towards what that person has already put in, so a trip where one person books everything in January does not look like they owe money in March.
Record a settlement between two members and pick the method: cash, JazzCash, Easypaisa or bank transfer. The balances update and the payment stays in the ledger, so nobody has to remember whether it happened.
Yes. Create a share link and choose what it reveals: totals only, the expense list, or the full ledger. It opens in any browser without signing in, which is usually enough for the one person in the group who will never install anything.
Keep reading
Same account, same data. These pages cover the parts of the app people usually come looking for next.
Five minutes of setup now is the difference between splitting a bill and reconstructing one.
Free plan · No card required · Delete your account any time