<!DOCTYPE html>
<html lang="en" dir="ltr">
  <head>
    <meta charset="utf-8" />
<meta name="keywords" content="investment company, liquidity risk management" />
<meta name="MobileOptimized" content="width" />
<meta name="HandheldFriendly" content="true" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="id" content="119321" />
<meta name="date" content="2017-11-15T17:39:13" />
<link rel="icon" href="/themes/custom/secgov/favicon.ico" type="image/vnd.microsoft.icon" />
<link rel="canonical" href="https://www.sec.gov/investment/investment-company-liquidity-risk-management-programs-faq" />
<link rel="shortlink" href="https://www.sec.gov/node/119321" />
<script src="/files/google_tag/primary/google_tag.script.js?sdd43i" defer></script>

    <meta name="origin" content="Drupal" />
    <meta name="viewport" content="width=device-width initial-scale=1.0 maximum-scale=3.0" />
    <title>SEC.gov | Investment Company Liquidity Risk Management Programs Frequently Asked Questions</title>
    <script>window.env = "production";</script>
    <link rel="stylesheet" media="all" href="/files/css/css_MgRniMmnJVbkRMwT8X_aLg7R7z2Tz56uxCoOh0R4Evk.css?delta=0&language=en&theme=secgov&include=eJxljV0OwiAQhC_UypHIQjcU3XYbZmnE00ujvOjjfPMn1LSaDzXLwsXHCtMtv7i4JBpIZliTvKcJHH1hYQLDjRhZ1h0TGow3F7p35ZKeox2BH3LHvDL1rz8-gB7X6gfx0_r7wy2lHiS3r3wDgW9G2g" />
<link rel="stylesheet" media="all" href="/files/css/css_qIRHHeJDFCaUMjFbMXXKyB9RwPkpu4bJePyRBSpUie4.css?delta=1&language=en&theme=secgov&include=eJxljV0OwiAQhC_UypHIQjcU3XYbZmnE00ujvOjjfPMn1LSaDzXLwsXHCtMtv7i4JBpIZliTvKcJHH1hYQLDjRhZ1h0TGow3F7p35ZKeox2BH3LHvDL1rz8-gB7X6gfx0_r7wy2lHiS3r3wDgW9G2g" />

    <script src="/files/js/js_ZR7IgTyJkG8aareVUdeKuOQQtTr88wGWJyAHxg0IbaA.js?scope=header&delta=0&language=en&theme=secgov&include=eJxljV0OwiAQhC_UypHIQjcU3XYbZmnE00ujvOjjfPMn1LSaDzXLwsXHCtMtv7i4JBpIZliTvKcJHH1hYQLDjRhZ1h0TGow3F7p35ZKeox2BH3LHvDL1rz8-gB7X6gfx0_r7wy2lHiS3r3wDgW9G2g"></script>

  <script >bazadebezolkohpepadr="661965948"</script><script type="text/javascript" src="https://www.sec.gov/akam/13/2774cf19"  defer></script></head>
  <body class="default-view path-node node--type-secarticle">

    <a href="#main-content" class="visually-hidden focusable" tabindex="1">
      Skip to main content
    </a>
    <noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-TD3BKV" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
      <div class="dialog-off-canvas-main-canvas" data-off-canvas-main-canvas>
    


<div class="page-container">
<div id="page-wrapper">
  <div id="page" >
    <div class="page-header" role="banner">
      <div class="header-content">
        <div id="global-header" class="region region-header">
    
<div id="block-digitalgovsearch" class="block global-header-digitalgov-search">
  
    
        <div class="body"><!--<div class="hide-for-small" id="global-search">
<form accept-charset="UTF-8" action="//secsearch.sec.gov/search" class="clearfix" id="global-search-form" method="get" name="form_iQueryForm">
<fieldset><legend></legend> <label class="overlabel" for="global-search-box">Search SEC.gov</label> <input name="utf8" type="hidden" value="?" /> <input class="affiliate" name="affiliate" type="hidden" value="secsearch" /> <input aria-autocomplete="list" aria-haspopup="true" autocomplete="off" class="usagov-search-autocomplete ui-autocomplete-input" id="global-search-box" name="query" role="textbox" tabindex="4" title="Search for" type="text" /> <span aria-hidden="true" class="button-label fa fa-search"> </span><input class="global-search-button" tabindex="5" title="Go" type="submit" value="" /></fieldset>
</form>

<p class="options"><a class="option-link" href="http://www.sec.gov/edgar/searchedgar/companysearch.html" tabindex="6">Company Filings</a> | <a class="option-link" href="http://www.sec.gov/search/search.htm" tabindex="7">More Search Options</a></p>
</div>-->
<div class="block block--search block--search-form" id="global-search" role="search">
<form accept-charset="UTF-8" action="//secsearch.sec.gov/search" class="clearfix" id="global-search-form" method="get" name="form_iQueryForm">
<fieldset><legend></legend>
<div class="search-box-container"><label class="overlabel" for="global-search-box">Search SEC.gov</label> <input name="utf8" type="hidden" value="?" /> <input class="affiliate" name="affiliate" type="hidden" value="secsearch" /> <input aria-autocomplete="list" aria-haspopup="true" autocomplete="off" class="usagov-search-autocomplete ui-autocomplete-input" id="global-search-box" name="query" role="textbox" title="Search for" type="text" /> <span aria-hidden="true" class="button-label fa fa-search"> </span> <input class="global-search-button" title="Go" type="submit" value="" /></div>
</fieldset>
</form>

<div class="menu-name-menu-utility-menu">
<p class="options"><span><a class="option-link" href="/edgar/searchedgar/companysearch">Company Filings</a></span> <!--<span><a class="option-link" href="http://www.sec.gov/search/search.htm">More Search Options</a></span>--></p>
</div>
</div>
</div>
  </div>
<div id="block-secgov-branding" class="site-branding block region__inner system_branding_block">
  <div class="block--menu-block">
    <div class="menu-block-wrapper menu-name-main-menu">
      
            
      
    <div class="banner-seal">
    <a href="/" title="SEC Emblem" rel="home" tabindex="2">
      <img src="/files/sec-logo.png" alt="SEC Emblem" />
    </a>
  </div>
  
    <div class="banner-org-name">
      <a href="/" title="U.S. Securities and Exchange Commission" rel="home" tabindex="3">U.S. Securities and <br>Exchange Commission</a>
  </div>
   

    <button id="mobile-menu-toggle" class="is-closed" aria-label="Menu Toggle">
    <span class="svg-icon svg-icon-sm" aria-hidden="true">q</span>
  </button>

    </div>
  </div>
</div>
  </div>


      </div>

      <div class="global-navigation" id="global-navigation">

        <div class="desktop-menu">
            <div class="navigation-wrapper region region-global-navigation">
    <div id="block-secgov-main-menu" class="block region__inner main">
  <div class="block--menu-block">
    <div class="menu-block-wrapper menu-name-main-menu">
      
            
          
    
              <ul id="home-menu" class="menu">
                          <li class="menu__item is-expanded expanded" >
                <a href="/about" title="About" class="menu__link">About</a>
                                <ul class="menu">
                          <li class="menu__item is-active is-leaf leaf ">
                <a href="/about/careers" title="Careers" class="menu__link">Careers</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/about/commissioners" title="Commissioners" class="menu__link">Commissioners</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/contact-information/sec-directory" title="Contact" class="menu__link">Contact</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/reports" title="Reports and Publications" class="menu__link">Reports and Publications</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/about/about-securities-laws" title="Securities Laws" class="menu__link">Securities Laws</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/about/mission" title="Mission" class="menu__link">Mission</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/about/commission-votes" title="Commission Votes" class="menu__link">Commission Votes</a>
              </li>
        </ul>
  
              </li>
                    <li class="menu__item is-expanded expanded" >
                <a href="/about/divisions" title="Divisions & Offices" class="menu__link">Divisions & Offices</a>
                                <ul class="menu">
                          <li class="menu__item is-active is-leaf leaf ">
                <a href="/page/corpfin-section-landing" title="Corporation Finance" class="menu__link">Corporation Finance</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/page/enforcement-section-landing" title="Enforcement" class="menu__link">Enforcement</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/investment-management" title="Investment Management" class="menu__link">Investment Management</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/dera" title="Economic and Risk Analysis" class="menu__link">Economic and Risk Analysis</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/divisions/trading-markets" title="Trading and Markets" class="menu__link">Trading and Markets</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/page/aljsectionlanding" title="Office of Administrative Law Judges" class="menu__link">Office of Administrative Law Judges</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/exams" title="Examinations" class="menu__link">Examinations</a>
              </li>
        </ul>
  
              </li>
                    <li class="menu__item is-expanded expanded" >
                <a href="/page/litigation" title="Enforcement" class="menu__link">Enforcement</a>
                                <ul class="menu">
                          <li class="menu__item is-active is-leaf leaf ">
                <a href="/litigation/litreleases" title="Litigation Releases" class="menu__link">Litigation Releases</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/litigation/admin" title="Administrative Proceedings" class="menu__link">Administrative Proceedings</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/litigation/opinions" title="Opinions and Adjudicatory Orders" class="menu__link">Opinions and Adjudicatory Orders</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/divisions/enforce/friactions" title="Accounting and Auditing" class="menu__link">Accounting and Auditing</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/litigation/suspensions" title="Trading Suspensions" class="menu__link">Trading Suspensions</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/enforcement/how-investigations-work" title="How Investigations Work" class="menu__link">How Investigations Work</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/divisions/enforce/receiverships" title="Receiverships" class="menu__link">Receiverships</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/enforce/information-for-harmed-investors" title="Information for Harmed Investors" class="menu__link">Information for Harmed Investors</a>
              </li>
        </ul>
  
              </li>
                    <li class="menu__item is-expanded expanded" >
                <a href="/page/regulation" title="Regulation" class="menu__link">Regulation</a>
                                <ul class="menu">
                          <li class="menu__item is-active is-leaf leaf ">
                <a href="/rules/rulemaking-activity" title="Rulemaking Activity" class="menu__link">Rulemaking Activity</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/rules/rulemaking-activity?aId=&search=&rulemaking_status=178631&division_office=All&regulation_year=" title="Proposed Rules" class="menu__link">Proposed Rules</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/rules/rulemaking-activity?aId=&search=&rulemaking_status=177456&division_office=All&regulation_year=" title="Final Rules" class="menu__link">Final Rules</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/rules/rulemaking-activity?aId=&search=&rulemaking_status=178151&division_office=All&regulation_year=" title="Interim Final Temporary Rules" class="menu__link">Interim Final Temporary Rules</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/rules/other" title="Other Orders and Notices" class="menu__link">Other Orders and Notices</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/rules/sro" title="Self-Regulatory Organizations" class="menu__link">Self-Regulatory Organizations</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/regulation/staff-interpretations" title="Staff Interpretations" class="menu__link">Staff Interpretations</a>
              </li>
        </ul>
  
              </li>
                    <li class="menu__item is-expanded expanded" >
                <a href="/education" title="Education" class="menu__link">Education</a>
                                <ul class="menu">
                          <li class="menu__item is-active is-leaf leaf ">
                <a href="/education/investor-education" title="Investor Education" class="menu__link">Investor Education</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/education/glossary" title="Glossaries" class="menu__link">Glossaries</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/education/smallbusiness" title="Small Business Capital Raising " class="menu__link">Small Business Capital Raising </a>
              </li>
        </ul>
  
              </li>
                    <li class="menu__item is-expanded expanded" >
                <a href="/edgar" title="Filings" class="menu__link">Filings</a>
                                <ul class="menu">
                          <li class="menu__item is-active is-leaf leaf ">
                <a href="/edgar/search-and-access" title="EDGAR – Search & Access" class="menu__link">EDGAR – Search & Access</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/edgar/filer-information" title="EDGAR – Information for Filers" class="menu__link">EDGAR – Information for Filers</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/edgar/searchedgar/companysearch" title="Company Filing Search" class="menu__link">Company Filing Search</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/filings/edgar-guide" title="How to Search EDGAR" class="menu__link">How to Search EDGAR</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/forms" title="Forms List" class="menu__link">Forms List</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/edgar/about" title="About EDGAR" class="menu__link">About EDGAR</a>
              </li>
        </ul>
  
              </li>
                    <li class="menu__item is-expanded expanded" >
                <a href="/newsroom" title="News" class="menu__link">News</a>
                                <ul class="menu">
                          <li class="menu__item is-active is-leaf leaf ">
                <a href="/news/pressreleases" title="Press Releases" class="menu__link">Press Releases</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/news/speeches-statements" title="Speeches and Statements" class="menu__link">Speeches and Statements</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/securities-topics" title="Securities Topics" class="menu__link">Securities Topics</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/news/upcoming-events" title="Upcoming Events" class="menu__link">Upcoming Events</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/news/sec-webcasts" title="Webcasts" class="menu__link">Webcasts</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/news/sec-videos" title="SEC Videos" class="menu__link">SEC Videos</a>
              </li>
                    <li class="menu__item is-active is-leaf leaf ">
                <a href="/news/media-gallery" title="Media Gallery" class="menu__link">Media Gallery</a>
              </li>
        </ul>
  
              </li>
        </ul>
  

  
    </div>
  </div>
