Train tickets go under Transport if they are a regular commute, and under Travel if they are a trip. Home visits and work journeys are usually needs, while a holiday ticket is a want. The date you pay is the date to record, even if you travel weeks later.
Is a train ticket a commute or a trip?
This is the first judgement, because it changes the budget the money belongs to. A suburban season ticket or a daily ticket to the office behaves like a fixed commute cost. A ticket for a journey of several hundred kilometres is irregular, planned in advance and usually tied to an occasion. Do not mix them in one category, or the steady commute cost gets buried under occasional big tickets.
Need or want?
- Need: the daily commute, a ticket to a job interview, travelling home for a family event you cannot miss.
- In between: the annual home trip at a festival. Many families treat it as a fixed yearly cost, so it belongs in a planned bucket, not in emergencies.
- Want: a leisure trip with friends or a sightseeing journey.
Nobody else can fix this line for you. A student who goes home every term and an employee who flies for work will not file the same ticket the same way, and that is fine as long as you are consistent.
Which sub-categories work?
| Sub-category | What goes in it | Why it helps |
|---|---|---|
| Transport > Commute | Season tickets and daily suburban fares | Shows the steady cost of going to work |
| Travel > Train journeys | Long-distance tickets for family or leisure | Lets you compare one festival trip against another |
| Work travel | Tickets you expect your employer to repay | Makes it easy to list claims later |
Keep the third one even if you rarely use it. It stops reimbursable tickets from polluting your personal travel figures.
When do you record it, at booking or at travel?
Record it when the money leaves your account. If you book a Diwali ticket in September, the expense lands in September. To avoid forgetting what the ticket was for, add a short note, such as the destination and travel month. When you review the year, you can group those notes into trips.
What about cancellations and refunds?
Record the refund as its own entry in the same category when it arrives, so that the net cost of the journey is visible. Say you book two tickets at ₹1,450 each, which is ₹2,900 in September, and then cancel one. After cancellation charges, suppose ₹1,100 comes back to you in October. The ticket you used cost ₹1,450 and the cancelled one cost you ₹350 (₹1,450 minus ₹1,100). Net spend is ₹2,900 − ₹1,100 = ₹1,800. These numbers are made up. Real charges depend on the booking rules, so read them on your ticket.
What if you paid by UPI, card or cash?
Online bookings paid by UPI or card appear in your statement, usually under a booking platform's name that will not say train. Upload that statement to SpendixAI and review the rows before saving. A rule for that merchant name is worth setting so that later bookings fall under Travel. Counter tickets paid in cash leave no trace, so enter them yourself, in a batch if you have several.
What about tickets you buy for other people?
If you book for a parent or a friend, decide in advance whether it is a gift, a loan or a shared cost. A gift stays in your travel line. A loan should not be an expense at all, and when they repay you, it is a repayment, not income. Write a short note on the entry so that you remember which it was.
Quick checklist
- Decide commute versus trip, then stick with it.
- Record the ticket when you pay.
- Add the destination or travel month as a note.
- Log refunds in the same category.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


