Purchase of new issue from issuer. This is in response to your letter in which you ask whether Board rule G-17, on fair dealing, or any other rule, regulation or federal law, requires an underwriter to purchase a bond issue from a municipal securities issuer at a “fair price.”

Rule G-17 states that, in the conduct of its municipal securities business, each broker, dealer and municipal securities dealer shall deal fairly with all persons and shall not engage in any deceptive, dishonest, or unfair practice. Thus, the rule requires dealers to deal fairly with issuers in connection with the underwriting of their municipal securities.  Whether or not an underwriter has dealt fairly with an issuer is dependent upon the facts and circumstances of an underwriting and cannot be addressed simply by virtue of the price of the issue. For example, in a competitive underwriting where an issuer reserves the right to reject all bids, a dealer submits a bid at a net interest cost it believes will enable it to successfully market the issue to investors. One could not view a dealer as having violated rule G-17 just because it did not submit a bid that the issuer considers fair. On the other hand, when a dealer is negotiating the underwriting of municipal securities, a dealer has an obligation to negotiate in good faith with the issuer. If the dealer represents to the issuer that it is providing the best market price available on this issue, and this is not the case, the dealer may violate rule G-17. Also, if the dealer knows the issuer is unsophisticated or otherwise depending on the dealer as its sole source of market information, the dealer’s duty under rule G-17 is to ensure that the issuer is treated fairly, specifically in light of the relationship of reliance that exists between the issuer and the underwriter. MSRB interpretation of December 1, 1997.

MSRB TRANSACTION REPORTING PROGRAM

QUESTIONS AND ANSWERS

October 1997

Most of these questions and answers were included in an MSRB mailing sent to each broker, dealer and municipal securities dealer on March 31, 1997. Questions numbered 60 and higher have been added since that mailing.

These questions and answers touch upon the following topics:

GENERAL QUESTIONS

CUSTOMER TRANSACTION REPORTING

• Preparing for Customer Transaction Reporting
• Completing the Customer Transaction Reporting Form
• Price and Yield
• Settlement Date
• Agency and Principal Transactions
• Control Numbers
• Records Amending and Cancelling Trades
• Submission of Files
• File Forwarding by NSCC
• Transaction Reporting to MSRB Using MSRB's Dial-Up Facility
• Testing Customer Transaction Reporting with the MSRB
• Record and File Format Questions
• Other Questions

 

INTER-DEALER TRANSACTION REPORTING

• Accrued Interest
• Executing Broker Symbol
• Time of Trade
• Problems in Inter-Dealer Transaction Reporting

 

QUESTIONS ADDED AFTER MARCH 1997

• Yield
• Commission
• File Format

 

GENERAL QUESTIONS

1. Q: What is the purpose of the requirement in MSRB rule G-14 to report each municipal securities transaction to the MSRB?

A: One purpose of the requirement is to make transaction information (e.g., prices and volumes) available to market participants. This is generally known as the "transparency" function of the MSRB Transaction Reporting Program. It is being accomplished at this time through a daily report that shows information such as the high, low and average prices of municipal securities that were traded four or more times on the previous day. A second, equally important, function of the program is market surveillance. Each transaction reported is entered into a database that essentially is an audit trail of transactions. This database is available only to the SEC, the NASD and other regulators charged with surveillance of the market. Transparency and surveillance functions have long been in existence in other major U.S. securities markets. The MSRB is responsible to bring these functions to full implementation in the municipal securities market.

2. Q: Have the requirements of G-14 been approved by the Securities and Exchange Commission?

A: Yes. The Commission approved the transaction reporting requirements described here on November 29, 1996 (Securities and Exchange Act Release No. 37998; see also MSRB Reports, Vol. 17, No. 1 [January 1997] at 3-8).

3. Q: When does compliance with these functions have to take place?

A: Inter-dealer transaction reporting began on January 23, 1995, with an amendment to rule G-14. (See MSRB Reports, Vol. 14, No. 5 [December 1994] at 3-6.) Each dealer should now be well aware of the specific requirements of reporting inter-dealer transactions. A number of notices have appeared in MSRB Reports indicating areas where attention is specifically needed to improve reporting. (See, e.g., MSRB Reports, Vol. 16, No. 2 [June 1996] at 9-12.) Customer transaction reporting begins with mandatory testing in July 1997 and full program operations are planned for early 1998.

4. Q: How does a dealer report municipal securities transactions to the MSRB?

A: The answer to the question differs depending upon whether the transaction is with another dealer ("inter-dealer transaction") or with an entity that is not a dealer ("customer transaction"). Inter-dealer transactions are reported by submitting the required transaction information, in proper form, to the automated comparison system for municipal securities. Dealers achieve both the automated comparison function and the transaction reporting function by submitting a single file to the comparison system. For customer transactions, dealers must produce a computer-readable file specifically for the MSRB and transmit that file to the MSRB each night.

CUSTOMER TRANSACTION REPORTING

Preparing for Customer Transaction Reporting

5. Q: What should dealers be doing now to prepare for customer transaction reporting?

A: After becoming familiar with the G-14 requirements, dealers should either be making changes to their computer systems necessary to produce and transmit customer transaction files, or making arrangements with clearing brokers or service bureaus who will do this on their behalf. Although the mandatory testing period does not begin until summer 1997, preparations should be made now.

6. Q: Is there anything else that a dealer can do now to prepare?

A: Each dealer should complete and return a Customer Transaction Reporting Form.

Completing the Customer Transaction Reporting Form

7. Q: In completing the information form for customer transaction reporting, whom should I identify as the "primary contact with the MSRB for purposes of customer transaction reporting"? Should I name our Municipal Securities Department Director or our Compliance Officer?

A: The primary contact should be the individual who will be ultimately responsible for ensuring that MSRB mailings and other communications (e.g., phone calls) on this subject will reach the appropriate persons in the firm. The primary contact will be the MSRB's initial contact regarding tests of customer transaction reporting.

8. Q: Who should be identified as the "point-of-contact regarding technical matters"?

A: The MSRB will contact this person on computer-related matters such as the firm's telecommunications and methods for transmitting files, how many characters each field should have in the record of a trade, what headers must be included in the files, etc.

9. Q: How do the above topics differ from the person designated for questions about the "correctness of trade details"?

A: A question about trade details might arise, for example, if MSRB calculates a yield that differs substantially from the dealer-reported yield for the same trade. MSRB staff may ask the dealer what it used to derive yield from dollar price to account for the difference. In general, the contact for "correctness of trade details" will be the person called if the question is about the substantive information being provided about a transaction.

10. Q: In response to the question on page one of the form, my firm does not effect municipal securities transactions, does not intend to do so and does not intend to submit transactions to the MSRB for other dealers. I will check the appropriate box and return the form. What should I do if my firm's plans later change?

A: Since all transactions in municipal securities will have to be reported to the MSRB, if a firm decides to begin effecting transactions or to submit transaction data, it should immediately contact the MSRB to obtain and complete this form.

11. Q: What is the "dial-up transmission facility" referred to in the form?

