OLTAS Data Entry Errors: RBI Seeks Compliance Confirmation
Current & verified — this is the latest version
Source: Reserve Bank of India · RBI/2005-06/86 · issued 30 Jul 2005 · ~2 min read
Quick answerRBI flags persistent data entry errors in Assessment Year and Minor Head fields under OLTAS. Banks must confirm implementation of maker-checker system and software validations by August 10, 2005, or face presumption of non-compliance.
The rule, in the simplest words
Make sure every branch has a maker‑checker system (one person enters data, another checks it) for OLTAS data entry.
Use software checks that automatically flag wrong values in the Assessment Year and Minor Head fields before the data is uploaded.
Tell RBI by fax that your bank has these systems in place; the fax number is 022‑2300370.
If you do not send a fax by August 10, 2005, RBI will assume you are not following the rules and may take action.
How it plays out — a real example
Riya, a branch manager in Mumbai, double‑checks the Assessment Year and Minor Head entries with her colleague before the data goes live. She then sends a quick fax to RBI confirming that the maker‑checker system and software validations are active, all while keeping her team motivated and on track.
What changed
RBI issued a fresh reminder to all agency banks about ongoing data entry errors in OLTAS reporting, specifically in Assessment Year and Minor Head fields. It referenced earlier circulars from 2004 that detailed software validation requirements and the maker-checker system. Banks were given a strict deadline of August 10, 2005, to confirm compliance or be deemed non-compliant.
What it means for you
Banks must urgently verify that their branches have fully implemented the maker-checker process and software validations for OLTAS data uploads. Failure to respond by the deadline will be taken as non-compliance, potentially leading to regulatory action. This impacts data quality for the Tax Information Network and government reporting.
What you must do
Confirm with your IT and operations teams that maker-checker system is active at all branches for OLTAS data entry.
Ensure software validations for Assessment Year and Minor Head fields are in place as per RBI circulars from 2004.
Send a compliance confirmation fax to RBI at 022-2300370 before August 10, 2005.
Review branch-level data entry logs to identify and correct any recurring errors in these two fields.
Who it affects
All agency banks including Jammu and Kashmir Bank Ltd., Branch-level staff handling OLTAS data entry, Bank IT and compliance teams
❓ Common questions
What specific data fields are causing errors in OLTAS?
The Directorate of Income Tax reported persistent errors in the Assessment Year and Minor Head fields during data upload to the Tax Information Network.
What is the deadline for banks to respond to this circular?
Banks must fax their compliance confirmation to RBI by August 10, 2005. No response will be treated as non-compliance with earlier instructions.
What earlier instructions are being referenced?
RBI circulars from July 28, September 4, and December 27, 2004, which mandated software validations, and a November 19, 2004 letter requiring the maker-checker system for data accuracy.
📜 Read the original circular — full text as issued by RBI
RBI/2005-06/86
DGBA. GAD. No. H-412 /42.01.034/ 2005-06
July 30, 2005
The Chairman/Chairman and Managing Director All Agency Banks including
Jammu and Kashmir Bank Ltd.
Dear Sir,
Data Entry Errors – OLTAS
It has been reported by Directorate of Income Tax (systems) that there are still a large number of data entry errors in respect of the following two fields, while reporting data under On Line Tax Accounting System (OLTAS):
i. Assessment year
ii. Minor Head
2. In this connection, your attention is invited to our various circulars/ letters viz. RBI/2004/75,164,and 314 dated July 28, September 4 and December 27, 2004 respectively wherein instructions on software validations were issued in detail to avoid mistakes in uploading the data of ‘assessment year’ and ‘minor head’ etc. to Tax Information Network. We also specifically draw your attention to para 4 of our letter DGBA. GAD. No. H 1872 -1903 dated November 19, 2004 regarding data quality and branch coverage in terms of which you were advised to follow ‘maker-checker system’ to ensure the accuracy of data before it is uploaded to TIN.
3. You are requested to let us know whether ‘maker-checker system’ and software validations as required are implemented at your branches to eliminate data entry errors to enable us to send a report in this regard to Government of India.
4. We shall be glad if you please advise this position immediately by fax (022-2300370) . In case no reply is received from your bank by August 10, 2005, it would be presumed that your bank has not yet complied with our instructions in this regard.
Yours faithfully,
(M.T.Varghese)
General Manager
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2005-06/86 · issued 30 Jul 2005. The plain-English explanation above is BankPulse’s own independent summary.
Confirm with your IT and operations teams that maker-checker system is active at all branches for OLTAS data entry.
Review branch-level data entry logs to identify and correct any recurring errors in these two fields.
💻 IT / Systems
Ensure software validations for Assessment Year and Minor Head fields are in place as per RBI circulars from 2004.
📜 Compliance
Send a compliance confirmation fax to RBI at 022-2300370 before August 10, 2005.
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 including Jammu and Kashmir Bank Ltd., Branch-level staff handling OLTAS data entry, Bank IT and compliance teams), your first concrete step on “OLTAS Data Entry Errors: RBI Seeks Compliance Confirmation” is: “Confirm with your IT and operations teams that maker-checker system is active at all branches for OLTAS data entry.” (RBI issued this 30 Jul 2005).
Action required: Confirm with your IT and operations teams that maker-checker system is active at all branches for OLTAS data entry.
Action required: Ensure software validations for Assessment Year and Minor Head fields are in place as per RBI circulars from 2004.
Action required: Send a compliance confirmation fax to RBI at 022-2300370 before August 10, 2005.
Action required: Review branch-level data entry logs to identify and correct any recurring errors in these two fields.
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=2407&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.