Twenty-four modules. 256 features. One register.

One screen answering the two questions an operating head asks every morning: is the register in balance, and what breaches today.

• Balance rail reading BALANCED or OUT BY n SHARES
• Incomplete-register state shown explicitly, never implied
• Day pack export for the morning call

Operations

Every investor instruction that reaches the RTA becomes a request with a type, a stage, an owner and a statutory clock. The legacy system has eleven list pages and no state. This is one queue with state.

• Statutory TAT clock per type, computed at intake
• Defensible clock pause — every pause records who and why
• Maker–checker enforced in the database, not the interface

Operations

The holder record as a single view across physical and demat, so a query on the phone is answered from one screen instead of five.

• Folio 360 — holdings, KYC, requests, dividends, correspondence
• Address history with effective dates, never overwritten
• Holder identity resolution across folios and ISINs

Operations

The one equation the RTA exists to keep true: issued capital equals physical plus NSDL plus CDSL plus suspense plus in-transit. Computed, not asserted.

• Variance is a stored column, computed by the database
• Continuity assertion between consecutive position dates
• Quarter gate — Reg. 76 cannot certify over an open break

Operations

What was sent, to whom, at which address, on what date, and whether it came back. An RTA that cannot prove despatch cannot defend a complaint.

• Address snapshot frozen at despatch, not looked up later
• Versioned templates — an old letter reproduces exactly
• Proof of despatch with carrier reference and return status

Operations

The mandate. Who the issuer is, which securities it has, what the RTA is contracted to do, and what capital is outstanding.

• ISIN succession keeps a face-value change related, not orphaned
• Capital event ledger behind every issued quantity
• Mandate onboarding checklist gating go-live

Registers

The share register in its original form. Distinctive numbers are the primary key of the physical world and the schema treats them that way.

• A database exclusion constraint refuses overlapping distinctive numbers
• Lineage across splits, consolidations and duplicate issues
• Register of members extract in the prescribed form, at any date

Registers

Beneficiary position files are the depositories’ statement of who holds what. They are evidence and they are kept as evidence.

• Four gates before a single row is committed
• Every raw file kept forever with its SHA-256
• Identifiers hashed and masked before they reach the database

Registers

Everything exchanged with NSDL and CDSL, in both directions, as files with hashes and a load status. The credentials belong to the RTA and live only on its node.

• One versioned parser per depository per file kind, with golden-file tests
• Missed-file alerting against expected arrival windows
• Credential vault the control plane never holds a key to

Registers

From board resolution to credited entitlement, as a sequence of steps each of which is signed off before the next opens.

• Record-date position combining both depositories and the physical register
• Fractional pool computed and its disposal recorded
• Each action links to the position movement it explains

Registers

Money leaving the issuer’s account against the register. Two-person release, full tax treatment, and an unpaid register that is a live worklist rather than a report.

• Bank file staged by one person and released by another, enforced in the database
• Section 194, 195 and 196D classification with 15G/15H and 197 handling
• Hold rules producing a named hold with a count and a value

Registers

A seven-year clock with statutory notices at fixed points. Missing a notice is a compliance failure that cannot be cured retrospectively.

• Maturity clock surfacing cases before they mature, not after
• IEPF-4 transfer as one transaction across action, depository and register
• Suspense holding tracked against the original folio for later claims

Registers

The 2023 norms made PAN, address, contact details, bank mandate, signature and nomination mandatory for physical folios, with freezing as the consequence.

• Folio KYC state derived from six components across all joint holders
• Penny-drop result recorded — a failed drop is a hold, not a warning
• Automatic freeze with the reason and the cure path shown to the holder

Oversight

Complaints are the thing SEBI measures the RTA by. Tracked as work with a clock, so the quarterly statement is a by-product rather than an exercise.

• SCORES intake matched to a folio and a service request
• Twenty-one-day resolution clock with escalation before breach
• Root-cause tagging, so the pattern is visible rather than the count alone

Oversight

Every certificate drafted from register data, signed by a named officer, filed on time, and archived with the evidence that supports it.

• Evidence pack per filing — an inspection is a download, not a fire drill
• Reg. 76 gated on there being no open reconciliation break
• A late filing is marked late and cannot be quietly backdated

Oversight

Every change carries a name and a time. This is what makes the rest of the system defensible.

• Hash-chained, append-only, with UPDATE and DELETE revoked in the database
• Eight years on write-once storage, partitioned by month
• Time-boxed inspection windows scoped to one issuer

Oversight

Deflect the routine query. Every request an investor can raise and track themselves is a call the desk does not take.

• Track by SRN — live stage, what is outstanding, expected disposal date
• Cure a deficiency by upload, which restarts the clock automatically
• Accessible on a phone, in the languages the holder base needs

Self-service

The issuer’s own people answer their own questions. The RTA stops being a bottleneck for routine reporting.

• Register dashboard scoped to the issuer’s own ISINs only
• Shareholding pattern, distribution and top holders, downloadable
• Payout approval with the hold summary visible before release

Self-service

Everything the system says to a person, in one place, with a record that it was said.

• Correspondence log with content, channel, time and delivery result
• Channel consent per holder, with the consent evidence retained
• Template versioning recorded on each item sent

Self-service

A maker on one issuer’s transfers desk must not be able to read another issuer’s register. Enforced by the database, not by the interface.

• Row-level security — a query that forgets its WHERE clause still returns nothing
• Segregation of duties enforced by constraint, not convention
• Mandatory multi-factor authentication, no shared logins

Platform

Paper is the raw material of this business. Scanned once, read by machine, confirmed by a human, and kept forever.

• Content-addressed document store with SHA-256
• Checklist enforcement — verification cannot be left with a document missing
• Machine suggestion and human confirmation both logged

Platform

One box that finds the thing, whatever the user happens to know about it.

• Folio, DP and client ID, PAN, name, certificate, distinctive number, SRN, DRN
• Fuzzy name matching, because the same person is spelled three ways
• Results scoped without revealing that anything was filtered

Platform

What the RTA bills for, how the desks are performing, and what the issuer’s board asks about.

• TAT performance by type, desk and person against the statutory norm
• Activity-based charging captured as it occurs
• Any table exportable, with the filter that produced it recorded in the file

Platform

One dedicated node per RTA, attached to a control plane that holds no register data and cannot reach in uninvited.

• Single-command provisioning from a bare server and a claim token
• Seventy-two hours of full local operation if the control plane is unreachable
• Weekly automated restore test, reported in the heartbeat

Platform