A: Most dealers will send customer trade data to the MSRB through National Securities Clearing Corporation (NSCC), but some low-volume transmissions may be done by dialing the MSRB's computer directly using a personal computer and telephone modem. By checking the appropriate box on the form, you may request more information about the dial-up facility from the MSRB. In response, the MSRB will mail information before testing begins that describes how the dial-up facility can be installed and used to report customer trades. (More detailed questions and answers about the dial-up facility are found below.)

12. Q: Where can I find a description of the data elements that must be included in transaction records?

A: The MSRB document entitled "File and Record Specifications for Reporting Customer Transactions" defines the data elements and provides format specifications for transaction records and files.

Price and Yield

13. Q: Both price and yield are required to be included for transactions on which the settlement date is known. Why is that?

A: One of the most difficult problems in collecting and disseminating accurate information on municipal securities transactions is that there are approximately 1.3 million different municipal securities. Typographical errors in trade input, for example, are always possible, and since there is generally not a stream of transaction data coming in on a specific issue, it is difficult for the system collecting the information to mechanically check reported information to ensure that it is not a likely input error. This is particularly important when it is recognized that the price information collected will be disseminated and reviewed by market participants on the next day and may be used as part of trading or investment decisions. Requiring both yield and price, along with the CUSIP number of the issue being reported, will allow the MSRB to mechanically perform mathematical checks that will help to ensure that the information being reported makes sense, given the coupon, maturity date and call features of the security. Other means of checking data accuracy also will be employed. For example, the CUSIP check digit is required to guard against typographical errors in the entry of CUSIP numbers. (More questions and answers about error correction are found below.)

14. Q: What if a yield cannot not be computed for a transaction done on a dollar price basis, for example, because the trade is in a variable rate security or in a defaulted security?

A: The trade may be submitted using a dollar price only in these cases. Note, however, that if the security is not known to the MSRB system as one which is a variable rate instrument or in default, the MSRB may contact you to ensure that its information about the security is correct and so that subsequent transaction input in the security will not be questioned in the future.

See also questions 60 and 61.

Settlement Date

15. Q: What if settlement for a transaction is not known because the transaction is in a new issue and settlement date has not been set?

A: The transaction should be reported with a yield or a dollar price and without a settlement date.

16. Q: If the settlement date for the transaction is determined after a submission is made without a settlement date, should the dealer report revised trade information to the MSRB?

A: No. If the only change in the transaction information is the settlement date on a new issue, the dealer should not send an amended transaction report. Once the settlement date for the new issue becomes known to the MSRB, that settlement date will be included in the transaction data automatically.

Agency and Principal Transactions

17. Q: When reporting dollar prices on agency transactions, should the effect of commissions be included in the dollar price submitted?

A: No. There is a separate field for submitting the commission amount on agency transactions. The MSRB will include the effect of the commission in the dollar price when aggregating principal and agency transactions and reporting price information on the daily report. There should be no "commissions" on principal transactions so that the dollar price given on principal transactions should be the net transaction dollar price to the customer.

18. Q: How should commissions be reported?

A: Commission is reported in dollars per $100 par value.

See also questions 62 and 63.

Control Numbers

19. Q: The file format requires each transaction submitted by a dealer to have a unique "control number" (unique for the dealer) that is no longer than 20 characters and that may be composed of alpha and/or numeric characters. Why is this necessary?

A: The control number given by the dealer is the mechanism by which the dealer identifies a specific transaction to the Transaction Reporting System. The dealer chooses its own numbering system; however, the control number for a transaction must be unique for the dealer within a three-year period. For example, if a dealer submits two different transactions with the same control number, the system may reject the second transaction. Use of the control number is critical so that the dealer may correct information submitted in error to the system. The MSRB also will use the dealer's control number to report back information to the dealer about the transaction.

Records Amending and Cancelling Trades

20. Q: Under what circumstances would a dealer need to correct information about a transaction submitted to the system?

A: An example might be a dealer who has made an input error resulting in the wrong price or yield being submitted for a transaction. Note that it is important for these errors to be corrected as soon as possible so that the audit trail and surveillance database is correct. Note also that it is important for errors like these to be minimized since the prices reported on trade date will be used for the daily reports appearing on the next business day.

21. Q: What will the MSRB do if it discovers a probable input error that has resulted in submitted transaction information?

A: As part of the daily process of collecting transaction information from dealers, the MSRB will send to each dealer that submitted transaction information a receipt with messages identifying errors in transactions that failed to meet acceptance testing, together with a copy of all such input records.

22 Q: What should happen next?

A: If the dealer finds that the record should be amended -- for example, because of a typographical error in the price -- he or she will submit an "Amend" record as soon as possible (i.e., a record with "A" as the "Cancel/Amend Code"). The "Amend" record must include the same dealer control number as the first report of the trade and must include all of the correct information about the trade. If the dealer finds that the questioned record was correct -- as might happen if the dealer knows features about the bond that affect the price/yield calculation and that are not in the MSRB's database -- a "Verify" record should be submitted, including the original dealer control number, to indicate that it is correct.

23. Q: What happens if I try to amend a transaction with a control number that I have not previously reported?

A: If a transaction is submitted with a "Cancel/Amend Code" of "A" and there is not an existing transaction in the database with that control number, the transaction information will be rejected -- that is, returned to the dealer for correction.

24. Q: Can I amend any information about a trade that I have previously reported?

A: No. The following fields cannot be amended: dealer identity, CUSIP number, and transaction control number. If you report a trade with an error in one of these fields, you should cancel the transaction report, as described below, and then report the trade using a new control number.

25. Q: Under what circumstances would a transaction be "cancelled" in the system and how is that done?

A: There may be limited numbers of instances in which customer transactions are reported, but the transactions later must be cancelled with customers due to circumstances beyond the dealer's control (for example, a new issue is cancelled). In this case, the dealer must submit a record with the control number of the transaction and with the "Cancel/Amend Code" set to "C" for "Cancel." Doing so will allow MSRB to indicate the transaction as cancelled in the surveillance database so that the database is accurate.

26. Q: For how long after initial submission is it possible for dealers to amend or cancel transactions that have been entered into the system?

A: This can be done for a period of three months after initial submission. However, for new issues for which there is no settlement date, it will be possible to submit cancellations until three months after the settlement date of the issue. Note that, while some numbers of cancellations and corrections are inevitable, it is important for dealers to minimize the need for these types of corrections by making sure that procedures are in place for reporting necessary information correctly in the initial submission.

Submission of Files

27. Q: When must a transaction be reported to the MSRB?

A: A transaction record, in the correct format, must reach the MSRB by midnight on trade date.

28. Q: How are these transaction records sent to the MSRB?

A: The records are put into a file with appropriate header information. The resulting file is sent to the MSRB.

29. Q: My firm is a clearing broker and will be submitting a file each day on behalf of many of our correspondents. Is there any special way in which the records in the file should be organized?

A: No. As long as the header information is correct and the information in each record is correct, the records within the file can be in any order. The header identifies the party submitting the file; the records may pertain to any number of executing dealers.

File Forwarding by NSCC

30. Q: My organization processes thousands of customer transactions in municipal transactions each day. How can such a large file be sent to the MSRB?

