A two-level category tree means a parent category such as Food with children such as Groceries, Eating out and Client meals, so you can see the whole food spend or each part. For a freelancer whose income arrives unevenly, that split is what tells you which spending can flex in a lean month and which cannot.
Why one Food bucket is not enough
Groceries are close to a fixed cost. Eating out is a choice. A lunch with a client may be neither: it is work. When all three sit in one bucket, a high Food total in a month with a big client project says nothing useful. Splitting them gives each its own story.
A starter tree for irregular income
| Parent | Children | Why this split |
|---|---|---|
| Food | Groceries, Eating out, Client meals | Fixed, flexible, work |
| Work costs | Software, Co-working, Travel to clients | Business running costs |
| Home | Rent, Utilities, Maintenance | Fixed monthly costs |
| Personal | Health, Subscriptions, Gifts | Everything else |
| Buffer | Tax set-aside, Slow-month fund | Money you park on purpose |
You can use colours to group parents visually, say green for Food and blue for Work costs, so a glance at a chart tells you which part of the tree you are looking at. SpendixAI supports custom categories and sub-categories with colour, plus settings such as a GST rate and an accounting code if you need them.
Build it in six steps
- List last three months' top ten merchants.
- Group them into no more than six parents.
- Under each parent, create two to five children, not more.
- Assign a colour to each parent.
- Write rules for your recurring merchants so they fall into the right child.
- Import a month and see what is left uncategorised.
A worked month with uneven income
Say a month's food spending is ₹8,400 on groceries, ₹3,900 eating out and ₹1,900 on lunches with clients. Food is ₹8,400 + ₹3,900 + ₹1,900 = ₹14,200. If income that month was ₹28,000, Food looks like 50.7 percent of it. But Client meals belong to work, so personal food is ₹12,300, which is 43.9 percent. And the part you can trim in a thin month, Eating out, is ₹3,900, or 13.9 percent of that income.
Those three percentages tell three different stories, and only the tree lets you see all of them.
How deep should it go?
Two levels is enough. A third level feels tidy for a week and then becomes work. If you want to know more about eating out, filter by merchant instead of adding a category.
- Keep children under five per parent.
- Use a name you would type when searching.
- Merge any child you have not used in three months.
Does AI help here?
Your own rules run first, then history and similar merchants, then an AI model for whatever is left, if you have AI on. You can turn it off, cap it with a monthly AI budget, or leave unmatched items for review. For a tree with six parents, we would write rules first and let corrections teach the rest.
Naming rules that keep the tree usable
- Use plural nouns for children and singular for parents only if that helps you.
- Avoid names like Misc or Other as children; they hide spending.
- Put one-off items in a Review child under the closest parent until you decide.
If you ever want to hand your category list to someone, the Export centre has a categories-and-tax-codes file, so a tidy tree pays off beyond your own reports.
Review in lean months
When income dips, read only the children: Eating out, Subscriptions and Gifts are the quickest levers, while Groceries and Rent are not. If you are unsure which of your costs have any tax or GST angle, take the category report to your CA and let them advise.
Useful ideas start with a clearer picture of your own spending.
Explore your reports
