Put cook salary under a household help or domestic staff sub-category inside your Home category, not under Food. The money pays for a person's time, so it behaves like a monthly service bill rather than like groceries. For most homes it is a fixed, recurring, personal expense, unless the cook works for a business you run.
Why household help and not Food?
If the salary sits inside Food, your food total jumps by the cook's pay and you can no longer tell whether the kitchen got more expensive or the vegetable bill went up. Groceries move with prices, guests and festivals. A cook's pay moves only when you agree a revision. Mixing the two hides both patterns, so keep one line for the person and a separate line for the ingredients they cook with.
There is a second reason. If you ever want to compare what your household spends on food with another month or another year, you want the figure to reflect shopping and cooking choices, not a hiring decision. A change of cook then shows up in one place, and your food numbers stay comparable.
Is cook salary a need or a want?
It depends on the household, and both answers are fair. Where both adults work long hours, or an elderly parent cannot stand at the stove, it is a need in the plainest sense. Where someone is at home all day and the cook is a convenience, many people would call it a want. What matters is that you choose once and apply the same label every month, so your need-versus-want totals mean the same thing a year from now.
A simple test: if the cook left tomorrow, would you look for a replacement within a week or two? If yes, tag it as a need.
Three ways to set up the sub-categories
- One line only: Household help, then Cook. Fine if the cook is your only domestic staff and you want the least setup.
- A staff split: Household help with Cook, Maid and Driver underneath, so each person's pay is visible on its own.
- A pay-type split: Cook salary and Cook bonus and gifts as two lines, so a Diwali bonus does not make one month look like a pay rise.
Fixed or variable, personal or business?
| Situation | How to file it | Why |
|---|---|---|
| Same amount every month | Fixed and recurring | Any change stands out straight away |
| Pay depends on meals cooked or days attended | Variable, same sub-category | Note the days in the description so the total can be explained |
| Festival bonus or a gift | One-off, its own sub-category | Keeps the base pay clean |
| Cook prepares food for your home-based tiffin or catering work | Business side, separate from personal | Stops household and business money mixing; ask your CA how to treat it |
What if you pay in cash, by UPI or by card?
A UPI payment is the easiest case: it appears on your statement as a transfer to a person's name, which looks like any personal transfer, so it needs a rule or a manual tag. In SpendixAI you can set your own rule so that transfers to that name go to Household help, then Cook, and later months follow it. Cash never reaches a statement, so add it by hand on the day you pay, in the same sub-category. Card payment for a cook is rare, but treat it the same way.
A worked example for a financial year
Say the cook is paid ₹6,000 a month on the 1st by UPI, plus ₹3,000 in cash at Diwali. Over April to March that is 12 x ₹6,000 = ₹72,000 in salary and ₹3,000 in bonus, so ₹75,000 in all, or ₹6,250 a month on average.
If you had filed the bonus under the same line, the Diwali month would show ₹9,000 against a usual ₹6,000, a jump of ₹3,000, or half again. The pay did not rise; the month just carried a gift. A separate bonus line avoids that false alarm.
Setting it up in ten minutes
- Create or pick Household help under your Home category.
- Add two sub-categories: Cook salary and Cook bonus and gifts.
- Tag the salary as a need or a want, once, and keep that choice.
- Add a rule or reminder for payday so the UPI transfer is filed without effort.
- At year-end, total the line and compare it with the agreed monthly figure.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