A: National Securities Clearing Corporation is providing its participants the ability to send the MSRB customer transaction file to NSCC along with other types of files that are sent to NSCC each day. NSCC will forward the MSRB customer transaction file to the MSRB.

31. Q: My firm uses another broker-dealer for clearing and processing municipal securities transactions. The clearing broker submits my inter-dealer transactions to NSCC on my behalf. Can the clearing broker submit my customer transaction reports to NSCC for forwarding on to the MSRB on my behalf?

A: Yes. The clearing broker can submit transaction reports for dealers for which it clears transactions. Note that the dealer effecting transactions is responsible for the clearing broker's performance in this regard. You should talk with your clearing broker now to ensure that it will provide this service.

32. Q: My firm uses a service bureau to submit inter-dealer transaction information to NSCC. Can the service bureau also submit customer transaction files to NSCC for forwarding to the MSRB?

A: Yes. As in the previous answer, the dealer effecting transactions is responsible to report the transactions correctly.

33. Q: Are there any special requirements for formatting the file to NSCC and getting the file to NSCC?

A: Yes. You should review NSCC's April 2, 1997 Important Notice on the interface requirements for customer transaction reporting (Notice No. A-4571 and P&S 4155). Similarly, if a clearing broker or service bureau will be sending your MSRB customer transaction files to NSCC for forwarding to the MSRB, they should ensure that the files can be sent in the correct format.

34. Q: Will customer transaction records submitted to NSCC for forwarding to the MSRB be included in the automated comparison system?

A: No. The MSRB customer transaction file sent to NSCC for forwarding to the MSRB is a totally separate file than the inter-dealer transactions and other files sent to NSCC for clearance and settlement purposes. NSCC will not process data in the MSRB customer transaction files, but will only forward the files to the MSRB. The use of NSCC for this purpose will allow dealers and service bureaus to use existing telecommunication channels set up between dealers and NSCC and between NSCC and the MSRB. Thus, it should provide efficiencies, especially for dealers that have many customer transactions each day. (An additional question on this subject is given below, under "Other Questions.")

Transaction Reporting to MSRB Using MSRB's Dial-Up Facility

35. Q: My firm submits its inter-dealer transactions to NSCC through a dial-up terminal or personal computer. Can I use this method of file transfer to transmit customer transaction files to NSCC for forwarding to the MSRB?

A: No; as noted in NSCC's Important Notice, all dial-up connections will be directly to the MSRB.

36. Q: How will this be done?

A: MSRB will offer a facility whereby dealers may send relatively small files directly to the MSRB by using a personal computer and a standard telephone modem, such as those made by Hayes, U.S. Robotics and others. The MSRB will provide telecommunications software by summer 1997 to dealers who ask for this service. Please note that this software will run only on computers using the Windows 95 or Windows NT operating systems. Also note that dealers using this method of transmitting files directly to the MSRB will still need a means to generate files from their own records that meet MSRB file and record format requirements.

Testing Customer Transaction Reporting with the MSRB

37. Q: What is the purpose of the mandatory testing?

A: The purpose of testing is to ensure each dealer that its own system can produce files containing the required information in the proper format, that it is able to correct erroneous input, and so forth. Testing is mandatory so that all dealers will be ready before the reporting requirement becomes effective in January 1998.

38. Q: What is the date for dealers to test their customer transaction reporting capabilities with the MSRB?

A: Mandatory testing will begin in July 1997. The MSRB plans to schedule the first tests with the dealers that have the greatest volume of customer trades and with service bureaus, followed by the lower-volume dealers. The MSRB will publicize the testing schedule before testing begins.

39. Q: What will happen during the test?

A: First, the MSRB will contact the designated primary contact person listed on your organization's MSRB Transaction Reporting form. Information will be obtained on how the organization will be submitting data, a fax number for the dealer to receive receipt/error logs from the MSRB, and technical details. Dates will be chosen to run your test. The contact person will arrange to send test files to the MSRB, using either NSCC or the MSRB dial-up facility, to establish that the telecommunications link is working, and that the trade records meet the format specifications.

40. Q: How long will the test last?

A: Each test cycle should take approximately five days. However, it may take more than one test cycle for a dealer to validate its methodology for creating files in the proper formats and for handling trade data corrections.

41. Q: Will there be special formats and test procedures for submission through NSCC?

A: Yes. As part of testing the communications, dealers and service bureaus will go through NSCC's usual procedures for setting up transmission of a new data stream or "SysID" - verifying that the file header meets Datatrak specifications, etc. Details are provided in the NSCC Important Notice previously mentioned (Notice No. A-4571 and P&S 4155).

Record and File Format Questions

42. Q: What is the format for the computer-readable file that must be sent to the MSRB each day to comply with the customer transaction reporting requirement?

A: For files sent directly to the MSRB via the MSRB dial-up facility, the physical formats for transaction records, and for the file header record that must precede them, are specified in the MSRB document entitled "File and Record Specifications for Reporting Customer Transactions." Files sent to NSCC will need to be in the format specified by NSCC. See NSCC's April 1997 Important Notice.

See also questions 64 through 66.

Other Questions

43. Q: Is the customer's identity included anywhere in the information reported?

A: No. The customer's identity is never submitted in reports of customer transactions. Each record must correctly indicate whether the transaction was a sale to a customer or a purchase from a customer, whether it is a principal or agency transaction, and certain other information.

44. Q: Are institutional and retail customer transactions reported in the same way?

A: Yes.

45. Q: How should the "Buy/Sell" code be reported?

A: If the dealer has sold securities to the customer, report this as "S" (sell). If the dealer has purchased securities from the customer, report this as "B" (buy).

46. Q: May I include my inter-dealer trades in the customer trade file I send to the MSRB?

A: No. All files submitted as part of a dealer's customer transaction file must report only customer transactions -- no inter-dealer transactions may be included.

INTER-DEALER TRANSACTION REPORTING

47. Q: How are inter-dealer transactions reported to the MSRB?

A: By submitting the transactions on trade date, to the automated comparison system, in the format and manner required by that system to obtain a comparison on the night of trade date. NSCC provides this information to the MSRB to accomplish transaction reporting for those trades. (Please note that these requirements are currently in effect under MSRB rule G-14.)

48. Q: What items are required by rule G-14, in addition to the items necessary to obtain an automated comparison of an inter-dealer trade on the night of trade date?

A: Specific items that are mandatory, in addition, to the information required for automated comparison, are: (i) accrued interest, on any transaction in which the settlement date is known; (ii) executing broker identity; and (iii) time of trade.

Accrued Interest

49. Q: Why does the MSRB need accrued interest in inter-dealer transaction reports?

A: For most transactions reported through the automated comparison system, dealers report a final money figure in lieu of a dollar price or yield. The MSRB derives a dollar price for these transactions by subtracting the reported accrued interest and dividing the result by the par amount traded. Therefore, if accrued interest is not reported correctly, the resulting dollar price may not be accurate.

Executing Broker Symbol

50. Q: Why does the MSRB need an "executing broker symbol"?

