TDR Codes Matrix: Selecting the precise technical code for unique cancellation scenarios.

Selecting the correct Ticket Deposit Receipt (TDR) reason code is the most critical step in claiming an IRCTC refund after chart preparation. The backend routes your claim directly to the Chief Commercial Manager (Refunds) of the respective railway zone. Picking a generic or incorrect code (like "Passenger not travelled" instead of "Train Diverted") will almost certainly trigger an automatic rejection.

TDR Matrix: Railway Service Failures

When the disruption is caused by Indian Railways, refunds are typically 100% of the base fare, provided the strict filing timeline is met. 

TDR Reason / Scenario	Filing Deadline	Supporting Action Needed
Train Late > 3 Hours (passenger opts not to travel)	Before actual departure of the train at the boarding station	None
Train Diverted - Not Touching Boarding/Destination	Within 72 hours of scheduled departure	None
Train Terminated Short of Destination	Within 72 hours of scheduled arrival time	Original GC/EFT receipt sent by post
AC Failure (in an AC Coach)	Within 20 hours of actual arrival at destination	Original TTE Certificate sent by post
Downgraded Class (e.g., proper coach not attached)	Within 2 days of certificate issuance	Original TTE Certificate sent by post

(Note: If a train is fully cancelled by IRCTC, e-tickets are automatically refunded to the source account; filing a TDR is not required).

TDR Matrix: Partial Travel & Waitlist Exceptions

When dealing with RAC, waitlisted, or partially confirmed group PNRs, the system's timing rules are unforgiving.

TDR Reason / Scenario	Filing Deadline	Supporting Action Needed
Party Partially Confirmed/Waitlisted (Waitlisted passengers did not travel)	Up to 72 hours of actual arrival	Original TTE Certificate sent by post
Party Partially Confirmed/Waitlisted (ALL passengers did not travel)	30 minutes before scheduled departure	None (File online)
Passenger Not Travelled (Due to RAC status post-charting)	30 minutes before scheduled departure	None (File online)
Party Partially Travelled (e.g., 2 boarded, 2 did not)	Up to 72 hours of actual arrival	Original TTE Certificate sent by post

  

Critical Rules for TDR Verification

• The Guard Certificate (GC/EFT): For any claim involving partial travel, AC failure, excess fare, or class downgrades, filing the online TDR is only step one. You must legally obtain a physical certificate from the Travelling Ticket Examiner (TTE) on the train and mail the original copy to IRCTC. 

• Tatkal Restrictions: Confirmed Tatkal tickets are non-refundable. TDRs filed for them will automatically be rejected unless a massive service failure occurred (e.g., train is late by more than 3 hours or diverted). 

• The 60-Day Lock: Once a TDR is submitted in the IRCTC backend, the PNR is locked. You cannot edit the reason code, and the manual review process by the specific railway zone usually takes 60 days or more to process the refund.

 

The TDR matrix includes highly specialized reason codes for complex edge cases. If your scenario falls into one of these categories, selecting a generic code will cause the manual reviewer to reject the claim, as they rely on the exact backend code to trigger the correct departmental verification.

 Here are the remaining advanced TDR codes and the unique rules governing them:

1. The "Linked Journey" Failures

If you are traveling on multiple trains to reach a destination, Indian Railways has a specific protocol for missed connections, provided you officially linked the PNRs during booking.

• Code: Missed connecting train due to late running of main train. 

• The Constraint: This TDR can only be filed if the arrival of the first train is delayed, causing you to miss the second train. You must retain the original ticket of the first leg and file the TDR for the second leg at the junction station (or online for e-tickets) within 3 hours of the actual arrival of the first train. If your PNRs were not linked in the IRCTC system prior to the journey, this code automatically rejects. 

2. Physical Coach Discrepancies

Sometimes the train arrives, but the physical makeup of the train is fundamentally flawed.

• Code: Proper coach not attached and passenger has to cancel journey.

• Usage: You booked a 3AC ticket, but the railway forgot to attach the B4 coach entirely, and no alternate accommodation was provided. 

• Timing: Must be filed within 3 hours of the train's actual departure. 

• Code: Passenger travelled in lower class.

• Usage: You booked 2AC, but the TTE could only find you a seat in Sleeper class. 