</div>
  </div>


        </div>

        <div class="mobile-menu" style="display: none;">
          
              <ul id="main-menu" class="menu">
                      <li class="menu__item is-expanded expanded">
      
        <a href="" class="menu__link">U.S. Securities and Exchange Commission</a>
                                <ul class="menu">
                      <li class="menu__item is-active is-leaf leaf">
      
        <a href="/about/divisions" class="menu__link" data-drupal-link-system-path="node/91856">Divisions & Offices</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/litigation.shtml" class="menu__link">Enforcement</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/rules.shtml" class="menu__link">Regulation</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/education" title="Education" class="menu__link" data-drupal-link-system-path="node/261726">Education</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/edgar" class="menu__link" data-drupal-link-system-path="node/91901">Filings</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/news" class="menu__link">Newsroom</a>
              </li>

        </ul>
  
              </li>

                  <li class="menu__item is-expanded expanded">
      
        <a href="/news" class="menu__link">Newsroom</a>
                                <ul class="menu">
                      <li class="menu__item is-active is-leaf leaf">
      
        <a href="/news/pressreleases" class="menu__link" data-drupal-link-system-path="news/pressreleases">Press Releases</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/news/testimony" class="menu__link">Testimony</a>
              </li>

        </ul>
  
              </li>

                  <li class="menu__item is-expanded expanded">
      
        <a href="/about/sec-rss" class="menu__link" data-drupal-link-system-path="node/111801">RSS Feeds</a>
                                <ul class="menu">
                      <li class="menu__item is-active is-leaf leaf">
      
        <a href="/news/pressreleases.rss" class="menu__link" data-drupal-link-system-path="news/pressreleases.rss">Press Releases</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/news/statements.rss" class="menu__link" data-drupal-link-system-path="news/statements.rss">Public Statements</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/news/speeches.rss" class="menu__link" data-drupal-link-system-path="news/speeches.rss">Speeches</a>
              </li>

                  <li class="menu__item is-active is-leaf leaf">
      
        <a href="/news/testimony.rss" class="menu__link" data-drupal-link-system-path="news/testimony.rss">Testimony</a>
              </li>

        </ul>
  
              </li>

        </ul>
  



                          <div id="local-nav">
    <nav role="navigation" aria-labelledby="block-im-menu" id="block-im">
            
  <h2 class="visually-hidden" id="block-im-menu">Investment Management</h2>
  

        
              <ul class="section-menu menu">
              <li class="menu__item is-active is-leaf leaf item-divisions-and-offices">
        <a href="/about/divisions" title="Divisions and Offices" class="menu__link" data-drupal-link-system-path="node/91856">Divisions and Offices</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-investment-management-">
        <a href="/investment-management" title="Investment Management " class="menu__link" data-drupal-link-system-path="node/160546">Investment Management </a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-im-senior-officers">
        <a href="/im-senior-officers" title="IM Senior Officers" class="menu__link" data-drupal-link-system-path="node/297551">IM Senior Officers</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-disclosure">
        <a href="/investment/fund-disclosure-at-a-glance" title="Disclosure" class="menu__link" data-drupal-link-system-path="node/123186">Disclosure</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-guidance-">
        <a href="/divisions/investment/guidance.shtml" title="Guidance " class="menu__link">Guidance </a>
                                <ul class="menu">
              <li class="menu__item is-active is-leaf leaf item-topical-reference-guide">
        <a href="/divisions/investment/topical-reference-guide" title="Topical Reference Guide" class="menu__link" data-drupal-link-system-path="divisions/investment/topical-reference-guide">Topical Reference Guide</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-staff-letters">
        <a href="/investment/investment-management-no-action-letters" title="Staff Letters" class="menu__link" data-drupal-link-system-path="node/192601">Staff Letters</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-guidance-updates">
        <a href="/investment/im-guidance-updates" title="Guidance Updates" class="menu__link" data-drupal-link-system-path="node/93066">Guidance Updates</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-information-updates">
        <a href="/about/divisions-offices/division-investment-management/information-updates" class="menu__link" data-drupal-link-system-path="node/93071">Information Updates</a>
              </li>

        </ul>
  

              </li>

          <li class="menu__item is-active is-leaf leaf item-rules">
        <a href="/investment/laws-and-rules" title="Rules" class="menu__link" data-drupal-link-system-path="node/151201">Rules</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-orders-&-notices">
        <a href="/investment/litigation" title="Orders & Notices" class="menu__link" data-drupal-link-system-path="node/85891">Orders & Notices</a>
                                <ul class="menu">
              <li class="menu__item is-active is-leaf leaf item-notices-of-effectiveness">
        <a href="https://www.sec.gov/cgi-bin/browse-edgar?action=geteffect" title="Notices of Effectiveness" class="menu__link">Notices of Effectiveness</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-investment-company-act-">
        <a href="https://www.sec.gov/rules/icreleases.shtml" title="Investment Company Act " class="menu__link">Investment Company Act </a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-investment-advisers-act-">
        <a href="/rules/iareleases" title="Investment Advisers Act " class="menu__link" data-drupal-link-system-path="node/336711">Investment Advisers Act </a>
              </li>

        </ul>
  

              </li>

          <li class="menu__item is-active is-leaf leaf item-data">
        <a href="/investment/analytics-office" title="Data" class="menu__link" data-drupal-link-system-path="node/164646">Data</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-forms">
        <a href="/forms" title="Forms" class="menu__link" data-drupal-link-system-path="forms">Forms</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-contact-">
        <a href="/about/divisions-offices/division-investment-management/contact" title="Contact " class="menu__link" data-drupal-link-system-path="node/91906">Contact </a>
              </li>

        </ul>
  





  </nav>

  </div>

                  </div>

      </div>
    </div>
          <div class="highlighted">
        <aside role="complementary" class="message section clearfix">
            <div class="region region-highlighted">
    <div data-drupal-messages-fallback class="hidden"></div>

  </div>


        </aside>
      </div>
    
    
                                
        
        
        
    
    <div class="page-content">
      <div id="main-wrapper" class="layout-main-wrapper layout-container clearfix">

                  

      
      
            <div id="sidebar-first" class="sidebar">
          <aside role="complementary" class="local-nav">
            <nav role="navigation">
                              <div id="local-nav">
    <nav role="navigation" aria-labelledby="block-im-menu" id="block-im">
            
  <h2 class="visually-hidden" id="block-im-menu">Investment Management</h2>
  

        
              <ul class="section-menu menu">
              <li class="menu__item is-active is-leaf leaf item-divisions-and-offices">
        <a href="/about/divisions" title="Divisions and Offices" class="menu__link" data-drupal-link-system-path="node/91856">Divisions and Offices</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-investment-management-">
        <a href="/investment-management" title="Investment Management " class="menu__link" data-drupal-link-system-path="node/160546">Investment Management </a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-im-senior-officers">
        <a href="/im-senior-officers" title="IM Senior Officers" class="menu__link" data-drupal-link-system-path="node/297551">IM Senior Officers</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-disclosure">
        <a href="/investment/fund-disclosure-at-a-glance" title="Disclosure" class="menu__link" data-drupal-link-system-path="node/123186">Disclosure</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-guidance-">
        <a href="/divisions/investment/guidance.shtml" title="Guidance " class="menu__link">Guidance </a>
                                <ul class="menu">
              <li class="menu__item is-active is-leaf leaf item-topical-reference-guide">
        <a href="/divisions/investment/topical-reference-guide" title="Topical Reference Guide" class="menu__link" data-drupal-link-system-path="divisions/investment/topical-reference-guide">Topical Reference Guide</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-staff-letters">
        <a href="/investment/investment-management-no-action-letters" title="Staff Letters" class="menu__link" data-drupal-link-system-path="node/192601">Staff Letters</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-guidance-updates">
        <a href="/investment/im-guidance-updates" title="Guidance Updates" class="menu__link" data-drupal-link-system-path="node/93066">Guidance Updates</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-information-updates">
        <a href="/about/divisions-offices/division-investment-management/information-updates" class="menu__link" data-drupal-link-system-path="node/93071">Information Updates</a>
              </li>

        </ul>
  

              </li>

          <li class="menu__item is-active is-leaf leaf item-rules">
        <a href="/investment/laws-and-rules" title="Rules" class="menu__link" data-drupal-link-system-path="node/151201">Rules</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-orders-&-notices">
        <a href="/investment/litigation" title="Orders & Notices" class="menu__link" data-drupal-link-system-path="node/85891">Orders & Notices</a>
                                <ul class="menu">
              <li class="menu__item is-active is-leaf leaf item-notices-of-effectiveness">
        <a href="https://www.sec.gov/cgi-bin/browse-edgar?action=geteffect" title="Notices of Effectiveness" class="menu__link">Notices of Effectiveness</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-investment-company-act-">
        <a href="https://www.sec.gov/rules/icreleases.shtml" title="Investment Company Act " class="menu__link">Investment Company Act </a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-investment-advisers-act-">
        <a href="/rules/iareleases" title="Investment Advisers Act " class="menu__link" data-drupal-link-system-path="node/336711">Investment Advisers Act </a>
              </li>

        </ul>
  

              </li>

          <li class="menu__item is-active is-leaf leaf item-data">
        <a href="/investment/analytics-office" title="Data" class="menu__link" data-drupal-link-system-path="node/164646">Data</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-forms">
        <a href="/forms" title="Forms" class="menu__link" data-drupal-link-system-path="forms">Forms</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-contact-">
        <a href="/about/divisions-offices/division-investment-management/contact" title="Contact " class="menu__link" data-drupal-link-system-path="node/91906">Contact </a>
              </li>

        </ul>
  





  </nav>

  </div>

                      </nav>

          </aside>
        </div>
                    <div id="content-wrapper" class="layout-main">

      <a id="main-content" tabindex="-1"></a>

    
    		
    
    
              <div id="content" class="content">
            <div class="main-content region region-content">
    <div id="block-secgov-content">
  
    
      
  
  <article class="article" role="article">
  
    

    <div class="article-content">
                




                    