A: This symbol is used for the audit trail function. It identifies the dealer that actually effected the transactions (in contrast to the dealer that submitted the trade to NSCC or who cleared the trade). It is particularly important for dealer identification when one dealer clears for several other dealers. The dealer that actually effected the transaction should be the one identified with this symbol.

51. Q: What symbol should be used for executing broker identity?

A: The four-character symbol of the firm or bank assigned by the NASD, for example, ABCD.

52. Q: Is it permissible for my firm to use our NSCC clearing number (e.g., 1234) instead of this symbol? In our case, this would serve the same purpose since we only clear for ourselves.

A: No. The four-character alphabetic symbol is required, as it is the standard identifier used in the surveillance database. Note that, when the customer reporting phase of the Program becomes operational, this NASD-assigned symbol will be the primary identifier.

53. Q: My organization does not have one of these symbols. Should we just use the symbol of the dealer that we clear through?

A: No, if your organization is a broker, dealer or municipal securities dealer and it is effecting trades in municipal securities (with other dealers or with customers), it must use its own symbol.

54. Q: How does a dealer obtain an NASD-assigned symbol if it does not already have one?

A: Call NASD Subscriber Services at (800) 777-5606 and explain that you need a symbol for reporting municipal securities transactions.

55. Q: Will the NASD assign a symbol, even though my organization is a dealer bank?

A: Yes.

Time of Trade

56. Q: Why does the MSRB need the time of trade?

A: This information is also needed for audit trail purposes. It is not currently used in the transparency component of the program.

57. Q: How is time of trade submitted for inter-dealer transactions?

A: It is submitted in military format (e.g., 1400 for 2:00 p.m.) and in terms of Eastern time.

Problems in Inter-Dealer Transaction Reporting

58. Q: What kind of problems has the MSRB seen in the inter-dealer transaction information submitted under rule G-14?

A: For the daily report generated by the Program, only compared transactions can be used for generating price and volume information. It accordingly is very important for dealers to ensure that their procedures for reporting inter-dealer transactions are designed to submit correct information reliably to the automated comparison system. A significant number of the following types of transaction in the automated comparison system indicates that a dealer is having problems that require a review of its procedures and corrective action: (i) stamped advisories; (ii) "as of" submissions; (iii) "demand-as-of" submissions coming in against the dealer; (iv) compared transactions that are deleted using either the "one-sided delete" function or using the "withhold" function.

59. Q: My firm clears through a clearing broker. When my firm does trades with another firm that also uses that same clearing broker, must that transaction be reported to the MSRB by submitting the trade to the automated comparison system?

A: Yes. Note that the submission to the automated comparison system is also required in this instance by rule G-12(f) on automated comparison.

QUESTIONS ADDED AFTER MARCH 1997

Yield

60. Q: Should I report to the MSRB the transactions's yield to maturity or another yield -- yield to first call, yield to par call, etc.? My system calculates several yields for use in customer confirmations.

A: Report the yield as required by MSRB rule G-15(a) for customer confirmations. Rule G-15(a) in most cases requires the yield to be computed to the lower of call or nominal maturity date. Exception: If the transaction was effected at par, the yield (coupon rate) should be reported on the customer trade record, even though rule G-15(a) allows the yield to be omitted from the confirmation in such a case.

If reporting the yield is not possible because the transaction was done on a dollar price basis and no settlement date has been set for a "when-issued" security, leave the yield blank or enter zero.

61. Q: How should I report negative yield?

A: Enter a negative number in the "yield" field. The minus sign may precede or follow the number, as long as it is inside the defined field area.

Commission

62. Q: Should the effect of the commission be reported in the yield?

A: Yes. You should report as yield the same "net" yield that is reported on customer confirmations. Therefore, the reported yield should include the effect of any commission (see MSRB rule G-15(a)).

63. Q: Should miscellaneous fees such as transaction fees be included in the commission field or elsewhere? If the sales representative receives a portion of the firm's profit, should that portion be reported?

A: No. Neither miscellaneous fees nor sales representatives' portions should be reported.

File format

64. Q: Can I include binary data in the customer transaction file, along with ASCII data?

A: No. Binary data should not be included, even in the unused portions of the record. Including binary data will likely cause errors such as skipped records when MSRB processes the file. 
 

Q: The MSRB file header record requires a "version number." What should be put here?

A: This field identifies the version of the MSRB format specification that applies to the file. Initially, use '0010' here.

65. Q: The header record requires a "record count" field. What should be put here?

A: Put here the count of the number of transactions being reported in this file. Do not count the header record(s). Depending on the format used, the record count is the same as the number of physical transaction records or one-half the number of physical transaction records.

66. Q: If the header record of a transaction file contains errors, how will MSRB inform the submitter of this fact?

A: If the header of a file forwarded by NSCC does not identify a submitter and site known to the MSRB, then MSRB staff will ask NSCC to follow up. (MSRB will not accept any direct submissions by dial-up from unknown parties.) Otherwise, MSRB will send a receipt/error message file or fax to the submitter. The header errors will be identified in the file in the first two records following the receipt record, using the same format as for transaction detail errors.

Copyright 2000 Municipal Securities Rulemaking Board. All Rights Reserved. Terms and Conditions of Use.

Recently, dealers have raised questions regarding how the prohibition on municipal securities business in rule G-37, on political contributions and prohibitions on municipal securities business, applies to certain situations. Rule G-37 prohibits any dealer from engaging in municipal securities business with an issuer within two years after any contribution to an official of such issuer made by: (i) the dealer; (ii) any municipal finance professional associated with such dealer; or (iii) any political action committee controlled by the dealer or any municipal finance professional.[1] If a municipal finance professional makes a political contribution to an issuer official for whom he is not entitled to vote, the dealer is prohibited from engaging in municipal securities business with that issuer for two years. The Board has been asked whether the prohibition on municipal securities business extends to certain services provided under contractual agreements with an issuer that pre-date the contribution. The Board is issuing the following interpretation of the prohibition on municipal securities business pursuant to rule G-37.

"New" Municipal Securities Business

 A dealer subject to a prohibition on municipal securities business with an issuer may not enter into any new contractual obligations with that issuer for municipal securities business.[2] The Board adopted rule G-37 in an effort to sever any connection between the making of political contributions and the awarding of municipal securities business. The Board believes that the problems associated with political contributions––including the practice known as "pay-to-play"––undermine investor confidence in the municipal securities market, which confidence is crucial to the long-term health of the market, both in terms of liquidity and capital-raising ability.

Pre-Existing Issue-Specific Contractual Undertakings

The Board believes that it is consistent with the intent of rule G-37 that a dealer subject to a prohibition on municipal securities business with an issuer be allowed to continue to execute certain issue-specific contractual obligations in effect prior to the date of the contribution that caused the prohibition. For example, if a bond purchase agreement was signed prior to the date of the contribution, a dealer may continue to perform its services as an underwriter on the issue. Also, if an issue-specific agreement for financial advisory services was in effect prior to the date of the contribution, the dealer may continue in its role as financial advisor for that issue. In the same manner, a dealer may act as remarketing agent or placement agent for an issue and also may continue to underwrite a commercial paper program as long as the contract to perform these services was in effect prior to the date of the contribution. Subject to the limitations noted below, these activities are not considered new municipal securities business and thus can be performed by dealers under a prohibition on municipal securities business with the issuer.

