(c) What is the effect of the marking of a security interest in favor of the United States in a Security Entitlement of a Participant on the books of a Federal Reserve Bank? Where a security interest in favor of the United States in a Security Entitlement of a Participant is marked on the books of a Federal Reserve Bank, such Reserve Bank may rely, and is protected in relying, exclusively on the order of an authorized Representative of the United States directing the transfer of the Security.
(d) Who is an authorized Representative of the United States, for purposes of paragraph (c) in this section? The official designated in the applicable regulations or in an agreement to which a Federal Reserve Bank is a party, governing the security interest.
(e)(1) Must the United States and the Federal Reserve Banks agree to act on behalf of any Person or to recognize the interest of any transferee of a security interest or other limited interest in favor of any Person? No, they need not agree to act or recognize any party's interest, except:
(i) To the extent of any specific requirement of Federal law or regulation, or
(ii) To the extent set forth in any specific agreement with the Federal Reserve Bank on whose books the interest of the Participant is recorded.
(2) May a security interest be created and perfected by a Federal Reserve Bank marking its books? Yes, a security interest in a Security Entitlement that is in favor of a Federal Reserve Bank or a Person may be created and perfected by a Federal Reserve Bank marking its books to record the security interest to the extent required by law, regulation, or an agreement with a Federal Reserve Bank or the Federal Reserve Bank Operating Circular.
(3) Does this security interest have priority over other interests? A security interest in a Security Entitlement marked on the books of a Federal Reserve Bank has priority over any other interest in the securities, except a security in favor of the United States, as provided in table (b) of this section.
(4) In addition to the method provided in paragraph (e)(2) of this section, may a security interest, including a security interest in favor of a Federal Reserve Bank, be perfected in another way? Yes, a security interest may be perfected by any method under applicable law as described in §§357.10(b) or 357.11.
(i) The applicable law governs the perfection, effect of perfection or non-perfection and priority of a security interest.
(ii) A security interest in favor of a Federal Reserve Bank shall be treated as a security interest in favor of a clearing corporation in all respects under that law.
(iii) A Federal Reserve Bank Operating Circular shall be treated as a rule adopted by a clearing corporation for these purposes.
§ 357.13 Obligations of the United States and the Federal Reserve Banks with respect to Book-entry Securities and security interests.
top
(a) Who is entitled to deal with an interest in a Book-entry Security that has been credited to a Participant's Security Account? Except in the case of a security interest in favor of the United States or a Federal Reserve Bank or otherwise as provided in §357.12 (e), for the purposes of this subpart B, the United States and the Federal Reserve Banks treat the Participant as exclusively entitled to perform the following functions, even if the Treasury or a Federal Reserve Bank has any information or notice to the contrary:
(1) Issue a Transfer Message,
(2) Receive interest and other payments with respect thereof, and
(3) Exercise all the rights and powers with respect to the Security,
(b) Are the Federal Reserve Banks and Treasury liable for Adverse Claims? The Federal Reserve Banks and Treasury are not liable to a Person asserting or having an Adverse Claim to a Security Entitlement or to a Book-entry Security in a Participant's Securities Account. This includes any such claim arising as a result of the transfer or disposition of a Book-entry Security by a Federal Reserve Bank, pursuant to a Transfer Message that the Federal Reserve Bank reasonably believes to be genuine.
(c) When is the obligation of the United States to pay interest and principal with respect to Book-entry Securities discharged? The obligation is discharged once payment is made as follows:
(1) A Federal Reserve Bank credits the appropriate amount of interest on Book-entry Securities to a Funds Account maintained at the Bank, or pays it as directed by the Participant.
(2) Book-entry Securities are redeemed according to their terms, a Federal Reserve Bank withdraws the securities from the Participant's Securities Account in which they are maintained, and either:
(i) Credits the amount of the Redemption proceeds, including both principal and interest, where applicable, to a Funds Account at the Bank, or
(ii) Pays such principal and interest as directed by the Participant.
(d) What does a Participant need to do in connection with the Redemption of a Book-entry Security? No action by the Participant is required.
§ 357.14 What authority does a Federal Reserve Bank have?
top
(a) Each Federal Reserve Bank has the authority as fiscal agent of the United States to:
(1) Perform functions with respect to the issuance of Book-entry Securities offered and sold by the Department to which this subpart applies, in accordance with the terms of the applicable offering circular and with procedures established by the Department;
(2) Service and maintain Book-entry Securities in accounts established for such purposes;
(3) Make payments of principal and interest, as directed by the Department;
(4) Effect transfer of Book-entry Securities between Participants' Securities Accounts as directed by the Participants; and
(5) Perform such other duties as fiscal agent that the Department may request.
(b) Each Federal Reserve Bank may issue Operating Circulars that are consistent with this part, governing the details of its handling of Book-entry Securities, Security Entitlements, and the operation of the book-entry system under this part.
§ 357.15 How can a debtor's interest in a Security Entitlement be reached by creditors?
top
(a) The interest of a debtor may be reached by creditors only by legal process upon the Securities Intermediary with whom the debtor's securities account is maintained. Exception: If a Security Entitlement is maintained in the name of a secured party, the debtor's interest may be reached by legal process upon the secured party.
(b) These regulations do not state whether a Federal Reserve Bank is required to honor an order or other notice of attachment in any particular case or class of cases.
Subpart C—Legacy Treasury Direct Book-Entry Securities System (Legacy Treasury Direct)
top
§ 357.20 Securities account in Legacy Treasury Direct®.
top
(a) Account. A securities account consists of:
(1) An account master record, and
(2) A securities portfolio.
(b) Security. A security in Legacy Treasury Direct is evidenced by the account master record and a description of the security as set out in the securities portfolio associated with an account master record.
(c) Account master record. An owner must establish an account master record before the owner may deposit a security in Legacy Treasury Direct. If the security is being purchased on original issue, the request that an account master record be established may be made on the form used for purchase of the security. If the security is being acquired other than on original issue, the request that an account master record be established should be made on the appropriate form that is provided by the Department. The account master record includes, but is not limited to, the following data:
(1) The exact form of registration in which the securities are held;
(2) The Legacy Treasury Direct account number;
(3) The correspondence address for the account;
(4) The TIN of the owner, or in the case of ownership by two individuals, of the first-named owner; and
(5) Payment instructions. (See §357.26.)
(d) Securities portfolio. The securities portfolio contains a description of each security and is the aggregate of all securities in the securities account.
(e) Statement of account. The Department shall send a statement of account (statement):
(1) Upon the establishment of an account master record;
(2) Upon a change in the securities portfolio;
(3) At an owner's request; or
(4) Upon the determination on December 31 that an owner has not received a statement of account for that current calendar year.
The statement shall contain information regarding the account as of the date of such statement. The price associated with each security in the securities portfolio will also appear on the statement.1 The statement may be sent to the correspondence address designated in the account master record, or may be sent by electronic means. When the statement is issued as a result of a change in ownership of a security, statements will be sent, where appropriate, to both the former and current owners. Other information regarding the account may be obtained in accordance with §357.24.
1 IRS regulations require reporting of income information on a security.
(1) If the security is a bill, the price information will be used to comply with this requirement. The earnings reported to IRS for the year of a bill's maturity will be the difference between the par value of the bill and its price.
(a) If a bill is deposited in Legacy Treasury Direct at original issue, the price shown will be the issue price.
(b) If a bill is transferred to Legacy Treasury Direct from TRADES, the price shown will be that included in the transfer wire or supplied subsequently by the bill owner. If a price is not furnished, the price shown will be the weighted average price of the bill of the longest maturity having the identical CUSIP number.
(c) If a bill is transferred from one Legacy Treasury Direct account to another, the price shown in the receiving (transferee's) account will be that shown on the transfer instructions or supplied subsequently by the transferee. If a price is not furnished, the price shown will be the weighted average price at original issue of the bill of the longest maturity having the identical CUSIP number, unless the term of the bill can be determined from the account record in which case the price shown will be the weighted average price at original issue of the bill with that term.
(2) If the security is a note or bond, the earnings reported to IRS for a year will be the periodic interest payments made during that year. If a note or bond is transferred to a Legacy Treasury Direct account between interest payment dates, the earnings reported to IRS for the transferee will show the interest for the entire interest payment period. The price for notes and bonds will be shown on the statement of account for the account owner's information. The price shown will be determined following the procedures described above for bills.
(3) The security owner should report directly to the IRS (a) adjustments to annual earnings amounts arising from acquisition of notes and bonds between interest payment periods and (b) price corrections for bills reported after preparation of the reports to the IRS.
(f) Confirmation notice. The Department shall send a confirmation notice (notice):
(1) Upon a change in an account master record;
(2) Upon scheduling or canceling a reinvestment; or
(3) To confirm the interest earned on a Treasury Inflation Indexed Security. The notice shall contain information regarding the account as of the date of such confirmation. The notice may be sent to the correspondence address designated in the account master record, or may be sent by electronic means. All changes reflected in paragraph (f) (1) and (2) of this section will be included in the next regularly scheduled statement of account. See paragraph (e) of this section for the statement schedule.
(g) Account maintenance fees. An annual maintenance fee shall be charged for each Legacy Treasury Direct securities account holding securities that in the aggregate exceed a stipulated par amount. The amount of the fee will be published by notice in the Federal Register. (Approved by the Office of Management and Budget under control number 1535–0068)
[51 FR 18265, May 16, 1986, as amended at 60 FR 4377, Jan. 23, 1995; 62 FR 18004, Apr. 11, 1997; 62 FR 32033, June 12, 1997]
§ 357.21 Registration.
top
(a) General. (1) Registration of a security conclusively establishes ownership, except in the case of partnership nominees, in which case the Department reserves the right to treat the registration as conclusive of ownership. The registration may not, except as provided in this Subpart, include any restriction on the authority of an owner to change the data in the account master record, transfer the security, or effect any other change in the securities portfolio.
(2) The registration of all securities held by an owner should be uniform with respect to the owner's name. An owner must be identified by the name by which the owner is ordinarily known, preferably including at least one full given name. A suffix, such as Sr. or Jr., must be included when ordinarily used, or when necessary to distinguish members of the same family.
(3) If an additional security is deposited in an existing account, the security will be registered in the same name and form of registration that appears in the designated account master record. One who holds a security as John Allen Doe should use that name when depositing another security rather than J. Allen Doe, or John A. Doe'. Minor variations in names used in acquiring a security to be deposited in an established account may be resolved by the Department.
(b) Natural persons. A security may be registered in the names of one or two individuals, but only in one of the following forms:
(1) Single ownership. In the name of one individual.
Example: Robert W. Woods
An individual who is sole proprietor of a business conducted under a trade name may include a reference to the trade name.
Example: John A. Doe, doing business as Doe's Home Appliance Store.
(2) Ownership by two individuals—(i) “And” form—Joint Ownership—(A) Without right of survivorship. In the names of two individuals, joined by the word “and”, and followed by the words “without right of survivorship”. A security so registered shall conclusively confer on each owner an undivided interest in the security.
Example: Elizabeth Black and Jane Brown, without right of survivorship.
Any request for registration which purports, by its terms, to preclude the right of survivorship, or which requests registration in the names of two persons without indicating whether survivorship rights attach (other than a registration under paragraph (b)(2)(ii) of this section), will be presumed to be a request for registration without right of survivorship. If a security is registered in this form, a transaction request, other than a request by one owner to transfer the security to the other owner, and other than a request for reinvestment, must be executed by both owners.
(B) With right of survivorship. In the names of two individuals, joined by the word “and”, and followed by the words “with right of survivorship”. A security so registered shall confer on each owner an undivided interest in the security and shall create a conclusive right of survivorship.
Example: Mark A. Doe and Mary B. Doe, with right of survivorship.
If a security is registered in this form, a transaction request, other than a request by one owner to transfer the security to the other owner, and other than a request for reinvestment, must be executed by both owners.
(ii) “Or” form—“Coownership”. In the names of two individuals, joined by the word “or”. A security so registered shall confer on each owner an undivided interest in the security and shall create a conclusive right of survivorship.
Example: Robert Woods or Laura Woods.
If a security is registered in this form, either coowner may make a transaction request, but if the Department receives conflicting requests at or about the same time, it may refuse to process them.
(iii) Beneficiary. In the name of one individual followed by the words “Payable on death to” (or “P.O.D.”) another individual.
Example: Jack S. Jones, payable on death to Marie Jones.
If a minor or an incompetent is named as a beneficiary, the status of the beneficiary must be identified in the registration. A minor or an incompetent may not be designated as an owner. See paragraphs (b)(3) and (4) of this section.
Example: John Perry, P.O.D. John Perry, Jr., a minor.
Registration in this form shall create ownership rights in the beneficiary only if the beneficiary survives the owner. During an owner's lifetime, a transaction request may be executed by the owner without the consent of the beneficiary. If the beneficiary dies before the owner, the security will be deemed to be registered in the owner's name alone.
(3) Minors—(i) General. A security may not be registered in the name of a minor in his or her own right as an owner. If a security is so registered and the Department thereafter receives evidence or information of that fact, the Department may suspend processing of any transaction request with respect to the security until either a legal guardian has been appointed or a natural guardian, as provided in paragraph (b)(3)(ii) of this section, has been recognized. Where a legal guardian is appointed, the Department will require a certified copy of the court order making such appointment. See §357.28(c).
(ii) Natural guardians of minors. A security may be registered in the name of a natural guardian of a minor for whose estate no legal representative has been appointed. The parent with whom the minor resides will be recognized as the natural guardian. If the minor resides with both parents, either or both may be recognized as natural guardian(s). If the minor does not reside with either parent, the Department may recognize the person who furnishes the minor's chief support as the natural guardian.
Examples: Michael Jones, as natural guardian of Alice Jones, a minor. Michael Jones and Evelyn Jones, as natural guardians of Alice Jones, a minor.
The security may also be registered in one of the forms authorized under paragraph (b)(2) of this section.
Examples: James Green, as natural guardian of William Green, a minor, and Anne Green, without right of survivorship. James Green, as natural guardian of William Green, a minor, POD Lynne Green.
(iii) Custodian under statute authorizing gifts to minors. A security may be registered as provided under an applicable gift to minors statute.
Example: Virginia McDonald, as custodian for Lynne Gorman, under the New York Uniform Gifts to Minors Act.
Any request to alter the rights of ownership of the security must be made as provided in the applicable statute.
(4) Incompetents—(i) General. A security may not be registered in the name of an individual in his or her own right as an owner if that individual is incompetent. If a security is so registered, or if the owner subsequently becomes incompetent after the security is purchased, and the Department receives evidence or information of that fact, the Department may suspend any transaction with respect to the security until a legal guardian, conservator, or other representative of the incompetent's estate has been appointed, or a voluntary guardian, as provided in paragraph (b)(3)(ii) of this section, has been recognized. Where a legal guardian, conservator, or other representative is appointed, the Department will require a certified copy of the court order making such appointment. See §357.28(c).
(ii) Voluntary guardian of incompetent. If a legal guardian has not been appointed, and the face amount of the securities held in one or more accounts in Legacy Treasury Direct® by an owner who had become incompetent does not exceed, in the aggregate, $20,000 (par amount), upon submission to, and approval by, the Department of an appropriate form, a relative or other person responsible for an incompetent's care and support will be recognized as voluntary guardian for purpose of making a transaction request under §357.28(b)(4). All persons known by the Department to have an interest in the incompetent's estate, as required by the application form, must agree to the designation of the voluntary guardian. The security may be re-registered in the name of the voluntary guardian.
Example: Richard Melrose, as voluntary guardian for James W. Brundige.
(c) Representatives. A security may be registered in the name of a representative of an estate. If there is more than one representative, the names of some representatives may be omitted if followed by language that indicates the existence of other representatives. In such cases, those named in the registration shall be conclusively presumed by the Department to have authority to make a transaction request on behalf of all the representatives. The form of registration must identify the specific capacity of the representative(s) and the estate represented.
Examples: ABC National Bank of Chicago, Illinois and Harold Smith, co-executors of the will (or administrators of the estate) of Charles Johnson, deceased. William Brown, guardian of the estate of Henry Jones, a minor.
Robert Smith, Richard Smith, et al., executors of the will of Lorraine Smith, deceased.
If the representative is a trustee, the form of registration must identify specifically the authority or document creating the trust.
Examples: Sarah Jones and XYZ Trust Co., trustees under the will of Matthew Smith, deceased. Cynthia Doe and Margaret Jones, trustees under agreement with Martha Roe, dated April 13, 1979. Cynthia Doe, trustee under declaration of trust, dated April 13, 1979. Richard Smith, James Jones, and Frank Brown, trustees under the will of Henry K. James, deceased. ABC Corporation, Myrna Banker, et al., trustees of Profit-Sharing Plan of Ace Manufacturing Co., under B/D resolution, dated May 18, 1975.
If there are several trustees designated as a board or authorized to act as a unit, their names should be omitted and the words, “Board of Trustees” substituted.
Example: Board of Trustees of Super Co. Retirement Fund, under collective bargaining agreement, dated March 18, 1969.
An organization (other than a bank) or individual seeking to act as trustee or custodian of an Individual Retirement Account (“IRA”), must be authorized to so act by the Internal Revenue Service. As appropriate, registration of the security should be in the form shown below:
Examples: ABC Bank, trustee for John Doe IRA, under agreement dated December 21, 1990.
EFG Broker, Inc., custodian for Mary Smith IRA, under agreement dated September 4, 1991.
(d) Private organizations (corporations, unincorporated associations and partnerships). A security may be registered in the name of a private corporation, unincorporated association, or partnership. The full legal name of the organization, as set forth in its charter, articles of incorporation, constitution, partnership agreement, or other documents from which its powers are derived, must be included in the registration. The name may be followed by a reference to a particular account or fund, other than a trust fund, such as an escrow account.
(1) A corporation. The legal name of a business, fraternal, religious, or other private corporation must be followed by descriptive words indicating the corporate status unless the term corporation or the abbreviation Inc. is part of the name or the name is that of a corporation or association organized under Federal law, such as a national bank or Federal savings and loan association.
Examples: Brown Manufacturing Co., a corporation (Education Fund). The Apex Manufacturing Corporation. XYZ National Bank of El Paso, TX. Goodworks, Unlimited, a not-for-profit corporation.
(2) An unincorporated association. Unless the name of a lodge, club, labor union, veterans or religious organization, or similar organization which is not incorporated (whether or not it is chartered by or affiliated with a parent organization which is incorporated) includes the words an unincorporated association, the registration must include descriptive words indicating the organization's unincorporated status. A security may not be registered in the name of an unincorporated association if the legal title to its property or the legal title to the funds with which the security is to be purchased is held by trustees. In such a case, the security should be registered in the name of the trustees in accordance with paragraph (c) of this section. The term unincorporated association should not be used to describe a trust fund, a partnership or a business conducted under a trade name.
Examples: Local Union No. 13, Brotherhood of Operating Engineers, an unincorporated association. The Simpson Society, an unincorporated association.
(3) Partnership. Unless the name of a partnership includes the word partnership, the registration must include descriptive words indicating partnership status.
Examples: Red & Blue, a partnership. Abco and Co., a nominee partnership.
(e) Governmental entities and officers. A security may be registered in the name of a State, county, city, town, village, school district, or other governmental entity, body, or corporation established by law. If a governmental officer is authorized to act as a trustee or custodian, a security may be registered in the title, or name and title, of the governmental officer. The form of registration should reflect the capacity in which the governmental entity or officer is authorized to hold property (e.g., it may be authorized to hold property in its own name or as trustee or custodian).
Examples: Laura Woods, Treasurer, City of Twin Falls, Mo. State of Michigan. Village of Gaithersburg, Md. Pennsylvania State Highway Administration (Highway Road Repair Fund). Insurance Commissioner of Florida, trustee for benefit of policy holders of Sunshine Insurance Co. under F.S.A. Sec. 629.104. Commonwealth of Virginia, in trust for Virginia Surplus Property Agency. Gleason County Cemetery Commission, trustee under Md. Code Ann. Sec. 310.29.
(f) The United States Treasury. A security may be registered in the name of an individual, with the United States Treasury as beneficiary, provided a reference to the statute which authorizes gifts to be made to the United States to reduce the public debt, is included.
Example: John S. Green, payable on death [or P.O.D.] to U.S. Treasury to reduce the public debt (31 U.S.C. 3113). (Approved by the Office of Management and Budget under control number 1535–0068)
[51 FR 18265, May 16, 1986, as amended at 57 FR 38774, Aug. 27, 1992]
§ 357.22 Transfers.
top
(a) General. A security may be transferred only as authorized by this part. A security may be transferred among accounts in Legacy Treasury Direct®, the commercial book-entry system, and TreasuryDirect®. A security may also be transferred between accounts in Legacy Treasury Direct. The Department may delay transfer of a newly purchased security from a Legacy Treasury Direct account to an account in commercial book entry or TreasuryDirect for a period not to exceed (30) calendar days from the date of issue. This provides time for the investor to become aware of any unauthorized debits.
(1) Identification of securities to be transferred. The owner must identify the securities to be transferred, in the manner required by the transaction request. If such identification is not provided, the request will not be processed and will be returned.
(2) Denominational amounts. A security may be transferred from an account only in a denominational amount authorized by the offering under which the security was issued. Any security remaining in the securities portfolio after the transfer must also be in an authorized denominational amount.
(3) When transfer effective. (i) Transfer within Legacy Treasury Direct or to Legacy Treasury Direct from the commercial book-entry system or TreasuryDirect. A transfer of a security within Legacy Treasury Direct, or to Legacy Treasury Direct from another book-entry system, is effective when an appropriate entry is made in the name of the transferee on the Legacy Treasury Direct records.
(ii) Transfer from Legacy Treasury Direct to the commercial book-entry system. A transfer of a security from Legacy Treasury Direct to the commercial book-entry system is effective as provided in Subpart B. If a transfer cannot be completed, and the security is sent back to Legacy Treasury Direct, the Department will redeposit the security in the original account.
(iii) Transfer from Legacy Treasury Direct to TreasuryDirect. A transfer of a security from Legacy Treasury Direct to TreasuryDirect is effective as provided in 31 CFR part 363. If the transfer cannot be completed, the Department will redeposit the security in the original account.
(b) Transfer to Federal Reserve Bank for sale of securities in the secondary market. (1) Upon authorization by the investor, an unmatured security may be transferred to a Federal Reserve Bank acting as the designated fiscal agent of the United States, to be sold on behalf of the investor.
(2) Definitions. In this section, unless the context indicates otherwise:
Dealer means an entity that is registered or has given notice of its status as a government securities broker or government securities dealer, pursuant to Section 15C(a)(1) of the Securities Exchange Act of 1934.
Par amount means the stated value of a security at original issuance.
Price means the dollar amount to be paid for a security expressed as a percent of its current par amount.
Security means any amount held in a Legacy Treasury Direct account which is represented by a separate CUSIP number.
Settlement amount, also referred to as net amount, is the amount deposited by the Federal Reserve Bank to the account of the investor at the financial institution designated by the investor to receive Legacy Treasury Direct payments. This amount is equal to the par amount of the securities multiplied by the price, plus any accrued interest, and less the transaction fee. For inflation indexed securities, the settlement amount also includes any applicable inflation adjustment, as provided in 31 CFR Part 356. The settlement amount may be less than the par amount of the security.
Settlement date is the date the settlement amount is released to the account at the financial institution designated by the investor for receipt of Legacy Treasury Direct payments.
Trade date means the date on which the Federal Reserve Bank enters into an agreement with a dealer for the sale of the security.
Yield, also referred to as yield to maturity, means the annualized rate of return to maturity on a fixed principal security expressed as a percentage. For an inflation-indexed security, yield means real yield, as defined in 31 CFR part 356.
(3) Procedure. On an approved Treasury form, the owner must authorize a transfer of the security from the investor's Legacy Treasury Direct account to the designated Federal Reserve Bank, and authorize the Federal Reserve Bank to sell the security. Rules in subpart C of this part governing the transfer of securities will apply to the transfer of the security to the Federal Reserve Bank. Generally, on the day that the security is transferred to the Federal Reserve Bank, the Federal Reserve Bank will make reasonable efforts to obtain a price quote from at least three dealers, and will enter into an agreement to sell the security to the dealer with the highest price quote for next day settlement. What constitutes reasonable effort shall be determined solely by the Federal Reserve Bank. On the next full business day after the trade date, the settlement amount shall be released by direct deposit (electronic funds transfer), as provided in §357.26 of this part, to the account at the financial institution designated by the investor to accept Legacy Treasury Direct payments, except when the Department determines that extraordinary circumstances exist that require payment by other means. In the event that the Federal Reserve Bank is unable to obtain at least one price quote for the security, the security will be returned to the Legacy Treasury Direct account of the investor on the next full business day following the receipt of the securities by the Federal Reserve Bank, and the Federal Reserve Bank will notify the investor.
(4) Confirmation. The Federal Reserve Bank will send a confirmation of the sale to the investor upon completion of the transaction. Such confirmation will include such information as price, trade date, settlement date, settlement amount, also referred to as net amount, transaction fee, and yield to maturity.
(5) Price. By authorizing the transfer and sale of the securities, the investor agrees to accept the price received by the Federal Reserve Bank from the dealer selected as having the highest price quote.
(6) Transaction fee. A transaction fee shall be charged for each security sold on behalf of the investor. If the Federal Reserve Bank is unable to complete the sale of the security, no fee will be charged. By authorizing the sale of the security, the investor authorizes the Federal Reserve Bank to withhold the transaction fee prior to the Federal Reserve Bank initiating the payment of the settlement amount to the account at the financial institution designated by the investor to receive Legacy Treasury Direct payments. The amount of the transaction fee will be published by notice in the Federal Register.
(7) Termination. This service may be terminated at anytime without prior notice at the discretion of the Department.
(8) Rights. The provisions applicable to Legacy Treasury Direct transactions in subpart C shall apply to this section. The provisions applicable to transactions in TRADES in subpart B shall not apply to this section.
(9) Irrevocability. The authorization of the investor for the transfer and sale of the securities shall be irrevocable when the transfer from the Legacy Treasury Direct account of the investor to the account at the Federal Reserve Bank is effected.
(10) Liability. The Department and the designated Federal Reserve Bank shall not be liable for changes in market conditions affecting the price received for the security, or for any loss which the investor may incur as a result of the transaction or the inability of the Federal Reserve Bank to complete the transaction.
(c) Transfer upon death of an owner—(1) Right of survivorship. If a security is registered in beneficiary form or a form which provides for a right of survivorship, upon the death of an owner, the beneficiary or survivor shall be the sole and absolute owner, notwithstanding any purported testamentary disposition by the decedent and notwithstanding any State or other law to the contrary. The Department will honor a transaction request by a beneficiary or a survivor (in the case of a security registered in the form described in §357.21(b)(2)(i)(B)) only upon proof of death of an owner.
(2) Succession under law of domicile. If a security is registered in a form that does not provide for a right of survivorship, succession shall be determined in accordance with the applicable law of the deceased owner's domicile at the time of death.
(d) Representative succession. If a security is registered in the name of a representative who has died, resigned, or been removed, succession shall be determined in accordance with applicable law and the terms of the document under which the representative was acting.
(e) Organizational succession—(1) Corporation and unincorporated association. If a security is registered in the name of a corporation or an unincorporated association that has been dissolved, merged or consolidated into another organization, succession shall be determined in accordance with applicable law and the terms of the documents by which the dissolution, merger, or consolidation was effected.
(2) Partnership. If a partnership is dissolved or terminated, succession shall be determined in accordance with applicable law and the terms of the partnership agreement.
(f) Succession of governmental officer. If a security is registered in the name and title of a governmental officer who has died, resigned, or has been removed, succession shall be determined in accordance with applicable law. (Approved by the Office of Management and Budget under control number 1535–0068)
[51 FR 18265, May 16, 1986; 51 FR 18884, May 23, 1986, as amended at 53 FR 10074, Mar. 29, 1988; 62 FR 46861, Sept. 4, 1997; 64 FR 6527, Feb. 10, 1999; 70 FR 57441, Sept. 30, 2005]
§ 357.23 Judicial proceedings—sovereign immunity.
top
(a) Department and Federal Reserve Banks not proper parties. The Department and the Federal Reserve Banks are not proper defendants in a judicial proceeding involving competing claims to a security held in Legacy Treasury Direct® nor are they subject to any injunction or restraining order issued with respect to a security. The Department will not recognize a notice of a pending or contemplated judicial or administrative proceeding affecting a security in Legacy Treasury Direct.
(b) Orders—(1) Ownership rights. The Department will recognize a final order entered by a court that affects ownership rights in a security in Legacy Treasury Direct if:
(i) The order is consistent with the provisions of this subpart and the terms and conditions of the security; and
(ii) The Department has received evidence of the order, as provided in paragraph (c) of this section.
(2) Transaction request. The Department will honor a transaction request submitted by a person appointed by a court and having authority under an order of a court to dispose of the security or payment with respect thereto if:
(i) The ordered disposition of the security or payments with respect thereto is consistent with the provisions of this subpart and the terms and conditions of the security; and
(ii) The Department has received evidence of the appointment and order, as provided in paragraph (c) of this section.
(c) Evidence required. Before the Department will recognize an order or determination entered by a court, the Department must have received a certified copy of the judgment, decree, or order and any additional documents deemed necessary by the Department. A certificate from the clerk of the court, bearing the seal of the court, must also be submitted stating that the judgment, decree, or order is still in full force and has not been stayed or appealed, and that the time for filing an appeal has passed. Before the Department will honor a transaction request submitted by a person appointed by a court, the Department must receive a certified copy of the order making the appointment and describing specifically the person's authority, and any additional documents deemed necessary by the Department. (Approved by the Office of Management and Budget under control number 1535–0068)
§ 357.24 Availability and disclosure of Legacy Treasury Direct® records.
top
(a) General. All records with respect to a Legacy Treasury Direct account are held confidential. Consistent with the Privacy Act (5 U.S.C. 552a), information relating to those accounts will be released only to the owner except:
(1) As provided in these regulations;
(2) As provided in Treasury regulations contained in 31 CFR Part 323; or
(3) As otherwise provided by law.
(b) Inquiries by owners. Information requested will be disclosed to an owner provided that:
(1) Sufficient information is provided to identify the owner; and
(2) Sufficient information is provided to identify the Legacy Treasury Direct account.
(c) Conditions for release. A request for information will be honored only if, in the sole judgment of the Department or the Federal Reserve Bank to which the inquiry is made, the identity and right of the requester to the information have been established.
[51 FR 18265, May 16, 1986; 51 FR 18884, May 23, 1986]
§ 357.25 Security interests.
top
(a) General. The Department will not recognize any notice or claim of a lien, encumbrance, or security interest of any kind, including a pledge, in a security in Legacy Treasury Direct® except as provided in §357.23 and in paragraph (b) of this section.
(b) Security for the performance of duty or obligation under Federal law. The Department will accept and hold pursuant to the provisions of 31 U.S.C. 9303, book-entry bonds, notes or bills submitted in lieu of a surety bond as security for the performance of a duty or obligation required by Federal law in accordance with said section.
§ 357.26 Direct Deposit.
top
(a) General. A payment by the Department with respect to a security shall be by direct deposit unless it is deemed necessary by the Department to make payment by another means. Direct Deposit payments are governed by the regulations at 31 CFR part 370.
(b) Names on account. Where the Legacy Treasury Direct® securities account is in the name of individual(s) in their own right, and the deposit account at the financial institution is in the name of individual(s) in their own right, the two accounts must contain at least one name that is common to both.
(c) Inquiry to financial institution. Where the deposit account to which payments are to be directed is held in the name of the financial institution itself acting as sole trustee, or as co-trustee, or is in the name of a commercially-managed investment fund, particular inquiry should first be made of the financial institution to make certain that the direct deposit payments can be received, and alternate arrangements made if it cannot do so.
(d) Payments to master account. All payments relating to a single account master record must be made to the same designated account at a financial institution.
(e) Deposit account. The deposit account to which payments are directed should preferably be established in a form identical to the registration of the securities account, particularly where the securities are registered jointly or with right of survivorship, to assure that the rights of ownership and of survivorship can be more easily identified and preserved. Neither the United States nor any Federal Reserve Bank shall be liable for any loss sustained because the interests of the holder(s) of a deposit account to which payments are made are not the same as the interests of the owner(s) of the security. (Approved by the Office of Management and Budget under control number 1535–0068)
[51 FR 18265, May 16, 1986, as amended at 57 FR 38774, Aug. 27, 1992; 61 FR 6113, Feb. 16, 1996; 64 FR 40487, July 26, 1999]
§ 357.27 Reinvestment.
top
(a) General. Upon the request of an owner, the redemption proceeds of a security may be reinvested at maturity in a new security in the same form of registration, provided a new security is then being offered by the Department and provision for reinvestment is made in the offering. The new security must be in an authorized denominational amount and will be issued in accordance with the terms of the offering. If the new security is issued at a premium or with accrued interest, an additional payment will be required from the investor. If the new security is issued at a discount, the difference will be remitted to the owner.
(b) Treasury bills. A request by an owner for a single or successive reinvestment of a Treasury bill must be made in accordance with the terms prescribed on the tender form submitted at the time of purchase of the original bill, or by a subsequent transaction request received not less than ten (10) business days prior to the maturity date of the bill. A request to revoke a direction to reinvest the proceeds of a bill must be received by the Department not less than ten (10) business days prior to the maturity date of the bill. If either a request for reinvestment or revocation of a reinvestment request is received less than ten (10) business days prior to maturity of the original bill, the Department may in its discretion act on such request if sufficient time remains for processing.
(c) Issue date not coincidental with maturity date. If the date on which a security matures or is called does not coincide with the issue date of the security being purchased through reinvestment, the Department may, at its option, hold the redemption proceeds in the same form of registration as the maturing or called security, but no interest shall accrue or be paid on such funds. (Approved by the Office of Management and Budget under control number 1535–0068)
[51 FR 18265, May 16, 1986, as amended at 62 FR 18694, Apr. 16, 1997]
§ 357.28 Transaction requests.
top
(a) General. Unless otherwise authorized by the Department, a transaction request must be submitted on a transaction request form. In the case of certain transactions specified by the Department, the owner's signature on the form must be certified or guaranteed, as provided in §357.31. If the transaction request form is received more than six (6) months after its execution, it will not be honored by the Department and will be returned to the sender for further instructions.
(b) Individuals—(1) General. A transaction request must be signed by the owner of the security. In addition to any required certification, a transaction request form executed by a person by mark, e.g., “(X)”, must be witnessed by a disinterested person. The following language should be added to the form and be signed by the witness:
Witness to signature by mark ____________________
Signature of witness ____________________
Address of witness
(2) Change of name. If an individual's name has been changed from that appearing in the registration, the individual should sign both names to the transaction request form and state the manner in which the change occurred.
Example: Deborah L. Gains, changed by order of court from Deborah G. O'Brien.
The individual must provide evidence, such as a certified copy of a court order, which confirms the change, unless it is indicated that the change of name resulted from marriage.
Example: Catherine M. Cole, changed by marriage from Catherine T. Murray.
(3) Natural guardians. A transaction request involving a security registered in the name of a natural guardian of a minor may be executed by the natural guardian. If a security is registered in the names of both parents as natural guardians of a minor, both must execute a transaction request. However, the Department will not honor a transaction request by the natural guardian(s):
(i) Which would transfer the security to a natural guardian in his or her own right; or
(ii) After the Department receives notice of the minor's attainment of majority, the qualification of a legal guardian or similar representative, or the death of the minor.
(4) Voluntary guardians. A transaction request involving a security belonging to an owner who has become incompetent may be executed by a voluntary guardian, but only after approval by the Department of the voluntary guardian's application for such designation. However, the Department will not honor a transaction request by the voluntary guardian:
(i) Which would transfer the security to a voluntary guardian in his or her own right; or
(ii) After the Department receives notice of the ward's restoration to competency, the qualification of a legal guardian or similar representative, or the death of the ward. See §357.21(b)(4).
(c) Representatives—(1) General. Any representative of an owner's estate, other than a trustee, may execute a transaction request form if the representative submits to the Department properly authenticated evidence of the authority to act. The evidence will not be accepted if dated more than one year prior to the date of submission of the transaction request.
(2) Decedent's estate has been settled previously. If a decedent's estate has been settled previously through judicial proceedings, the persons entitled may make a transaction request. A certified copy of the court-approved final accounting for the estate, the court's decree of distribution, or other appropriate evidence will be required.
(3) Special provisions under the law of the jurisdiction of the decedent's domicile. If there is no formal or regular administration and no representative of the decedent's estate is to be appointed, the person appointed to receive or distribute the assets of a decedent's estate without regular administration under applicable local law summary or small estates procedures may make a transaction request. Appropriate evidence will be required.
(4) When administration is required. If the total redemption value of the Treasury securities and undelivered payments, if any, held directly on our records that are the property of the decedent's estate is greater than $100,000, administration of the decedent's estate will be required. The redemption value of savings bonds and the principal amount of marketable securities will be used to determine the value of securities, and will be determined as of the date of death. Administration may also be required at the discretion of the Department for any case.
(5) Voluntary representative for small estates of decedents that are not being otherwise administered. (i) General. A voluntary representative is a person qualified according to paragraph (c)(5)(iii) of this section, to make a transaction request. The voluntary representative procedures are for the convenience of the Department; entitlement to the decedent's securities and held payments, if any, is determined by the law of the jurisdiction in which the decedent was domiciled at the date of death. Voluntary representative procedures may be used only if:
(A) There has been no administration, no administration is contemplated, and no summary or small estate procedures under applicable local law have been used;
(B) The total redemption value of the Treasury securities and held payments, if any, that are the property of the decedent's estate is $100,000 or less as of the date of death; and
(C) There is a person eligible to serve as the voluntary representative according to paragraph (c)(5)(iii) of this section.
(ii) Authority of voluntary representative. A voluntary representative may make a transaction request to distribute the securities to or for the benefit of the persons entitled by laws of the jurisdiction in which the decedent was domiciled at the date of death.
(iii) Order of precedence for voluntary representative. An individual eighteen years of age or older may act as a voluntary representative according to the following order of precedence: A surviving spouse; if there is no surviving spouse, then a child of the decedent; if there are none of the above, then a descendant of a deceased child of the decedent; if there are none of the above, then a parent of the decedent; if there are none of the above, then a brother or sister of the decedent; if there are none of the above, then a descendant of a deceased brother or sister of the decedent; if there are none of the above, then a next of kin of the decedent, as determined by the law of the jurisdiction in which the decedent was domiciled at the date of death. As used in this order of precedence, child means a natural or adopted child of the decedent.
(iv) Liability. By serving, the voluntary representative warrants that the distribution of securities or proceeds is to or on behalf of the persons entitled by the law of the jurisdiction in which the decedent was domiciled at the date of death. The United States is not liable to any person for the improper distribution of securities or proceeds. Upon distribution of the securities or proceeds at the request of the voluntary representative, the United States is released to the same extent as if it had paid or delivered to a representative of the estate appointed pursuant to the law of the jurisdiction in which the decedent was domiciled at the date of death. The voluntary representative shall indemnify and hold harmless the United States and all creditors and persons entitled to the estate of the decedent. The amount of the indemnification is limited to an amount no greater than the value received by the voluntary representative.
(v) Creditor. If there has been no administration, no administration is contemplated, no summary or small estate procedures under applicable local law have been used, and there is no person eligible to serve as a voluntary representative pursuant to paragraph (e) of this section, then a creditor may make a claim for payment of the amount of the debt, providing the debt has not been barred by applicable local law.
(d) Private organizations—(1) Corporations and unincorporated associations. A transaction request involving a security registered in the name of a corporation or an unincorporated association (either in its own right or in a representative capacity), may be executed by an authorized person on its behalf. The request must be supported by evidence of the person's authority to act.
(2) Partnerships. A transaction request involving a security registered in the name of a partnership must be executed by a general partner.
(e) Government entities. A transaction request involving a security registered in the name of a State, county, city, school district, or other governmental entity, public body or corporation, must be executed by an authorized officer of the entity. The request must be supported by evidence of the officer's authority to act.
(f) Public officers. A transaction request involving a security registered in the title of a public officer must be executed by the officer. The request must be supported by evidence of incumbency.
(g) Attorneys-in-fact. A transaction request made by an attorney-in-fact must be accompanied by the original power of attorney or a properly authenticated copy. A power of attorney must be executed in the presence of a notary public or a certifying individual. See §357.31. The power of attorney will not be accepted if it was executed more than two (2) years before the date the transaction request was executed, unless the power provides that the authority of the attorney-in-fact continues notwithstanding the incapacity of the principal. If two or more attorneys-in-fact are named, all must execute the transaction request unless the power authorizes fewer than all to act. A transaction request executed by an attorney-in-fact seeking transfer of a security to the attorney-in-fact will not be accepted unless expressly authorized by the document appointing the attorney-in-fact. (Approved by the Office of Management and Budget under control number 1535–0068)
[51 FR 18265, May 16, 1986; 51 FR 18884, May 23, 1986, as amended at 70 FR 57431, Sept. 30, 2006]
§ 357.29 Time required for processing transaction request.
top
For purposes of a transaction request affecting payment instructions with respect to a security, a proper request must be received not less than ten (10) business days preceding the next payment date. If a transaction request is received less than ten (10) business days preceding a payment date, the Department may in its discretion act on such request if sufficient time remains for processing. If a transaction request is received too late for completion of the requested transaction, the transaction request will be acted upon with respect to future payments only. (Approved by the Office of Management and Budget under control number 1535–0068)
[51 FR 18265, May 16, 1986, as amended at 62 FR 18694, Apr. 16, 1997]
§ 357.30 Cases of delay or suspension of payment.
top
If evidence required by the Department in support of a transaction request is not received by the Department at least ten (10) business days before the maturity date of the security, or if payment at maturity has been suspended pursuant to 31 CFR 370.10, in cases of reinvestment, the Department will redeem the security and hold the redemption proceeds in the same form of registration as the security redeemed, pending further disposition. No other interest shall accrue or be paid on such proceeds after the security is redeemed.
[64 FR 40487, July 26, 1999]
§ 357.31 Certifying individuals.
top
(a) General. The following individuals may certify signatures on transaction request forms:
(1) Officers and employees of depository institutions, corporate central credit unions, and institutions that are members of Treasury-recognized signature guarantee programs who have been authorized:
(i) Generally to bind their respective institutions by their acts;
(ii) Unqualifiedly to guarantee signatures to assignments of securities; or
(iii) To certify assignments of securities.
(2) Officers and authorized employees of Federal Reserve Banks.
(3) Officers of Federal Land Banks, Federal Intermediate Credit Banks and Banks for Cooperatives, the Central Bank for Cooperatives, and Federal Home Loan Banks.
(4) Commissioned officers and warrant officers of the Armed Forces of the United States but only with respect to signatures executed by Armed Forces personnel, civilian field employees, and members of their families.
(5) Such other persons as the Commissioner of the Public Debt or his designee may authorize.
(b) Foreign countries. The following individuals are authorized to certify signatures on transaction request forms executed in a foreign country:
(1) United States diplomatic or consular officials.
(2) Managers and officers of foreign branches of depository institutions and institutions that are members of Treasury-recognized signature guarantee programs.
(3) Notaries public and other officers authorized to administer oaths, provided their official position and authority are certified by a United States diplomatic or consular official under seal of the office.
(c) Duties and liabilities of certifying individuals— (1) General. Except as specified in paragraph (c)(2) of this section, a certifying individual shall require that the transaction request form be signed in the certifying individual's presence after he or she has established the identity of the person seeking the certification. An employee who is not an officer should insert the words “Authorized signature” in the space provided for the title. A certifying individual and the organization for which he or she is acting are jointly and severally liable for any loss the United States may incur as a result of the individual's negligence in making the certification.
(2) Signature guaranteed. The transaction request form need not be executed in the presence of a certifying individual if he or she unqualifiedly guarantees the signature, in which case the certifying individual shall, after the signature, add the following endorsement: “Signature guaranteed, First National Bank of Smithville, Smithville, NH, by A.B. Doe, President”, and add the date. In guaranteeing a signature, the certifying individual and the organization for which he or she is acting warrant to the Department that the signature is genuine and that the signer had the legal capacity to execute the transaction request.
(3) Absence of signature guaranteed by depository institution. A transaction request form need not be actually signed by the owner in any case where a certifying individual associated with a depository institution has placed an endorsement on the form reading substantially as follows: “Absence of signature by owner and validity of transaction guaranteed, Second State Bank of Jonesville, Jonesville, NC, by B.R. Butler, Vice President”. The endorsement should be dated, and the seal of the institution should be added. This form of endorsement is an unconditional guarantee to the Department that the institution is acting for the owner under proper authorization.
(d) Evidence of certifying individual's authority. The authority of a certifying individual to act is evidenced by affixing to the certification the following:
(1) Officers and employees of depository institutions. The institution's seal or signature guarantee stamp; if the institution is an authorized paying agent for U.S. Savings Bonds, a legible imprint of the paying agent's stamp; or, if the institution is a member of the Security Transfer Agents Medallion Program (STAMP), a legible imprint of the STAMP signature guarantee stamp.
(2) Officers and authorized employees of institutions that are members of Treasury-recognized signature guarantee programs. A legible imprint of the program's signature guarantee stamp, e.g., the STAMP, SEMP, MSP stamp for members of the Securities Transfer Agents Medallion Program, the Stock Exchanges Medallion Program, or the New York Stock Exchange Incorporated Medallion Signature Program, respectively.
(3) Officers and authorized employees of Federal Reserve Banks. Whatever is prescribed in procedures established by the Department.
(4) Officers and employees of corporate central credit unions and other entities listed in paragraph (a)(3) of this section. The entity's seal.
(5) Notaries public, diplomatic or consular officials. The official seal or stamp of the office. If the certifying individual has no seal or stamp, then the official's position must be certified by some other authorized individual, under seal or stamp, or otherwise proved to the satisfaction of the Department.
(6) Commissioned or warrant officers of the United States Armed Forces. A statement which sets out the officer's rank and the fact that the person executing the transaction request is one whose signature the officer is authorized to certify under the regulations in this part.
(7) Such other persons as the Commissioner of the Public Debt or his designee may authorize. The evidence specified by the Commissioner or his designee.
(e) Interested persons not to act as certifying individual. Neither the transferor, the transferee, nor any person having an interest in a security involved in the transaction may act as a certifying individual. However, an authorized officer or employee of a depository institution or of an institution that is a member of a Treasury-recognized signature guarantee program may act as a certifying individual on a transaction request for transfer of a security to the institution, or any request executed by another individual on behalf of the institution.
[59 FR 59038, Nov. 15, 1994]
§ 357.32 Submission of transaction requests; further information.
top
Transaction requests and requests for forms and information may be submitted to any Federal Reserve Bank or to the Bureau of the Public Debt, Legacy Treasury Direct®, Washington, DC 20239–0001. A list of the addresses of Federal Reserve Banks will be available upon request to the Bureau. The Federal Reserve Banks, as fiscal agents of the United States, are authorized to perform such functions as may be delegated to them by the Department in order to carry out the provisions of this part.
Subpart D—Additional Provisions
top
§ 357.40 Additional requirements.
top
In any case or any class of cases arising under these regulations, the Secretary of the Treasury (“Secretary”) may require such additional evidence and a bond of indemnity, with or without surety, as may in the judgment of the Secretary be necessary for the protection of the interests of the United States.
§ 357.41 Waiver of regulations.
top
The Secretary reserves the right, in the Secretary's discretion, to waive any provision(s) of these regulations in any case or class of cases for the convenience of the United States or in order to relieve any person(s) of unnecessary hardship, if such action is not inconsistent with law, does not adversely affect any substantial existing rights, and the Secretary is satisfied that such action will not subject the United States to any substantial expense or liability.
[61 FR 43630, Aug. 23, 1996]
§ 357.42 Liability of Department and Federal Reserve Banks.
top
The Department and the Federal Reserve Banks may rely on the information provided in a tender, transaction request form, or Transfer Message, and are not required to verify the information. The Department and the Federal Reserve Banks shall not be liable for any action taken in accordance with the information set out in a tender, transaction request form, or Transfer Message, or evidence submitted in support thereof.
[61 FR 43630, Aug. 23, 1996]
§ 357.43 Liability for transfers to and from Legacy Treasury Direct®.
top
A depository institution or other entity that transfers to, or receives, a security from Legacy Treasury Direct is deemed to be acting as agent for its customer and agrees thereby to indemnify the United States and the Federal Reserve Banks for any claim, liability, or loss resulting from the transaction.
§ 357.44 [Reserved]
top
§ 357.45 Supplements, amendments, or revisions.
top
The Secretary may, at any time, prescribe additional supplemental, amendatory or revised regulations with respect to securities, including charges and fees for the maintenance and servicing of securities in book-entry form.
Appendix A to Part 357—Discussion of Final Rule
top
Background
Twenty-four written comments were received to the notice of proposed rulemaking from various sources, including Federal agencies, trade associations, as well as financial and commercial investment institutions. With the exception of one bank, all commentators endorsed the concept of a certificateless security.
The grouping and identification of the comments received have been made on a section-by-section basis, with an explanation of the action taken with respect thereto. As circumstances necessitated the publication of the rule in two segments, in order to make each part more understandable, certain definitions, such as those for “Department” and “securities”, have appeared in the proposed rule for both Legacy Treasury Direct® and TRADES, and were slightly modified in the proposed rules on TRADES. Because these modifications represent non-substantive clarifications, and to avoid confusion as between the two portions of the rules, the definitions as used in TRADES have been adopted.
Section-By-Section Analysis
Section 357.21 Registration.
The forms of registrations provided for securities to be held in Legacy Treasury Direct have different legal effect from those currently provided for in the case of definitive Treasury securities and for the Treasury's book-entry Treasury bill system. A comment was received that, as a result, this could lead to some confusion, and that the Treasury bill forms of recordation currently offered should be changed, particularly since Treasury bills will be phased into Legacy Treasury Direct gradually. The Bureau believes that the benefits of uniformity of rights and interests that Legacy Treasury Direct investors will derive far outweigh any possible confusion. As for confusion with the current Treasury bill book-entry system, given the fact that Treasury bills have a term of not more than a year, it is believed that the problem, if any, will be short-lived.
Given the importance of the change that Legacy Treasury Direct provides as to registration, the discussion thereof that accompanied the Notice of Proposed Rulemaking is re-published below.
“Forms of Registration. The proposed rule provides the investor with a variety of registration options. They are essentially similar to those provided for registered, definitive marketable Treasury securities. Investors should be particularly aware that, where the security is held in the names of two individuals, the registration chosen may establish rights of survivorship.
“The reason for establishing the rights of ownership for securities held in Legacy Treasury Direct is that it will give investors the assurance that the forms of registration they select will establish conclusively the rights to their book-entry securities. It will also serve to eliminate some of the uncertainties, as well as possible conflicts, between the varying laws of the several States.
“A Federal rule of ownership is being adopted by the Treasury for Legacy Treasury Direct securities. This regulatory approach is consistent with the one previously taken in the case of United States Savings Bonds. It will have the effect of overriding inconsistent State laws. See, Free v. Bland, 369 U.S. 663 (1962).
“In the case of individuals (who are likely to be by far the majority of holders of securities in Legacy Treasury Direct), the options offered will permit virtually all the preferred forms of ownership. At the investor's option, it will be possible to provide for the disposition of the securities upon death through rights of survivorship.
“Coownership registration. One option is the coownership form of registration, i.e., “A or B.” Unlike the current Treasury bill book-entry system being administered by the Bureau of the Public Debt, a security held in Legacy Treasury Direct registered in this form will be transferable upon the written request of either coowner. Other changes in the account may also be made upon the request of either party. While this form of registration will facilitate the receipt of payments and provide ease in conducting transactions, care should obviously be exercised in designating a coowner.
“Joint ownership. For those who would prefer to have the transferability of a security held in two names contingent upon the request of both, the joint form of registration will be appropriate. This form of registration, i.e., “A and B, with [without] the right of survivorship,” will require the agreement of both parties to conduct any authorized transaction.
“Beneficiary form. The beneficiary form, i.e., “A payable on death to (POD) B,” will permit the owner to have sole control of the account during his/her lifetime, but in the event of death, the account will pass by right of survivorship to the beneficiary.”
One commentator questioned the “natural guardian” and “voluntary guardian” forms of registration provided in the regulations, pointing out that financial institutions are reluctant to establish an account in the name of a natural guardian of a minor because of the uncertainties as to who might be entitled to the funds on the death of the natural guardian or minor, or when the minor reached majority. It was mentioned that a bank would be reluctant to open an account in the name of a voluntary guardian, or to release funds from an existing account to a voluntary guardian because of the potential risk in the event of a claim from a court-appointed guardian. It seems apparent that the comment was prompted by the provision that appeared in the proposed rule that the account held in Legacy Treasury Direct and the deposit account to which payments are to be directed should be in the same form. As hereafter pointed out in the discussion under the payment section, this is not a requirement.
While parents are universally recognized as the natural guardians of the person of minors, they have generally not been recognized as entitled to control the estates of these minors, except perhaps in the case of small amounts. Traditionally, the guardian of the estate of a minor involves judicial appointment and supervision. In order to provide a means of dealing with the problem of disposing of securities inadvertently registered in the name of minors without requiring the appointment of a legal guardian and to provide a means for investing funds of a minor, which did not technically qualify for investment under the Uniform Gifts to Minors Act, the Department decided to provide recognition for natural guardians.
The voluntary guardianship procedure is wholly a creature of the Department's regulations. It was established in recognition of the burden placed on an incompetent's estate and his/her family by requiring the appointment of a legal guardian to receive the interest on, or to redeem securities for, the account of an individual who has become incompetent, at least where the incompetent's estate is relatively modest. This form of registration is not available on original issue and is limited to an aggregate of $20,000 (par amount) of Legacy Treasury Direct securities. The $20,000 limit in connection with the use of the voluntary guardianship procedure is in keeping with the limits used in connection with the summary administration of decedents' estates under the laws of many States.
Section 357.23 Judicial proceedings.
No comments were received regarding the provisions on judicial proceedings. Given their importance, the discussion that accompanied the publication thereof in proposed form is included here.
Judicial proceedings. Under the principle of sovereign immunity, neither the Department nor a Federal Reserve Bank, acting as fiscal agent of the United States, will recognize a court order that attempts to restrain or enjoin the Department or a Federal Reserve Bank from making payment on a security or from disposing of a security in accordance with instructions of the owner as shown on the Department's records.
“The Department will recognize a final court order affecting ownership rights in Legacy Treasury Direct securities provided that the order is consistent with the provisions of subpart C and the terms and conditions of the security, and the appropriate evidence, as described in §357.23(c), is supplied to the Department. For example, the Department may recognize final orders arising from divorce or dissolution of marriage, creditor or probate proceedings, or cases involving application of a State slayer's act. The Department will also recognize a transaction request submitted by a person appointed by a court and having authority under an order of a court to dispose of the security or payment with respect thereto, provided conditions similar to those above are met.”
Section 357.25 Security interests.
Legacy Treasury Direct is not designed to reflect or handle the various types of security interests that may arise in connection with a Treasury bond, note or bill. However, the Treasury has from time to time and to a limited extent held in safekeeping, for such agencies as the Customs Service and Immigration and Naturalization Service, Treasury securities submitted in lieu of surety bonds in accordance with 31 U.S.C. 9303. While the Federal Reserve Banks handle the majority of such pledges and will continue to do so, as this statute requires the Treasury to accept these Government obligations so pledged, a provision has been added for accepting and holding book-entry securities submitted for such purposes.
Section 357.26 Payments.
(a) General. Most comments focused on the provisions on payments. A key feature of Legacy Treasury Direct will be the making of payments by the direct deposit method (also known as the electronic funds transfer or ACH method). Checks will be issued only under extraordinary circumstances. A number of comments endorsed the concept of payment by direct deposit as an improvement given the difficulties associated with checks.
One comment expressed concern as to who would have the burden of resolving errors in cases where a receiving financial institution fails to properly credit a payment. The Department has concluded that while the direct deposit payment method is not without risks, it is far superior to the use of checks, in terms of the risks, potential losses, and costs. In a case where a receiving institution fails to act in accordance with the instructions given it, the Bureau intends to use its best efforts to assist investors in rectifying the error.
(b) Direct deposit. A number of comments expressed the view that the Legacy Treasury Direct payment system should adopt either the rules governing the direct deposit of Government payments (31 CFR part 210), or the rules of the National Automated Clearing House Association (“NACHA Rules”), but not separate rules. The final rules have adopted some of the existing practices applicable to commercial ACH payments, but it is not possible for the Department of the Treasury to conform to all of these rules. For example, the Treasury has no authority to indemnify recipients of direct deposit payments, although such indemnification by a sender is contemplated in the NACHA rules and was advocated in several comments. It should also be noted that the rules applicable to Legacy Treasury Direct payments are modeled, to some extent, on the rules for Government direct deposit payments in order to take advantage of the large number of entities that are a part of the Government direct deposit network. See the discussion under paragraph (b)(2). Where there are unique rules applicable to Legacy Treasury Direct, however, they are explained here.
Given the variance between the procedures set out in the proposed rules and existing practice, and the increased burdens resulting therefrom, several clearing house associations and financial institutions requested that the implementation of Legacy Treasury Direct be delayed from July 1986 to July 1987. The Treasury is satisfied that the added burdens that would have been imposed on financial institutions to receive Legacy Treasury Direct payments under the proposed rules have been effectively eliminated in the final rule. Thus, Treasury plans to implement the system on or about the original target date. The final rules are being published, however, in advance of actual implementation so as to give financial institutions an opportunity to make whatever remaining, minor procedural changes as may be necessary.
(b)(1) Information on deposit account at financial institution. The proposed regulations provided that the owner of a security in Legacy Treasury Direct, or in the case of ownership by two individuals, the first-named owner, must be an owner of, and so designated, on the account at the receiving financial institution. The regulations also provided that in any case in which a security is held jointly or with right of survivorship, the account at the financial institution should be established in a form that assures that the rights of each joint owner or survivor will be preserved.
The rule requiring the naming of the first-named owner on the receiving financial institution account was based on tax reporting considerations. It has now been determined that the first-named security owner need not be named on the receiving deposit account.
The rule relating to establishment of the receiving account in joint ownership cases in the same form as the registration of the security was intended to be a notice to investors of a potential problem, rather than a requirement. In cases where an investor intends a beneficiary, joint owner or coowner to receive securities after the investor's death, this intention may be defeated if the recipient is not also named on the receiving deposit account. It is up to the investor to examine his or her particular circumstances and determine whether the form in which the deposit account will be held is satisfactory. This matter has been clarified in paragraph (b)(1)(v) of the final rule. Except for the restriction described in paragraph (b)(1)(ii) (see below), the Treasury does not intend to establish any limitations on how the receiving deposit account is held.
Several comments addressed the issue of the registration of the security versus the title of the deposit account. Two comments pointed out that if the deposit account must be in the same form as the registration of the security, then existing traditional forms of ownership for bank accounts, which do not include all the forms of registration for securities held in Legacy Treasury Direct, would not suffice. Concerns were also expressed that with multiple forms of ownership, financial institutions could become involved in disputes with investors. As noted above, there is no requirement that the Legacy Treasury Direct account and the deposit account be identical. The responsibility to choose the title of the deposit account rests with the investor.
Another comment objected to the rule that the first-named security owner be named on the receiving deposit account because the rule would eliminate the possibility of payment to an account at a financial institution in the name of a mutual fund, security dealer, or insurance company. Although the change in the tax reporting rule described above permits payment to such accounts, as well as to trust accounts, since it appears that there is a question as to the capability of some receiving institutions to handle such payments, investors are strongly urged to consult their financial institution before requesting such payment arrangements. See paragraph (b)(1)(iii).
It should be emphasized that any payments that must be made by check will be made in the form in which the Legacy Treasury Direct account is held, which may be different than the form of the deposit account. Investors should be aware that this may result in checks being issued, and thus payment being made, in a form different than they intended the direct deposit payments to be made. For example, if Investor A purchases a security in his or her name alone with instructions that payments be directed to a financial institution for the account of a money market fund, any checks that must be issued will be drawn in the name of Investor A. This could happen if Investor A furnishes erroneous payment instructions and the problem cannot be resolved before a payment date, in which case a check would be issued.
The one restriction on the form of the deposit account that appears in paragraph (b)(1)(ii) of the final regulations is a rule that where the Legacy Treasury Direct account is in the name of individual(s), and the receiving deposit account is also in the name of individual(s), one of the individuals on the Legacy Treasury Direct account must be named on the deposit account. This rule is intended to provide a means to determine the disposition of the payment, if necessary. The Treasury does not expect financial institutions to monitor this rule.
Provision has been made in paragraph (b)(1)(vii) to permit financial institutions to request “mass changes” of deposit account numbers without the submission of individual requests from investors to Legacy Treasury Direct. This procedure is intended for use where an institution changes all or an entire group of its account numbers, typically as a result of an organizational change. Legacy Treasury Direct will honor requests from a financial institution to change deposit account numbers under such circumstances, with the understanding that the institution agrees to indemnify the Treasury and the security owners for any losses resulting from errors made by the institution. If the institutions does not wish to use the “mass change” procedure, then the change in account number must be requested by the investor, using the authorized transaction request form. See §357.28.
Some institutions voiced concern in general about investor errors in furnishing the Legacy Treasury Direct a deposit account number and the financial institution's routing number. Although the Treasury plans to provide as much assistance to investors as possible, the investor must bear the responsibility for securing accurate payment information. Investors are urged to consult with their receiving institution to verify the accuracy of the payment information, since neither the Treasury nor the receiving financial institution would be responsible for payment errors resulting from erroneous information provided by investors.
The proposed rule provided in §357.26(b)(1)(iii) that the designation of a financial institution by a security owner to receive payments from Legacy Treasury Direct would constitute the appointment of the financial institution as agent for the owner for the receipt of payments. The crediting of a payment to the financial institution for deposit to the owner's account, in accordance with the owner's instructions, would discharge the United States of any further responsibility for the payment. One comment noted that, in contrast, the rule in 31 CFR 210.13 for Federal recurring payments is that the United States is not acquitted until the payment is credited to the account of the recipient on the books of a financial institution.
Although, in principle, the same rules should apply to all Government payments, the proposed Legacy Treasury Direct rule has been retained in the final regulations on the basis of the major differences in the procedures to be used in Legacy Treasury Direct. Most significantly, the Treasury will not be securing any written verification (i.e., an enrollment form) from a financial institution as to the accuracy of the deposit account number and other payment information, as is now the practice in the case of payments under 31 CFR part 210. Under these circumstances, the Treasury cannot, in effect, guarantee that a payment will be credited by a financial institution to the correct account. It should also be noted that this rule on acquittance of the United States is consistent with the provision in §357.10(c) of the proposed regulations on TRADES. In practice, however, the Treasury plans to participate actively in seeking to locate and recover any payments that have been misdirected.
(b)(2) Agreement of financial institution. The proposed rule provided, in §357.26(b)(2), that a financial institution which has agreed to accept payments under 31 CFR part 210 shall be deemed to have agreed to accept payments from Legacy Treasury Direct. The rule further provided that an institution could not be designated to receive Legacy Treasury Direct payments unless it had agreed to accept direct deposit payments under 31 CFR part 210.
One financial institution commented that a receiving institution that has already agreed to accept part 210 payments should have the choice as to whether to accept payments from Legacy Treasury Direct. The basis for this comment was the perception that the receipt of Legacy Treasury Direct payments would require the implementation of special procedures by the financial institution and expose it to additional risks. As explained earlier, the Treasury has significantly modified the procedures and reduced the requirements imposed upon a financial institution in order to receive Legacy Treasury Direct payments, and decreased as well the risks an institution will incur in the receipt of such payments. Thus, the proposed rule on eligibility of receiving institutions has been retained in the final rule in essentially the same form.
Two other comments were made to the effect that the category of institutions receiving payments should be broadened. In deciding to authorize payments to all institutions receiving part 210 payments, the Treasury considered the fact that many more institutions are designated endpoints for Government (direct deposit) payments than for commercial ACH payments. In order to afford investors the widest choice of recipient institutions, all institutions that had agreed to accept part 210 payments were designated as authorized recipients. Treasury has now broadened the rule further to also authorize those financial institutions that are willing to agree to accept part 210 payments in the future. This rule will permit investors to designate institutions that are not now receiving Government direct deposit payments as the recipients of their Legacy Treasury Direct payments if the institutions make appropriate arrangements with the Federal Reserve Bank of their District.
(b)(3) Pre-notification. A significant feature of the Legacy Treasury Direct payment procedure will be the use of a pre-notification message sent to the receiving financial institution in advance of the first payment. This procedure, already in use for commercial ACH payments, alerts the institution that a payment will be made and provides an opportunity for verification of the accuracy of the account information.
The proposed regulations provided that the financial institution would be required to reject the pre-notification message within four calendar days after the date of receipt if the information contained in the message did not agree with the records of the institution or if for any other reason the institution would not be able to credit the payment. The rules also stated that a failure to reject the message within the specified time period would be deemed an acceptance of the pre-notification and a warranty that the information in the message was accurate.
Because there was some confusion over when the pre-notification message woud be sent, the final rules clarify, in paragraph (b)(3)(i), that in most cases, this will occur shortly after establishment of a Legacy Treasury Direct account. The Treasury has under consideration a system change that would permit a second pre-notification to be sent closer to the time of the payment if the first payment is to occur a substantial length of time after account establishment.
One of the items of information contained in a pre-notification message is the name the investor has indicated appears on the deposit account. Comments were received that existing procedures and software do not permit automatic verification of the account name. Although there is apparently some variation in practice, and some institutions undertake to verify the account name information manually, the Treasury has decided to drop the account name verification requirement in the final rules. This means that under paragraph (b)(3)(ii), a financial institution need only verify the account number and type designations on the pre-notification message. However, the Treasury urges institutions which are able to verify account names to do so and encourages the development of software that would have this capability.
A number of comments urged that the four-day period provided for an institution to reject a pre-notification message be lengthened. After consideration of the various alternatives proposed, the Treasury has concluded that an eight-day period will meet the needs of most institutions. See paragraph (b)(3)(ii) of the final rule. In responding to a pre-notification message, an institution may use the NACHA's “notification of change” procedure, standardized automated rejection codes, or any other similar standard procedure. Upon receipt of such notification, the Treasury will either make the necessary changes in the Legacy Treasury Direct account or contact the investor, depending on the circumstances.
One commentator objected to the warranty by the receiving institution as to the accuracy of the pre-notification information, particularly in view of the manual verification or changes in procedures that would be required, and the resulting possibility of error. As previously noted, the requirement to verify an account name has been eliminated. In addition, language has been added to make it clear that the verification is limited to the time of pre-notification. The Treasury is of the view that the warranty is a useful concept in encouraging institutions to respond to pre-notification messages and will benefit all concerned by increasing the likelihood that payments will be made accurately and to the appropriate party.
(b)(5) Responsibility of financial institution. The proposed regulations provided, in §357.26(b)(5)(ii), that a financial institution that receives a Legacy Treasury Direct payment on behalf of a customer would be required to promptly notify the Treasury when it has made a change in the status or ownership of the customer's deposit account, such as the deletion of the first-named owner of the security from the title of the account, or when the institution is on notice of the death or incompetency of the owner of the deposit account.
Several financial institutions objected to this requirement on the grounds that it would be burdensome and would require the development of new procedures to monitor the changes in deposit accounts. Specifically, several institutions indicated they would be unable to relate the receipt of Legacy Treasury Direct payments, which would be handled in a centralized area of the institution, to the changes being made in a deposit account, which are handled in another operational area of the institution. These institutions said they would not necessarily be aware of who is the first-named owner of the security in Legacy Treasury Direct, and that more responsibility should be placed on the security owner in reporting changes.
In response to these comments, the Treasury has narrowed the notification rule, in paragraph (b)(5)(ii) of the final rule, to require a financial institution to notify Legacy Treasury Direct only in cases where it is on notice of the death or legal incapacity of an individual named on the deposit account, or where it is on notice of the dissolution of a corporation named in the deposit account. Upon receipt of notice by the area of the institution that receives credit payments, the institution will be required to return any Legacy Treasury Direct payments received thereafter.
(b)(6) Payments in error/duplicate payments. The proposed regulations, in §357.26(b)(6), set out rules describing the procedure that would be followed in cases where the Treasury or a Federal Reserve Bank has made a duplicate payment or a payment in error. First, the financial institution to which the payment was directed would be provided with a notice asking for the return of the amount of the payment remaining in the deposit account. If the financial institution were unable to return any part of the payment, it would be required to notify the Treasury or its Federal Reserve Bank, and provide the names and addresses of the persons who withdrew funds from the deposit account after the date of the duplicate payment or the payment in error. If the financial institution did not respond to the notice within 30 days, the financial institution's account at its Federal Reserve Bank could be debited in the amount of the duplicate or improper payment.
Several institutions raised objections about various aspects of the above procedures. One stated that 30 days was an insufficient time to respond and urged conformity with the rules in 31 CFR part 210 permitting a 60-day response time. Some objected to furnishing information about the persons who withdrew money from an account. Several objected in principle to the provision authorizing the debiting of their accounts. Several comments indicated that if a payment is returned by a financial institution using an automated payment reversal procedure, then only the full amount of the payment (not a partial amount) can be reversed.
In the final rule, the Treasury has clarified the procedures. The requirement to provide the names of persons who withdrew funds from an account has been changed. In paragraph (b)(6)(i), financial institutions are asked to provide only such information as they have about the matter. The debiting of an institution's account at a Federal Reserve Bank is intended to be simply a last resort if the institution fails totally to respond to the notice of a duplicate payment or payment made in error. See paragraph (b)(6)(iii). The time provided for response to this notice has been lengthened to 60 days.
The final rule has also been clarified in paragraph (b)(6)(i) to provide that the amount that should be returned is an amount equal to the payment. The Treasury reserves the right, however, to request the return by other than automated means of a partial amount of a payment made in error. It is anticipated that such a procedure would occur only if the notice of a payment made in error is not issued immediately after the payment was made.
(d) Handling of payments by Federal Reserve Banks. Some of the comments raised a question about the liability of the Federal Reserve Banks in making payments. The proposed rule, in §357.26(d)(2), provided that each Federal Reserve Bank would be responsible only to the Department and would not be liable to any other party for any loss resulting from its handling of payments. This rule was taken from the existing regulations in 31 CFR part 210 (see §210.3(f)), and is simply a restatement of existing law.
In making payments, the Federal Reserve Banks are acting in the capacity as fiscal agents of the United States, pursuant to 12 U.S.C. 391. They are not acting in an individual (banking) capacity. If a Federal Reserve Bank misdirects a payment contrary to instructions provided by the investor, the United States, as principal, may remain liable to the investor for the payment. The United States could seek to recover any loss from its agent, the Fedeal Reserve Bank. However, because the proposed rule simply stated a legal conclusion and tended to create the impression that the rule was broader than intended, it has been omitted from the final regulations.
Section 357.31 Certifying individuals.
For clarity, the warranties which accompany the use of a “Signature guaranteed” stamp have been set out.
Section 357.42 Preservation of existing rights.
This section has been deleted. The same subject-matter will be covered in §357.1, as finally adopted.
Section 357.43 Liability of Department and Federal Reserve Banks.
This section was published as §357.42 in the notice of proposed rulemaking for TRADES. The final version will be published after all the comments on the rulemaking for TRADES have been reviewed and considered.
Section 357.46 Supplements, amendments, or revisions.
Provision for “charges and fees for services and maintenance of book-entry Treasury securities” has been added in the event circumstances should dictate their imposition.
[51 FR 18260, May 16, 1986; 51 FR 18884, May 23, 1986]
Appendix B to Part 357—TRADES Commentary
top
Introduction
The adoption of regulations for the Treasury/Reserve Automated Debt Entry System (“TRADES”) is the culmination of a multi-year Treasury process of moving from issuing securities only in definitive (physical/certificated/paper) form to issuing securities exclusively in book-entry form. The TRADES regulations provide the legal framework for all commercially-maintained Treasury book-entry securities. For a more detailed explanation of the procedural and legal development of book-entry and the TRADES regulations, see the preamble to the rule proposed March 4, 1996 (61 FR 8420), as well as the earlier proposals cited therein 51 FR 8846 (March 14, 1986); 51 FR 43027 (November 28, 1986); 57 FR 12244 (April 9, 1992).
Comparison of TRADES and Legacy Treasury Direct
A person may hold interests in Treasury book-entry securities either in TRADES1 or Legacy Treasury Direct. The following summarizes the major differences between the two systems.
1 In TRADES a Person's interest in a Treasury book-entry security is a Security Entitlement, as described in TRADES. A Participant's interest in a marketable Treasury book-entry security also is a Security Entitlement. A Participant's Security Entitlement is different than a Security Entitlement as described in Revised Article 8, with respect to the Participant's rights against the issuer. A non-Participant's Security Entitlement is described in Revised Article 8.
Persons holding Treasury book-entry securities in TRADES hold their interests in such securities in a tiered system of ownership accounts. In TRADES, Treasury, through its fiscal agents, the Federal Reserve Banks, recognizes the identity only of Participants (persons with a direct account relationship with a Federal Reserve Bank). While Participants may be beneficial owners of interests in Treasury book-entry securities, there are many beneficial owners of such interests that are not Participants. Such beneficial owners hold their interests through one or more Securities Intermediaries such as banks, brokerage firms or securities clearing organizations.
In TRADES, the rights of non-Participant beneficial owners may be exercised only through their Securities Intermediaries. Neither Treasury nor the Federal Reserve Banks have any obligation to a non-Participant beneficial owner of an interest in a Treasury book-entry security. Two examples illustrate this principle. First, except where a pledge has been recorded directly on the books of a Federal Reserve Bank pursuant to §357.12(c)(1), Federal Reserve Banks, as Treasury's fiscal agents, will act only on instructions of the Participant in whose Securities Account the Treasury book-entry security is maintained in recording transfers of an interest in a Treasury book-entry security. A beneficial owner of the interest that is a non-Participant has no ability to direct a transfer on the books of a Federal Reserve Bank. Second, Treasury discharges its payment obligation with respect to a Treasury book-entry security when payment is credited to a Participant's account or paid in accordance with the Participant's instructions. Neither Treasury nor a Federal Reserve Bank has any payment obligation to a non-Participant beneficial owner of an interest in a Treasury book-entry security. A non-Participant beneficial owner receives its payment when its Securities Intermediary credits the owner's account.
Persons holding Treasury book-entry securities in Legacy Treasury Direct, on the other hand, hold their securities accounts on records maintained by Treasury through its fiscal agents, the Federal Reserve Banks. The primary characteristic of Legacy Treasury Direct is a direct account relationship between the beneficial owner of a Treasury book-entry security and Treasury. In Legacy Treasury Direct, Treasury discharges its payment obligation when payment is credited to the depository institution specified by the beneficial owner of the Treasury book-entry security, paid directly to the beneficial owner by check, or paid in accordance with the beneficial owner's instructions. Unlike TRADES, Legacy Treasury Direct does not provide a mechanism for the exchange of cash to settle a secondary market transaction, nor are pledges of Treasury book-entry securities held in Legacy Treasury Direct generally recognized. Accordingly, Legacy Treasury Direct is suited for persons who plan to hold their Treasury securities until maturity, and provides an alternative for investors who are concerned about holding securities through intermediaries and who do not wish to hold their interests in Treasury securities indirectly in TRADES.
Scope of Regulation
Just as the scope of Revised Article 8 is limited,2 the scope of this regulation is limited. It is not a comprehensive codification of the law governing securities, transactions in securities or the law of contracts for the purchase or sale of securities. Similarly, it is not a codification of all laws that could affect a person's interest in a Treasury book-entry security. For example, state laws regarding divorce or intestate succession could well affect which persons have rights in the interest in a Treasury book-entry security. Moreover, the regulations deal with certain aspects of transactions in Treasury securities, such as perfection of a security interest and its effects and not other aspects, such as the contractual relationship between a debtor and its secured party, which are left to applicable law3 . See the discussion under §357.10 of the Section-by-Section Analysis.
2 U.C.C. Revised Article 8, Prefatory Note at 12.
3 The regulations in 31 CFR 306.118(b), which are being supplanted by TRADES, state that “applicable law” covers how a transfer or pledge is “effected” as well as perfected. Except with respect to security interests marked on the books of a Federal Reserve Bank, TRADES does not address how a security interest in a Treasury book-entry security is created or what law governs the creation of a security interest. Section 357.11(a) of TRADES, which establishes the choice of law for interests other than those covered by §357.10, addresses the choice of law with respect to the perfection, effect of perfection or non-perfection, and priority of security interests, but does not address the law governing creation or attachment of a security interest. This is consistent with the scope and choice of law provisions of Revised Article 8.
Section-by-Section Analysis
Section 357.0 Dual book-entry systems.
Section 357.0 sets forth that Treasury provides two systems for maintaining Treasury book-entry securities—TRADES and Legacy Treasury Direct. Subpart A of part 357 of 31 CFR contains general information about TRADES and Legacy Treasury Direct. Subpart B contains the TRADES regulations. Subpart C contains the Legacy Treasury Direct regulations. Subpart D contains miscellaneous provisions. Thus, in its totality, part 357 sets forth in one place the complete set of governing rules for Treasury securities issued in book-entry form.
Section 357.1 Effective date.
Section 357.1 establishes the effective date for TRADES. TRADES applies to outstanding securities formerly governed by 31 CFR part 306, subpart O. Conforming changes to parts 306, 356, and 358 are being made to coincide with the publication of TRADES in final form. Consistent with the approach set forth in Revised Article 8 (see §8–603 and the official comment thereto), on and after the effective date these regulations will apply to all transactions, including transactions commenced prior to the effective date. Revised Article 8, in Section 8–603, gave secured parties four months after the effective date to take action to continue the perfection of their security interests. TRADES, through its delayed effectiveness, provides a similar period. In TRADES, January 1, 1997, becomes the date by which such actions must be completed.
The effective date for TRADES is January 1, 1997. While TRADES is based in large part on Revised Article 8 that has received widespread attention in the financial community and already has been adopted in 28 states,4 Treasury has determined that TRADES will be effective on January 1, 1997, to ensure a smooth transition to TRADES. In making that determination, Treasury has taken into account the time required by other Government-Sponsored Enterprises (GSEs) to promulgate similar regulations for their securities. Such an effective date, when combined with TRADES having been published in proposed form with a 60-day comment period, should provide sufficient time for an orderly transition to the new TRADES rules.
4 As of August 1, 1996, those states are: Alabama, Alaska, Arizona, Arkansas, Colorado, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maryland, Massachusetts, Minnesota, Mississippi, Nebraska, New Mexico, Oklahoma, Oregon, Pennsylvania, Texas, Utah, Vermont, Virginia, Washington, West Virginia and Wyoming. See discussion accompanying footnote 11.
Section 357.2 Definitions.
Section 357.2 contains definitions for use in subparts B and C. While most of the definitions are straightforward, four terms—Participant, Entitlement Holder, Security Entitlement and Securities Intermediary—are critical to an understanding of the proposed TRADES regulations.
(a) Participant. A Participant is a person that has a securities account relationship in its name with a Federal Reserve Bank. Accordingly, the Federal Reserve Bank and Treasury know both the identity of the persons maintaining these accounts and the Treasury book-entry securities held in these accounts.
(b) Securities Intermediary. Securities Intermediaries are persons (other than individuals, except as described below) that are in the business of holding interests in Treasury book-entry securities for others. Participants can be, and usually are, Securities Intermediaries.
In addition, entities such as clearing corporations, banks, brokers and dealers can be Securities Intermediaries in a single chain of ownership of a Treasury security. An individual, unless registered as a broker or dealer under the federal securities laws, cannot be a Securities Intermediary. As an illustration of a possible chain of ownership, in the following chart, the Federal Reserve Bank, Participant and Broker-Dealer are all Securities Intermediaries.
|