<div id="page-title">
<h1 class="article-type">
  
        
                                                                                                                                                                                                          
                                    <span class="hide">Other</span>
                                    
                                                                                                                                    </h1>
<!-- Subscribe link, RSS, Email -->
<div id="addthis-icons">
  <div class="addthis-wrapper">
    <div class="hide-for-print appIconsDetail" style="visibility: visible;">
      <div class="addthis_toolbox addthis_default_style hide-for-small" data-ui-click="true">
        <a class="addthis_button_print at300b" title="Print Page" href="#" tabindex="0">
          <span class="fa fa-print"></span>
        </a>
        <a class="addthis_button_mailto at300b" target="_blank" title="Email Page" href="#" tabindex="0">
          <span class="fa fa-envelope"></span>
        </a>
      <div class="atclear"></div>
    </div>
    <div class="addthis_toolbox addthis_default_style addthis_32x32_style hide-for-medium-up show-for-small addthis_mobile">
      <a class="addthis_button_mailto at300b" target="_blank" title="Email Page" href="#" tabindex="0">
        <span class="fa fa-envelope"></span>
      </a>
    </div>
    <div class="atclear"></div>
    </div>
  </div>
</div>
</div>

              <div class="content aside other">
              
        <div >
        <h1 class="article-title">Investment Company Liquidity Risk Management Programs Frequently Asked Questions</h1>
                </div>

        
                  <p class="article-publishdate">
                            Nov. 15, 2017
                       </p>
        
                <p class="release-number"></p>
              
      <div class="article-content-body">
      
            <div class="article-body"><p>The staff of the Division of Investment Management has prepared the following responses to questions related to the investment company liquidity risk management (“LRM”) program requirements adopted in October 2016 and expects to update this document from time to time to include responses to additional questions. These responses represent the views of the staff of the Division of Investment Management. They are not a rule, regulation, or statement of the Commission, and the Commission has neither approved nor disapproved this information. The Adopting Release for investment company LRM programs (“Adopting Release”) is available at: https://www.sec.gov/rules/final/2016/33-10233.pdf. We define “rule” as Rule 22e-4 under the Investment Company Act.</p>

<h2>Sub-Advised Funds</h2>

<p><strong>1. Q. The rule defines “person(s) designated to administer the program” as “the fund or In-Kind ETF’s investment adviser, officer, or officers (which may not be solely portfolio managers of the fund or In-Kind ETF) responsible for administering the program and its policies and procedures</strong> <strong>. . . .” May the program administrator delegate responsibilities to a sub-adviser under the fund’s liquidity risk management program, subject to appropriate oversight?</strong></p>

<p><strong>A. </strong>Yes. The rule requires a fund to adopt and implement a written LRM program, with a board-approved “person(s) designated to administer the program” (“program administrator”). The Adopting Release explains that the term “adviser” as used in the Adopting Release and the rule generally refers to any person, including a sub-adviser, that is an “investment adviser” of an investment company.<a href="#_ftn1" name="_ftnref1" title="">[1]</a> A fund’s sub-adviser could thus be designated as program administrator.<a href="#_ftn2" name="_ftnref2" title="">[2]</a></p>

<p>The Commission also recognized in the Adopting Release that sub-advisers could serve as third parties who could assist the program administrator in managing liquidity risk.<a href="#_ftn3" name="_ftnref3" title="">[3]</a> Thus, the staff believes that the program administrator also could delegate specific responsibilities to a sub-adviser under the fund’s LRM program (<em>e.g.</em>, providing liquidity classifications for the fund’s investments). Neither the rule nor the Adopting Release prescribes whether or how a program administrator could delegate responsibilities—either for administering the entire LRM program or for handling discrete responsibilities under the fund’s LRM program. Therefore, the staff believes that, subject to appropriate oversight, a program administrator has flexibility regarding delegation, provided that each responsibility is delegated to, and assumed and handled by, an appropriate entity. We note, however, that the fund at all times retains ultimate responsibility for complying with the rule, and the program administrator is responsible under the rule for the administration of the LRM program. A fund may wish to implement policies and procedures regarding the scope of and conditions on permitted delegation of responsibilities by the program administrator, and the program administrator may in turn wish to implement policies and procedures to oversee those to whom it has delegated responsibilities under the LRM program, including sub-advisers if applicable to ensure that those responsibilities are appropriately fulfilled. Similarly, a fund’s policies and procedures may permit an entity with delegated responsibilities to appoint sub-delegates and task them with handling certain portions of its delegated responsibilities, provided that the entities with sub-delegated authority are appropriately supervised. [Jan. 10, 2018]</p>

<p><strong>2. Q. Does an adviser (including a sub-adviser) have an independent obligation to adopt and implement a liquidity risk management program?</strong></p>

<p><strong>A.</strong> No. The rule requires funds—not advisers—to adopt and implement LRM programs. However, the staff believes that the rule and Adopting Release clearly contemplate a role for advisers and their personnel in handling responsibilities under funds’ LRM programs. For example, as discussed in response to Q. 1, this role could take the form of administering funds’ LRM programs or handling specific program responsibilities delegated by the program administrator.<a href="#_ftn4" name="_ftnref4" title="">[4]</a> [Jan. 10, 2018]</p>

<p><strong>3. Q. In the staff’s view, may an adviser (including a sub-adviser) administer, or have specific delegated responsibilities under, multiple fund LRM programs that differ from one another?</strong></p>

<p><strong>A.</strong> Yes. The staff recognizes that (i) an adviser (including a sub-adviser) may provide advisory services to multiple funds (including funds in multiple fund complexes), and (ii) funds, advisers, and sub-advisers currently assess, manage, and review liquidity risk using a diverse set of practices. The Adopting Release acknowledges the need for a fund’s LRM program to be appropriately tailored to the fund’s risks and circumstances, and the staff believes the rule’s framework accommodates, and is fully consistent with, continued diversity and evolution of liquidity risk management practices.<a href="#_ftn5" name="_ftnref5" title="">[5]</a> An adviser (including a sub-adviser) may have responsibilities under multiple fund LRM programs that differ from one another (including multiple programs within the same fund complex), and the staff believes that such an adviser is under no obligation to reconcile the elements of those programs; the programs’ underlying methodologies, assumptions, or practices; or the program outputs (<em>e.g.</em>, liquidity classifications of fund investments). [Jan. 10, 2018]</p>

<p><strong>4. Q. If an adviser (including a sub-adviser) has responsibilities under multiple fund LRM programs, either in its role as the designated program administrator or under specific delegated responsibilities, which program should control for a particular fund?</strong></p>

<p><strong>A.</strong> Notwithstanding the diversity of fund LRM programs under which an adviser (including a sub-adviser) may have responsibilities, each fund’s board-approved LRM program will control how an adviser or sub-adviser carries out any of its responsibilities under the rule (<em>e.g.</em>, liquidity classification of the fund’s investments). [Jan. 10, 2018]</p>

<p><strong>5. Q. May different funds classify the same investment differently?</strong></p>

<p><strong>A.</strong> Yes. As the Commission stated in the Adopting Release, the Commission recognizes that different funds may classify the liquidity of similar investments differently based on the facts and circumstances informing their analysis.<a href="#_ftn6" name="_ftnref6" title="">[6]</a> This could result in classifications of the same investment that vary from fund to fund. Under the rule, a fund must take into account “relevant market, trading, and investment-specific characteristics” in classifying its portfolio investments’ liquidity, as well as the investments’ market depth, based on trades of the size that a fund would “reasonably anticipate trading.” Funds—including funds in the same complex—could use differing methodologies and assumptions with respect to the market, trading, and investment-specific characteristics, as well as market depth and reasonably anticipated trade size, and thereby appropriately arrive at different classifications for the same instrument. [Jan. 10, 2018]</p>

<p><strong>6. Q. If a fund’s adviser and sub-adviser (assuming it has one) have differing conclusions regarding an investment’s appropriate liquidity category, how should the fund’s liquidity program policies and procedures address those differences?</strong></p>

<p><strong>A.</strong> In the staff’s view, a fund’s program administrator could delegate responsibility for the classification of investments to either its adviser or sub-adviser, in which case that entity’s decisions would control how the fund classifies its investments. Alternatively, the program administrator could adopt an approach where the adviser and sub-adviser(s) each have some input into the fund’s liquidity classifications. In the latter case, and for a variety of reasons (including those set forth in the response to Q. 5 above), a fund’s adviser and sub-adviser may reach differing conclusions regarding an investment’s appropriate liquidity category. Therefore, the staff believes that the fund’s LRM program policies and procedures could address how the fund would resolve those differences. For instance, the staff believes that a fund’s policies and procedures could stipulate that, in the event of a classification difference, a specified party’s determination (<em>e.g.</em>, program administrator, adviser, or sub-adviser) would control, or establish another method (<em>e.g.</em>, a factor analysis or hierarchy or adopt the most conservative (<em>i.e.</em>, least liquid) classification) for resolving classification differences. These examples are meant to be illustrative only, and fund LRM programs could employ other ways of addressing any differences. [Jan. 10, 2018]</p>

<p><strong>7. Q. Suppose that (i) a fund has multiple sub-advisers, each with discretion to manage its own distinct “sleeve” (a “manager-of-managers” structure), (ii) the fund’s sub-advisers have been delegated responsibility under the liquidity program for classifying the investments in the sub-advisers’ respective sleeves, and (iii) more than one sleeve holds the same investment. If each sub-adviser classifies the commonly-held investment differently, in the staff’s view must the program administrator reconcile those differences for purposes of compliance with the rule?</strong></p>