Dealers also have asked questions regarding certain terms in contracts to provide on-going municipal securities business that allow for additional services or compensation. For example, a dealer may have an agreement to provide remarketing services for a municipal securities issue, the terms of which allow the issuer to change the "mode" of the outstanding bonds from variable to a fixed rate of interest or from Rule 2a-7 eligible to non-Rule 2a-7 eligible. [3] Generally, the per bond fee increases if the dealer sells fixed rate municipal securities or non-money market fund securities. Also, an agreement to underwrite a commercial paper program may include terms for increasing the size of the program. While the per bond fee probably does not increase if more commercial paper is underwritten, the amount of money paid to the dealer does increase. The Board views the provisions in existing contracts that allow for changes in the services provided by the dealer or compensation paid by the issuer as new municipal securities business and, therefore, rule G-37 precludes a dealer subject to a prohibition on municipal securities business from performing such additional functions or receiving additional compensation.

Non-Issue Specific Contractual Undertakings

Dealers also at times enter into long-term contracts with issuers for municipal securities business, e.g., a five-year financial advisory agreement. If a contribution is given after such a non-issue-specific contract is entered into that results in a prohibition on municipal securities business, the Board believes the dealer should not be allowed to continue with the municipal securities business, subject to an orderly transition to another entity to perform such business. This transition should be as short a period of time as possible and is intended to give the issuer the opportunity to receive the benefit of the work already provided by the dealer and to find a replacement to complete the work, as needed.

* * *

The Board recognizes that there is a great variety in the terms of agreements regarding municipal securities business and that the interpretation noted above may not adequately deal with all such agreements. Thus, the Board is seeking comment on how a prohibition on municipal securities business pursuant to rule G-37 affects contracts for municipal securities business entered into with issuers prior to the date of the contribution triggering the prohibition on business. In particular, the Board is seeking comment on other examples whereby a dealer may be contractually obligated to perform certain activities after the date of the triggering contribution. If other examples are provided, the Board would like comments on how these situations should be addressed pursuant to rule G-37.

Based upon the comments received on this notice, the Board may issue additional interpretations or amend the language of rule G-37. 

[1] The only exception to rule G-37’s absolute prohibition on municipal securities business is for certain contributions made to issuer officials by municipal finance professionals. Contributions by such persons to officials of issuers do not invoke application of the prohibition on business if (i) the municipal finance professional is entitled to vote for such official and (ii) contributions by such municipal finance professional do not exceed, in total, $250 to each official, per election.

[2] The term "municipal securities business" is defined in the rule to encompass certain activities of dealers, such as acting as negotiated underwriters (as managing underwriter or as syndicate member), financial advisors, placement agents and negotiated remarketing agents. The rule does not prohibit dealers from engaging in business awarded on a competitive bid basis.

[3] SEC Rule 2a-7 under the Investment Company Act of 1940 defines eligible securities for inclusion in money market funds

Financial advisor to conduit borrower.  This is in response to your letter concerning rule G-37, on political contributions and prohibitions on municipal securities business. You state that your firm served as financial advisor to the underlying borrower, not the governmental issuer, for a certain issue of municipal securities. You ask whether you are required to report this financial advisory activity on Form G-37/G-38.

Rule G-37(g)(vii) defines the term "municipal securities business" to include "the provision of financial advisory or consultant services to or on behalf of an issuer with respect to a primary offering of municipal securities in which the dealer was chosen to provide such services on other than a competitive bid basis." If the financial advisory services your firm provided were to the underlying borrower and not "to or on behalf of an issuer,"[1] then your firm was not engaging in "municipal securities business" and these financial advisory services are not required to be reported on Form G-37/G-38.  MSRB interpretation of January 23, 1997.
__________

[1] Rule G-37(g)(ii) defines "issuer" as the governmental issuer specified in section 3(a)(29) of the Securities Exchange Act.

Fairness opinions. This is in response to your letter concerning the retention of your firm by issuers to render a fairness opinion on the pricing associated with certain negotiated issues of general obligation municipal securities issued by [state deleted] governmental units. You ask whether the rendering of these fairness opinions on the pricing of municipal securities issues is a financial advisory activity which must be disclosed on Form G-37/G-38 as municipal securities business.

Rule G-23, on activities of financial advisors, states in paragraph (b) that a financial advisory relationship shall be deemed to exist when

a broker, dealer, or municipal securities dealer renders or enters into an agreement to render financial advisory or consultant services to or on behalf of an issuer with respect to a new issue or issues of municipal securities, including advice with respect to the structure, timing, terms and other similar matters concerning such issue or issues, for a fee or other compensation or in expectation of such compensation for the rendering of such services. [Emphasis added]

Thus, the activity your firm performs on behalf of issuers of municipal securities pursuant to an agreement (i.e. , rendering advice with respect to the terms of a new issue) establishes that a financial advisory relationship exists between your firm and these issuers.

Rule G-37, on political contributions and prohibitions on municipal securities business, requires dealers to report municipal securities business to the Board on Form G-37/G-38. The definition of "municipal securities business" contained in rule G-37(g)(viii) includes

the provision of financial advisory or consultant services to or on behalf of an issuer with respect to a primary offering of municipal securities in which the dealer was chosen to provide such services on other than a competitive bid basis.

Pursuant to the information contained in your letter, your firm should submit a Form G-37/G-38 during each quarter in which the firm reaches an agreement to provide the financial advisory services you described. If your firm has an on-going financial advisory arrangement with an issuer, your firm would need to list each new issue in which your firm acted as financial advisor during the quarter in which the new issue settled. I have enclosed for your information a copy of the Rule G-37 and Rule G-38 Handbook which includes instructions for completing and filing Form G-37/G-38. MSRB interpretation of January 10, 1997.

Automated settlement involving multidepository participants. This will respond to your letter concerning the requirements of rule G-12(f)(ii) applicable to transactions involving firms that are members of more than one registered securities depository. Your inquiry concerns situations in which a dealer that is a member of more than one depository executes a transaction with another dealer that is a member of one or more depositories. Your question is whether such dealers may specify the depository through which delivery must be made, either as a term of an individual transaction or with standing delivery instructions.

Your inquiry was referred to the Committee of the Board with the responsibility for interpreting the Board’s automated clearance and settlement rules, which has authorized my sending this response.

The rule does not specify which depository shall be used for settlement if the transaction is eligible for settlement at more than one depository.

The Board is of the view that, under rule G-12(f), parties to a transaction are free to agree, on a trade-by-trade basis or with standing delivery agreements, on the depository to be used for making book-entry deliveries. Absent such an agreement, a seller may effect good delivery under rule G-12(f) by delivering at any depository of which the receiving dealer is a member. MSRB interpretation of November 18, 1985.

NOTE: Revised to reflect subsequent amendments.

