Statement of accounts after each mutual fund transaction
The statement of accounts (SOA) issued after each mutual fund transaction is a regulatory document dispatched by the Registrar and Transfer Agent (RTA) – CAMS or KFintech – to the investor within five business days of processing any transaction on a folio. It confirms the details of the transaction (amount, NAV, units) and displays the updated unit balance post-transaction. The SOA is the investor’s primary real-time acknowledgement that a mutual fund transaction has been correctly processed and recorded on the folio.
The post-transaction SOA is distinct from the periodic Consolidated Account Statement (CAS), which is issued monthly (if a transaction occurred) or half-yearly. The SOA is an immediate, transaction-specific confirmation.
Regulatory basis
Regulation 36 of the SEBI (Mutual Funds) Regulations, 1996 requires AMCs to send an account statement to investors “as soon as practicable” after a transaction. SEBI circulars have progressively tightened this:
- SEBI circular SEBI/IMD/CIR No.7/13239/03 (2003): Required account statements within three working days for electronic transactions.
- SEBI circular CIR/IMD/DF/16/2011 (8 August 2011): Specified that for the first SIP instalment, the statement must be dispatched within ten working days, and for subsequent SIP instalments, the annual CAS (or the half-yearly CAS) suffices rather than individual SOAs per instalment.
- SEBI circular SEBI/HO/IMD/DF2/CIR/P/2021/024 (4 March 2021): Revised and consolidated the SOA dispatch requirements, confirming the five-business-day window.
Transaction types that trigger an SOA
An SOA is dispatched for every transaction type, including:
- Purchase (lump sum): New investment or additional investment in an existing folio
- First SIP instalment: The first instalment of a new SIP mandate
- Redemption: Full or partial redemption of units
- Switch-out and switch-in: Both legs of a switch transaction each trigger an SOA from the respective scheme
- STP debit and credit: Each Systematic Transfer Plan transaction generates SOAs for both source and destination schemes
- SWP: Each Systematic Withdrawal Plan payment generates an SOA
- IDCW payout: If units change due to dividend reinvestment, an SOA is generated
- Folio-level changes: KYC update confirmation, nominee change, bank account change
For ongoing SIP instalments (after the first), SEBI permits the periodic CAS to substitute for individual SOAs, so investors with monthly SIPs will not receive an SOA for each SIP instalment after the first – they receive the monthly CAS instead.
Contents of a post-transaction SOA
A typical SOA contains:
| Field | Description |
|---|---|
| Investor name and folio | Identifies the investor and folio |
| PAN | As registered on the folio |
| Transaction type | Purchase, redemption, switch, IDCW, etc. |
| Transaction date | The business day on which the transaction was processed |
| Applicable NAV | NAV used for the transaction |
| Amount | Rupee amount of the transaction |
| Units transacted | Units purchased, redeemed, or switched |
| Exit load deducted (if any) | Exit load amount deducted on redemption |
| Units before transaction | Unit balance before this transaction |
| Units after transaction | Unit balance after this transaction |
| Redemption proceeds | For redemptions, the net amount dispatched to the investor’s bank account |
| Bank account details (last 4 digits) | Bank account to which redemption proceeds are credited |
| Processing date | Date the transaction was processed (may differ from trade date) |
Delivery modes
SOAs are dispatched:
- By e-mail: To the registered e-mail address on the folio. This is the default mode for investors who have provided an e-mail address.
- By post: A physical SOA is dispatched by post for investors without a registered e-mail address, or on explicit request.
- Push notification: Platforms such as Zerodha Coin or Groww send app/SMS notifications for transactions placed through them, supplementing the RTA-generated SOA.
The SOA PDF is password-protected; the standard password is the first holder’s PAN in uppercase.
SOA as a transaction record
The SOA is the investor’s primary documentary evidence that a transaction was processed at a specific NAV on a specific date. It is important to retain SOAs for:
- Tax purposes: The SOA for a purchase confirms the acquisition date and cost for capital gains computation. The SOA for a redemption confirms the redemption date and proceeds.
- Dispute resolution: If a transaction is disputed (e.g., wrong NAV applied, wrong units allotted), the SOA is the reference document for raising a complaint with the AMC, RTA, or the SEBI SCORES (Complaints Redress System) portal.
- Loan documentation: Banks and NBFCs may request recent SOAs as proof of fresh mutual fund investments offered as collateral.
SOA vs CAS vs account statement
| Document | Trigger | Coverage | Frequency |
|---|---|---|---|
| SOA (post-transaction) | Each transaction | Single transaction details | After each transaction |
| CAS (CAMS/KFin) | Month with transaction + half-yearly | All folios, full transaction history | Monthly or half-yearly |
| Detailed account statement | On demand | Full folio history | As requested |
See also
- Consolidated Account Statement (CAS)
- CAMS mutual fund account statement
- KFintech mutual fund account statement
- IDCW intimation
- ITR-ready capital gains statement
- Mutual fund
References
- SEBI (Mutual Funds) Regulations, 1996, Regulation 36 – Account statement obligations.
- SEBI circular SEBI/HO/IMD/DF2/CIR/P/2021/024, 4 March 2021 – SOA dispatch timeline consolidation.
- SEBI circular CIR/IMD/DF/16/2011, 8 August 2011 – SIP statement requirements.
- CAMS and KFin investor services documentation (accessed May 2026).