<p><strong>A.</strong> Much like in the case of an adviser and sub-adviser discussed in Q. 6, in a manager-of-managers structure, the staff recognizes that multiple sub-advisers may have differing views regarding the appropriate liquidity category for their investments. Sub-advisers may manage their respective sleeves autonomously, with no reference to (or visibility into) the other sleeves. Consequently, just as funds (including funds within a complex) may classify the same investment differently, so too may sub-advisers of the same fund, because they may be guided by differing assumptions and methodologies. If such classification differences were to arise, the staff believes that neither the fund, program administrator, nor the adviser nor the sub-advisers with delegated LRM responsibilities would be under any obligation to resolve these differences for compliance purposes (<em>e.g.</em>, in connection with monitoring for compliance with the fund’s highly liquid investment minimum (if applicable) and the 15% limit on illiquid investments). The staff believes, however, that a fund’s policies and procedures could have a process for resolving these differences, similar to those discussed in Q. 6.</p>

<p>As discussed below, however, a fund <u>must</u> reconcile such classification differences for purposes of reporting on Form N-PORT. [Jan. 10, 2018]</p>

<p><strong>8. Q. If a fund that operates under a manager-of-managers structure classifies the same investment held in multiple sleeves differently as outlined above for compliance purposes, how should the fund report the investment’s liquidity classification on Form N-PORT? </strong></p>

<p><strong>A. </strong>Form N-PORT does not permit a fund to report more than one liquidity classification of a single investment. If, as outlined above, a fund classifies the same investment held in multiple sleeves differently for purposes of compliance with the rule, the staff believes that its policies and procedures should have a process for selecting a single classification for that investment for purposes of Form N-PORT reporting.</p>

<p>When determining the overall liquidity classification of an entire investment position classified differently by multiple sub-advisers, the staff believes that a fund may use any reasonable method for resolving this difference, so long as the fund applies that method consistently. The staff believes that the fund could, for example: (i) adopt the classification of the sub-adviser with the largest position in the investment; (ii) calculate a weighted average (based on each sub-adviser’s classification and its respective position size) and round to the nearest classification; or (iii) use the most conservative (<em>i.e.,</em> least liquid classification). These examples are meant to be illustrative only, and fund LRM programs could employ other ways of determining a single classification for purposes of Form N-PORT reporting.</p>

<p>The staff encourages a fund that has diverging liquidity classifications for an investment for compliance purposes but a single classification for reporting that investment on Form N-PORT to note this in the Form’s Explanatory Notes section. For example, a fund could describe which of the methods described above the fund used to resolve differences in the classification of a single investment. The staff notes that any information included in the Explanatory Notes section is non-public if it is related to a non-public reporting item, such as the item requiring a fund to report its monthly position-level liquidity classification information.<a href="#_ftn7" name="_ftnref7" title="">[7]</a> [Jan. 10, 2018]</p>

<h2 style="margin-bottom: 10px;">ETFs</h2>

<p><strong>9. Q. In its discussion of circumstances under which an In-Kind ETF may use cash to meet redemptions, the Adopting Release states that such an ETF’s use of cash may “correspond to uninvested cash in the fund’s portfolio (which, to the extent that this amount of cash equals the fund’s cash position in the portfolio, would be an ‘in-kind’ redemption) . . . .” The Adopting Release then states that “if an In-Kind ETF were to use more than a <em>de minimis </em>amount of cash (as determined in accordance with its written policies and procedures) to meet redemptions (for any of the reasons discussed above or otherwise), it would not qualify as an In-Kind ETF . . . .” For purposes of defining and testing compliance with its <em>de minimis</em> cash amount, in the staff’s view may an ETF exclude the amount of cash in redemption proceeds that is proportionate to the ETF’s uninvested portfolio cash, irrespective of amount? </strong></p>

<p><strong>A</strong>. Yes. The Commission specifically recognizes in the Adopting Release that to the extent the amount of cash (<em>i.e.</em>, U.S. currency) in a redemption equals the fund’s cash position in the portfolio, the redemption is “in-kind” and is not considered “cash” that is subject to the <em>de minimis</em> amount.<a href="#_ftn8" name="_ftnref8" title="">[8]</a> Therefore, the staff believes that an ETF may exclude cash in redemption proceeds that is proportionate to the ETF’s uninvested portfolio cash for purposes of defining and testing compliance with its <em>de minimis </em>cash amount. [Jan. 10, 2018]</p>

<p><strong>10. Q. In the event that an ETF is no longer able to qualify for the In-Kind ETF exception, must a fund immediately come into compliance with the classification and highly liquid investment minimum requirements of the LRM program?</strong></p>

<p><strong>A. </strong>The staff understands there are practical considerations that would prevent a fund that loses its status as an In-Kind ETF from coming into immediate compliance with these requirements of the LRM program. Therefore, the staff would not recommend enforcement action if such an ETF comes into compliance with these requirements as soon as reasonably practicable after the ETF no longer qualifies for the In-Kind ETF exception. The staff notes that an ETF must indicate in Item E.5 of Form N-CEN its current status as an In-Kind ETF for the reporting period.</p>

<p><strong>11. Q. According to the Adopting Release, an In-Kind ETF’s policies and procedures “would determine the amount of cash and the types of transactions that it will treat as <em>de minimis</em>” for purposes of qualifying as an In-Kind ETF. Notwithstanding the lack of a bright line test in the rule or Adopting Release for what constitutes a <em>de minimis</em> amount of cash, is there a <em>de minimis</em> cash amount that the SEC staff would view as reasonable?</strong></p>

<p><strong>A.</strong> The Adopting Release states that “ETFs that redeem more than a<em> de minimis</em> amount in cash can have substantially similar liquidity risks as mutual funds. . . .”<a href="#_ftn9" name="_ftnref9" title=""><sup><sup>[9]</sup></sup></a> Those ETFs are, as stated in the Adopting Release, subject to the same LRM program requirements as mutual funds, including the rule’s investment classification and highly-liquid investment minimum requirements. Defining what constitutes a <em>de minimis</em> amount of cash in its policies and procedures is a determination that the rule and Adopting Release leave to each ETF, and therefore what is <em>de minimis </em>may differ among ETFs.<a href="#_ftn10" name="_ftnref10" title=""><sup><sup>[10]</sup></sup></a> The staff believes that it would be reasonable for an In-Kind ETF to determine that if the percentage of its overall redemption proceeds paid in cash does not exceed 5% (subject to permissible exclusions, such as set forth in Q. 9), such use would be <em>de minimis.</em><a href="#_ftn11" name="_ftnref11" title=""><sup><sup>[11]</sup></sup></a></p>

<p>The staff further believes that an In-Kind ETF may determine that cash use of more than 5% in redemptions is <em>de minimis. </em>In making such a determination, the staff believes that an ETF should evaluate its particular facts and circumstances, including the ETF’s LRM program and whether a redemption(s) in cash in excess of 5% could give rise to liquidity risks substantially similar to those of mutual funds.</p>

<p>However, the staff believes that, if an ETF’s percentage of overall redemption proceeds paid in cash exceeds 10% (subject to permissible exclusions, such as set forth in Q. 9), it would be unreasonable (subject to permissible exclusions, such as set forth in Q. 9), to consider it a <em>de minimis</em> amount of cash for purposes of qualifying as an In-Kind ETF. The staff notes that this framework for assessing <em>de minimis</em> use of cash in the context of fund redemptions would not necessarily be representative of a <em>de minimis</em> amount in the context of other requirements under the federal securities laws. [Jan. 10, 2018]</p>

<p><strong>12. Q. In its discussion of the “In-Kind ETF” definition and what would constitute a <em>de minimis </em>amount of cash thereunder, the Adopting Release notes that there may be circumstances under which an In-Kind ETF may use cash to meet redemptions. The Adopting Release then states, “[b]y way of example, an ETF that normally redeems in-kind, but delivers all cash to a single authorized participant [an “AP”] that elects to receive cash, would not be an ETF that uses a <em>de minimis</em> amount of cash.” In the staff’s view, does this statement indicate that an ETF engaging in a single redemption transaction consisting entirely of cash is necessarily precluded from qualifying as an In-Kind ETF under the rule?</strong></p>

<p><strong>A. </strong>In the staff’s view, where an ETF has agreed to accommodate an AP’s <em>election</em> to receive cash as a standard practice, that ETF may be exposed to the risks that the rule is generally designed to address, and thus would not be able to qualify as an In-Kind ETF. However, if the delivery of all cash to a single AP is at the ETF’s discretion (and not the election of the AP to receive cash as a standard practice), then the choice to provide cash or in-kind redemptions would be under the ETF’s control, and thus the ETF would not be exposed to the risk that it would need to sell investments to make a cash redemption in adverse liquidity situations. Accordingly, the staff believes that a redemption transaction consisting entirely of cash does not necessarily preclude an ETF from qualifying as an In-Kind ETF so long as such a redemption transaction as a proportion of the ETF’s aggregate redemption transactions does not exceed the <em>de minimis</em> amount of cash defined in the ETF’s policies and procedures, and the AP who receives the cash redemption is not an AP who has elected to receive cash redemptions as a standard practice. [Jan. 10, 2018]</p>

<p><strong>13. Q. What methods may an In-Kind ETF use to test whether its cash use is <em>de minimis? </em> </strong></p>

<p><strong>A.</strong> Although the rule and Adopting Release do not prescribe a precise methodology for how an ETF should test to determine whether it continues to qualify as an In-Kind ETF (thus leaving this determination to each ETF), the staff believes that an In-Kind ETF may take a variety of reasonable approaches to determine whether its cash use is <em>de minimis</em>, so long as the approach the ETF selects is consistently applied. For example, the staff would not object if an In-Kind ETF were to determine that a reasonable approach might include (i) testing each individual redemption transaction, to ensure that each has no more than a <em>de minimis</em> cash amount, or (ii) testing its redemption transactions in their totality over some reasonable period of time to ensure that, on average, its aggregate redemption transactions have no more than a <em>de minimis</em> cash amount.<a href="#_ftn12" name="_ftnref12" title="">[12]</a> The staff believes that a reasonable period of time for a fund with frequent redemption basket activity might be a day or a week, while a reasonable period for a fund with less frequent redemption basket activity may be up to a month. The staff does not believe that using a period of time over a month would be reasonable. A fund may choose to use either its daily net or total redemptions for each day of the period of time it selects when determining whether its cash use is <i>de minimis</i>. Regardless of the method used, the staff believes that the ETF’s policies and procedures should describe the ETF’s approach for testing compliance and the time period used, and they should be applied consistently. [Feb. 21, 2018]</p>

<p><strong>14. Q. The Adopting Release also states that an ETF that has lost its status as an In-Kind ETF “may be able to conclude that it qualifies as an In-Kind ETF in later years if such circumstances are not repeated.” Does it follow from this that an ETF must wait, in all circumstances, at least two years before it can re-qualify as an In-Kind ETF?</strong></p>

