Common Reasons An ISIN Application Gets Delayed
Reviewed on: 28 July 2026. Reviewed by Abhipra RTA Team.
An ISIN application usually slows down when the company submits before its records are ready. The common blockers are capital mismatches, unclear security-class treatment, incomplete board authority, outdated signatory evidence, missing RTA confirmation, document-format gaps and weak response tracking after depository queries.
![]()
Why ISIN Delay Is Often A Readiness Issue
ISIN activation is not just a code-generation step. The issuer, RTA and depository workflow needs to confirm the legal identity of the company, the securities proposed for admission, authorised signatories, capital records, board approvals and operational responsibility after activation.
NSDL's issuer admission process for unlisted public and private companies includes issuer and securities admission, document upload, verification, signed documents, RTA confirmation and fee/payment actions. A gap in any of these areas can lead to queries, rework or a paused file.
Applicability And Key Dates
Rule 9B applies to private companies other than small companies, subject to the rule, exemptions and company-specific timelines. The 30 June 2025 extension for certain non-producer private companies is already a past date as of 28 July 2026, so a delayed ISIN file in that category should be treated as remediation and evidence creation.
Companies that recently ceased to be small companies, producer companies, unlisted public companies, Section 8 companies, foreign-owned companies or issuers with preference shares, debentures or warrants should obtain professional review before assuming the timeline or document pack is straightforward. REQUIRES HUMAN LEGAL REVIEW.
Common Delay Causes And Controls
| Delay cause | What usually goes wrong | Control before submission |
|---|---|---|
| Capital mismatch | Register of members, certificates, allotment filings and financial statements do not reconcile. | Prepare a capital reconciliation note before filing the depository/RTA pack. |
| Security-class ambiguity | Equity shares, preference shares, debentures or convertibles are treated as one generic bucket. | Map every instrument and identify whether separate admission/ISIN treatment is required. |
| Weak board authority | The resolution does not cover dematerialisation, RTA appointment, depository admission or follow-up powers. | Use a board note that names authorised signatories and permitted actions clearly. |
| Signatory gaps | Specimen signatures, officer authority or contact details are outdated or incomplete. | Confirm current signatories and preserve certified evidence through controlled channels. |
| RTA scope uncertainty | The RTA confirmation or service scope does not align with issuer onboarding and post-activation support. | Confirm RTA appointment, scope, contacts and responsibility matrix before submission. |
| Query drift | Depository/RTA queries are answered piecemeal, with no single owner or version trail. | Maintain a query log with owner, date, response evidence and closure status. |
Documents And Process
The company should begin with an ISIN-readiness file rather than a loose document folder. The file should include the applicability note, board approval, authorised signatory evidence, RTA confirmation, security-class inventory, capital reconciliation, latest constitutional documents, relevant filings and a query tracker.
If documents contain PAN, bank details, address proof, signatures, KYC documents or shareholder-sensitive information, they should move through controlled intake. Readers should not email passwords, OTPs, unmasked bank credentials, signatures or full KYC packets unless a secure submission method has been provided.
Common Errors
The first error is sending the application before reconciling capital changes after the latest financial statements. Allotments, conversions, splits, consolidations, redemptions and buybacks can affect the file.
The second error is assuming that one equity-share ISIN solves every instrument. Preference shares, debentures and convertible instruments may need separate review.
The third error is keeping the project with only one employee. ISIN activation usually needs coordination among the board-authorised signatory, company secretary, finance team, RTA and professional adviser.
The fourth error is treating a depository query as a one-off email. Every query should be logged, responded to with evidence and closed with a preserved trail.
Depository Scale Context
CDSL's official business statistics page, updated for 30 June 2026, shows why accurate issuer data matters in a large demat ecosystem.
| Indicator | CDSL value shown | Why it matters for ISIN readiness |
|---|---|---|
| Investor accounts, excluding closed accounts | 18,59,20,991 | Issuer records must support precise downstream investor servicing. |
| Equity securities available for demat | 46,939 | Equity admission should be mapped to the correct class and terms. |
| Debt instruments and others available for demat | 70,894 | Non-equity instruments need separate operational review where applicable. |
| Depository participants | 588 | Clean issuer/RTA records reduce downstream servicing friction. |
How Abhipra Can Assist
Abhipra can support companies with ISIN-readiness review, RTA onboarding, document-index preparation, security-class mapping, share-capital reconciliation, depository coordination and query tracking. The company's legal advisers, company secretary and board should approve final applicability, board wording, instrument classification and filings.
Need assistance with Rule 9A/Rule 9B applicability, ISIN activation, RTA appointment, share-capital reconciliation or corporate actions?
Contact Abhipra RTA Services at rtaservices@abhipra.com, call 011-42390783, or contact +91-9818080700.
Share the company's name, CIN, company type, latest audited financial year, security classes and approximate number of shareholders for a preliminary discussion.
ISIN Delay-Control Workflow

The practical workflow is to identify applicability, reconcile capital records, map every security class, confirm board and signatory authority, verify RTA scope, submit the depository file, log each query, close each response with evidence and preserve the final admission file for PAS-6, transfers, transmissions and corporate actions.
| Step | Evidence to keep | Owner to identify |
|---|---|---|
| Pre-submission readiness | Applicability note, board approval, security-class inventory and capital reconciliation. | Company secretary with finance input. |
| RTA/depository file preparation | RTA confirmation, authorised signatory evidence, document index and submission trail. | RTA coordination owner. |
| Query handling | Query log, response date, supporting evidence and revised document version. | Board-designated officer with RTA support. |
| Activation closure | Final admission/ISIN evidence and post-activation shareholder-service file. | Company secretary and RTA. |
Source Links
- NSDL: Join as an Issuer
- NSDL: Securities and company search
- CDSL: Our Business and depository statistics
- SEBI: RTA Regulations, 2025
- SEBI: Master Circular for Registrars to an Issue and Share Transfer Agents, 2026
- India Code: Companies Act, 2013
- MCA: Companies Act and rules e-book area
- e-Gazette: Companies (Prospectus and Allotment of Securities) Second Amendment Rules, 2023
Disclaimer
This article is for general educational information and does not constitute legal, tax, investment or transaction advice. Applicability depends on the company's and investor's facts and on the law, circulars and depository instructions in force on the relevant date.