Household expense tracking, designed for the way Indian households actually work

Q: Can a household member see who logged each expense?

Not in the default analytics. /ask aggregates across the whole household. If you want per-person breakdown, you can phrase the question that way and the bot will filter accordingly.

Indian households rarely fit the "one user, one app" pattern that most personal-finance tools assume. Hisaab is shaped around shared ledgers from day one.

Open in Telegram

Free tier · 20 messages and 2 questions per day

Across India, the typical household budget is touched by more than one person. A couple manages bills and groceries. A joint family tracks shared monthly expenses against pooled income. Three flatmates split rent, electricity, and the gas cylinder. None of these scenarios fit a tracker designed around an individual user.

Hisaab's primary unit is a household — a group of people who log into the same ledger. Solo users are just households of one. Adding a partner, parent, or flatmate is one Telegram command.

The shape of the household model

When you /start the bot, Hisaab creates a fresh household with you as the only member. Every expense you log is scoped to that household.

When someone joins your household via /join CODE, all of their expenses land in the same pool. Either of you can /ask "how much did we spend on groceries this month?" and get a household-level answer.

Common household setups

Couple, no kids. Both partners log everything. Single shared budget.
Family with shared expenses. Parents log groceries, bills, school fees; kids of working age log their own contributions. One ledger, one monthly summary.
Three flatmates. Each logs joint expenses they paid for (rent, gas, Wi-Fi) and asks /ask at month-end to see who paid what.
Spouse + visiting parent. A short-term visitor can be invited; they leave the household with /leave when they fly back.

What Hisaab does well in shared mode

Per-household privacy. Every analytics query is hard-scoped to your household at both the prompt and SQL-validator level. Other households cannot see your data.
Per-household categorisation. If your family teaches the bot that "Lavonne" is a grocer (not a restaurant), the override applies to your household alone.
Easy in, easy out. Joining is a single /join. Leaving is a single /leave. Deletion is a single /delete.

Frequently asked

Is there a limit to household size?

There's no hard limit, but in practice 2-5 members is where the model is most useful. Beyond that, you may want sub-categorisation that the current bot doesn't support yet.

Can a household member see who logged each expense?

Not in the default analytics. /ask aggregates across the whole household. If you want per-person breakdown, you can phrase the question that way and the bot will filter accordingly.

Can different households use different categories?

Categories are global (food, rent, transport, etc.) but each household can teach the bot custom merchant→category mappings — these stay scoped to your household.

Does each household member need their own Telegram account?

Yes — Hisaab uses Telegram user IDs as identity. Two people sharing one phone need two Telegram accounts to be tracked separately.

Try Hisaab — free, no install.

Open in Telegram