Duplicate PAN identification: update requests undergo RCC duplicity checks and are marked for surrender or forced update. Core field PAN update requests from service providers are subject to mandatory RCC review, during which RCC may seek reconfirmation or documentation; upon RCC approval the request is queued for an automated duplicity check. If identified duplicates are found to belong to the same person, RCC marks the request duplicate and service providers must re-verify-confirmed duplicates prompt direction to approach the assessing officer for surrender, whereas non-duplicates may be resent with a force-flag for automatic update.
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.
Duplicate PAN identification: update requests undergo RCC duplicity checks and are marked for surrender or forced update.
Core field PAN update requests from service providers are subject to mandatory RCC review, during which RCC may seek reconfirmation or documentation; upon RCC approval the request is queued for an automated duplicity check. If identified duplicates are found to belong to the same person, RCC marks the request duplicate and service providers must re-verify-confirmed duplicates prompt direction to approach the assessing officer for surrender, whereas non-duplicates may be resent with a force-flag for automatic update.
Full Summary is available for active users!
Note: It is a system-generated summary and is for quick reference only.
TaxTMI 
of 
Join Channel
TaxTMI 