<p>A. No. The staff believes that there is no specific period of time that a fund must wait before it can determine that it once again qualifies as an In-Kind ETF. As noted in Q.10 above, an In-Kind ETF that loses its status should come into compliance with these requirements as soon as reasonably practicable after the ETF no longer qualifies for the In-Kind ETF exception. However, the staff believes that the determination of whether an ETF qualifies as an In-Kind ETF after such status has been lost is a facts and circumstances determination. The staff believes that an ETF that loses its status as an In-Kind ETF should consider whether it is it appropriate to avail itself of the In-Kind ETF exemption, in light of the statement in the Adopting Release that an In-Kind ETF’s written policies and procedures should describe how it analyzes its ability to redeem in-kind in all market conditions such that it is unlikely to suddenly fail to qualify for the exception.<a href="#_ftn13" name="_ftnref13" title="">[13]</a> Nonetheless, the staff believes that an ETF that lost its status as an In-Kind ETF could potentially avail itself of the In-Kind ETF exception again if it makes a reasonable determination, based on its particular facts and circumstances, that the event that caused it to lose its status as an In-Kind ETF was an extraordinary one-time event that is unlikely to occur again. The staff believes that such an ETF should describe the factors it generally would consider in making this determination in its policies and procedures.<a href="#_ftn14" name="_ftnref14" title="">[14]</a> [Jan. 10, 2018]</p>

<p><strong>15. Q. May an ETF, including an ETF with little or no operating history, consider factors other than its redemption history in determining whether it qualifies as an In-Kind ETF?</strong></p>

<p><strong>A. </strong>Although the staff believes that an ETF’s backward-looking redemption history is ordinarily relevant in determining whether it qualifies as an In-Kind ETF, it is not, by itself, dispositive. The staff believes that an ETF’s “in-kind” analysis also may have a forward-looking component. For example, the staff believes that a new ETF could conclude that it qualifies as an In-Kind ETF based on an analysis of its policies and procedures and its expected redemption practices.</p>

<p>In addition, the staff believes that an ETF with an operating history could consider material changes to its policies and procedures and redemption practices and their anticipated effects. For instance, the staff believes that if an ETF changes its policies and procedures to restrict its ability to meet redemptions using cash, and if the ETF otherwise reasonably concludes that its use of cash to meet redemptions is likely to decline to a <em>de minimis</em> level and reasonably expects to maintain such levels going forward, depending on the circumstances it may determine that it qualifies as an In-Kind ETF, notwithstanding recent redemption transaction history, based on an analysis of material changes made to its policies and procedures to maintain compliance. [Jan. 10, 2018]</p>

<h2>Asset Class Liquidity Classification</h2>

<p><strong>16. Q. A fund may classify and review portfolio investments according to their asset classes, provided that it has a process for separately classifying and reviewing “any investment within an asset class if the fund or its adviser has information about any market, trading, or investment specific considerations that are reasonably expected to significantly affect the liquidity characteristics of that investment as compared to the fund’s other portfolio holdings within that asset class.” How may a fund approach this exception process?</strong></p>

<p><b>A.</b> The staff believes that a fund choosing to use an asset class method of investment classification may identify liquidity characteristics it <em>reasonably expects </em>would make an investment a <em>significant </em>departure from the range of liquidity characteristics present within its asset class.<a href="#_ftn15" name="_ftnref15" title="">[15]</a> Put differently, different investments within an asset class may be expected to exhibit a range of varying liquidity profiles. The staff does not believe that investments falling within that range should trigger this process. Moreover, not every deviation in an investment’s liquidity characteristics from those of the range of others in its asset class should trigger separate review and classification, but rather only the ones that have a significant effect on those liquidity characteristics. The staff recognizes that more sensitive exception methodologies may result in numerous false positives, which would limit the utility of this asset classification method in identifying true significant outliers, thereby undermining the balance the Commission sought to strike in permitting class-based classification. [Feb. 21, 2018]</p>

<p><strong>17. Q. How may a fund wishing to classify and review investments according to their asset classes identify exceptions?</strong></p>

<p><b>A.</b> The staff believes that a fund relying on this classification method should include in its policies and procedures a reasonable framework for identifying exceptions to asset class classifications.<a href="#_ftn16" name="_ftnref16" title="">[16]</a> This framework may rely on automated processes. The staff believes that a fund which has such a reasonable framework may generally rely on the results of those processes, and need not subsequently justify every classification on a CUSIP-by-CUSIP basis. The staff expects, however, that a fund making use of a reasonable framework, or automated processes, would conduct periodic testing of the framework and processes to determine whether they are properly identifying those investments meriting treatment as an exception to the class-based classification as part of their required review of the adequacy and effectiveness of the liquidity risk management programs’ implementation. [Feb. 21, 2018]</p>

<p><strong>18. Q. If a fund identifies a potential exception when using an asset class methodology approach, must it immediately reclassify that investment?</strong></p>

<p><b>A.</b> The staff believes that there is no presumption that a fund that identifies <em>potential </em>exceptions must necessarily reclassify them. Upon further review, a fund may conclude that classification of the investment with other investments within the same asset class is still appropriate, even if the liquidity characteristics of the investment has changed, because the particular investment’s liquidity remains within the liquidity bucket assigned to the asset class as a whole. [Feb. 21, 2018]</p>

<h2>Reasonably Anticipated Trading Size</h2>

<p><strong>19. Q. Liquidity classification of investments requires consideration of the “sizes that the fund would reasonably anticipate trading” and market depth. If a fund classifies investments based on their asset class or classes, how may it consider this market depth factor?</strong></p>

<p><b>A.</b> A fund that classifies investments based on asset class is subject to rule 22e-4(b)(l)(ii)(B), which applies to classifications of “portfolio investments or asset classes (as applicable).” The staff believes that this provision permits an aggregated analysis for those investments that a fund classifies by asset class (see Q. 17 for a discussion of how exceptions to an asset class may be identified). For example, if a fund has identified “Asset Class X” as appropriately grouped together, then for purposes of this analysis, the staff believes that the fund could arrive at reasonably anticipated trading sizes for all of its “Asset Class X” investments, and use those reasonably anticipated trading sizes in classifying all of its “Asset Class X” investments. When a fund uses aggregated reasonably anticipated trading sizes for asset classes that have positions of widely varying size in its portfolio, the staff believes that the fund should consider whether using fixed dollar amounts is a reasonable approach (instead of using percentages of the full position), because using fixed dollar amounts on positions of widely varying size may result in unreasonable trading sizes in some cases. [Feb. 21, 2018]</p>

<p><strong>20. Q. When a fund conducts the market depth analysis for an investment, must the fund consider amounts it would “reasonably anticipate trading” for reasons other than meeting redemptions, or liquidity risk management generally?</strong></p>

<p><b>A.</b> The staff believes that determining sizes that the fund reasonably anticipates trading does not require funds to predict which specific portfolio positions it will sell in advance or consider actual trades executed for reasons other than meeting redemptions. Funds may sell portfolio positions for reasons that are unrelated to meeting investor redemptions or liquidity risk management. As discussed in Q. 21, the staff believes that a fund may make a reasonable assumption about the sizes that it will reasonably anticipate trading, and use that assumed size throughout its classification process. A fund could continue to use that assumed reasonably anticipated trading size even in cases where a fund anticipates fully liquidating a position for investment reasons (<em>e.g.</em>, because holding it is no longer consistent with the fund’s investment objective or strategy) in the near term. [Feb. 21, 2018]</p>

<p><strong>21. Q. When a fund conducts the market depth analysis for an investment, must the fund determine precisely what it would sell, in particular quantities, and in a particular sequence in response to redemptions?</strong></p>

<p><b>A.</b> In determining a reasonably anticipated trading size for each portfolio investment or asset class (as applicable), the staff does not believe that a fund should attempt to predict its future portfolio management decisions related to meeting redemptions, but rather should estimate a portion of an investment that it reasonably believes it could choose to sell to meet redemptions. Accordingly, the staff believes that it may be appropriate for a fund to make certain simplifying assumptions in conducting this analysis and arriving at reasonably anticipated trading size assumptions. For example, a fund could conclude that selling all portfolio investments <em>pro rata </em>in response to a redemption would be a reasonable baseline assumption (notwithstanding that actual amounts sold could be higher or lower than a <em>pro rata </em>assumption would indicate), and determine reasonably anticipated trading sizes accordingly. The staff believes that funds also could consider other assumptions, as they deem appropriate. Ultimately, the rule requires that the fund make assumptions about the sizes that that the fund would anticipate trading in a reasonable manner, but does not specify a particular method of doing so. The staff believes that a zero or near zero reasonably anticipated trade size would not be a reasonable assumption, as it would transform any illiquid assets into highly liquid assets in a manner inconsistent with the Commission’s goals in adopting rule 22e-4. [Feb. 21, 2018]</p>

<h2>Price Impact Standard</h2>

<p><strong>22. Q. In classifying an investment, a fund must consider how quickly it may convert the investment to cash (or sell or dispose of it, as applicable) “without [ ] significantly changing the market value of the investment .” Must a fund employ a single, fixed numerical price impact assumption in classifying all of its investments?</strong></p>

<p><b>A.</b> The staff believes that a fund has the flexibility to establish the meaning(s) of what constitutes a “significant change in market value” in its policies and procedures. The staff recognizes that these price impact assumptions are subjective, due to the variety of inputs that may reasonably be used by any fund or portfolio manager. Accordingly, the staff believes that what constitutes a significant change in market value may vary by fund, asset class, or investment. Therefore, the staff believes that a fund does not need to employ as a price impact assumption a fixed amount or percentage, and a fund may have differing standards for different investments and/or asset classes, although a fund may also choose to use a fixed number if reasonably determined. [Feb. 21, 2018]</p>

<h2>Classifying Investments in Pooled Investment Vehicles</h2>

<p><strong>23. Q. How may a fund approach liquidity classification of an investment in another pooled investment vehicle (<em>e.g.</em>, a mutual fund, ETF, closed-end fund, or private fund)?</strong></p>

<p><b>A.</b> The rule’s investment classification requirements and category definitions are predicated on how long it would take a fund to convert an investment to cash, or sell or dispose of the investment (depending on the category). The staff believes that a fund that invests in other pooled investment vehicles (“pools”) may focus on the liquidity of the pool’s shares or interests when classifying those investments. For pool shares that trade on exchanges (<em>e.g.</em>, shares of ETFs and closed-end funds), the staff believes that it may be appropriate for a fund to evaluate their liquidity in much the same way that it would evaluate the liquidity of other exchange-traded investments (<em>e.g.</em>, common stock), and generally only “look through” to the pool’s underlying investments under circumstances when the fund has reason to believe that doing so could materially alter its view of the liquidity of the pool’s shares.<a href="#_ftn17" name="_ftnref17" title="">[17]</a></p>

<p>For pools that offer redeemable securities or withdrawal rights (<em>e.g.</em>, mutual funds or private funds), the staff believes that a fund generally would focus on the pool’s ordinary redemption rights or practices, and “look through” to the pool’s underlying investments only under circumstances when the fund has a reason to believe that the pool may not be able to honor those rights or meet redemptions in accordance with its customary practice. [Feb. 21, 2018]</p>

<h2>Provisional Investment Classification Activity and Related Compliance Monitoring</h2>

<p><strong>24. Q. How frequently should a fund conduct reviews to ensure compliance with its highly liquid investment minimum (if applicable) and the 15% limit on illiquid investments?</strong></p>