The Board has received inquiries whether a municipal securities dealer must send a confirmation to a customer when the customer utilizes the dealer to tender bonds pursuant to a put option. Board rule G-15(a)(i) requires dealers to send confirmations to customers at or before the completion of a transaction in municipal securities. The Board believes that whether a dealer that accepts for tender put bonds from a customer is engaging in "transactions in municipal securities" depends on whether the dealer has some interest in the put option bond.

In the situation in which a customer puts back a bond through a municipal securities dealer either because he purchased the bond from the dealer or he has an account with the dealer, and the dealer does not have an interest in the put option and has not been designated as the remarketing agent for the issue, there seems to be no "transaction in municipal securities" between the dealer and the tendering bondholder and no confirmation needs to be sent. The Board suggests, however, that it would be good industry practice to obtain written approval of the tender from the customer, give the customer a receipt for his bonds and promptly credit the customer's account. Of course, if the dealer actually purchases the security and places it in its trading account, even for an instant, prior to tendering the bond, a confirmation of this sale transaction should be sent.[1]

If a dealer has some interest in a put option bond which its customer has delivered to it for tendering, a confirmation must be sent to the customer. A dealer that is the issuer of a secondary market put option on a bond has an interest in the security and is deemed to be engaging in a municipal securities transaction if the bond is put back to it.

In addition, a remarketing agent, (i.e., a dealer which, pursuant to an agreement with an issuer, is obligated to use its best efforts to resell bonds tendered by their owners pursuant to put options) who accepts put option bonds tendered by customers also is deemed to be engaging in a "transaction in municipal securities" with the customer for purposes of sending a confirmation to the customer because of the remarketing agent's interest in the bonds.[2] The Board's position on remarketing agents is based upon its understanding that remarketing agents sell the bonds that their customers submit for tendering, as well as other bonds tendered directly to the trustee or tender agent, pursuant to the put option. The customers and other bondholders, pursuant to the terms of the issue, usually are paid from the proceeds of the remarketing agents' sales activities.[3]

[1] This would apply equally in circumstances in which the dealer has an interest in the put option bond.

[2] Of course, remarketing agents also must send confirmations to those to whom they resell the bonds.

[3] If these funds are not sufficient to pay tendering bondholders, such bondholders usually are paid from certain funds set up under the issue's indenture or from advances under the letter of credit that usually backs the put option.

The Board has received a number of inquiries from municipal securities brokers and dealers regarding the application of the Board’s rules to transactions in put option bonds. Put option or tender option bonds on new issue securities are obligations which grant the bondholder the right to require the issuer (or a specified third party acting as agent for the issuer), after giving required notice, to purchase the bonds, usually at par (the "strike price"), at a certain time or times prior to maturity (the "expiration date(s)") or upon the occurrence of specified events or conditions. Put options on secondary market securities also are coming into prominence. These instruments are issued by financial institutions and permit the purchaser to sell, after giving required notice, a specified amount of securities from a specified issue to the financial institution on certain expiration dates at the strike price. Put options generally are backed by letters of credit. Secondary market put options often are sold as an attachment to the security, and subsequently are transferred with that security. Frequently, however, the put option may be sold separately from that security and re-attached to other securities from the same issue.

Of course, the Board’s rules apply to put option bonds just as they apply to all other municipal securities. The Board, however, has issued a number of interpretive letters on the specific application of its rules to these types of bonds. These interpretive positions are reviewed below.

Fair Practice Rules

1. Rule G-17

Board rule G-17, regarding fair dealing, imposes an obligation on persons selling put option bonds to customers to disclose adequately all material information concerning these securities and the put features at the time of trade. In an interpretive letter on this issue,[1] the Board responded to the question whether a dealer who had previously sold put option securities to a customer would be obligated to contact that customer around the time the put option comes into effect to remind the customer that the put option is available. The Board stated that no Board rule would impose such an obligation on the dealer.

In addition, the Board was asked whether a dealer who purchased from a customer securities with a put option feature at the time of the put option exercise date at a price significantly below the put exercise price would be in violation of any Board rules. The Board responded that such dealer may well be deemed to be in violation of Board rules G-17 on fair dealing and G-30 on prices and commissions.

2. Rule G-25(b)

Board rule G-25(b) prohibits brokers, dealers, and municipal securities dealers from guaranteeing or offering to guarantee a customer against loss in municipal securities transactions. Under the rule, put options are not deemed to be guarantees against loss if their terms are provided in writing to the customer with or on the confirmation of the transaction and recorded in accordance with rule G-8(a)(v).[2] Thus, when a municipal securities dealer is the issuer of a secondary market put option on a municipal security, the terms of the put option must be included with or on customer confirmations of transactions in the underlying security. Dealers that sell bonds subject to put options issued by an entity other than the dealer would not be subject to this disclosure requirement.

Confirmation Disclosure Rules

1. Description of Security

Rules G-12(c)(v)(E) and G-15(a)(i)(E)[*] require inter-dealer and customer confirmations to set forth

a description of the securities, including… if the securities are… subject to redemption prior to maturity, an indication to such effect.

Confirmations of transactions in put option securities, therefore, would have to indicate the existence of the put option (e.g., by including the designation "puttable" on the confirmation), much as confirmations concerning callable securities must indicate the existence of the call feature. The confirmation need not set forth the specific details of the put option feature.[3]

Rules G-12(c)(v)(E) and G-15(a)(i)(E)[†] also require confirmations to contain

a description of the securities including at a minimum… if necessary for a materially complete description of the securities, the name of any company or other person in addition to the issuer obligated, directly or indirectly, with respect to debt service…

The Board has stated that a bank issuing a letter of credit which secures a put option feature on an issue is "obligated… with respect to debt service" on such issue. Thus, the identity of the bank issuing the letter of credit securing the put option also must be indicated on the confirmation.[4]

Finally, rules G-12(c)(v)(E) and G-15(a)(i)(E)[‡] requires that dealer and customer confirmations contain a description of the securities including, among other things, the interest rate on the bonds. The Board has interpreted this provision as it pertains to certain tender option bonds with adjustable tender fees to require that the net interest rate (i.e., the current effective interest rate taking into account the tender fee) be disclosed in the interest rate field and that dealers include elsewhere in the description field of the confirmation the stated interest rate with the phrase "less fee for put."[5]

2. Yield Disclosure

Board rule G-12(c)(v)(I) requires that inter-dealer confirmations include the

yield at which transaction was effected and resulting dollar price, except in the case of securities which are traded on the basis of dollar price or securities sold at par, in which event only dollar price need be shown (in cases in which securities are priced to call or to par option, this must be stated and the call or option date and price used in the calculation must be shown, and where a transaction is effected on a yield basis, the dollar price shall be calculated to the lowest of price to call, price to par option, or price to maturity);

