The plain answer
Updating your demat account details runs through the broker app, and every meaningful change verifies before it takes effect. Small changes like nominee and email are quick; core changes like PAN, Aadhaar and address re-verify the KYC and follow a document-first sequence: update the source document, then update the account. The one habit that prevents most stalls is keeping the Aadhaar-mobile linkage current, because every other verification leans on it.
The account record is a mirror of your source documents, not an independent registry. That single fact explains every speed and every stall on this page: the broker verifies a change against PAN, Aadhaar or a bank proof, and if the source document is stale, the mirror cannot update. Fix the document, and the account update becomes a formality; skip the document, and no amount of retrying moves it.
The two classic cases this page keeps returning to are the marriage name change and the post-move address change, because they are the updates most people attempt in the wrong order. In both, the account record is the last thing to change, not the first: the marriage certificate or Aadhaar address update comes first, and the broker app only mirrors a document that has already changed at the source.
What each change needs
| Change | Document needed | Typical speed |
|---|---|---|
| Nominee | New nominee’s PAN and date of birth | Days, after verification |
| OTP on the new email | Minutes | |
| Mobile number | OTP through registered channels | Minutes to days |
| Bank account | Account proof in your name | Days, after verification |
| Address | Updated Aadhaar first | Days, after Aadhaar settles |
| PAN / Aadhaar correction | The corrected document itself | Longest; re-verifies core KYC |
| Name change | Marriage certificate or gazette, plus updated PAN | Slowest; usually a form route |
| Signature change | A physical form at most DPs | Slowest; verified offline |
Read the table by the last column, because the speed column is the honest one. Two updates are effectively instant because they verify online in the session: email, and a mobile change that matches the Aadhaar-linked number. Everything else waits on a document check, which is why the page keeps returning to the source-first sequence.
One row deserves a footnote: the nominee change is covered in depth on the nomination page, because it is the only update on this list with succession consequences. Every other row is about keeping the account operable; that one is about who receives the assets.
The two bottom rows, name and signature, are the heavyweight class for a reason: they change the identity itself, not a contact detail, so the verification is intentionally deeper. A bank account can be swapped out with a proof; a name change rewrites the KYC record and drags every linked check behind it, which is why the form route and the supporting documents apply.
The order that makes updates fast
- Source document first. Fix Aadhaar or PAN at the source before touching the account. The account update is a reflection; the source is the fact.
- Mobile linkage second. The Aadhaar-linked mobile receives the verification OTPs. Without it, every other update stalls at step one.
- Account update third. With the source current and the linkage live, the app update verifies in one pass.
The order works because verification is a chain, not a menu. Each step depends on the one before it, and the failures people report are almost always an earlier link: the address that is not in Aadhaar yet, the mobile that changed at the telecom provider but not at Aadhaar, the bank account whose name does not match the PAN record.
The most common real walkthrough is the address change after a move: update the address in Aadhaar first, wait for the change to settle, then submit the same address in the broker app, where it verifies against Aadhaar in one pass. The people who skip the Aadhaar step retry the app three times and get the same rejection three times, because the verification is reading a document that still shows the old city.
A mobile change, step by step
The mobile number is the highest-leverage field on the account: it receives the OTPs that authorise everything else, so a wrong number quietly blocks every future update and every future login reset. The change sequence when the number itself is new:
- Update the mobile number in Aadhaar first, at an Aadhaar centre or online
- Update the number with your bank and any linked mandates
- Request the mobile change in the broker app
- Verify with the OTP sent to registered channels
- The change takes effect and prints on the next CAS
The Aadhaar step comes first because the demat verification checks against the number on file with Aadhaar. A SIM that works in your hand is not the same as a number registered at Aadhaar, and the account system cannot tell the difference by looking at the phone; it can only compare records.
The OTP step is the protection working: the change verifies through channels that already belong to you before the record moves. If a verification OTP arrives without you having requested a change, treat it as a warning sign and check the account immediately, the same drill as the compromised account guide.
A mobile change ripples, and the ripples are part of the job. The bank’s SMS alerts and UPI registrations read the SIM, the Aadhaar record feeds the demat verification, and the broker’s two-factor logins follow the account record. Do the change in the source-first order and the ripples settle in the same pass; change only the SIM and you end up with a phone that works and a record that points elsewhere, which is the exact state that lets OTPs reach the wrong hands.
PAN-Aadhaar mismatches
The KYC record rests on two identity documents, PAN and Aadhaar, and the verification compares them. A mismatch, a middle name in one but not the other, a spelling difference, a maiden name after marriage, fails the check and stalls the update. The broker cannot fix the source document; only the issuing authority can.
The resolution path mirrors the page’s golden rule: correct the document that carries the error first, whether that is an Aadhaar correction or a PAN correction, then resubmit the account update with the corrected record. Marriage-name changes add one document to the chain, the marriage certificate or gazette notification, which is the proof that links the old name to the new one.
The linkage between the two documents is itself a statutory matter: the Income-tax Act requires the PAN-Aadhaar linkage for PAN validity, which is why the securities KYC leans on both records matching. In practice the direction of the fix follows the error: a name misspelled only in Aadhaar is an Aadhaar correction; a name outdated only on the PAN is a PAN correction; a name changed by marriage is both, in sequence, with the certificate linking the two.
The cost of ignoring a mismatch compounds, because the mismatch does not age out. Every future verification that touches the name field, payouts, KYC re-verification, even a future demat account opening, hits the same wall. A mismatch fixed today costs one correction; a mismatch left in place costs one correction plus every failed verification in between.
Bank account changes
The bank account on file is the payout destination: when you sell shares, the money settles only to a bank account registered in your name on the demat account. A new bank account therefore needs the account proof, typically a cancelled cheque or a statement carrying your name and the account number, and the verification that the name on the bank account matches the KYC name.
Two practical points on top of the basic flow. First, if the old bank account was primary for payouts, set the new one as primary explicitly; adding an account and receiving payouts into it are two different settings. Second, close the old bank account only after the new one is verified on the demat record, so no payout in flight lands in a closed account.
The structure to keep in mind: brokers let you register more than one bank account, but every account on the record must be in your name, and the primary designation decides where sell proceeds land. The same-name rule is the fraud control here, which is why a payout request to an account not registered on the demat record simply will not be processed, no matter how urgent the call claiming otherwise sounds.
When updates need a form
Most changes are fully digital, but two heavyweight updates typically need a physical route: name changes, which carry legal significance and need the supporting documents in original or certified form, and signature changes, which most DPs verify offline because the signature is a paper-era control that online checks cannot validate. The broker or depository tells you when a change needs the form; assume the name and signature rows do.
The form route is slower and may carry a processing charge, which the pricing page lists. The discipline is the same as the digital route: attach the source document, complete every field exactly as the records show, and keep the acknowledgment. A form returned once for a missing enclosure costs more time than a careful first submission.
What blocks an update
| Blocker | What it looks like | The fix |
|---|---|---|
| Document mismatch | The update rejects with a verification error | Fix the source document first, then resubmit |
| Account freeze | The update form is disabled or rejected | Clear the freeze with the broker first |
| Name mismatch on PAN vs Aadhaar | KYC verification fails repeatedly | Correct the wrong document at the issuing authority |
| Incomplete enclosure | A physical form comes back | Attach every listed document and resubmit in one set |
| Pending verification | The old value still prints on the CAS | Wait for the cycle, or chase the reference number |
The blockers table is the troubleshooting map for every stalled update, and the first column predicts where most people get stuck: the document mismatch. When an update rejects twice in a row, stop resubmitting and start comparing the account record against the source document, because the difference between the two is the rejection, and only one of them can be changed from the broker app.
The freeze case deserves its own note. A frozen account, whether for a missing nomination choice or a regulatory reason, blocks most updates until the freeze is cleared, because the freeze is a protective block on the account itself, not on a single field. The freeze guide covers the reasons and the clearing process; treat the freeze as step zero of any update it is blocking.
The one habit that makes every blocked update cheaper: keep the reference number of each request. Every submission, online or on paper, carries a tracking identifier, and support resolves a request with a reference in minutes that takes days to reconstruct without one. Screenshot the confirmation, note the number, and a stalled update becomes a chaseable ticket instead of a mystery.
When the change shows up
The monthly consolidated account statement is the confirmation layer for every update on this page. A change verified mid-month prints on the next CAS, and the statement is the document that proves the record, which is why the audit habit on this page reads the CAS rather than trusting memory.
Two timing notes round out the picture. First, the CAS follows the depository’s statement cycle, so a change submitted just after a statement lands may wait most of a month to appear in print, even though the record updated on day one. Second, the app’s profile view updates faster than the statement, because it reads the live record. Check the app for speed and the CAS for proof, and use both.
Why every change verifies
The verification exists because the account details are the keys to the assets: the bank mandate moves money, the mobile receives the OTPs, the address decides where statements and documents go. A change that skipped verification would be the single most valuable target in the fraud playbook, which is why the depositories and SEBI require every meaningful change to re-verify against a proof document or a registered channel. The friction is the protection.
The fraud pattern the verification blocks is simple to describe: a changed mobile number redirects every OTP, a changed bank account redirects every payout, and a changed address redirects every physical document. Together the three changes would move the account to someone else without moving the shares at all, which is why each one verifies independently against channels that already belong to you.
The verification itself comes in three strengths, and the strength follows the risk of the field. Contact changes verify with an OTP on a channel you already hold, which is quick and online. Identity-adjacent changes verify against a document, which is slower. And the heaviest changes, name and signature, verify offline against originals, because no online check can carry the weight of rewriting an identity. The speed column in the table at the top of this page is just this ladder in reverse.
What people usually get wrong
Changing my SIM updates my account mobile
The account record is separate from the SIM. Until the record updates through verified channels, OTPs keep going to the old number.
I can update my address directly in the broker app
The address must be verifiable against a proof document. Aadhaar first, then the account, is the sequence that actually works.
Updates are instant
Every meaningful change verifies, and verification takes minutes to days depending on the field. The speed follows the document, not the tap.
One update fixes every field at once
Each field updates separately, with its own document and its own verification. A corrected PAN does not correct the address or the mobile on the account.
Questions people ask
Nominee, email and most bank mandate changes go through quickly after verification. PAN and Aadhaar corrections are slower because they re-verify the core KYC, and address changes follow the Aadhaar update first. The speed follows the document, not the tap: a change the system can verify online is fast, and one that needs a document check is slower.
The KYC address is verified against a proof document, and Aadhaar is the standard one. A new address that is not yet in Aadhaar cannot be verified against it, which is why the sequence is Aadhaar first, demat second. The same logic applies to the PAN: the account reflects the source document, so fix the source before touching the account.
Only after you update the mobile on the account, and the update verifies through the Aadhaar-linked number or the registered channels. The SIM changing does not update the record, which is how OTPs keep going to old numbers. The full sequence is in the step-by-step section below, and the Aadhaar step comes first for a reason: the demat verification leans on the number Aadhaar has on file.
Standard updates through the app carry no published fee at the major brokers. Physical form processing, where the broker still requires it, may carry a processing charge, which the pricing page lists. The cost to watch is not money but time: a mismatched document stalls the update and every verification behind it.
The update stalls, because KYC verification compares the records and a mismatch fails the check. Fix the source first: correct the name in Aadhaar or PAN, whichever carries the error, then resubmit the account update. Marriage-name changes are the common case, and they need the supporting document, such as the marriage certificate or an updated PAN, before the account can follow.
The next monthly CAS prints the current records, so the statement is the confirmation. Check the field you changed on the next statement, and check the nominee line while you are there. If the change does not appear within a cycle, the update is still pending verification, and a support ticket with the reference number resolves it faster than a second submission.
Sources
- Securities and Exchange Board of India. “Legal framework , circulars,” KYC requirements for securities markets. Accessed 16 August 2026.
- Central Depository Services (India) Limited. “Official website , depository services,” account modification documentation. Accessed 16 August 2026.
- National Securities Depository Limited. “Official website , depository services,” account modification documentation. Accessed 16 August 2026.
- Upstox. “Open a free Demat account,” KYC and account update flow. Accessed 16 August 2026.