A two-level category tree gives each broad theme a parent, such as Food, and each habit a child, such as Groceries and Eating out. Couples find it useful because the argument about food spending usually hides two very different habits. Keep the tree shallow, name children by behaviour rather than shop, and test it on one month of real transactions before adding more.
Why one Food category hides the story
Say your Food total is ₹22,000 for the month. That number could mean a stocked kitchen or a heavy delivery habit, and the two call for different conversations. Splitting Food into Groceries, Eating out and Delivery shows which part moved.
A sample tree to start from
| Parent | Children | What goes in |
|---|---|---|
| Food | Groceries | Kirana, vegetables, milk, supermarket |
| Food | Eating out | Restaurants, cafes, street food |
| Food | Delivery | Food delivery apps |
| Home | Rent and maintenance | Rent, society dues, repairs |
| Home | Help | Maid, cook, driver |
| Fun | Outings | Movies, trips, events |
A worked example with made-up numbers
Say a couple spends ₹22,000 on food in a month. With the split, the figures read: Groceries ₹11,500, Eating out ₹6,000 and Delivery ₹4,500. The three add up to 11,500 + 6,000 + 4,500 = ₹22,000.
Now compare with the target the two of you set. If you agreed ₹8,000 a month for eating out and delivery together, the combined actual is 6,000 + 4,500 = ₹10,500, which is ₹2,500 above target, while Groceries on its own is within the range you expected. The conversation becomes about two lines rather than a vague sense that food is expensive.
How many levels do I really need?
Two is enough for a household. A third level asks you to decide more on every row and the numbers get too thin to read. Aim for about eight to twelve parents and no more than a handful of children under each.
- Name children by what you do, not where you shop.
- Keep a catch-all child such as Other under each parent for odd items.
- Give each parent a colour so charts are easy to scan.
- Merge children that never go over a few hundred rupees.
Setting it up in SpendixAI
SpendixAI supports custom categories and sub-categories with colours, so Food can hold Groceries, Eating out and Delivery, each with its own colour. Create the parents first, add the children, then import a statement and let your rules and history place the rows. Review what is left and correct it. Each correction becomes history for later months.
Common mistakes with category trees
- Too many children: twenty small categories mean each row needs a decision and the totals are noisy.
- Shop-based names: a child called Big Bazaar mixes groceries, clothes and household items.
- Duplicate homes: if Milk can sit in Groceries or Daily needs, rows will scatter.
- No review: a tree that is never revisited fills with unused children.
Couples with separate accounts have one more choice: share one tree and let each person import their own statements, with the account kept on each transaction. That way the categories match and the totals can be compared fairly. Agree the tree once, write it down, and revisit it every quarter.
Reviewing the tree after a month
- Open the totals by child category for the month.
- Look for a child that is much larger than the others and see whether it should be split.
- Look for children with only one or two rows and merge them.
- Move any rows that landed in the wrong child and add a rule for the payee.
- Share the totals with your partner and set the next month's targets.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


