All Courses are free for limited time.
NISM Professor

RTA inter-operable platform

A single, user-friendly platform built jointly by all RTAs for mutual fund transactions, service requests, complaints and investment reports across fund houses — the workbook gives no rupee figure for it.

In plain language

An investor with folios at several fund houses used to have to deal with each RTA separately for a purchase, a service request or even a simple query. The RTA inter-operable platform is the industry's joint answer to that friction: one interface, built by all the RTAs together, standing in front of all of them.

The workbook gives no threshold, fee or numeric limit for this platform — it describes what it does, not a figure attached to it.

How it works

The platform, developed jointly by all the RTAs, provides a user-friendly interface for:

  • mutual fund transactions — purchase, redemption, switch and similar;
  • initiating and tracking service requests — a change of email ID, contact number or bank account details, for example;
  • initiating and tracking queries and complaints;
  • accessing investment-related reports — mutual fund holdings in both demat and standard form (with RTAs and depositories sharing information to build these), transaction reports including historic transactions, capital gains/loss reports, and details of unclaimed dividend or redemption amounts.

The platform is required to adopt the same Cyber Security and Cyber Resilience Framework that applies to QRTAs, and to comply with SEBI's Business Continuity Plan and Disaster Recovery guidelines. Because it is a joint venture, all RTAs are jointly responsible for compliance across the platform, including its system audit and cyber security audit.

A worked example

Every rupee figure below is illustrative. The workbook describes what the platform does and attaches no threshold, fee, limit or value to it — none of these numbers is a workbook figure, and no minimum folio value is needed to use the platform.

Mr Kadam holds mutual fund folios across three different AMCs, serviced by two different RTAs:

FolioFund houseServiced byValue
MF-11204AMC 1RTA XRs 4,20,000
MF-38867AMC 2RTA XRs 2,60,000
MF-90513AMC 3RTA YRs 1,20,000
TotalRs 8,00,000

Before this platform existed, working out his position for the year meant three separate approaches to two RTAs. Through the platform he does all of it from one interface:

  1. A transaction — he redeems Rs 1,50,000 from MF-11204, leaving that folio at Rs 2,70,000 and his total at Rs 6,50,000.
  2. A service request — he tracks a pending change of bank account on MF-38867, filed with a different fund house four days earlier.
  3. A complaint — he raises one about a statement never received for MF-90513.
  4. Reports — he pulls a consolidated capital gains/loss statement across all three folios:
FolioGain or loss
MF-11204+ Rs 62,000
MF-38867+ Rs 18,000
MF-90513− Rs 9,000
Net for the year+ Rs 71,000

The same report shows Rs 3,400 of unclaimed dividend sitting against MF-90513 — money he did not know he was owed, on a folio serviced by the RTA he deals with least. Rs 71,000 of net gains and Rs 3,400 of unclaimed money, assembled in one place, without his knowing which RTA sits behind which fund house.

Because the platform shares the same cyber security and BCP/DR obligations SEBI places on QRTAs, and because all RTAs on it are jointly responsible for its compliance, a failure at one RTA's end does not let the others point elsewhere — the audit trail covers the platform as a whole.

Why NISM asks about it

Chapter 7 (Registrars and Transfer Agents Regulations), section 7.7, describes the platform and its four service categories, and its sample question asks which services it facilitates — the correct answer being all three of mutual fund transactions, service requests, and investment reports, against options that name only one or two. Expect a question testing whether a specific investor-facing feature (say, a complaint, or a capital gains report) is one the platform covers.

Common exam traps

  • The platform is built jointly by all RTAs, not by a single RTA or by SEBI itself.
  • It spans four service categories — transactions, service requests, queries/complaints, and reports — a complete list is the safest answer to a "which of these" question.
  • The workbook gives no numeric limit, fee or threshold for the platform itself — do not invent one; the examinable content here is entirely about what the platform does.
  • All RTAs share joint responsibility for compliance, including system and cyber security audits, because it is a shared platform rather than any one RTA's private system.
  • This is distinct from MF Utility and MF Central, which are separately named industry platforms with their own specific roles — do not conflate the three.

Where this is taught

Free preparation for NISM Series II-B

Related terms

← All terms
Something look wrong? Report it