EASIEST Data Quality: Mandatory Assessee Code on G.A.R.7 Challans
Current · Source: Reserve Bank of India · RBI/2007-08/225 · issued 15 Jan 2008 · ~2 min read
Quick answerRBI mandates that from Jan 22, 2008, banks must not accept Central Excise/Service Tax payments via EASIEST unless the G.A.R.7 challan bears a valid 15-digit assessee code. Banks must verify codes via NSDL website or registration certificates, and digitize location codes accordingly.
The rule, in the simplest words
Banks must check for a valid 15-digit [taxpayer identification number] on payment forms
Banks should use the NSDL website to verify [taxpayer identification numbers] if they are not in the bank's directory
Banks must enter the complete address of the taxpayer and a valid location code
If a taxpayer doesn't have a valid [taxpayer identification number], banks can use their PAN/TAN [unique registration numbers] instead
How it plays out — a real example
A bank officer in Mumbai, responsible for handling EASIEST payments, must verify the 15-digit assessee code on a G.A.R.7 challan before accepting a Central Excise payment from a taxpayer. If the code is missing or invalid, the officer must ask the taxpayer to provide proof of their PAN/TAN registration and then digitize the code accordingly. This ensures that the payment is processed correctly and avoids any potential data quality issues.
What changed
RBI has made it mandatory for taxpayers to quote the assessee code and location code on G.A.R.7 challans. Banks are now required to reject any challan without a valid assessee code. Additionally, from January 22, 2008, NSDL will only accept RT 51 and RT 58 records with structurally valid assessee codes for challans with cheque tender dates after that date.
What it means for you
Banks must tighten their front-end verification processes for EASIEST payments to avoid rejection of records. Non-compliance could lead to operational disruptions and data quality issues. Banks need to train staff on the four scenarios for handling assessee codes and ensure proper digitization of location codes and addresses.
What you must do
Train branch staff to reject G.A.R.7 challans without a valid 15-digit assessee code.
Implement verification procedures using the NSDL-EASIEST website for assessee codes not in the directory.
Ensure digitization of location codes as per the directory or NSDL website, and capture complete assessee addresses.
Update systems to handle cases where assessees lack a valid code, using PAN/TAN-based codes as specified.
Prepare for the January 22, 2008 deadline when NSDL will reject records without structurally valid assessee codes.
Who it affects
All agency banks participating in EASIEST, Bank branches accepting Central Excise and Service Tax payments, Taxpayers making payments under EASIEST
Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).
What happens if a taxpayer does not have an assessee code?
The bank should ask for proof of PAN/TAN registration and a location code. For Central Excise, digitize PAN + 'XM' + 'ZZZ'; for Service Tax, digitize PAN/TAN + 'ST' + 'ZZZ'. If no location code, use the Commissionerate code associated with the branch plus 'ZZZZ'.
How should banks verify an assessee code not in the directory?
Check the NSDL-EASIEST website (www.cbec.nsdl.com) using the search feature. If found, accept the challan and digitize the assessee code and location code as displayed on the website.
What is the deadline for implementing these changes?
From January 22, 2008, NSDL will only accept RT 51 and RT 58 records with structurally valid assessee codes for challans with cheque tender dates after that date. Banks must comply immediately.
📜 This document’s life story (1 recorded event, each backed by RBI’s own words)
RBI’s words: “point 4 of paragraph 2 of our circular under reference stands modified to the extent explained above”
📜 Read the original circular — full text as issued by RBI
i) In cases where the tax-payer wants to make a payment but does not have a valid assessee code, the bank should ask the tax-payer to produce proof of its PAN / TAN registration. It is also mandatory for the tax-payer to mention the location code.
ii) After verification of the PAN/TAN, the bank should accept the challan and digitize the same as under :
Assessee code to be digitized in case of Central Excise (major account head 0038) as :
1-10 digits : 10-digit PAN
11-12 digits : XM
13-15 digits : ZZZ
Assessee code to be digitized in case of Service Tax (major account head 0044) as :
1-10 digits : 10-digit PAN / TAN
11-12 digits : ST
13-15 digits : ZZZ
iii) In case the assessee is unable to provide a valid location code, the location code may be digitized as :
1-2 digits : any Commissionerate Code associated to the bank branch
3-6 digits : ZZZZ
Location code can also be obtained by clicking on 'Know Your Location Code' in the website http://exciseandservicetax.nic.in
iv) It will be mandatory to digitize the complete address of the assessee (as per validations in the file format).
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2007-08/225 · issued 15 Jan 2008. The plain-English explanation above is BankPulse’s own independent summary.
Train branch staff to reject G.A.R.7 challans without a valid 15-digit assessee code.
💻 IT / Systems
Update systems to handle cases where assessees lack a valid code, using PAN/TAN-based codes as specified.
📜 Compliance
Implement verification procedures using the NSDL-EASIEST website for assessee codes not in the directory.
Ensure digitization of location codes as per the directory or NSDL website, and capture complete assessee addresses.
Prepare for the January 22, 2008 deadline when NSDL will reject records without structurally valid assessee codes.
Grouped from the action items above — a single circular may involve more than one team.
Worked example & action-note template
Example: if you are a Branch Manager at a bank this circular applies to (All agency banks participating in EASIEST, Bank branches accepting Central Excise and Service Tax payments, Taxpayers making payments under EASIEST), your first concrete step on “EASIEST Data Quality: Mandatory Assessee Code on G.A.R.7 Challans” is: “Train branch staff to reject G.A.R.7 challans without a valid 15-digit assessee code.” (RBI issued this 15 Jan 2008).
Circular: RBI/2007-08/225 -- EASIEST Data Quality: Mandatory Assessee Code on G.A.R.7 Challans
Issued: 15 Jan 2008
Action required: Train branch staff to reject G.A.R.7 challans without a valid 15-digit assessee code.
Action required: Implement verification procedures using the NSDL-EASIEST website for assessee codes not in the directory.
Action required: Ensure digitization of location codes as per the directory or NSDL website, and capture complete assessee addresses.
Action required: Update systems to handle cases where assessees lack a valid code, using PAN/TAN-based codes as specified.
Action required: Prepare for the January 22, 2008 deadline when NSDL will reject records without structurally valid assessee codes.
Owner: ____________ Target date: ____________
Board/committee approval needed? Y / N
Evidence filed in compliance register on: ____________
Built only from this circular’s own published fields — not legal advice; always confirm against the official RBI source.
💬 Banker Discussion
Discuss this circular with fellow bankers — reply, upvote what helps, report what doesn’t belong. Be professional; no client data. Views are the commenter’s own, not BankPulse’s.
BankPulse Compliance Evidence Pack — generated 05 Aug 2026 · status cross-checked against RBI’s official withdrawal register (refreshed weekly). Official RBI source: https://www.rbi.org.in/Scripts/NotificationUser.aspx?Id=4014&Mode=0 — Plain-English summary by BankPulse (bankpulse.ai), reviewed by our expert reviewer, CA Amit Jain. Independent platform, not affiliated with the Reserve Bank of India; is our own plain-English paraphrase, not RBI’s original wording.
Help us keep this accurate
Found an inaccuracy or have an improvement? Tell us. Every report is reviewed by our team before any change is made — nothing goes live unverified.
Public beta — plain-English informational summaries. Always verify against the official RBI source (circular number cited on every page) before making compliance, credit, treasury, audit, or operational decisions. · Join our WhatsApp channel ↗
BANKPULSE · FREE DAILY BRIEF
Get RBI updates for your role
Every important RBI update, decoded in plain English — for your career, exams & financial awareness.
We collect only your email, name and role, used solely to send your brief — never sold or shared. Withdraw anytime via the unsubscribe link in any email. Independent platform, not affiliated with the RBI. Information, not legal advice.
REPORT AN ERROR · BETA
Spotted an error? Earn 500 BankPulse Credits
Help us stay accurate. If your correction is verified true and approved by our founder, you earn 500 BankPulse Credits — redeemable when the platform monetises.
Reviewed by a human before any credit is awarded. We never change the site from crowd input without verification.
WANT A NEW FEATURE · BETA
What would make BankPulse more useful for you?
Tell us what to build next — a tool, a data view, a role page, anything. We read every suggestion.
Thank you — your ideas directly shape what we build.