Deprecated: Optional parameter $content declared before required parameter $post is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/functions.php on line 840

Deprecated: Return type of WP_Theme::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 553

Deprecated: Return type of WP_Theme::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 594

Deprecated: Return type of WP_Theme::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 534

Deprecated: Return type of WP_Theme::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-theme.php on line 543

Warning: Private methods cannot be final as they are never overridden by other classes in /home/blogcert/public_html/wp-includes/class-wp-session-tokens.php on line 69

Deprecated: Optional parameter $object_id declared before required parameter $taxonomy is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/nav-menu.php on line 1060

Deprecated: Return type of WP_REST_Request::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 934

Deprecated: Return type of WP_REST_Request::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 954

Deprecated: Return type of WP_REST_Request::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 966

Deprecated: Return type of WP_REST_Request::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-request.php on line 977

Deprecated: Return type of WP_Block_List::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 151

Deprecated: Return type of WP_Block_List::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 175

Deprecated: Return type of WP_Block_List::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 164

Deprecated: Return type of WP_Block_List::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 186

Deprecated: Return type of WP_Block_List::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 138

Deprecated: Return type of WP_Block_List::offsetExists($index) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 75

Deprecated: Return type of WP_Block_List::offsetGet($index) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 89

Deprecated: Return type of WP_Block_List::offsetSet($index, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 110

Deprecated: Return type of WP_Block_List::offsetUnset($index) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 127

Deprecated: Return type of WP_Block_List::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-includes/class-wp-block-list.php on line 199

Deprecated: Optional parameter $block_name declared before required parameter $block_content is implicitly treated as a required parameter in /home/blogcert/public_html/wp-includes/blocks.php on line 405

Deprecated: Return type of WPCF7_FormTag::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 386

Deprecated: Return type of WPCF7_FormTag::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 378

Deprecated: Return type of WPCF7_FormTag::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 372

Deprecated: Return type of WPCF7_FormTag::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/plugins/contact-form-7/includes/form-tag.php on line 390

Warning: The magic method OCDI\OneClickDemoImport::__wakeup() must have public visibility in /home/blogcert/public_html/wp-content/plugins/one-click-demo-import/inc/OneClickDemoImport.php on line 128

Deprecated: Optional parameter $type declared before required parameter $wrapper is implicitly treated as a required parameter in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/class-fs-logger.php on line 145

Deprecated: Return type of FS_Key_Value_Storage::offsetExists($k) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 309

Deprecated: Return type of FS_Key_Value_Storage::offsetGet($k) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 317

Deprecated: Return type of FS_Key_Value_Storage::offsetSet($k, $v) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 301

Deprecated: Return type of FS_Key_Value_Storage::offsetUnset($k) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 313

Deprecated: Return type of FS_Key_Value_Storage::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 328

Deprecated: Return type of FS_Key_Value_Storage::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 339

Deprecated: Return type of FS_Key_Value_Storage::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 350

Deprecated: Return type of FS_Key_Value_Storage::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 362

Deprecated: Return type of FS_Key_Value_Storage::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 375

Deprecated: Return type of FS_Key_Value_Storage::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/blogcert/public_html/wp-content/themes/wp-sierra/freemius/includes/managers/class-fs-key-value-storage.php on line 389

Deprecated: trim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/blogcert/public_html/wp-includes/class-wp.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in /home/blogcert/public_html/wp-includes/wp-db.php on line 3008

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378

Warning: Cannot modify header information - headers already sent by (output started at /home/blogcert/public_html/wp-includes/class-wp-block-list.php:14) in /home/blogcert/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1378
{"id":6840,"date":"2024-10-03T05:09:56","date_gmt":"2024-10-03T05:09:56","guid":{"rendered":"https:\/\/blog.certifiedfinancialguardian.com\/?p=6840"},"modified":"2024-10-03T05:09:57","modified_gmt":"2024-10-03T05:09:57","slug":"sebi-to-tighten-disclosures-on-expenses-expense-ratio-returns-yields-and-risk-o-meter-for-mutual-funds","status":"publish","type":"post","link":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/2024\/10\/03\/sebi-to-tighten-disclosures-on-expenses-expense-ratio-returns-yields-and-risk-o-meter-for-mutual-funds\/","title":{"rendered":"SEBI to Tighten Disclosures on Expenses, Expense Ratio, Returns, Yields and Risk-o-Meter for Mutual Funds"},"content":{"rendered":"\n

The capital market regulator, the Securities and Exchange Board of India (SEBI)<\/a>, in order to facilitate enhanced transparency, make it easy to understand for investors, and standardise the approach towards disclosures by mutual funds, last week on September 27, 2024, released a consultation paper.<\/p>\n\n\n\n

In it certain changes have been proposed that shall help you, the investors make an informed investment decision. Here’s what the regulator has proposed.<\/p>\n\n\n\n

Disclosure of Expenses, Expense Ratio, Returns of Regular Plan and Direct Plan<\/strong><\/p>\n\n\n\n

Mutual funds, as you may know, are required [under Regulation 59 of SEBI (Mutual Funds) Regulations, 1996] to make half-yearly disclosure of unaudited financial results, which among others include recurring expenses, expense ratios<\/a>, returns and compounded annualised yield.<\/p>\n\n\n\n

At present, this is mandatory for the Regular Plan of mutual fund schemes. But considering that the expense ratio of the Regular Plan and Direct Plan<\/a> is different, the regulator has proposed that the expenses and the expense ratio of the Direct Plan also be disclosed in standard format.<\/p>\n\n\n\n

Notably, mutual fund distributors usually suggest to investors the type of schemes they should consider investing in and often provide a Regular Plan as the default option.<\/p>\n\n\n\n

Similarly, there are some investors who seek the services of an investment advisor, who are allowed to recommend only Direct Plan of mutual fund schemes.<\/p>\n\n\n\n

Likewise, some investors prefer to invest directly with the fund houses or through online platforms offering Direct Plans.<\/p>\n\n\n\n

[Read: 5 Best Active Equity Mutual Funds with Low Expense Ratio And High Returns<\/a>]<\/p>\n\n\n\n

You see, the difference in the expense ratio of the Direct plan and Regular plan of diversified equity mutual funds ranges from 0.4% to 2%, with an average difference of about 1.2%.<\/p>\n\n\n\n

Now while a marginal difference may not seem much at the outset, over the longer investment horizon, it does make a difference in the corpus you can build — thanks to the power of compounding.<\/p>\n\n\n\n

Table 1: Difference in Expense Ratio and Impact on Your Wealth<\/em><\/strong><\/p>\n\n\n\n

\n
\n\n\t\n\t\t\n\t\t\t\n\t\t\t\n\t\t\t
Particulars<\/td>\n\t\t\tDirect Plan (in Rs)<\/td>\n\t\t\tRegular Plan with 0.5% higher Exp. Ratio (in Rs)<\/td>\n\t\t\tRegular Plan with 1% higher Exp. Ratio (in Rs)<\/td>\n\t\t<\/tr>\n\t\t
Amount invested<\/b><\/td>\n\t\t\t10,00,000<\/td>\n\t\t\t10,00,000<\/td>\n\t\t\t10,00,000<\/td>\n\t\t<\/tr>\n\t\t
Value after 30 years<\/b><\/td>\n\t\t\t29,959,922<\/td>\n\t\t\t26,196,666<\/td>\n\t\t\t22,892,297<\/td>\n\t\t<\/tr>\n\t<\/tbody>\n<\/table>\n<\/div>\n<\/center>\n\n\n\n\n

For illustration purposes only.<\/p>\n\n\n\n

The table above illustrates how a small difference in the expense ratio could weigh on the corpus. At the end of a 30-year period, the corpus under the Direct plan would have appreciated to nearly Rs 3 crore in the example above.<\/p>\n\n\n\n

[Read: Direct vs Regular Plan: Can Expense Ratio Make Significant Difference to Your Mutual Fund Returns?<\/a>]<\/p>\n\n\n\n

Considering these finer points, which often investors overlook, the regulator vide the consultation paper has also proposed that mutual fund houses make separate disclosure returns during the half year and compounded annualised yields for both Regular Plan and Direct Plan.<\/p>\n\n\n\n

To standardise the above disclosures, it is said that the format for half-yearly financial statements for mutual fund schemes shall be reviewed and finalised by the Association of Mutual Funds in India (AMFI)<\/a>, in consultation with SEBI.<\/p>\n\n\n\n

Enhanced Disclosure of Risk-o-meter:<\/strong><\/p>\n\n\n\n

The regulatory guideline makes it mandatory for mutual funds to depict the risk of the scheme through a pictorial illustration of a meter, called the Risk-o-meter.<\/p>\n\n\n\n

SEBI introduced the Risk-o-meter in July 2015, as a replacement to its earlier colour code labelling.<\/a> All mutual funds are now mandated to publish a Risk-o-meter at the beginning of all scheme-related documents.<\/p>\n\n\n\n

The current Risk-o-meters provides a visual description of the risk involved in a scheme, ranging from low, low to moderate, moderate, moderately high, high, and very high.<\/p>\n\n\n\n

To further enhance the pictorial representation of risk, it is proposed by the regulator that the Risk-o-meter should be colour-coded as low risk in Irish Green, low to moderate risk in Chartreuse, moderate risk in Neon Yellow, moderately high risk in Caramel, high risk in Dark Orange, and very high risk in Red.<\/p>\n\n\n\n

\"\"<\/p>\n\n\n\n

For illustration purposes only
(Image source:\u00a0
SEBI Consultation Paper, September 27, 2024<\/a>)<\/p>\n\n\n\n

For example, as illustrated above, the risk depicted by the Risk-o-meter in the above case is, moderately high.<\/p>\n\n\n\n

[Read: Are You Setting Your Risk-Return Expectations Right While Investing in Mutual Funds?<\/a>]<\/p>\n\n\n\n

If there is any change in the Risk-o-meter, the regulator has proposed that this should be communicated to the unitholders of that particular scheme by way of a Notice cum Addendum as well as an e-mail or SMS.<\/p>\n\n\n\n

To standardise the format of the disclosure and for ease of understanding of the change in the level of risk for unitholders of that particular scheme, the regulator has also proposed that mutual funds shall disclose the existing Risk-o-meter along with the revised Risk-o-meter (adjacent to existing one).<\/p>\n\n\n\n

At present, the SEBI’s consultation paper is open for public comments. The comments or suggestions can be submitted latest by October 18, 2024, through this link-
https:\/\/www.sebi.gov.in\/sebiweb\/publiccommentv2\/PublicCommentAction.do?doPublicComments=yes<\/a>.<\/p>\n\n\n\n

At PersonalFN, we believe that given that individual investors are gradually choosing the Direct Plan of mutual funds<\/a>, and for the Risk-o-meter to truly depict the risk a scheme carries with meaningful colour codes, the regulator has taken steps in the right direction in the interest of investors to make an informed choice.<\/p>\n\n\n\n

SEBI is continually taking measures for the well-being of investors at large with constructive feedback from the Indian mutual fund industry.<\/p>\n\n\n\n

Nevertheless, ensure that you are investing in mutual funds considering your age, risk profile, broader investment objective, envisioned financial goals, and time in hand before those goals befall by following a sensible asset allocation<\/a> rather than investing in an ad hoc manner.<\/p>\n\n\n\n

If you have any doubt about selecting suitable mutual fund schemes for your portfolio (or any other investment product for that matter), don’t hesitate to seek the help of SEBI-registered investment advisors who can guide you throughout your investment journey.<\/p>\n\n\n\n

Be a thoughtful investor.<\/p>\n\n\n\n

Happy Investing!<\/p>\n\n\n\n

This article first appeared on PersonalFN\u00a0here<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

The capital market regulator, the Securities and Exchange Board of India (SEBI), in order to facilitate enhanced transparency, make it easy to understand for investors, and standardise the approach towards disclosures by mutual funds, last week on September 27, 2024, released a consultation paper. In it certain changes have been proposed that shall help you, the…<\/p>\n","protected":false},"author":2,"featured_media":6843,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"cybocfi_hide_featured_image":""},"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/posts\/6840"}],"collection":[{"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/comments?post=6840"}],"version-history":[{"count":1,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/posts\/6840\/revisions"}],"predecessor-version":[{"id":6844,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/posts\/6840\/revisions\/6844"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/media\/6843"}],"wp:attachment":[{"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/media?parent=6840"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/categories?post=6840"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.certifiedfinancialguardian.com\/index.php\/wp-json\/wp\/v2\/tags?post=6840"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}