OLTAS Data Quality: PAN & CIN Accuracy (2007 Circular)
Current · Source: Reserve Bank of India · RBI/2007-08/206 · issued 06 Dec 2007 · ~1 min read
Quick answerRBI warns agency banks that errors in PAN or CIN uploaded to OLTAS deny taxpayers credit. Banks must verify PAN via TIN-NSDL, insist on PAN proof, and ensure CIN matches customer records. Single errors cause grievances and reputational risk.
The rule, in the simplest words
When a bank puts tax payment info into OLTAS, the PAN (tax ID) must be correct or the taxpayer won't get credit.
The CIN (payment receipt number) given to the customer must match exactly what the bank uploads.
Banks must check PANs using the TIN-NSDL website before uploading.
Even one wrong PAN or CIN can cause a taxpayer problem and hurt the bank's reputation.
Branch staff need to be trained to be very careful with these numbers.
How it plays out — a real example
Rajesh, a branch manager at an agency bank, receives a corporate tax payment. Before uploading the challan to OLTAS, he uses the TIN-NSDL site to verify the PAN, checks the CIN against the customer's receipt, and confirms the date of tender. This prevents a tax credit failure.
What changed
RBI issued this circular in 2007 to address ongoing errors in PAN and CIN uploads. It is not a new directive but the original instruction.
What it means for you
Banks must ensure accurate PAN and CIN uploads to avoid taxpayer credit failures and reputational risk, as per longstanding RBI guidance.
What you must do
Use bulk PAN verification facility from TIN-NSDL site before uploading challan data.
Insist on proof of PAN from taxpayers where needed.
Ensure the CIN given to the customer is exactly the one uploaded to OLTAS.
Double-check the 'date of tender' field for accuracy.
Sensitize branch staff on the importance of data quality and associated risks.
Who it affects
All agency banks including Jammu and Kashmir Bank Ltd., Branch staff handling OLTAS challan uploads, Taxpayers relying on correct tax credit
❓ Common questions
Is this a new requirement?
No, this is the original 2007 circular from RBI. It is not a new directive.
📜 Read the original circular — full text as issued by RBI
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2007-08/206 · issued 06 Dec 2007. The plain-English explanation above is BankPulse’s own independent summary.
Sensitize branch staff on the importance of data quality and associated risks.
📜 Compliance
Use bulk PAN verification facility from TIN-NSDL site before uploading challan data.
Insist on proof of PAN from taxpayers where needed.
Ensure the CIN given to the customer is exactly the one uploaded to OLTAS.
Double-check the 'date of tender' field for accuracy.
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 Compliance officer at a bank this circular applies to (All agency banks including Jammu and Kashmir Bank Ltd., Branch staff handling OLTAS challan uploads, Taxpayers relying on correct tax credit), your first concrete step on “OLTAS Data Quality: PAN & CIN Accuracy (2007 Circular)” is: “Use bulk PAN verification facility from TIN-NSDL site before uploading challan data.” (RBI issued this 06 Dec 2007).
Circular: RBI/2007-08/206 -- OLTAS Data Quality: PAN & CIN Accuracy (2007 Circular)
Issued: 06 Dec 2007
Action required: Use bulk PAN verification facility from TIN-NSDL site before uploading challan data.
Action required: Insist on proof of PAN from taxpayers where needed.
Action required: Ensure the CIN given to the customer is exactly the one uploaded to OLTAS.
Action required: Double-check the 'date of tender' field for accuracy.
Action required: Sensitize branch staff on the importance of data quality and associated risks.
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=3980&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.