• Constraint: You must travel, but you are entitled to the difference in fare. You must get this endorsed by the TTE on the train (a physical certificate) and file the TDR within 2 days.

 3. The VIKALP Rejection Code

As discussed in the VIKALP internals, if the algorithm shifts you to an alternate train but you choose not to take it:

• Code: Passenger shifted to alternate train via VIKALP but did not travel. 

• Constraint: Because the system treats you as a confirmed passenger on the new train, you must file this TDR up to 3 hours before the scheduled departure of the alternate train, not your original train.

 4. The "Strike / Agitation" Force Majeure Code

• Code: Train cancelled/diverted due to Bandh/Agitation/Natural Calamity. 

• The Constraint: Unlike standard IRCTC cancellations (which refund automatically), disruptions caused by public strikes or floods sometimes require manual TDR filing if the train is stopped mid-journey. The refund is calculated on a pro-rata basis (you are refunded for the untravelled distance only).

 5. The "Charting Downgrade" Code

Occasionally, a passenger books a Confirmed ticket, but during final chart preparation, the system physically lacks the space (due to a coach being detached for maintenance) and drops the passenger's status down to RAC or Waitlisted.

• Code: Change in reservation status from confirmed to waitlisted/part waitlisted/RAC after chart preparation. 

• The Constraint: This is a tricky scenario. Even though the railway made the error, the standard RAC/Waitlist timeline immediately applies. You must file the online TDR at least 30 minutes before the scheduled departure of the train. If you wait until after the train departs, assuming you deserve a refund for the railway's mistake, the system will reject the claim.

 5. The "No Room Provided" Code

This happens when you have a Confirmed or RAC ticket, you board the train, but someone else is legally occupying your berth (e.g., duplicate seat allotment error by the charting system), and the TTE cannot find you alternative accommodation.

• Code: After charting no room provided. 

• The Constraint: You must get off the train and file this TDR within 3 hours of the actual departure of the train from your boarding station. 

6. TTE Disputes and Double Charges

If you have a valid e-ticket but get into a dispute with the Travelling Ticket Examiner (TTE) who forces you to pay a penalty or buy a new ticket (e.g., they mistakenly claim your ID is invalid, or their Handheld Terminal is glitching).

• Code: Wrongly charged by TTE. 

• Code: Travelled without proper ID proof. (Used when you paid the penalty on-board but later found your ID and want to appeal) 

• The Constraint: For both of these, the online TDR is just a placeholder. You must physically mail the Excess Fare Ticket (EFT) receipt that the TTE handed you to the Chief Commercial Manager of Refunds. These specific codes trigger a discretionary manual review, where a human officer investigates the TTE's logbook.

 The "Other" Text Box Trap

When filing a TDR online, there is an option at the very bottom of the dropdown list titled "Other." Selecting this opens a free-text box for you to type your reason.

• The Trap: Railway refund officers process thousands of claims daily using automated sorting based on the standard codes. Claims filed under "Other" bypass this sorting and are placed at the very bottom of the manual review queue. Only use "Other" if your situation is so bizarre that absolutely none of the standard matrix codes apply. 

The Final Post-Filing Rule

If your TDR requires mailing a physical certificate (like a Guard Certificate or EFT), you have 15 days from the date you filed the online TDR to ensure the envelope reaches the IRCTC office in New Delhi. If the physical proof does not arrive within this window, the online claim will be dismissed regardless of the reason code selected. It is always recommended to use Speed Post or Registered Post so you have a tracking number to prove delivery.

 The Station Master Override Protocol

Most partial-travel or on-board failure codes require the original Travelling Ticket Examiner (TTE) to issue a Guard Certificate (GC) or Excess Fare Ticket (EFT). 

The Edge Case: If you cannot find the TTE, or the TTE refuses to issue the certificate during the chaos of a downgraded coach or AC failure, you have a backup option. You must approach the Station Master or the Ticket Checking Staff at the destination station immediately upon arrival. They have the authority to verify the train's logs (e.g., confirming the AC in coach B2 was indeed broken) and stamp your printout or issue a physical endorsement. This endorsement is legally identical to a TTE certificate when mailed to IRCTC.

The "Fatal Error" TDR Traps

