SEBI Revamps DNVS: Subject Now Mandatory to Verify Letters and Notices
The Securities and Exchange Board of India (SEBI) has revamped its Document Number Verification System (DNVS), adding another check to the process used to authenticate physical letters, notices and show-cause notices issued in the regulator's name.
The change was announced on 1 October 2026 through Press Release No. 60/2026. The key change is simple but useful: the subject matter of the communication is now a mandatory verification field. SEBI has also aligned the system with the outward-number format generated through its E-Office workflow.
For investors, listed companies, intermediaries and professionals who handle regulatory correspondence, the practical value is straightforward. A SEBI notice can carry a response deadline or trigger legal, compliance and financial work. DNVS gives the recipient a first-line authenticity check before the organisation starts acting on the communication.
What changed in the revamped DNVS?
SEBI originally launched DNVS on 3 April 2025. The regulator's original DNVS announcement created a public mechanism for checking whether a physical communication carrying SEBI credentials had actually been issued by the regulator.
The October 2026 revamp does not create a new portal. It strengthens the existing verification process by adding the communication's subject as a mandatory matching field and aligning the document number with SEBI's E-Office outward-number format.
| Detail required | What to enter |
|---|---|
| Document Number | The outward/document number printed on the SEBI communication |
| Sender's Name | Name of the SEBI official issuing the communication |
| Date of Issue | The date shown on the letter or notice |
| Recipient Name | Name of the person or entity to whom the communication was issued |
| Subject | The subject stated on the communication; this is now a mandatory verification input |
The current SEBI DNVS authentication page displays all five document fields.
The verifier must authenticate themselves first
The live DNVS page does not begin with the document number. It first asks the person carrying out the check to enter their name, relationship with the recipient and mobile number, complete a CAPTCHA and validate the mobile number using an OTP. The document-credential screen follows after that step.
This matters in practice because the person verifying a notice may not be the person named on it. A compliance officer, company secretary, finance team member, lawyer or another authorised person may be carrying out the check for the recipient.
What does a successful DNVS match prove?
A successful match confirms that a communication carrying the details entered by the verifier was issued by SEBI. That makes DNVS an authenticity control for the communication's identifying credentials.
It does not mean that SEBI has separately verified every factual statement, allegation, calculation or conclusion contained in the letter. SEBI has specifically clarified that document authentication does not constitute verification of the contents of the communication.
The distinction is important. DNVS answers the first question: was a communication with these details issued by SEBI? It does not answer the second: is every factual or legal proposition in that communication correct?
A genuine show-cause notice, inspection letter or information request may still require a detailed review of facts, records and applicable law before a response is prepared.
What happens if DNVS says no record is found?
A failed match should not automatically be treated as proof that the document is fake. The first step is to compare every input with the original communication, especially the outward number, sender's name, date, recipient and subject.
If the details are correct but the communication still does not match, do not treat the online result as conclusive. Recheck the document number, sender, date, recipient and subject. If the mismatch remains unresolved, seek clarification directly from SEBI before acting on the communication.
Where the communication contains a response deadline, the recipient should track that date separately while the authenticity issue is being resolved. DNVS verification should not be assumed to pause or extend a deadline stated in a SEBI communication.
What about older SEBI communications?
For an older SEBI communication, start with the current DNVS authentication page. If the document cannot be authenticated online, verify it directly with SEBI before relying on it or treating the absence of a match as proof that the communication is invalid.
This is especially relevant for audit, legal and compliance teams reviewing older regulatory files. A missing online match should trigger an additional verification step rather than an immediate conclusion about authenticity.
Why does the new subject field matter?
The subject is more than another box on the screen. It gives the verification process an additional document-specific point of comparison.
A regulated entity may receive several SEBI communications during the year, sometimes involving the same company or intermediary. One may reach the compliance team, another the finance function and another the legal department. Requiring the subject alongside the outward number, sender, date and recipient makes the matching exercise more specific.
That does not change the legal effect of a notice. It improves the quality of the authenticity check carried out before the notice is acted upon.
A practical workflow for finance, legal and compliance teams
SEBI's revamp does not by itself impose a new filing requirement on recipients. However, organisations that regularly receive regulatory correspondence can use DNVS as an early control in their inward-document process.
- Preserve the communication as received. Keep the original document or an unaltered scanned copy, together with the date and mode of receipt.
- Authenticate the document through DNVS. Enter the details from the original communication rather than from an internal email summary.
- Record the verification result. For significant matters, retain the verification date, the person who performed the check and the result shown by DNVS.
- Diary the response deadline separately. Authentication and substantive response management are different controls.
- Escalate unresolved mismatches. Recheck the inputs and use SEBI's stated confirmation channel where the online result remains unresolved.
- Review the substance independently. Once authenticity is addressed, assess the factual, legal, accounting and regulatory issues raised in the communication.
This is a practical control recommendation, not a separate SEBI-mandated checklist. Its purpose is to keep the authenticity question separate from the work needed to respond to the communication.
Example: how the control could work inside a company
Suppose a listed company receives a physical notice carrying a response deadline. The company secretary scans the notice and sends it to legal and finance. Before the teams start drafting a response, an authorised employee opens DNVS, completes mobile authentication and enters the outward number, issuing official, date, recipient and subject exactly as printed.
If the system confirms issuance, the company records that result and moves to the substantive review. If no record is found, the team first checks for a data-entry error and then uses the official confirmation route if the mismatch remains. In either case, the response deadline continues to be tracked independently.
The value of this process is not complexity. It is that one short verification step can prevent an organisation from treating an unverified physical communication as established regulatory correspondence.
DNVS is not the same as SCORES
DNVS is an authentication facility. It is not an investor grievance portal.
An investor who has a complaint against a stock broker, depository participant, mutual fund or listed company follows a different route through SEBI's grievance framework. For investor complaints involving brokers or listed companies, see the SEBI SCORES complaint process and timelines.
The distinction is useful: DNVS checks whether a SEBI communication was issued; SCORES is used for eligible investor grievances.
Does the DNVS revamp create a new compliance filing?
No separate filing obligation arises merely because SEBI has revamped the verification system. Press Release No. 60/2026 concerns the authentication facility for SEBI communications.
The letter being verified may, of course, contain its own response, disclosure or information requirement. Any such obligation comes from that communication and the applicable regulatory framework, not from the act of using DNVS.
Can someone verify a SEBI letter on the recipient's behalf?
Yes. The current DNVS interface asks the verifier to state their relationship with the recipient, and the SEBI update also provides for verification by the recipient or a person acting on the recipient's behalf.
That makes the facility usable in normal organisational workflows where regulatory correspondence is handled by a professional team rather than personally by the named recipient.
What recipients should change now
For organisations that regularly receive SEBI correspondence, the most useful change is procedural: add DNVS authentication to the front of the regulatory-mail workflow for physical letters and notices.
A simple record can capture the document number, date received, verification date, verification result, person performing the check and the response deadline. This creates a clearer audit trail without turning the process into a separate compliance exercise.
For listed-company disclosure requirements, see the SEBI LODR Regulation 30 material-event disclosure guide, including materiality thresholds and disclosure timelines.
Bottom line
SEBI's October 2026 DNVS revamp is a focused system change with practical value. The subject of the communication is now part of the mandatory verification inputs, and the system is aligned with SEBI's E-Office outward-number format.
For recipients, the sensible sequence is: authenticate the communication, preserve the record, identify the deadline and then analyse the substance. A successful DNVS match confirms issuance; it does not replace a legal or factual review of what the communication says. An unresolved or older communication should be verified directly with SEBI rather than ignored or treated as invalid solely because of an online mismatch.
Official source
Official source: SEBI — Authenticate Document Issued by SEBI (DNVS)
Regulatory information can change. For a live matter, check the current SEBI communication and official source before acting.
