A waitlisted train ticket is money that has left your account for a journey you may not make. Log it as a pending booking with the amount paid, the expected outcome if it does not confirm, and a note of any backup you plan. When the status settles, update the record so the final cost of the journey is clear, whichever way it ended.
How do I log a ticket whose fate is unknown?
Create one entry for the payment on the day you pay, and give it a status such as Waitlisted. Add the date of travel, the amount, the booking reference and what you expect to happen. A short set of status words keeps things simple: Waitlisted, Confirmed, Auto-cancelled, Refund pending, Refunded.
What happens to the money if the ticket never confirms?
Railway rules on what happens to unconfirmed tickets, and what is deducted from the refund, are set by the railways and can change, so read the terms shown at booking and in your ticket details. For your record, write down the refund amount shown to you and the date by which you expect it, and treat the difference from the amount paid as the likely cost of the attempt.
Say the ticket was ₹1,150 and the platform shows a refund of ₹1,090 if it auto-cancels. The expected cost of the attempt is 1,150 minus 1,090, which is ₹60.
Do I need a backup plan line?
Yes, if you must travel on that date. A backup plan is a cost you may or may not incur, so keep it as a separate planned line rather than as spending. Suppose a bus seat on the same route is ₹1,400. Write it down as a possible cost, and decide in advance when you will book it: for example, two days before departure if the status is still waitlisted.
What if I book a second, confirmed ticket?
Then you hold two tickets for one journey. Say the second ticket is ₹1,650. Record it as the journey's real ticket, and link the waitlisted one to it, so the two are read together. If the waitlisted ticket then auto-cancels, the full picture is this.
| Item | Amount in ₹ |
|---|---|
| Waitlisted ticket paid | 1,150 |
| Refund received on auto-cancel | 1,090 |
| Confirmed ticket paid | 1,650 |
| Net cost of the journey | 1,710 |
Net cost is 1,150 minus 1,090, plus 1,650, which is 1,710. Of that, ₹60 is the price of having tried. If the waitlisted ticket confirms instead, you may cancel the second one yourself, and then the same arithmetic applies in reverse: you pay the deduction on the cancelled ticket.
A short status guide
- Waitlisted: money paid, outcome unknown. Expected refund shown.
- Confirmed: this is the real journey cost. Remove any backup line.
- Auto-cancelled: refund pending. Set a follow-up date.
- Refund pending: write the date you expect it.
- Refunded: match the credit to the payment, note the net cost, and close.
One practical habit: set a reminder for the day before departure, which is when most people learn the final position. Update the entry that same evening, so your record never shows a status that is already out of date.
Where RAC fits
A reservation against cancellation ticket sits between waitlisted and confirmed: you may get a seat to share. Treat it like a waitlisted ticket in your log, because the final status can still change.
Using SpendixAI for this
If you pay by UPI or card, import the statement and review the rows, and add the expected refund and status in your own notes. Keep the backup line outside your actual spending until you book it.
Checklist before the chart is prepared
- Log the payment and the status today.
- Write the expected refund and the likely deduction.
- Decide the date on which you will book a backup.
- If you book a second ticket, link the two.
- Update the status the moment it changes.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

