AO code population and duplicate refund deletion required; centres must apply the supplied patch and report compliance. A patch addresses refunds posted under suspense and duplicate refund entries by providing Deletion of duplicate challan/refund and population of AO code on refund data. Centres must take two full backups, ensure no users are active, download and execute the patch from the specified server path, copy executables to the file server renaming or backing up same-named files, and report implementation by the stated deadline; prior OLTAS Instructions must already be implemented and routine 'Correction due to wrong BSR' runs should be performed.
Cases where this provision is explicitly mentioned in the judgment/order text; may not be exhaustive. To view the complete list of cases mentioning this section, Click here.
Provisions expressly mentioned in the judgment/order text.
AO code population and duplicate refund deletion required; centres must apply the supplied patch and report compliance.
A patch addresses refunds posted under suspense and duplicate refund entries by providing Deletion of duplicate challan/refund and population of AO code on refund data. Centres must take two full backups, ensure no users are active, download and execute the patch from the specified server path, copy executables to the file server renaming or backing up same-named files, and report implementation by the stated deadline; prior OLTAS Instructions must already be implemented and routine 'Correction due to wrong BSR' runs should be performed.
Full Summary is available for active users!
Note: It is a system-generated summary and is for quick reference only.