The question: "I want Food as one total, but I also want groceries and eating out separate. Do I need subcategories, and how deep should the tree go?" Short answer: yes, use exactly two levels. A parent for the big picture, a handful of children for the questions you actually ask yourself.
Why two levels and not three?
A third level looks tidy on day one and becomes a chore by week three. Every extra level means one more decision per transaction, and tired people at 11 pm stop deciding. Two levels give you a monthly view at parent level and a "where did the food money go" view at child level, which is nearly everything anyone needs.
How do I design the tree? Steps
- Start from the questions you ask, not from the categories you can imagine. "How much on eating out?" needs a child. "How much on pencils?" does not.
- Aim for 8 to 10 parents: Housing, Food, Transport, Health, Education, Bills, Shopping, Fun, Family, Savings and debt.
- Give each parent two to four children, only where you will act on the answer.
- Keep an "Other" child under each parent as a safety net, and review it monthly.
- Decide the edge cases once: a cafe meal with a client goes where? Write the rule next to the name.
- Give each parent one colour so charts read at a glance.
What does the Food branch look like with numbers?
Hypothetical month for a two-person household.
| Parent | Child | Amount (₹) |
|---|---|---|
| Food | Groceries and vegetables | 9,600 |
| Food | Eating out | 3,400 |
| Food | Delivery apps | 2,750 |
| Food | Chai and snacks | 950 |
| Food total | All four children | 16,700 |
The parent total is 9,600 plus 3,400 plus 2,750 plus 950, which is ₹16,700. Notice what the child split shows: eating out plus delivery is ₹6,150, about 37 percent of the Food total, while groceries are the rest. Without children, you would only see ₹16,700 and nothing to act on.
Is this possible in SpendixAI?
Yes. SpendixAI supports categories and sub-categories, each with its own colour, and you can create your own set instead of using the defaults. Reports can then be read by parent or by sub-category. Change a category once and it applies to the transactions filed under it, so test with one month before you reorganise a whole year.
What should I check after setting it up?
- Does any child have fewer than three transactions a month? Merge it into a sibling.
- Is "Other" larger than your smallest real child? Something needs naming.
- Do old transactions still sit under deleted or renamed categories?
- Do the children add up to the parent in every report?
What is the honest limit?
A tree cannot settle a genuinely mixed purchase. A big shop that is half groceries and half household cleaning will land in one child unless you split the transaction. Pick the dominant one and accept a small error rather than spending ten minutes per bill.
When should a child become its own parent?
Promote a child when it grows large or gets its own decisions. If "Eating out" is a fifth of your Food total and you review it weekly, it may deserve its own parent. A good test is whether you would set a separate monthly limit for it. If yes, promote it; if no, leave it as a child.
The opposite is true for tiny children. Anything under a handful of transactions a month is noise. Merge it into its sibling and rename the sibling clearly, for instance "Groceries and household" instead of two thin categories.
A starter tree to copy and trim
- Food: Groceries, Eating out, Delivery apps, Chai and snacks.
- Transport: Fuel, Cab and auto, Metro and bus, Vehicle upkeep.
- Bills: Electricity, Mobile and internet, Subscriptions.
- Shopping: Clothes, Home items, Gadgets.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

