Keep shared spending in one place
Create a group for a trip, a home or another shared expense. Record a purchase once so the people involved can see the amount, who paid and how it was split. Balances show who owes whom.
Expensease
A mobile app for shared bills and personal spending. Record what you paid, choose how to split it and keep track of repayments.
A simple example with three friends.
Alex owes you ₹300.00.
Sam owes you ₹300.00.
Interactive example with sample data. This is not the upcoming app interface. No payment is made.
Use Expensease for shared costs with friends, flatmates or a partner, and for your own day-to-day spending. Each expense records who paid and who needs to contribute.
Early release · iOS / Android / WebShared groups and personal trackers keep different spending needs in the same app.
Create a group for a trip, a home or another shared expense. Record a purchase once so the people involved can see the amount, who paid and how it was split. Balances show who owes whom.
Divide an expense equally, enter exact amounts or use percentages. If more than one person paid, record each contribution. Expenses in different currencies stay separate, so a balance in one currency is not silently combined with another.
Pay using the payment app or method you already use, then record the settlement in Expensease. This keeps the shared record up to date without asking everyone to remember which payments have been made.
Personal trackers keep solo expenses separate from group spending. Use category budgets, monthly insights and recurring entries for regular bills. On iPhone, receipt scanning and voice capture provide additional ways to enter an expense.
The work behind Expensease is as much about dependable money records as it is about entering a bill. Shared expenses and personal tracking use the same product, with different everyday needs.
An expense records both sides of the transaction: each person’s contribution and each person’s share. Settlements use the same expense model, so a repayment changes the balance through the ledger rather than through a separate manual adjustment. That structure supports partial repayments and multiple payers while keeping the original record understandable.
The iPhone client is written in SwiftUI and uses the existing Node.js service rather than a second backend. The wider repository also contains the web and Android clients. API versions and shared money rules matter here because a bill entered on one surface must mean the same thing when someone else opens it elsewhere.
The product makes capture easier with receipt and voice entry on iPhone, but correctness comes first. Personal spending and shared finance are separate modes, and currencies remain explicit. The interface is being redesigned, so this case study keeps screenshots out until the replacement screens are ready.