<p><b>A.</b> These requirements are critical to the functioning of rule 22e-4, and as such, the staff believes that regular monitoring is essential to compliance with the rule. Several factors affect a fund’s compliance with these requirements. These include a change in the value or size of an existing investment, the acquisition of a new investment and the reclassification of an existing investment. The staff believes a fund should calculate the value of existing investments for this purpose in conjunction with its daily computation of net asset value. The staff believes a fund should classify newly acquired investments as discussed in Q. 27 and should reclassify existing investments under the circumstances discussed in Q. 28. The staff notes that monitoring for compliance with these limits does not require a fund to reclassify its existing investments on a daily basis, because the fund may use the classifications that it last verified and determined as part of this monitoring process (generally the last reported classification on Form N-PORT). [Feb. 21, 2018]</p>

<p><strong>25. Q. May a fund voluntarily choose to provisionally classify an investment at times other than its required monthly classification?</strong></p>

<p><b>A.</b> As used in these FAQs, a “provisional classification” is any liquidity classification other than a final classification determination reported to the Commission on Form N-PORT or verified reclassifications made pursuant to an intra-month compliance monitoring (see Q. 24). Use of provisional classification is voluntary and the rule does not require a fund to use it. The staff believes that such a provisional classification could include any form of liquidity classification (made pursuant to the classification provisions of rule 22e-4 or otherwise) that the fund chooses to use as part of its liquidity management program.</p>

<p>A fund may conclude that a voluntary provisional classification may assist it in assessing and managing its liquidity risk. It also may be helpful in a fund’s efforts to enhance its program by improving the quality of classifications. The staff recognizes that a fund may employ other means of assessing and managing liquidity risk that the rule does not specifically require (particularly with respect to assessing the liquidity of portfolio investments), and the staff believes that the rule’s intent is not to dissuade a fund from employing liquidity risk management practices that go beyond what is required in the rule and that the fund finds beneficial. <em>See also</em> Q. 32. [Feb. 21, 2018]</p>

<p><strong>26. Q. If the fund’s compliance monitoring, or, if a fund uses provisional classifications, provisional classifications suggest that the fund may have fallen below its HLIM (if applicable) or exceeded the 15% limitation on illiquid investments, would it trigger obligations to report to the board or SEC?</strong></p>

<p><b>A.</b> The staff believes that funds should review provisional classifications (if used) and compliance monitoring that indicates the potential occurrence of such an event in accordance with the funds reasonably designed policies and procedures. The staff believes that if the fund verifies and determines that the fund has in fact fallen below its HLIM or exceeded the 15% limitation on illiquid investments, based on compliance monitoring or by finalizing a provisional reclassification according to its policies and procedures, the fund would be subject to the applicable reporting requirements. Every fund subject to rule 22e-4 must at all times comply with the rule’s requirements relating to its 15% illiquid investment limit and HLIM. [Feb. 21, 2018]</p>

<h2>Timing and Frequency of Classification of Investments</h2>

<p><strong>27. Q. When must a fund initially classify a newly acquired investment, or consider for reclassification an investment in which the fund has increased or decreased its position?</strong></p>

<p><b>A.</b> The rule does not specify when a fund initially must classify a newly acquired investment, but requires at least monthly review of the classifications status of the investments held in a fund’s portfolio.<a href="#_ftn18" name="_ftnref18" title="">[18]</a> The staff would not object if a fund classifies a newly acquired investment, or considers for reclassification an investment in which the fund has increased or decreased its position, during its next regularly scheduled monthly classification, except as noted in Qs 28 (intra-month re-evaluations), and 31 (illiquid investments). [Feb. 21, 2018]</p>

<p><strong>28. Q. A fund must classify its investments at least monthly in connection with its Form N-PORT reporting obligations, and “more frequently if changes in relevant market, trading, and investment-specific considerations are reasonably expected to materially affect one or more of its investments’ classifications.” What are the SEC staff’s views on intra-month classification reviews?</strong></p>

<p><b>A.</b> As discussed in section III. C. 5 of the Release, a fund generally is not required to reassess its investments’ liquidity classification on an intra-month basis. Instead, rule 22e-4 requires an intra-month re-evaluation of an investment’s liquidity classification when a fund becomes aware of changes in relevant market, trading and investment-specific considerations that are <em>reasonably expected </em>to <em>materially affect </em>an existing classification of that particular investment. The staff does not believe that this intra-month review requirement creates a <em>de facto </em>ongoing review requirement for classification. The staff would not object if a fund complies with this intra-month review obligation by identifying in its policies and procedures events that it reasonably expects would materially affect an investment’s classification. The staff would not object if reasonable policies and procedures limits such events to those that are objectively determinable (<em>e.g.</em>, a trading halt or delisting of a security, an issuer or counterparty default or bankruptcy, significant macro-economic developments (such as a sovereign default), or events like extraordinary natural disasters or political upheavals, for funds with concentrated geographic exposures). [Feb. 21, 2018]</p>

<p><strong>29. Q. If a change occurs that triggers an intra-month classification review, must the fund re-classify all of its investments or just the ones affected by the change?</strong></p>

<p><b>A.</b> The staff believes that a fund must review and determine whether to reclassify only those particular investments that the fund reasonably expects to be materially affected by the change in question. [Feb. 21, 2018]</p>

<h2>Pre-trade Activity and the 15% Limitation on Illiquid Investments</h2>

<p><strong>30. Q. Must a fund classify an investment that it is purchasing (or considering purchasing) on a pre-trade basis?</strong></p>

<p><b>A.</b> No. The rule requires a fund to “classify each of the fund’s portfolio investments” and review those classifications at least monthly thereafter. A fund is not required to classify an investment (or conduct any related compliance monitoring) prior to acquisition.</p>

<p><strong>31. Q. For purposes of the 15% illiquid investment limit, how should a fund meet its obligations with respect to intra-month investment acquisitions when it generally classifies its investments at the end of the month, or is an in-kind ETF that is not subject to the classification requirements?</strong></p>

<p><b>A.</b> The staff believes that a fund should implement reasonably designed policies and procedures to appropriately limit illiquid investments, so that the fund will not acquire any illiquid investment that would cause it to exceed this 15% limitation. However, as discussed in Q. 30, this does not require the fund to engage in pre-trade classification. The staff believes that one reasonable method for a fund to comply with the 15% illiquid investment limit with respect to acquisitions is to preliminarily identify certain asset classes or investments that the fund reasonably believes are likely to be illiquid (“preliminary evaluation”). We expect that the fund could base this reasonable belief on its previous trading experience (including its experience in the investment’s typical market depth and price impact when trading), on its understanding of the general characteristics of the asset classes it is preliminarily evaluating, or through other means. A fund could choose to determine that certain investments identified in such asset classes that it purchases are illiquid based solely on this preliminary evaluation, and not engage in any further analysis under the rule at that time. Alternatively, if the preliminary evaluation establishes a reasonable basis for believing that an investment is likely to be illiquid, but the fund wishes to further evaluate its status, the fund may then, as a secondary step, determine whether it is an illiquid investment using the classification process set forth in rule 22e-4. Investments in asset classes the fund acquires that it does not reasonably believe are likely to be illiquid would not need to be classified when performing this preliminary analysis. Funds would then review the liquidity of all of their holdings, including all new acquisitions, as part of their monthly classification review. As discussed in the guidance provided in the Liquidity Delay Release <a href="#_ftn19" name="_ftnref19" title="">[19]</a>, In-Kind ETFs should also review the illiquid status of their investments at least monthly, or more frequently in certain circumstances.</p>

<p>The staff believes funds could automate such a preliminary evaluation of asset classes or investments, and they could base that evaluation on the general characteristics of the investments the fund purchases. For example, in establishing the list of asset classes or investments that the fund believes have a reasonable likelihood of being illiquid, the fund could take into account the trading characteristics of the investment (for example, whether it is a restricted security or has structural liquidity limitations, the trading history of the asset class, or whether the investment typically requires significant negotiations to trade) and use such characteristics to form the reasonable belief of illiquidity.</p>

<p>In evaluating the likelihood of an asset class or investment being illiquid, we do not believe it would be reasonable to assume that a fund is only selling a single trading lot when looking at the market depth of the asset or class. However, a fund would not need to evaluate the actual size of its holdings in the asset class or engage in the full process of evaluating its reasonably anticipated trading size for the asset class under the rule. Instead, a fund could use any reasonable method in evaluating the market depth of the asset classes or investments it identifies as likely being illiquid in the preliminary evaluation.</p>

<p>Much as discussed in Q. 17, the staff believes that a fund making use of a preliminary evaluation, or using automated processes, would conduct periodic testing of the framework and processes to determine whether they continue to be accurate as part of their required review of the adequacy and effectiveness of the liquidity risk management programs’ implementation.</p>

<p>Funds may use other reasonable approaches as well. For example, a fund often will not be at risk of violating this provision when it acquires illiquid investments if a fund’s current percentage of illiquid investments is well below 15%, and therefore an acquisition of an illiquid investment generally may not cause the fund to exceed the limitation (unless the investment’s size in relation to the fund’s net assets were quite large). Accordingly, the staff believes that a reasonable approach may be for the fund’s policies and procedures to require additional monitoring in reviewing acquisitions as the fund’s percentage of illiquid investments increases. For example, if an acquisition could cause a fund to exceed the 15% limitation, the fund’s procedures could prohibit the acquisition of (i) investments within certain asset classes that the fund deems to be presumptively illiquid, regardless of position size (<em>e.g.</em>, investments that have restrictions on transferability), (ii) additions to investments that the fund has classified as illiquid investments as of the most recent finalized classification for each investment, and/or (iii) investments the fund has provisionally classified as illiquid investments.</p>

<p>We note that the staff believes that the methods discussed above would be reasonable approaches for a fund to help assure itself that it has not violated either the 15% illiquid investment limit or the HLIM during the intra-month period between scheduled classifications. Nonetheless, if the fund’s classification process indicates that the fund violated either of these limits, as discussed in Q. 32 and 33 below, a fund would be required to report such events on Form N-LIQUID and to its board. [Feb. 21, 2018]</p>

<h2>Related Reporting Requirements</h2>

<p><strong>32. Q. Rule 22e-4, rule 30b1-10, and Form N-LIQUID require reporting to the fund board and SEC within certain prescribed periods when a fund has exceeded the 15% limitation on illiquid investments, or fallen below its highly liquid investment minimum (if applicable). When does such a reportable event occur?</strong></p>

