|
VOLUME 20 - BULLETIN #153
TO:
|
ALL CLEARING MEMBERS
|
FROM:
|
BUSINESS SYSTEMS GROUP
|
DATE:
|
May 16, 2000
|
SUBJECT:
|
Allocate & Claim Transactions via the Internet (ACT)
|
As previously announced in Volume 20 – Bulletin # 109, the Clearing Corporation is beginning a program to implement one-sided entry for the following transactions:
• EFP’s or Exchange for Physicals (transaction type ‘9’)
• Misclears (transaction type ‘3’)
• Transfers (transaction types ‘7’ and ‘8’)
In addition to changing submission to one sided entry, system interfaces to clearing will change to eliminate 3270 communication and replace it with either web based browser technology or with API’s (Application Program Interface) that are being developed using the TREX record format. The scheduled launch of one-sided transactions will begin with EFPs on June 12th, 2000. A new system is being developed that can be accessed through BOTCC®’s web page at www.botcc.com to handle these transactions. Firms will be able to access this system, which has been named ACT (Allocate & Claim Transactions), either through the Internet or through BOTCC’s new customer network. Please be aware that by accessing this application via the Internet response time cannot be guaranteed. We suggest that firms access these applications via the Intranet available through the Customer Network.
After June 12th, EFP transactions will edit if entered into OTIS. These transactions will no longer be viewable in OTIS. They will only be accessible through the ACT system. All current users that have access to OTIS will have access to the ACT system. A new password will be assigned for initial entry. This password can then by synchronized with the users OTIS password for ease of transition.
Only Selling EFP transactions can be entered via MQM TREX messages or by using the Summary Creation screen in the ACT system. An API message will be generated confirming that a selling transaction has been entered. The Buyer will receive an API message indicating that there is a transaction to claim. To claim this transaction, an API message can be submitted using the TREX record format or the transaction can be claimed using the ACT system. Once claimed, API messages will be generated to both the Buyer and Seller confirming this transaction. MQM messages for the ACT system will be generated Real Time. There will be no RJE feeds created for these transactions. If MQM fails or if an emergency arises, an end of day FTP file will be created containing all of these transactions.
Attached you will find the new TREX record block that has been developed, EFP Business Rules that have been defined for this project, and a matrix that has been developed to facilitate API messages that will need to be used when
transmitting and receiving these transactions. A new TREX record A7 block was developed to allow the submitting side of a one-sided transaction to supply the opposite firms account number. The Subcommittee felt that this would aid the opposite side of the transaction to identify where this trade would reside.
The following is a list of hardware, software, and other requirements, which provide optimum performance:
HARDWARE REQUIREMENTS
• 100 MHz or higher Pentium-class machine
SOFTWARE REQUIREMENTS
• 128-bit encrypted version of Netscape Communicator v4.7 or higher (or)
• 128-bit encrypted version of Microsoft Internet Explorer v5.1 or higher
OTHER REQUIREMENTS
• User ID and Password for firm/individual (OTIS User ID)
• Access to the World Wide Web through an Internet Service Provider or network connection
• Cookies enabled on web browser
Without the above listed requirements, users will be unable to access this application.
Should you have any questions, please call or e-mail one of the following Business Systems Analysts:
EFP BUSINESS RULES
1. Only one side of an EFP Trade will be entered in the trade entry systems. The Seller will enter the trade.
2. A browser based on-line system will be provided to enter EFP trades. The system will be accessible from the BOTCC web site. The OTIS system will not be used.
3. Position updates will occur when the EFP is claimed. A buy and sell record will be generated by the ACT system and merged into the clearing process immediately.
4. Reversals can be performed on claimed transactions.
5. The EFP and ACT data will be kept on the database for a rolling week (i.e. Wednesday to previous Tuesday, Thursday to previous Wednesday…) and the system will purge data. The cleanup program will be parameterized to allow for flexibility in the cleanup time line.
6. EFPs can be given up. The ACT system will make use of the existing Give-up software to create the give-up data and users will need to go into the existing Give-up system or use the Give-up API (GAPI) to process their data. When the Give-up functionality is incorporated into the ACT system, the existing Give-up system will be disabled and the Give-up trades will be processed by ACT.
7. A new TREX block (A7) will be used to allow entry of a carrying firm’s account number for an allocation.
8. Over Allocations are not allowed.
9. Over Claims are not allowed.
|
|
|
|
|
|
TRADE EXCHANGE (TREX)
|
|
|
|
RECORD LAYOUT
|
|
(This is used for including an Opposite Firm Account on a One Sided Trade Transaction)
|
|
|
|
|
|
|
|
|
|
POSITION
FROM TO
|
FIELD NAME AND FORM
|
SAMPLE DATA
|
FORMAT
|
DESCRIPTION AND COMMENTS
|
R-EX
|
|
|
1
|
2
|
Block 7
|
A7
|
AN
|
Special Block
|
C
|
|
|
3
|
17
|
Opposite Firm Account Number
|
OPPOSITEACOUNT1
|
AN
|
Opposite Firm Account Number for single sided transactions.
|
AN
|
|
18
|
30
|
Reserved for future use
|
Blank
|
AN
|
RESERVED FOR FUTURE USE
|
B
|
|
Special Block A7 – Opposite Firm Account for One Sided Trades
Used for designation of the opposite firms' account number when submitting a one sided trade.
Opposing Firm’s Account Number in the situation of a one-sided trade. The ACT project uses this block to bring in the opposing firm’s account number for a one-sided trade through use of the ACT API.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Submit EFP
|
|
|
Allocate EFP via API
|
|
|
Claim via API
|
|
|
|
Auto-Allocate EFP
|
|
|
|
|
|
|
|
From:
|
EXEC
|
BOTCC
|
|
EXEC
|
BOTCC
|
BOTCC
|
|
CARRY
|
BOTCC
|
BOTCC
|
|
EXEC
|
BOTCC
|
BOTCC
|
BOTCC
|
|
|
|
|
To:
|
BOTCC
|
EXEC
|
|
BOTCC
|
EXEC
|
CARRY
|
|
BOTCC
|
CARRY
|
EXEC
|
|
BOTCC
|
EXEC
|
EXEC
|
CARRY
|
|
|
|
|
|
Pit or PJA
|
Alert
|
|
|
Confirm
|
Alert
|
|
|
Confirm
|
Alert
|
|
Pit or PJA
|
Alert
|
Confirm
|
Alert
|
|
Pos
|
Pos
|
|
EFP
|
API
|
|
API
|
API
|
API
|
|
API
|
API
|
API
|
|
Mark
|
API
|
API
|
API
|
|
from
|
to
|
Selected Fields
|
Summary
|
Summary
|
|
Allocation
|
Allocation
|
Allocation
|
|
Claim
|
Claim
|
Claim
|
|
Autoalloc
|
Summary
|
Allocation
|
Allocation
|
|
1
|
184
|
Main block
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
1
|
3
|
Message Identifier
|
1
|
ESA
|
|
EA
|
EAC
|
EAA
|
|
EC
|
ECC
|
ECA
|
|
EA
|
ESA
|
EAC
|
EAA
|
|
21
|
24
|
Message Length
|
|
0363
|
|
0214
|
0363
|
0248
|
|
0214
|
0363
|
0248
|
|
|
0363
|
0363
|
0248
|
|
25
|
25
|
Action Code
|
A
|
A
|
|
A
|
A
|
A
|
|
A
|
A
|
C
|
|
A
|
A
|
A
|
A
|
|
40
|
44
|
Clearing Member Firm
|
002
|
002
|
|
002
|
002
|
998
|
|
998
|
998
|
002
|
|
002
|
002
|
002
|
998
|
|
50
|
51
|
Trans Type Code
|
9
|
9
|
|
9
|
9
|
9
|
|
9
|
9
|
9
|
|
9
|
9
|
9
|
9
|
|
52
|
52
|
Buy/Sell Code
|
1
|
1
|
|
2
|
2
|
1
|
|
1
|
1
|
2
|
|
1
|
1
|
2
|
1
|
|
76
|
80
|
Opposite Clearing Firm
|
|
|
|
998
|
998
|
002
|
|
002
|
002
|
998
|
|
998
|
998
|
998
|
002
|
|
101
|
105
|
Quantity
|
00003
|
00003
|
|
00003
|
00003
|
00003
|
|
00003
|
00003
|
00003
|
|
00003
|
00003
|
00003
|
00003
|
|
109
|
118
|
Account Number
|
1234500000
|
1234500000
|
|
1234500000
|
1234500000
|
9876543210
|
|
9876543210
|
9876543210
|
1234500000
|
|
1234500000
|
1234500000
|
1234500000
|
9876543210
|
|
140
|
145
|
Trade ID Sequence Number
|
Summ #
|
Summ #
|
|
Summ #
|
Summ #
|
Detail #
|
|
Detail #
|
Detail #
|
Detail #
|
|
Summary #
|
Summary #
|
Summary #
|
Detail #
|
|
168
|
168
|
APS/GUS Indicator
|
|
|
|
|
F
|
T
|
|
|
T
|
F
|
|
|
|
F
|
T
|
|
1
|
30
|
A7 BLOCK
|
|
30
|
|
30
|
30
|
30
|
|
30
|
30
|
30
|
|
|
30
|
30
|
30
|
|
3
|
17
|
Carry Account
|
|
|
|
9876543210
|
9876543210
|
1234500000
|
|
1234500000
|
1234500000
|
9876543210
|
|
9876543210
|
9876543210
|
9876543210
|
1234567890
|
|
1
|
115
|
M1 BLOCK
|
|
115
|
|
0
|
115
|
0
|
|
0
|
115
|
0
|
|
|
115
|
115
|
0
|
|
110
|
115
|
Trade ID /Ref Num
|
|
Summ #
|
|
|
Detail #
|
|
|
|
Buy or SC #
|
|
|
|
Summary #
|
Detail #
|
|
|
1
|
34
|
M2 BLOCK
|
|
34
|
|
0
|
34
|
34
|
|
0
|
34
|
34
|
|
|
34
|
34
|
34
|
|
14
|
18
|
Status
|
|
PEND
|
|
|
ALLOC
|
ALLOC
|
|
|
CLAIM
|
CLAIM
|
|
|
ALLOC
|
ALLOC
|
ALLOC
|
|
|
|
|
Mark trade for giveup:
|
ESA
|
BOTCC alerts executing firm that a Summary has been created using the Sell Rec ID at Main-140 and providing Summary Reference # at M1-110
|
|
|
|
|
Allocation via API:
|
EA
|
Executing firm identifies Summary to be allocated using Summary Reference # at Main -140
|
|
|
|
|
|
EAC
|
BOTCC confirms allocation for Summary (Summary Reference ID at Main-140) and provides Detail Reference # assigned at M1-110.
|
|
|
|
|
|
EAA
|
BOTCC alerts claiming firm that allocation to it has been made and provides Detail Reference # at Main-140
|
|
|
|
|
Claim via API:
|
EC
|
Carrying firm sends claim of allocation using Detail Reference # at Main-140.
|
|
|
|
|
|
ECC
|
BOTCC confirms claim for allocation (Detail Reference # at Main-140) and provides either a Buy ID (which is will be the record ID for the resulting trade) or a Sub Claim Reference # (if the claim is a sub claim transaction) at M1-110.
|
|
|
|
|
|
ECA
|
BOTCC alerts executing firm that status of allocation (Detail Reference # at Main-140) has changed from ALLOC to CLAIM
|
|
|
|
|
Auto-Allocate
|
ESA
|
BOTCC alerts executing firm that a Summary has been created using Trade Rec ID at Main-140 and providing Summary Reference # at M1-110.
|
|
|
|
|
|
EAC
|
BOTCC confirms automatic allocation to executing firm, providing both Summary Reference # at Main-140 and Detail Reference # at M1-110.
|
|
|
|
|
|
EAA
|
BOTCC alerts claiming firm that allocation to it has been made and provides Detail Reference # at Main-140.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change claiming firm on allocation via API
|
|
|
Change other allocation fields
|
|
|
|
|
|
From:
|
EXEC
|
BOTCC
|
BOTCC
|
BOTCC
|
|
EXEC
|
BOTCC
|
BOTCC
|
|
|
|
|
To:
|
BOTCC
|
EXEC
|
Old CARRY
|
New CARRY
|
|
BOTCC
|
EXEC
|
CARRY
|
|
|
|
|
|
|
Confirm
|
Alert
|
Alert
|
|
|
Confirm
|
Alert
|
|
Pos
|
Pos
|
|
API
|
API
|
API
|
API
|
|
API
|
API
|
API
|
|
from
|
to
|
Selected Fields
|
Allocation
|
Allocation
|
Allocation
|
Allocation
|
|
Allocation
|
Allocation
|
Allocation
|
|
1
|
184
|
Main block
|
|
|
|
|
|
|
|
|
|
1
|
3
|
Message Identifier
|
EA
|
EAC
|
EAA
|
EAA
|
|
EA
|
EAC
|
EAA
|
|
21
|
24
|
Message Length
|
0211
|
360
|
0245
|
0245
|
|
0211
|
0245
|
0245
|
|
25
|
25
|
Action Code
|
C
|
C
|
D
|
A
|
|
C
|
C
|
C
|
|
40
|
44
|
Clearing Member Firm
|
9
|
9
|
9
|
9
|
|
002
|
002
|
998
|
|
50
|
51
|
Trans Type Code
|
999
|
999
|
002
|
002
|
|
9
|
9
|
9
|
|
52
|
52
|
Buy/Sell Code
|
2
|
2
|
1
|
1
|
|
2
|
2
|
1
|
|
76
|
80
|
Opposite Clearing Firm
|
999
|
999
|
002
|
002
|
|
998
|
998
|
002
|
|
101
|
105
|
Quantity
|
00003
|
00003
|
00003
|
00003
|
|
00003
|
00003
|
00003
|
|
109
|
118
|
Account Number
|
1234500000
|
1234500000
|
9876543210
|
9999999999
|
|
1234500000
|
1234500000
|
0555444333
|
|
140
|
145
|
Trade ID Sequence Number
|
Detail #
|
Detail #
|
Detail #
|
Detail #
|
|
Detail #
|
Detail #
|
Detail #
|
|
168
|
168
|
APS/GUS Indicator
|
|
F
|
T
|
T
|
|
|
F
|
T
|
|
169
|
173
|
APS Group ID
|
|
|
|
|
|
|
|
|
|
1
|
27
|
A7 BLOCK
|
27
|
27
|
27
|
27
|
|
27
|
27
|
27
|
|
3
|
17
|
Carry Account
|
9999999999
|
9999999999
|
1234500000
|
1234500000
|
|
0555444333
|
0555444333
|
1234500000
|
|
1
|
115
|
M1 BLOCK
|
0
|
0
|
0
|
0
|
|
0
|
0
|
0
|
|
110
|
115
|
Trade ID /Ref Num
|
|
|
|
|
|
|
|
|
|
1
|
34
|
M2 BLOCK
|
0
|
34
|
34
|
34
|
|
0
|
34
|
34
|
|
14
|
18
|
Status
|
|
ALLOC
|
ALLOC
|
ALLOC
|
|
|
ALLOC
|
ALLOC
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Change claiming firm
|
EA
|
Executing firm sends change to carrying firm and account on allocation using Detail Reference # at Main-140.
|
|
|
|
|
|
EAC
|
BOTCC confirms allocation change to carrying firm (Detail Reference # at Main-140)
|
|
|
|
|
|
|
EAA
|
BOTCC alerts old carrying firm to delete allocation specifying Detail Reference # at Main-140.
|
|
|
|
|
|
EAA
|
BOTCC alerts new carrying firm to add allocation providing Detail Reference # at Main-140.
|
|
|
|
|
|
Change other allocation fields
|
EA
|
Executing firm sends change to carry account on allocation using Detail Reference # at Main-140.
|
|
|
|
|
|
EAC
|
BOTCC confirms change to allocation to executing firm using Detail Reference # at | |