If you file a TDR for a Confirmed Ticket with the code Passenger Not Travelled after the chart is prepared, but you fail to do it at least 4 hours before departure, the backend system accepts the submission but automatically flags it for a 100% deduction. The TDR will sit in "Pending" status for 60 days only to be rejected, because the timeline rule explicitly voids the refund.

 

To definitively close out the topic, you only need to understand the administrative lifecycle of a TDR once it leaves your hands, and the final "Red Flags" that cause automatic rejections.

1. The TDR Lifecycle (What Happens in the Backend)

When you submit the correct TDR code, it does not go to a generic IRCTC customer service desk. It enters a bureaucratic pipeline. You can track this in your IRCTC account, where your claim will move through these specific statuses:

• TDR Filed: Your claim has been registered in the IRCTC database. 

• Forwarded to Zonal Railway: IRCTC has transferred your file to the Chief Commercial Manager (CCM-Refunds) of the specific railway zone that operated your train (e.g., Western Railway, Northern Railway). IRCTC has no authority to approve the refund from this point forward; they merely act as the messenger. 

• Registered with Zonal Railway: The zone has received the digital file (and your physical TTE certificate, if applicable) and assigned it to an investigating officer. 

• Approved / Repudiated: "Repudiated" is the railway's term for "Rejected." If approved, the zone releases the funds back to IRCTC, who then credits your bank account. This entire lifecycle legally takes up to 60 days, but can stretch to 90 days for complex TTE disputes.

 2. The "Auto-Refund" Fatal Trap

There is one massive trap that passengers frequently fall into regarding cancelled trains.

• The Rule: If Indian Railways completely cancels a train due to operational reasons, floods, or accidents, do not file a TDR for an e-ticket. The CRIS backend is programmed to automatically sweep the system and issue a 100% refund to the source account for all e-tickets on a cancelled train. 

• The Trap: If you panic and manually file a TDR for a cancelled train using the code Train Cancelled, you actually disrupt the automated sweep. Your ticket is pulled out of the auto-refund queue and dumped into the manual TDR review queue, delaying your money by 60 days for no reason. 

3. The Tatkal "Passenger Not Travelled" Reality

While we touched on Tatkal tickets, this specific scenario deserves a final warning.

• Many passengers book a Confirmed Tatkal ticket, miss the train, and immediately file a TDR using the code Passenger Not Travelled. 

• The Backend Logic: The system will allow you to submit this TDR without an error message, giving you false hope. However, the backend is hard-coded to reject this. Under extant railway rules, no refund is granted on confirmed Tatkal tickets under any circumstances unless the railway itself fails to run the train on time (e.g., delayed by 3+ hours).

When your TDR claim requires physical proof of a service failure—such as a downgraded class, AC failure, or partial travel—filing online is only the first step. You must mail the original physical certificate (Guard Certificate or Excess Fare Ticket) obtained from the Travelling Ticket Examiner (TTE) or Station Master.

1. The Exact Mailing Address

Send your documents to the main IRCTC internet ticketing hub: 

        Group General Manager/IT
        Indian Railway Catering and Tourism Corporation Ltd.
        Internet Ticketing Centre, IRCA Building
        State Entry Road
        New Delhi – 110055

2. The Step-by-Step Mailing Process

1.File the Online TDR First:

Before mailing anything, log into your IRCTC account and file the TDR online. Note down the TDR Reference Number that the system generates. You must adhere to the strict filing timelines (e.g., within 20 hours for AC failure, or within 72 hours for partial travel).

2.Prepare a Cover Letter:

Write a brief application letter. You must include your Full Name, PNR Number, TDR Reference Number, Date of Journey, Train Number, and a short, one-sentence description of the reason for the claim.

3.Attach the Original Certificate:

Staple the original Guard Certificate (GC) or Excess Fare Ticket (EFT) to your cover letter. Do not send a photocopy—IRCTC will instantly reject it. (Pro-tip: Take a clear photo of the certificate with your smartphone for your own records before mailing it).

4.Use Trackable Mail:

Always send the envelope via Speed Post or Registered Post through India Post. You must have a tracking number to prove that the envelope reached the IRCTC office within the required timeframe.

Once IRCTC receives your original certificate, they will physically attach it to your digital TDR file and forward it to the Chief Commercial Manager of the specific railway zone that operated your train. From there, the manual review process usually takes 60 to 90 days before the refund is credited back to your original payment method.

_____