Which details may need formal correction
- Name, spelling, initials or surname order.
- Date of birth or year of birth.
- Gender/identity field where applicable.
- Other core identity particulars drawn from service or pension records.
These are different from ordinary contact details because they can affect matching across pension, tax, Aadhaar, family and service systems.
Find the authoritative source first
Before filing the request, list every record that contains the disputed detail: service record, PPO/corrigendum, Aadhaar, PAN, bank and any other relevant certificate. Identify which record is legally/administratively authoritative for the pension correction. If two source records conflict, do not choose whichever version is easiest to upload.
General correction workflow
- Sign in through the official SPARSH account.
- Open the personal-details/record-correction service available.
- Select the exact field that is wrong.
- Enter the corrected value as supported by the authoritative record.
- Upload the specified evidence.
- Explain a mismatch briefly if the form provides a remarks field.
- Submit once and save the acknowledgement.
- Track any Record Office/sanctioning-authority remark.
- After approval, verify the dashboard and any revised pension document.
Name correction
Check spelling, spaces, initials, surname order and expansion of initials. If Aadhaar, PAN and service records use different versions, the problem may require more than one correction in the proper sequence. Avoid making an unsupported spelling change simply to match a bank or tax document.
Date-of-birth correction
Date-of-birth corrections can be especially sensitive because they rely on authoritative records and applicable service rules. Use only genuine supporting records and the route directed by the competent authority. Do not alter a scanned certificate or create an inconsistent date elsewhere merely to pass validation.
Why a request may be returned
| Reason | What it means |
|---|---|
| Conflicting evidence | The submitted documents do not establish one clear authoritative value. |
| Insufficient evidence | The correction needs another specified record/certificate. |
| Wrong authority | The source service record must be corrected first. |
| Unreadable scan | The reviewer cannot verify the key field. |
| Duplicate case | An earlier correction is already under examination. |
After approval
- Verify the corrected identity field in SPARSH.
- Check whether an ePPO/corrigendum or related document was generated where applicable.
- Review PAN/Aadhaar/bank matching if the correction affects validation.
- Keep the approval order permanently with pension records.
Fraud and document integrity
Never create an edited “proof” to support a pension-record correction. Submit only genuine records. Do not send complete identity documents to unknown agents or allow a caller to remote-control your device.
Frequently asked questions
Can I change my name just because another document uses a different spelling?
First determine the authoritative record and correct the appropriate source.
Is date-of-birth correction an ordinary profile edit?
No. It can require strong documentary evidence and competent-authority review.
What if Aadhaar and service records differ?
Identify which record requires formal correction and follow the proper sequence.
Can I edit a scanned certificate?
No. Submit genuine records only.
Why was the request forwarded to another authority?
The disputed field may originate in the service/sanction record rather than SPARSH itself.
Should I submit multiple correction requests?
Avoid duplicates. Track the existing case.
What should I verify after approval?
Check the profile and any revised pension document that should reflect the change.
Should I keep the final order?
Yes. Keep it permanently with your pension records.