OLTAS: Multiple Uploads & March Residual Data Allowed
No longer current — replaced by Master Circular DGBA.GAD.No.3/42.01.034/2015-16
Source: Reserve Bank of India · RBI/2004-05/413 · issued 04 Apr 2005 · ~2 min read
Quick answerRBI now permits agency banks to upload past tax collection data (RT-01) multiple times for the same nodal scroll date, and to transmit March residual data as a separate RT-01 record alongside current FY records until April 16, 2005.
What changed
Previously, banks could submit data for a specific nodal scroll date/nodal branch/major head combination only once per day. Now, TIN accepts multiple RT-01 files for the same combination on different dates, allowing past data to be merged with current data. For April 1-16, 2005, banks must transmit two separate RT-01 records: one for March 31, 2005 residual and one for the current date, with a single RT-05 summary per major head.
What it means for you
Banks can now correct or complete past tax collection reports without waiting for a new cycle, reducing reconciliation headaches. The March residual procedure (until April 16) allows FY 2004-05 data to be captured, but no previous FY data should be tagged with a scroll date after March 31, 2005.
Historical instruction — do not use for current compliance. This is what was required at the time; it no longer reflects current RBI requirements. If no replacement rule is linked above, that only means none is recorded on our register yet — it does not prove no later applicable rule exists. Confirm on the official RBI source below.
What banks were required to do at the time
Upload March residual data (FY 2004-05) as a separate RT-01 record alongside current FY 2005-06 RT-01 for each file transmitted between April 1-16, 2005.
Use the new multiple-upload facility to submit any past data not uploaded earlier, merging it with current nodal branch scrolls as needed.
Ensure no previous financial year data is uploaded with a nodal scroll date later than March 31, 2005.
Coordinate with your Nodal Officer to align with DIT(Systems) letter F. No-SW/07/01/03/04/DIT(S)-19602 dated March 18, 2005.
Who it affects
All agency banks handling tax collection under OLTAS, Nodal officers and IT teams managing TIN submissions, Bank branches dealing with March residual tax data
❓ Common questions
Regulatory timeline
Decoded by BankPulse2026-06-19 21:05 IST
Superseded by — Master Circular DGBA.GAD.No.3/42.01.034/2015-16
Status change: superseded09 Jul 2026, 04:02 IST
Built from our lineage records — each fact carries its provenance; missing history simply is not shown (never guessed).
Can we upload missing data from previous financial years after April 16, 2005?
Yes, in extreme eventuality, following the procedure in para (a) and (b) of the circular. However, no data of previous financial year should be uploaded with a nodal scroll date later than March 31, 2005.
What is the procedure for March residual data during April 1-16, 2005?
Banks must transmit two separate RT-01 records: one for the March 31, 2005 residual and one for the current date (FY 2005-06). A single RT-05 summary record per major head is still required daily.
📜 This document’s life story (1 recorded event, each backed by RBI’s own words)
📜 Read the original circular — full text as issued by RBI
RBI/2004-05/413
DGBA.GAD.NO.H-5312/42.01.034/2004-05
April 4, 2005
The Chief Executive Officer
All Agency Banks
(As per list)
Dear Sir,
Accounting of past data in On-line Tax Accounting System(OLTAS) and Accounting of March Residual
Please refer to the discussion held in the meeting held at Indian Banks’ Association on March 04, 2005. As you may please recall, among other things, the requirement of submitting data relating to a particular nodal scroll date/nodal branch (ZAO)/major head combination to Tax Information Network (TIN) on a single day only was also discussed in the meeting. In this connection, keeping in view the need to have complete reporting of collection data on OLTAS and also to ensure uploading of residual/missing data, the Directorate of Income Tax (Systems) has made the following changes in the reporting systems:
a. Multiple files for any particular nodal scroll date/nodal branch(ZAO)/major head code combination will be accepted on different dates by TIN. Now, it will be possible to upload additional RT-01 record of a previous nodal scroll date along with a RT-01 of a current nodal scroll date although a nodal scroll for the previous date is already uploaded.
b. The banks can now upload any past data not uploaded earlier and they can merge the nodal branch scroll of an earlier date in the RT-01 of the current date. The facility of multiple upload of previous nodal branch scroll data will be effective without restriction of the number of times nodal branch scrolls of the same date have been uploaded earlier.
c. For files being transmitted to TIN, during the period from April 1, 2005 to April 16, 2005, two separate RT-01 records will have to be transmitted by the banks. The first RT-01 record will have nodal branch scroll dated March 31, 2005 (March residual) while the second RT-01 record will be that of the current date (financial year 2005-06). However, as usual, there will be one summary record i.e. RT-05 for each major head daily. The procedure of uploading March Residual data for financial year 2004-05 would continue upto April 16, 2005.
d. All data of previous financial year not uploaded earlier was required to be uploaded by March 31, 2005. However, in the extreme eventuality in which some missing data of previous financial year is to be uploaded even after March 31, 2005/April 16, 2005, the banks may do so following the procedure explained in para (a) & (b) above. However, no data of previous financial year should be uploaded in a nodal branch scroll bearing date later than March 31, 2005.
2. In this connection, a reference is also invited to the letter F. No-SW/07 /01/03/04/DIT(S)-19602 dated March 18, 2005 addressed to your Nodal Officer by the Directorate of Income Tax (Systems), New Delhi.
3. Please acknowledge receipt.
Yours faithfully,
Sd/-
(M.T.Varghese)
General Manager
Reproduced for reference with acknowledgment — Source: Reserve Bank of India · RBI/2004-05/413 · issued 04 Apr 2005. The plain-English explanation above is BankPulse’s own independent summary.
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=2179&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.