What Is the Distinctive Number Database? (DN)

The distinctive number database is the depositories' centralised record of every equity share a listed company has issued, tracked by distinctive number. Physical shares are recorded at DN level; dematerialised shares are recorded as an overall DN range. Its purpose is reconciliation: making the number of shares a company says it has issued match the number the market can actually account for. SEBI set it up by circular dated June 5, 2015 and it now sits in the Master Circular for Registrars to an Issue and Share Transfer Agents.

What does the DN database actually contain?

Para 16.2 lists the fields it makes available in respect of issued capital, and the list is more useful than the name suggests:

• DN range and the number of equity shares issued.
• The name of the stock exchange where the shares are listed.
• Dates: in-principle listing, final trading approval, dealing permission, and date of allotment.
• Whether shares are held in physical or demat form.
• Whether shares were dematerialised under a temporary (frozen) ISIN or a permanent (active) ISIN.

That last field is the one worth noticing. The frozen-versus-active ISIN distinction is how the system marks share capital that exists but is not yet freely tradable, and the DN database carries it alongside the allotment record.

Who is responsible for keeping it current?

The depositories create and maintain the database. Issuers and their registrars and transfer agents do the updating, through an interface the depositories provide. Para 16.3 sets three obligations:

1. Update DN information for all physical share capital and the overall DN range for dematerialised share capital, for all listed companies.
2. Keep the fields current on a continuous basis for subsequent changes. The named fields are Distinctive Numbers (From), Distinctive Numbers (To), Number of Equity Shares, Name of Stock Exchange, Physical or Demat, date of allotment and date of issue, meaning the date of credit to the beneficial owner account. The named triggers include further issues, fresh issuance, new listing, and other change or alteration in capital such as buy-back, forfeiture of shares or capital reduction.
3. Capture and update DN information continuously while processing dematerialisation and rematerialisation request confirmations and executing corporate actions.

What happens when the records disagree?

The stock exchanges also provide and update data in the DN database, which creates the possibility of a mismatch between what the exchange holds and what the issuer or RTA has recorded. Para 16.4 puts the burden on the issuer or RTA to take steps to match the records and update them.

Para 16.5 states the consequence in one line: failure by issuers or RTAs to ensure reconciliation of the records as required shall attract appropriate actions under the extant laws.

Why a share-count reconciliation database matters

Almost every ownership number an investor reads is a percentage, and every percentage has issued capital in its denominator. A shareholding pattern reports promoter, FII and DII holding as a share of total issued capital. A minimum public shareholding test measures against the same base. So does free float.

The DN database is the plumbing that keeps that denominator honest, together with the reconciliation of share capital audit report, which is the periodic certification of the same reconciliation. Neither is something an investor queries directly. Both are why the issued-capital figure on a filing can be relied on.

For the account-level side of the same system, see what is dematerialisation of shares and what is rematerialisation of shares, the two transactions para 16.3.3 requires to be captured in the database as they are processed.

Flock reports the filings themselves, each stamped with its date and linked back to the exchange or regulator that published it. What any of it means for you is your call to make.