Common Account Number

An investor who owns funds from five different AMCs normally deals with five different sets of forms, five logins and five folio numbers. MF Utilities (MFU) is a transaction aggregating platform built to remove that friction — it connects investors, distributors, banks, RTAs and AMCs on one system.

When an investor registers on MFU, they are allotted a Common Account Number (CAN). Every mutual fund holding the investor maps to that one CAN, whichever AMC or RTA services the underlying folios.

KYC is the gate. An investor must be KYC compliant to register for a CAN; if they are not, MFU facilitates the KYC registration alongside the CAN allotment.

One form, many schemes. MFU offers a Common Transaction Form so an investor can transact in multiple schemes across participating mutual funds using a single form, submitted through a distributor or a neutral Point of Service, regardless of which RTA services the fund. A single payment can cover multiple subscriptions made under that one form.

Mapping and multiplicity. An investor's existing holdings are mapped to the CAN using PAN, holding pattern and other parameters — and because holding patterns differ (single, joint, first-holder variations), an investor can end up with more than one CAN.

One detail overrides another. The bank and nomination details given to MFU when registering for the CAN override whatever was on record in the individual folios. Getting this wrong on the MFU form silently changes where redemption proceeds go, even for folios opened years earlier through a different route.

Mr Ashok Verma holds mutual fund folios with four AMCs, opened over several years through three different distributors. He registers on MF Utilities.

1. MFU checks his KYC — already compliant, so no fresh KYC is triggered.
2. Based on his PAN and holding pattern, MFU maps his existing folios (all held singly, in his own name) to one CAN.
3. He fills a single Common Transaction Form to invest Rs 25,000 in a scheme from AMC A and Rs 15,000 in a scheme from AMC B, and makes one payment of Rs 40,000 covering both.
4. During registration he updates his bank account to a new one. From that point, redemption proceeds for every folio mapped to the CAN go to the new account — including a folio at AMC C that he never separately updated.

His wife also invests, but some of her units are held jointly with him and some singly. Because the holding pattern differs across her folios, MFU allots her two separate CANs — one for the singly-held folios, one for the jointly-held ones.

Chapter 6, section 6.3.3 (Aggregating platforms), alongside MFCentral and the stock exchange platforms (NMF II, BSE StAR MF). Expect a question on what a CAN consolidates (an investor's mutual fund holdings across AMCs), the KYC precondition, and the trap that CAN-level bank and nomination details override the folio-level ones.

• A CAN is not a folio number. A folio belongs to one AMC; a CAN sits above many folios across AMCs.
• One investor can have more than one CAN — MFU maps by PAN, holding pattern and mode of holding, and a change in any of those can mean a new CAN.
• KYC compliance is a precondition, not a byproduct — an investor who is not KYC compliant gets routed through KYC registration as part of CAN allotment.
• Bank and nomination details registered against the CAN override the folio's own records. This is the single most examinable trap in this section.
• MFU is a transaction aggregator; it does not replace the AMC or the RTA as the legal record-keeper of the units.