<p><b>A.</b> As a general matter, a reportable event occurs under the rule when a fund exceeds the 15% limitation on illiquid investments or has fallen below its HLIM (if applicable) (s<em>ee</em> Q. 26). The staff understands, however, that a fund may potentially exceed a limit if, for example, the fund’s policies and procedures require a fund to determine whether to reclassify an investment when a third party service provider’s system or a sub-adviser reclassifies one or more of a fund’s investments. In other cases, a provisional classification may indicate a liquidity issue, but the fund has not yet verified and made a final determination that such an issue actually exists. In these circumstances, a fund may need a reasonable amount of time to determine and verify for itself the impact and validity of the reclassification on the fund’s compliance with its limits. In general, the staff believes that this verification and final determination process should be completed within three business days or less, including the day that the triggering event was observed. In those limited circumstances, the staff believes that a fund’s reporting obligation would be triggered not by the event itself, but instead when the fund has determined and verified (within three business days of the event) that the fund has in fact exceeded the 15% illiquid investment limit or fallen below its HLIM (if applicable) (<em>see also</em> Q. 33 for guidance on reporting the time period for the event on Form N-LIQUID in such cases). [Feb. 21, 2018]</p>

<p><strong>33. Q. The rule states that (i) a fund’s highly liquid investment minimum may not be changed during any period of time that the fund’s assets that are highly liquid investments are below the determined minimum without approval from the fund’s board of directors, including a majority of directors who are not interested persons of the fund, and (ii) if a fund experiences a shortfall in its highly liquid investment minimum that lasts more than 7 consecutive calendar days, it must report certain information to its board. Form N-PORT requires a fund to disclose the number of days the fund’s holdings in highly liquid investments fell below its highly liquid investment minimum. Similarly, Form N-LIQUID requires a fund to disclose specific dates on which the fund’s investments (i) exceeded or returned to or below the 15% limitation on illiquid investments, and (ii) fell below its highly liquid investment minimum. How should a fund identify these periods?</strong></p>

<p><b>A.</b> As discussed in Q. 32, once a fund has determined and verified that a reportable event has occurred because it is not in compliance with one or both of these limits, the staff believes that the time period begins for how long the fund has to report the event to the Commission or its Board. However, the periods of time reported on Form N-LIQUID or to the board as a result of the event should also include the additional days, if any, during which the fund engaged in determining and verifying that it is not in compliance after the triggering event took place. For example, a fund might purchase an asset that made it exceed the 15% illiquid asset limit on a Monday, verify and determine that the asset was illiquid and that the fund was out of compliance on a Wednesday, and report the event to the Commission on a Thursday. In the report, it should indicate that the fund was out of compliance beginning on Monday, on the trade date of the event that led to the fund being out of compliance with the relevant limit, and not as of the Wednesday when it was verified and determined. Form N-LIQUID is a text form that requires funds to report the date(s) that a fund was out of compliance with the HLIM or 15% illiquid investment limit, and funds may thus wish to indicate on the form both the date of the triggering event and the date it was determined and verified to address any ambiguity. [Feb. 21, 2018]</p>

<p><b>34. Q. Some foreign markets have holiday closures of their securities markets that may last seven or more calendar days (an “extended holiday closure”). Funds are generally aware of these extended holiday closures in advance of the holiday. If a fund holds securities that are traded only in such a foreign market, would it need to file Form N-LIQUID solely because of such an extended holiday closure?</b></p>

<p><b>A.</b> Under rule 22e-4 investments that cannot be sold or disposed of in current market conditions in seven calendar days or less without the sale or disposition significantly changing the market value of the investment are defined as illiquid. As a result, investments affected by an extended holiday closure become temporarily illiquid under this rule. However, the staff believes that an anticipated extended holiday closure presents liquidity risk to a fund holding investments in those securities markets that differs from the liquidity risk N-LIQUID is designed to flag. To the extent that investments become illiquid due solely to an extended holiday closure, they are illiquid for a known, temporary duration, and the fund can generally plan its liquidity risk management relating to the market closure in advance. Similarly, such a fund can notify relevant parties in advance, including its board of directors, of investments that will be affected by extended holiday closures and how it expects to manage its liquidity risk during such closures. The staff believes that such advance board notification would satisfy the board notification requirement of paragraph (b)(1)(iv)(A) of the rule. Accordingly, the staff would not object if a fund does not file Form N-LIQUID for an investment that becomes illiquid solely due to an extended holiday closure. Nonetheless, a fund should still consider the potential impacts of any market closure as part of its liquidity risk management program and manage the associated liquidity risk. [Apr. 10, 2019]</p>

<h2>ETFs and Investment Classification</h2>

<p><strong>35. Q. An ETF may not qualify as an “in-kind ETF” (and therefore would be subject to the rule’s investment classification requirements and potentially its highly liquid investment minimum requirements), but may nevertheless satisfy a large percentage of its redemptions in-kind. May this be relevant for how such an ETF (or fund that uses in-kind redemptions) classifies its investments and sets its highly liquid investment minimum?</strong></p>

<p><b>A.</b> Rule 22e-4’s classification requirement is predicated on how long it would take a fund to convert an investment to cash, or sell or dispose of the investment (depending on the category). An ETF does not convert to cash (or sell or dispose of) investments that it distributes in-kind to meet redemptions. An ETF that does not meet the definition of In-Kind ETF but nevertheless redeems shares in-kind to any material extent may have a different liquidity profile, and face different liquidity risks, than a similar one that does not. Accordingly, the staff believes that it may be appropriate for such an ETF to reflect these differences in its classification procedures and in designating a highly liquid investment minimum. On the other hand, increasingly less liquid assets may be more difficult or costly for an ETF to transfer in-kind. In addition, the staff believes that a zero or near zero reasonably anticipated trade size would transform any illiquid assets into highly liquid assets in a manner inconsistent with the Commission’s intent in adopting rule 22e-4. Further, the staff believes that the rule’s reasonably anticipated trading size requirement presupposes a size greater than a single trading lot.</p>

<p>Balancing these considerations, the staff believes that an ETF could take reasonably anticipated in-kind redemption activity into account when determining appropriate reasonably anticipated trading size or market depth assumptions for its investments. When using in-kind redemptions, the staff believes that an ETF should set an appropriate minimum trade size that takes into account the liquidity considerations discussed above.</p>

<p>This guidance would apply to any mutual fund that redeems in-kind to any material extent. The staff believes this is consistent with the policy repeated often in the Adopting Release, that each fund—including an ETF—should design its liquidity risk management program, including its investment classification methodology and its highly liquid investment minimum, based on the fund’s particular liquidity considerations and risks. [Feb. 21, 2018]</p>

<div>
<hr align="left" size="1" width="33%" />
<div id="ftn1">
<p><a href="#_ftnref1" name="_ftn1" title="">[1]</a> <em>See</em> Adopting Release at footnote 279 and accompanying text.</p>
</div>

<div id="ftn2">
<p><a href="#_ftnref2" name="_ftn2" title="">[2]</a> <em>See</em> Adopting Release at footnote 810 and accompanying text.</p>
</div>

<div id="ftn3">
<p><a href="#_ftnref3" name="_ftn3" title="">[3]</a> <em>See</em> Adopting Release at footnote 818 and accompanying text.</p>
</div>

<div id="ftn4">
<p><a href="#_ftnref4" name="_ftn4" title="">[4]</a> <em>See e.g., </em>Adopting Release at footnote 66 and accompanying text.</p>
</div>

<div id="ftn5">
<p><a href="#_ftnref5" name="_ftn5" title="">[5]</a> <em>See</em> Adopting Release at footnote 180 and accompanying text.</p>
</div>

<div id="ftn6">
<p><a href="#_ftnref6" name="_ftn6" title="">[6]</a> <em>See</em> Adopting Release at footnote 311 and accompanying text.</p>
</div>

<div id="ftn7">
<p><a href="#_ftnref7" name="_ftn7" title="">[7]</a> <em>See</em> General Instruction F of Form N-PORT.</p>
</div>

<div id="ftn8">
<p><a href="#_ftnref8" name="_ftn8" title="">[8]</a> <em>See</em> Adopting Release at footnote 852 and accompanying text.</p>
</div>

<div id="ftn9">
<p><a href="#_ftnref9" name="_ftn9" title="">[9]</a> <em>See</em> Adopting Release at footnotes 842-845 and accompanying text.</p>
</div>

<div id="ftn10">
<p><a href="#_ftnref10" name="_ftn10" title="">[10]</a> <em>Id. </em>(“An In-Kind ETF generally should describe in its policies and procedures...the circumstances in which the In-Kind ETF may use a <em>de minimis </em>amount of cash to meet a redemption and what amount of cash would qualify as such.”)</p>
</div>

<div id="ftn11">
<p><a href="#_ftnref11" name="_ftn11" title="">[11]</a> <em>See</em> Q.13 on methods an In-Kind ETF may use for this calculation.</p>
</div>

<div id="ftn12">
<p><a href="#_ftnref12" name="_ftn12" title="">[12]</a> <em>See</em> Adopting Release at footnote 854 and accompanying text.</p>
</div>

<div id="ftn13">
<p><a href="#_ftnref13" name="_ftn13" title="">[13]</a> <em>See</em> Adopting Release at footnote 854 and accompanying text.</p>
</div>

<div id="ftn14">
<p><a href="#_ftnref14" name="_ftn14" title="">[14]</a> <em>See</em> Adopting Release at footnote 854 and accompanying text.</p>
</div>

<div id="ftn15">
<p><a href="#_ftnref15" name="_ftn15" title="">[15]</a> <em>See, e.g., </em>Liquidity Adopting Release at text accompanying n 436 (discussing how a particular investment should be classified differently than its asset class if its market was “exceptional in terms of size, breadth or depth” or if the bid ask spreads were “generally wider, narrower or more volatile” than other assets in the class.)</p>
</div>

<div id="ftn16">
<p><a href="#_ftnref16" name="_ftn16" title="">[16]</a> <em>See, e.g., </em>Liquidity Adopting Release at text accompanying n. 435 (discussing how reasonably designed policies and procedures would “likely include specifying the sources of inputs that inform its exception processes” and the “particular variables that could affect the fund’s classification of certain investments”).</p>
</div>

<div id="ftn17">
<p><a href="#_ftnref17" name="_ftn17" title="">[17]</a> <em>See, e.g., </em>Liquidity Adopting Release at text following n. 524 (discussing certain circumstances where a fund may wish to look through an ETF to its underlying holdings if those holdings’ liquidity may impair the liquidity of the ETF).</p>
</div>

<div id="ftn18">
<p><a href="#_ftnref18" name="_ftn18" title="">[18]</a> <em>See </em>rule 22e-4 (b)(1)(ii).</p>
</div>

<div id="ftn19">
<p><a href="#_ftnref19" name="_ftn19" title="">[19]</a> <em>See </em>15% guidance in Investment Company Liquidity Risk Management Programs; Commission Guidance for In-Kind ETFs, Investment Company Act Release No. IC-33010 (Feb. 22, 2018) ("Liquidity Delay Release").</p>
</div>
</div>
</div>
      
                          </div>

              
                <div class="article-more-topics">
          
        </div>
                              </div>

          <div id="sidebar-second">
		
                <div class="block related-materials">
          <h2>Related Materials</h2>
      <ul>
              <li>Changes to January 10, 2018 version</li>
              <li>Changes to February 21, 2018 version</li>
          </ul>
  
        </div>
              </div>
            </div>

    <div class="article-date modified">
          Modified: April 10, 2019
      </div>
  