Rule G-15(a)(i)(I)[#] requires that customer confirmations include information on yield and dollar price as follows:

(1) for transactions effected on a yield basis, the yield at which transaction was effected and the resulting dollar price shall be shown. Such dollar price shall be calculated to the lowest of price to call, price to par option, or price to maturity.

(2) for transactions effected on the basis of dollar price, the dollar price at which transaction was effected, and the lowest of the resulting yield to call, yield to par option, or yield to maturity shall be shown.

(3) for transactions at par, the dollar price shall be shown.

In cases in which the resulting dollar price or yield shown on the confirmation is calculated to call or par option, this must be stated, and the call or option date and price used in the calculation must be shown.

Neither of these rules requires the presentation of a yield or a dollar price computed to the put option date as a part of the standard confirmation process. In many circumstances, however, the parties to a particular transaction may agree that the transaction is effected on the basis of a yield to the put option date, and that the dollar price will be computed in this fashion. If that is the case, the yield to the put date must be included on confirmations as the yield at which the transaction was effected and the resulting dollar price computed to the put date, together with a statement that it is a "yield to the [date] put option" and an indication of the date the option first becomes available to the holder.[6] The requirement for transactions effected on a yield basis of pricing to the lowest of price to call, price to par option or price to maturity, applies only when the parties have not specified the yield on which the transaction is based.

In addition, in regard to transactions in tender option bonds with adjustable tender fees, even if the transaction is not effected on the basis of a yield to the tender date, dealers must include the yield to the tender date since an accurate yield to maturity cannot be calculated for these securities because of the yearly adjustment in tender fees.[7]

Delivery Requirements

In a recent interpretive letter, the Board responded to an inquiry whether, in three situations, the delivery of securities subject to put options could be rejected.[8] The Board responded that, in the first situation in which securities subject to a "one time only" put option were purchased for settlement prior to the option expiration date but delivered after the option expiration date, such delivery could be rejected since the securities delivered were no longer "puttable" securities. In the second situation in which securities subject to a "one time only" put option were purchased for settlement prior to the option expiration date and delivered prior to that date, but too late to permit the recipient to satisfy the conditions under which it could exercise the option (e.g., the trustee is located too far away for the recipient to be able to present the physical securities by the expiration date), the Board stated that there might not be a basis for rejecting delivery, since the bonds delivered were "puttable" bonds, depending on the facts and circumstances of the delivery. A purchasing dealer who believed that it had incurred some loss as a result of the delivery would have to seek redress in an arbitration proceeding.

Finally, in the third situation, securities which were the subject of a put option exercisable on a stated periodic basis (e.g., annually) were purchased for settlement prior to the annual exercise date so that the recipient was unable to exercise the option at the time it anticipated being able to do so. The Board stated that this delivery could not be rejected since "puttable" bonds were delivered. A purchasing dealer who believed that it had incurred some loss as a result of the delivery would have to seek redress in an arbitration proceeding.

[1] See [Rule G-17 Interpretive Letter - Put option bonds: safekeeping, pricing,] MSRB interpretation of February 18, 1983.

[2] Rule G-8(a)(v) requires dealers to record, among other things, oral or written put options with respect to municipal securities in which such municipal securities broker or dealer has any direct or indirect interest, showing the description and aggregate par value of the securities and the terms and conditions of the option.

[3] See [Rule G-12 Interpretive Letter - Confirmation disclosure: put option bonds,] MSRB interpretation of April 24, 1981.

[4] See [Rule G-15 Interpretive Letter - Securities description: securities backed by letters of credit,] MSRB interpretation of December 2, 1982.

[5] See [Rule G-12 Interpretive Letter - Confirmation disclosure: tender option bonds with adjustable tender fees,] MSRB interpretation of March 5, 1985.

[6] See [Rule G-12 Interpretive Letter - Confirmation disclosure: put option bonds,] MSRB interpretation of April 24, 1981.

[7] See fn. 5.

[8] See [Rule G-12 Interpretive Letter - Delivery requirements: put option bonds,] MSRB interpretation of February 27, 1985.

[*] [Currently codified at rule G-15(a)(i)(C)(2)(a). See also current rule G-15(a)(i)(C)(2)(b).]

[†] [Currently codified at rule G-15(a)(i)(C)(1)(b).]

[‡] [Currently codified at rule G-15(a)(i)(B)(4). See also current rule G-15(a)(i)(B)(4)(c).]

[#] [Currently codified at rule G-15(a)(i)(A)(5). See also current rule G-15(a)(i)(A)(5)(c)(vi)(D).]

The Board has received inquiries concerning situations in which syndicate managers charge fees for designated sales that do not appear to be actual expenses incurred on behalf of the syndicate or may appear to be excessive in amount. For example, one commentator has described a situation in which the syndicate managers charge $.25 to $.40 per bond as expenses on designated sales and has suggested that such a charge seems to bear no relation to the actual out-of-pocket costs of handling such transactions.

G–17 provides that

In the conduct of its municipal securities business, each broker, dealer, and municipal securities dealer shall deal fairly with all persons and shall not engage in any deceptive, dishonest, or unfair practice.

The Board wishes to emphasize that syndicate managers should take care in determining the actual expenses involved in handling designated sales and may be acting in violation of rule G-17 if the expenses charged to syndicate members bear no relation to or otherwise overstate the actual expenses incurred on behalf of the syndicate.

Delivery requirements: put option bonds. In a previous telephone conversation [name omitted] of your office had inquired whether any or all of the following deliveries of securities which are subject to a put option could be rejected:

(1) Certain securities are the subject of a "one time only" put option, exercisable by delivery of the securities to a designated trustee on or before a stated expiration date. An inter-dealer transaction in the securities—described as "puttable" securities—is effected for settlement prior to the expiration date. Delivery on the transaction is not made, however, until after the expiration date, and the recipient is accordingly unable to exercise the option, since it cannot deliver the securities to the trustee by the expiration date.

(2) Certain securities are the subject of a "one time only" put option, exercisable by delivery of the securities to a designated trustee on or before a stated expiration date. An inter-dealer transaction in the securities—described as "puttable" securities—is effected for settlement prior to the expiration date. Delivery on the transaction is made prior to the expiration date, but too late to permit the recipient to satisfy the conditions under which it can exercise the option (e.g., the trustee is located too far away for the recipient to be able to present the physical securities by the expiration date).

(3) Certain securities are the subject of a put option exercisable on a stated periodic basis (e.g., annually). An inter-dealer transaction in the securities—described as "puttable" securities—is effected for settlement shortly before the annual exercise date on the option. Delivery on the transaction, however, is not made until after the annual exercise date, so that the recipient is unable to exercise the option at the time it anticipated being able to do so.

I am writing to confirm my previous advice to him regarding the Board’s consideration of his inquiry.

As I informed him, his inquiry was referred to a Committee of the Board which has responsibility for interpreting the "delivery" provisions of the Board’s rules; that Committee has authorized my sending this response. In considering the inquiry, the Committee took note of the provisions of Board rule G-12(g), under which an inter-dealer delivery may be reclaimed for a period of eighteen months following the delivery date in the event that information pertaining to the description of the securities was inaccurate for either of the following reasons:

(i) information required by subparagraph (c)(v)(E) of this rule was omitted or erroneously noted on a confirmation, or

(ii) information material to the transaction but not required by subparagraph (c)(v)(E) of this rule was erroneously noted on a confirmation.

Under this provision, therefore, a delivery of securities described on the confirmation as being "puttable" securities could be reclaimed if the securities delivered are not, in fact, "puttable" securities.

The Committee is of the view that, in the first of the situations which he cited, the delivery could be rejected or reclaimed pursuant to the provisions of rule G-12(g). In this instance the securities were traded and described as being "puttable" securities; the securities delivered, however, are no longer "puttable" securities, since the put option has expired by the delivery date. Accordingly, the rule would permit rejection or reclamation of the delivery.

In the third case he put forth, however, this provision would not be applicable, since the securities delivered are as described. Accordingly, there would not be a basis under the rules to reject or reclaim this delivery, and a purchasing dealer who believed that it had incurred some loss as a result of the delivery would have to seek redress in an arbitration proceeding or in the courts. This may also be the result in the second case he cited, depending on the facts and circumstances of the delivery. MSRB interpretation of February 27, 1985.

The Board has received inquiries concerning situations in which a municipal securities dealer alters the settlement date on transactions in "when-issued" securities. In particular, the Board has been made aware of a situation in which a dealer sells a "when-issued" security but accepts the customer’s money prior to the new issue settlement date and specifies on the confirmation for the transaction a settlement date that is weeks before the actual settlement date of the issue. The dealer apparently does this in order to put the customer’s money "to work" as soon as possible. The Board is of the view that this situation is one in which a customer deposits a free credit balance with the dealer and then, using this balance, purchases securities on the actual settlement date. The dealer pays interest on the free credit balance at the same rate as the securities later purchased by the customer.

Rule G-17 provides that

In the conduct of its municipal securities business, each broker, dealer, and municipal securities dealer shall deal fairly with all persons and shall not engage in any deceptive, dishonest, or unfair practice.

The Board believes that this practice would violate rule G-17 if the customer is not advised that the interest received on the free credit balance would probably be taxable. In addition, the Board notes that a dealer that specifies a fictitious settlement date on a confirmation would violate rule G-15(a) which requires that the settlement date be included on customer confirmations.

Automated clearance: use of comparison systems. I am writing to confirm the substance of our conversations with you at our meeting on October 3 to discuss certain of the issues that have arisen since the August 1 effective date of the requirements of rule G-12(f) for the use of automated comparison services on certain inter-dealer transactions in municipal securities. In our meeting you explained certain problems that have become apparent since the implementation of these requirements, and you inquired as to our views concerning the application of Board rules to these difficulties or appropriate procedures to remedy them. The essential points of our responses are summarized below.

In particular, you indicated that the use of the "as of" (or "demand as of") feature of the automated comparison system has, in some cases, caused inappropriate rejections of deliveries of securities. This occurs, you explained, because the comparison system is currently programmed to display an alternative settlement date of two business days following the date of successful comparison of the transaction, if such comparison is accomplished through use of the "as of" or "demand as of" feature.[1] As a result, in certain cases involving transactions compared on an "as of" basis dealers have attempted to make delivery on the transaction on the contractual settlement date, and have had those deliveries rejected, since the receiving party recognizes only the later "alternative settlement date" assigned to the transaction by the comparison system. You inquire whether such rejections of deliveries are in accordance with Board rules.

I note that this "alternative settlement date" has significance for clearance purposes only, and does not result in a recomputation of the dollar price or accrued interest on the transaction.

As we advised in our conversation, the receiving dealer clearly cannot reject a good delivery of securities made on or after the contractual settlement date on the basis that the delivery is made prior to the "alternative settlement date" displayed by the comparison system. Both dealers have a contract involving the purchase of securities as of a specified settlement date, and a delivery tendered on or after that date in "good delivery" form must be accepted. A dealer rejecting such a delivery on the basis that it has been made prior to the "alternative settlement date" would be subject to the procedures for a "close-out by seller" due to the improper rejection of a delivery, as set forth in Board rule G-12(h)(ii).[2]

* * *

You also advised that some dealers who are using the automated comparison system are using their own delivery tickets, rather than the delivery tickets generated by the system, at the time they make delivery on the transaction. As a result, you indicated, there have been rejections of these deliveries, since the receiving dealer is unable to correlate these deliveries with its records of transactions compared through the system. You suggested that the inclusion of the "control numbers" generated by the comparison system on these self-generated delivery tickets would help to eliminate these unnecessary rejections and facilitate the correlation of receipts and deliveries with records of transactions compared through the system. As I indicated in our conversation, the Board concurs with your suggestion. The Board strongly encourages dealers who choose to use their own delivery tickets for transactions compared through the automated system to display on those tickets the control number or other number identifying the transaction in the system.[3] This would ensure that the receiving dealer can verify that it knows the transaction being delivered and that it was successfully compared through the system.

* * *

You also noted that many municipal securities dealers have continued the practice of sending physical confirmations of transactions, in addition to submitting such transactions for comparison through the automated system. You advised that this is causing significant problems for certain dealers, since they are required to maintain a duplicate system in order to provide for the review of these physical confirmations.

The Board is aware that certain municipal securities dealers chose to maintain parallel confirmation systems following implementation of the automated comparison requirements on August 1 in order to ensure that they maintained adequate control over their activities, and recognizes that for many such dealers this was an appropriate and prudent course of action.[4]  However, the Board wishes to emphasize that its rules do not require the sending of a physical confirmation on any transaction which has been submitted for comparison through the system. On the contrary, the continued use of unnecessary physical comparisons increases the risk of the duplication of trades and deliveries and substantially decreases the efficiencies and cost savings available from the use of the automated comparison system. The Board believes that all system participants must understand that the use of the automated comparison system is of primary importance. Accordingly, the Board strongly suggests that the mailing of unnecessary physical confirmations should be discontinued once a dealer is satisfied that it has adequate control over its comparison activities through the system.

You and others have suggested that it would be helpful if dealers which are unable to discontinue the mailing of physical confirmations would identify those transactions which have also been submitted for comparison through the system through some legend or stamp placed on the physical confirmation sent on the transaction. The Board concurs with your suggestion, and recommends that, during the short remaining interim when dealers are continuing to use duplicate physical confirmations, they include on physical confirmations of transactions submitted to the automated comparison system a stamp or legend in a prominent location which clearly indicates that the transaction has been submitted for automated comparison. MSRB interpretation of January 2, 1985.

[1] For example, a transaction of trade date October 19 for settlement October 25 fails to compare through the normal comparison cycle. Due to this failure to compare, the transaction is dropped from the comparison system on October 23; however, due to a resolution of the dispute, both parties resubmit the trade on an “as of” basis on October 24, and it is successfully compared on that date. Due to the delay in the comparison of the transaction, the system will display an “alternative settlement date” on this transaction of October 26 on the system-generated delivery tickets.

[2] I understand that [Registered Clearing Agency] is taking steps to have the contractual settlement date reflected on delivery tickets produced with respect to transactions compared on an “as of” or “demand as of” basis. We believe that this will be most helpful in clarifying and receiving dealer’s contractual obligation to accept a proper delivery made on or after the date.

[3] I understand that proper utilization of the comparison system control number is a reliable method for identifying and referring to transactions.

[4] The Board is also aware that on certain transactions dealers will need to send physical confirmations to document the terms of a specific agreement concluded as the time of trade (e.g., a specification of a rating). In such circumstances the Board anticipates that physical confirmations will continue to be sent.