Built for SEBI-registered Registrars and Transfer Agents
The register either balances, or it tells you by how much.
Registry is a share registry platform for SEBI-registered Registrars and Transfer Agents. 256 features across 24 modules, running on one dedicated node per RTA — your database, your depository credentials, your backups.
Written against the SEBI regulations, a decade-old incumbent back office read screen by screen, and nine months of real beneficiary position files.
Reconciliation run
INE0ABC01234 · 28 Jul 2026 · 09:14 IST
Issued capital
12,00,00,000
- Physical
- 84,50,000
- NSDL
- 7,42,30,000
- CDSL
- 3,68,20,000
- Suspense
- 5,00,000
Reconciliation for ISIN INE0ABC01234 on 28 July 2026. Issued capital 12,00,00,000 shares, made up of physical 84,50,000, NSDL 7,42,30,000, CDSL 3,68,20,000 and suspense 5,00,000. Variance is zero and the run is balanced.
The one equation
Computed by the database. Not asserted by a person.
Issued capital equals physical plus NSDL plus CDSL plus suspense plus in-transit. The variance is a stored column derived from its components, so it cannot be edited independently of them.
issued = physical + NSDL + CDSL + suspense + in_transit
Every non-zero variance becomes a break
With a reference, a nature, an owner, an age and an explanation field. A break clears only when a named person records a cause.
Breaks keep their first-seen date
A two-month-old break does not look new because it appeared in today’s run as well.
Reg. 76 is gated on the worklist
A quarter cannot be certified while a break is open. The filing screen refuses and names the breaks.
Movements are classified, not guessed
Offsetting NSDL and CDSL movement is inter-depository transfer. Net movement is matched against corporate actions, demats, remats and IEPF transfers.
Ingest
Four gates before a single row is committed.
The first three reject the file outright. The fourth loads it and raises a break — because the position is real, and it is the explanation that is missing.
Every file is kept forever with its SHA-256. When a depository disputes a figure two years later, the file you received is the argument.
- 1
Gate 1 — Shape
23 columns in order, plus the _meta sheet
- 2
Gate 2 — Control totals
SUM(qty) per depository = _meta counts
- 3
Gate 3 — Row integrity
No duplicate account keys · no negatives · pledged + locked ≤ total
- 4
Gate 4 — Continuity
Δ NSDL + Δ CDSL = 0, or a register event explains it
The platform
Twenty-four modules, from the command deck to node operations.
Operations
67The desk. What the register does every day.
- M01Command deck
- M02Service requests
- M03Folios and holders
- M04Reconciliation
- M05Outward and despatch
Registers
77The record itself, in every form it takes.
- M06Issuer and ISIN master
- M07Physical certificates
- M08Benpose
- M09Depository interface
- M10Corporate actions
- M11Dividend and payout
- M12IEPF and unclaimed
Oversight
39What you show an inspector.
- M13KYC and investor compliance
- M14Grievance, SCORES and ODR
- M15Regulatory filings
- M16Audit trail and inspection
Self-service
26Work the desk no longer has to do.
- M17Investor portal
- M18Issuer portal
- M19Notifications and correspondence
Platform
47The machine underneath.
- M20Identity, roles and access
- M21Documents and extraction
- M22Search
- M23MIS, billing and analytics
- M24Node operations
Deployment
We cannot reach your register. That is the design, not a policy.
Each RTA runs a dedicated node — its own server, database, object store, depository credentials, backups and encryption keys. The control plane holds fleet metadata only, and it has no inbound path. It leaves signed commands in a queue the node collects on its own schedule.
Depository credentials stay put
NSDL and CDSL issue credentials to the RTA, not to a software vendor. On your own machine is where they belong.
Seventy-two hours of offline grace
A compliance officer’s first question is what happens if the vendor disappears. The answer is nothing.
Residency is a machine, not a filter
Data residency and the SEBI cyber-security framework are simpler to evidence when the boundary is physical.
What the real data changed
Forty-three weekly position files were parsed end to end. All forty-three carried producer-supplied control totals that matched exactly. Two of the forty-two weekly transitions showed a net change in demat holding with nothing in the incumbent register explaining it — one of 1,28,16,000 shares and one of 31,000.
That finding is why the continuity gate exists, and why module M04 works the way it does. It is not a marketing claim. It is what nine months of one live issuer’s files actually contained.
Where the requirements came fromOversight
Every filing drafted from register data, with the evidence attached.
An inspection becomes a download rather than a fire drill.
| Regulation | Certifies | Frequency |
|---|---|---|
| 7(3) | RTA compliance certificate | Half-yearly |
| 13(3) | Investor complaints statement | Quarterly |
| 31(1) | Shareholding pattern | Quarterly |
| 40(9) | Transfer, transmission and duplicate certificate | Half-yearly |
| 74(5) | Securities dematerialised and certificates destroyed | Quarterly |
| 76 | Reconciliation of share capital audit | Quarterly |
| IEPF-2 | Statement of unclaimed dividend | Annual |
| IEPF-4 | Transfer of shares to the IEPF Authority | As due |
Redundancy
Three tiers. Automatic failover is deliberately not the default.
For a share register, a ten-minute human-confirmed promotion is usually the better trade than automatic promotion plus split-brain risk.
Standard
Single node, continuous WAL archive, nightly full, offsite encrypted copy
- RPO
- ~5 min
- RTO
- 2–4 h
An RTA with a handful of mandates
Resilient
DefaultPrimary plus hot standby in the same datacentre, streaming replication, manual promotion
- RPO
- ~0
- RTO
- 10–15 min
The default. Most will want this.
Critical
Resilient plus an asynchronous DR node in a second Indian region, quarterly failover drill
- RPO
- ~0 local, ~15 min regional
- RTO
- ~30 min regional
Large issuer books, high public visibility
Bring your own file. We will run it through the gates.
A demo runs against a real position file — yours, if you want — so you see the gates, the balance rail and the break worklist behave on data you already know.
Book a demo