</article>

  </div>

  </div>


        </div>
      
        
      
      </div>

      
    </div>
    </div>

          <footer class="page-footer">
                  <div class="page-footer-top">
              <div class="region region-footer-top">
    
<div id="block-globalfooterstayconnectedfooter" class="block stay-connected-footer">
  
    
        <div class="body"><p class="data-exempt" id="stay-connected-footer"><a href="/news/socialmedia.shtml"><span>SOCIAL MEDIA</span></a><br class="new-line" />
<a href="https://twitter.com/SECGov"><span class="fa fa-lg fa-twitter"><span class="visually-hidden">1</span></span> <span class="hide-for-small">Twitter </span></a> <a href="https://www.facebook.com/SECgov"><span class="fa fa-lg fa-facebook"><span class="visually-hidden">2</span></span> <span class="hide-for-small">Facebook</span></a> <a href="https://www.instagram.com/secgov"><span class="fa fa-lg fa-instagram"><span class="visually-hidden">2</span></span> <span class="hide-for-small">Instagram</span></a> <a href="/about/secrss.shtml"><span class="fa fa-lg fa-rss"><span class="visually-hidden">3</span></span><span class="hide-for-small">RSS</span></a> <a href="http://www.youtube.com/user/SECViews"><span class="fa fa-lg fa-youtube-play"><span class="visually-hidden">4</span></span><span class="hide-for-small">YouTube</span></a><br class="hide-for-medium-up" />
<a href="https://www.linkedin.com/company/us-securities-and-exchange-commission?trk=company_name"><span class="fa fa-lg fa-linkedin"><span class="visually-hidden">6</span></span><span class="hide-for-small">LinkedIn</span></a> <!--<a href="//www.pinterest.com/secgov"><span class="fa fa-lg fa-pinterest-p"><span class="visually-hidden">7</span></span> <span class="hide-for-small">Pinterest</span></a>--> <a href="//public.govdelivery.com/accounts/USSEC/subscriber/new"><span class="fa fa-lg fa-envelope"><span class="visually-hidden">8</span></span> <span class="hide-for-small">Email Updates</span> </a></p>
</div>
  </div>

  </div>


          </div>
                <div class="page-footer-cols">
          <div>
    <nav role="navigation" aria-labelledby="block-aboutthesec-menu" id="block-aboutthesec">
            
  <h2 id="block-aboutthesec-menu">About The SEC</h2>
  

        
              <ul class="section-menu menu">
              <li class="menu__item is-active is-leaf leaf item-budget-&-performance">
        <a href="/about/offices/ofm/ofm-documents" class="menu__link" data-drupal-link-system-path="node/111606">Budget & Performance</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-careers">
        <a href="/about/careers" class="menu__link" data-drupal-link-system-path="node/41311">Careers</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-commission-votes">
        <a href="/about/commission-votes" class="menu__link" data-drupal-link-system-path="node/111231">Commission Votes</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-contact">
        <a href="/contact-information/sec-directory" class="menu__link" data-drupal-link-system-path="node/102846">Contact</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-contracts">
        <a href="/page/oacqsectionlanding" class="menu__link" data-drupal-link-system-path="node/3841">Contracts</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-data-resources">
        <a href="/sec-data-resources" class="menu__link" data-drupal-link-system-path="node/191566">Data Resources</a>
              </li>

        </ul>
  





  </nav>
<nav role="navigation" aria-labelledby="block-governmenttransparency-menu" id="block-governmenttransparency">
            
  <h2 id="block-governmenttransparency-menu">Transparency</h2>
  

        
              <ul class="section-menu menu">
              <li class="menu__item is-active is-leaf leaf item-accessibility-&-disability">
        <a href="/disability/sec_access" class="menu__link" data-drupal-link-system-path="node/111766">Accessibility & Disability</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-foia">
        <a href="/foia-services" class="menu__link" data-drupal-link-system-path="node/946556">FOIA</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-inspector-general">
        <a href="/oig" class="menu__link" data-drupal-link-system-path="node/41456">Inspector General</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-no-fear-act-&-eeo-data">
        <a href="/page/eeosectionlanding" class="menu__link" data-drupal-link-system-path="node/3781">No FEAR Act & EEO Data</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-ombuds">
        <a href="/ombuds" title="Ombuds" class="menu__link" data-drupal-link-system-path="node/96081">Ombuds</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-whistleblower-protection">
        <a href="/whistleblower" class="menu__link" data-drupal-link-system-path="node/99851">Whistleblower Protection</a>
              </li>

        </ul>
  





  </nav>
<nav role="navigation" aria-labelledby="block-otherwebsites-menu" id="block-otherwebsites">
            
  <h2 id="block-otherwebsites-menu">Websites</h2>
  

        
              <ul class="section-menu menu">
              <li class="menu__item is-active is-leaf leaf item-investor.gov">
        <a href="https://www.investor.gov" class="menu__link">Investor.gov</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-related-sites">
        <a href="/links" class="menu__link" data-drupal-link-system-path="node/100276">Related Sites</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-usa.gov">
        <a href="https://www.usa.gov" class="menu__link">USA.gov</a>
              </li>

        </ul>
  





  </nav>
<nav role="navigation" aria-labelledby="block-siteinformation-menu" id="block-siteinformation">
            
  <h2 id="block-siteinformation-menu">Site Information</h2>
  

        
              <ul class="section-menu menu">
              <li class="menu__item is-active is-leaf leaf item-plain-writing">
        <a href="/plainwriting" class="menu__link" data-drupal-link-system-path="node/111701">Plain Writing</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-privacy-&-security">
        <a href="/privacy" class="menu__link" data-drupal-link-system-path="node/111706">Privacy & Security</a>
              </li>

          <li class="menu__item is-active is-leaf leaf item-site-map">
        <a href="/sitemap" class="menu__link" data-drupal-link-system-path="node/111831">Site Map</a>
              </li>

        </ul>
  





  </nav>

  </div>


        </div>
      </footer>
    
                <script>
        if (typeof dataLayer != "undefined") dataLayer.push({"pageType": "investment-company-liquidity-risk-management-programs-faq"});
      </script>
        </div>
</div>
</div>


  </div>

    

    <a href="#" class="back-to-top"><i class="fa fa-chevron-circle-up" aria-hidden="true"></i>Return to Top</a>

    <div class="overlap">
  <!-- Subscribe link, RSS, Email -->
  <div id="addthis-icons-508" class="visibly-hidden">
    <div class="addthis-wrapper">
      <div class="appIconsDetail hide">
        <div class="addthis_toolbox addthis_default_style hide-for-small">
          <a class="addthis_button_print at300b" title="Print Page" href="#">
            <span class="fa fa-print"></span>
          </a>
          <a class="addthis_button_facebook at300b" title="Share on Facebook" href="#">
            <span class="fa fa-facebook"></span>
          </a>
          <a class="addthis_button_twitter at300b" title="Tweet Page" href="#">
            <span class="fa fa-twitter"></span>
          </a>
          <a class="addthis_button_mailto at300b" target="_blank" title="Email Page" href="#">
            <span class="fa fa-envelope"></span>
          </a>
          <a class="addthis_button_compact at300m" href="#" title="More Sharing Options">
            <span class="fa fa-plus"></span>
          </a>
        <div class="atclear"></div>
      </div>
      <div class="addthis_toolbox hide">
        <a class="addthis_button_facebook at300b" title="Share on Facebook" href="#">
          <span class="fa fa-facebook"></span>
        </a>
        <a class="addthis_button_twitter at300b" title="Tweet Page" href="#">
          <span class="fa fa-twitter"></span>
        </a>
        <a class="addthis_button_mailto at300b" target="_blank" title="Email Page" href="#">
          <span class="fa fa-envelope"></span>
        </a>
      </div>
      <div class="atclear"></div>
      </div>
    </div>
  </div>
</div>

    <script type="application/json" data-drupal-selector="drupal-settings-json">{"path":{"baseUrl":"\/","pathPrefix":"","currentPath":"node\/119321","currentPathIsAdmin":false,"isFront":false,"currentLanguage":"en"},"pluralDelimiter":"\u0003","suppressDeprecationErrors":true,"data":{"extlink":{"extTarget":false,"extTargetNoOverride":false,"extNofollow":false,"extNoreferrer":false,"extFollowNoOverride":false,"extClass":"0","extLabel":"(link is external)","extImgClass":false,"extSubdomains":true,"extExclude":".*\\.gov|http:\/\/www.xbrl.org\/utr\/2013-05-17\/utr.xml|http:\/\/www.xbrl.org\/dtr\/type\/numeric-2009-12-16.xsd|http:\/\/www.xbrl.org\/dtr\/type\/nonNumeric-2009-12-16.xsd|https:\/\/secir.secure.force.com\/ombudsman\/OMMSForm","extInclude":"","extCssExclude":".data-exempt","extCssExplicit":"","extAlert":true,"extAlertText":"You are now leaving the SEC Website. The link you have selected is located on another server. Please click on the OK button below to proceed to the selected site. The SEC does not endorse this web site, its sponsor, or any of the policies, activities, products, or services offered on the site or by any advertiser on the site.","mailtoClass":"0","mailtoLabel":"(link sends email)","extUseFontAwesome":false,"extIconPlacement":"append","extFaLinkClasses":"fa fa-external-link","extFaMailtoClasses":"fa fa-envelope-o","whitelistedDomains":null}},"user":{"uid":0,"permissionsHash":"be93764d3e8de6c48387d9f2c599940f17294deeee6c67667df88d64322d3b56"}}</script>
<script src="/files/js/js_mIXuAYEwDmUa0z4m8pGJvZRv8YrQPyyxhiIOgtVYu68.js?scope=footer&delta=0&language=en&theme=secgov&include=eJxljV0OwiAQhC_UypHIQjcU3XYbZmnE00ujvOjjfPMn1LSaDzXLwsXHCtMtv7i4JBpIZliTvKcJHH1hYQLDjRhZ1h0TGow3F7p35ZKeox2BH3LHvDL1rz8-gB7X6gfx0_r7wy2lHiS3r3wDgW9G2g"></script>
<script src="/themes/custom/secgov/js/third-party/addthis_widget.js?sdd43i" async></script>
<script src="/files/js/js_kgyhkKvsEJc_F08suXf_coAzuVqc6BQYtY8nFRLCflk.js?scope=footer&delta=2&language=en&theme=secgov&include=eJxljV0OwiAQhC_UypHIQjcU3XYbZmnE00ujvOjjfPMn1LSaDzXLwsXHCtMtv7i4JBpIZliTvKcJHH1hYQLDjRhZ1h0TGow3F7p35ZKeox2BH3LHvDL1rz8-gB7X6gfx0_r7wy2lHiS3r3wDgW9G2g"></script>


  <noscript><img src="https://www.sec.gov/akam/13/pixel_2774cf19?a=dD04Y2I4MzAyZDlkZGY3YWRhYmM3NTZhMTJhN2E2NzBkZmE5OWNmNzMzJmpzPW9mZg==" style="visibility: hidden; position: absolute; left: -999px; top: -999px;" /></noscript></body>
  </html>