Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

The following are the options in the Create Pending Trade Rule Detail panel, where you can specify general criteria used to identify pending transactions. Some options appear only in the grid at the bottom of the panel.

OptionTagDescription

Entity Information



Entity ID1163Specifies the unique identifier of the entity. If you specify an entity, ensure the entity's Pending Trade Eligible Indicator field (tag 3679) is set to Yes so the entity is eligible for pended transaction activity when used with pending trade rules.
Entity Name1164Specifies the name of the entity.

Security Information



Issue Name961Specifies the name of the security.
Ticker13Specifies the system of letters used to uniquely identify a security.
Xref Type1234Specifies the cross reference security type, such as SEDOL, CUSIP, and so on.
Xref ID1233Specifies the cross reference security identifier.
Processing Security Type3931Specifies the processing security type (PST). You can create a pending trade rule detail at the processing security type level. 
Security Type82Specifies the type of security. You can create a pending trade rule detail at the security type level. 
Position Quantity122Displays the current quantity of the position.

Rule Options



Pending Trade Indicator3695

Indicates whether to process pending transactions for entities eligible for pending trade activity that meet the rule criteria. Options include:

  • Yes. Assign a Pending status to transactions that meet criteria of the pending trade rule detail. The PT Rule Name and additional fields in the Rule Options area of the grid become available.
  • No. Do not assign a Pending status to transactions that meet criteria of the pending trade rule detail. The transaction can process straight through to the STAR accounting engine. 
PT Rule Name17026

Identifies the name of the pending trade rule associated with the selected pending trade rule detail. This field appears if you set Pending Trade Indicator to Yes. 

If you specify a value, the system applies the pending trade rule detail only to transactions for one or more entities that have the same PT Rule Name value assigned at the entity level. Otherwise, if you do not specify a rule name for this field, the system applies the pending trade rule detail only to transactions for entities that do not have a PT Rule Name value assigned at the entity level, as well as to master funds eligible for the pending trade workflow. You can associate a PT Rule Name with one or more entities, but cannot associate it with master funds.

Message Type 3822Specifies the message type associated with the transaction. Options include:
  • MTOPEN. The rule applies to open transactions. 
  • MTCLOSE. The rule applies to close transactions. 
  • MTCANCEL, The rule applies to cancel transactions. If you select this value, you can then specify values for the Cancel Strategy field, the CXL & Target Release Strategy field, and the Manual Cancel Strategy field.
  • MTADJUST. The rule applies to adjust transactions.
Event Type3821

Specifies the event type if you do not specify a message type for the transaction. See the About Event Types section for more information. This field appears if you do not specify a value for the Message Type field. This value is not used for processing. Options include:

  • BUY
  • CONVERSION
  • REC
  • BUYFUT
  • BUYVARMAR
  • OPENFUTURE
  • SELLFUT
  • SELLVARMAR
  • SHORTSELL
  • TBAOPEN
  • WRITE
  • OPENSWAP
  • SELL
  • DEL
  • BUYCVR
  • BUYFUT
  • BUYVARMAR
  • CALLEXRST
  • CLOSEFUTURE
  • EXERCISE
  • PUTASNST
  • PUTEXRST
  • SELLFUT
  • SELLVARMAR
  • TBACLOSE
  • CLOSESWAP
  • TRADEFWD 
  • SPOT
  • JNLCVR
  • FNDSPLTMRG
  • LPOPEN
  • LPCALL
  • LPCLOSE
  • LPCASH
  • LPCAP
Event Type7001

Specifies the event type for an MTOPEN event. See the About Event Types section for more information. This field appears if you specify a value for the Message Type field of MTOPEN. This value is not used for processing. Options include:

  • BUY
  • CONVERSION
  • REC
  • BUYFUT
  • BUYVARMAR
  • OPENFUTURE
  • SELLFUT
  • SELLVARMAR
  • SHORTSELL
  • TBAOPEN
  • WRITE
  • OPENSWAP
  • LPOPEN
Event Type 7002

Specifies the event type for an MTCLOSE event. See the About Event Types section for more information. This field appears if you specify a value for the Message Type field of MTCLOSE or MTCANCEL. This value is not used for processing. Options include:

  • SELL
  • DEL
  • BUYCVR
  • BUYFUT
  • BUYVARMAR
  • CALLEXRST
  • CLOSEFUTURE
  • EXERCISE
  • PUTASNST
  • PUTEXRST
  • SELLFUT
  • SELLVARMAR
  • TBACLOSE
  • CLOSESWAP
  • FNDSPLTMRG
  • LPCLOSE
Event Type7005

Specifies the event type for an MTADJUST event. See the About Event Types section for more information. This field appears if you specify a value for the Message Type field of MTADJUST. This value is not used for processing. Options include:

  • LPCALL
  • LPCASH
  • LPCAP
  • LPCOMMIT
Cancel Strategy16620

Determines which, if any, cancel (MTCANCEL) transactions associated with the pending trade rule detail to pend during automated processing. This field appears if you set the Message Type to MTCANCEL. Options include:

  • Do Not Pend Cancel Trades. The system does not pend any cancel transactions that meet the rule criteria. 
  • Pend All Cancel Trades. The system pends all cancel transactions that meet the rule criteria. That is, it adds them to the Pending Trades table. 
  • Pend Only If Target Is Pending. The system pends cancel transactions that meet the rule criteria only if the target transaction associated with the cancel transaction is in the Pending Trades table. In that case it adds the cancel transaction to the Pending Trades table.
CXL & Target Release Strategy16621

Indicates whether to release pending cancel transactions to the STAR engine during automated processing for cancellation. It applies when you select a Message Type of MTCANCEL. This field appears if you set the Cancel Strategy to pend all or some cancel trades. Options include:

  • Release to STAR. The system releases both the pending cancel transaction and its target transaction to the STAR accounting engine, where it subsequently cancels them.
  • Do Not Release to STAR. The system does not release the pending cancel transaction and its target transaction to the STAR accounting engine. The system cancels the transaction directly from the Pending Trades table. It assigns both trades to the CANCELLED status in the Pending Trades table. This option allows you to avoid having to release a pending transaction to STAR before canceling it, yet still maintain the ability to keep a record of the trade for downstream reporting.
Manual Cancel Strategy16622

Indicates whether to duplicate the target trade related to a cancel transaction during a manual cancel trade so you can possibly resubmit it as a pending transaction. This field appears if you set the Message Type to MTCANCEL. Options include:

  • Create Duplicate of Target Trade. Following a manual cancel trade, the system sends an identical copy of the target trade back to the Pending Trades table for possible resubmission. 
  • Do Not Create Duplicate. Following a manual cancel trade, cancels the target trade without adding it back to the Pending Trades table. The system does not send an identical copy of the target trade back to the Pending Trades table for possible resubmission. 
PT Transaction Type17021

Determines whether the system sends manual and/or automated trades that meet the pending trade rule detail criteria for review in the Pending Trades table prior to processing in the STAR accounting engine. An automated transaction has its Update Source (tag 988) value set to MTADMIN. This option becomes available if you set Pending Trade Indicator to Yes. Options include:

  • Manual. The system sends manually submitted trades to the Pending Trades table for review, and allows automated trades to process straight through to the STAR accounting engine. 
  • Automated. The system sends automated trades to the Pending Trades table for review, and allows manually submitted trades to process straight through to the STAR accounting engine. 
  • Both. Default. The system sends both manually submitted and automated trades to the Pending Trades table for review. 
PT Review Required17022

Determines whether the transaction requires review in the Pending Trades table prior to processing in the STAR accounting engine, such that you must release the trade individually and cannot release it in a group of pending trades. This field appears if you set Pending Trade Indicator to Yes. Options include:

  • Yes. The transaction does require individual review. You can release the pending transaction only using the Edit and Release Pending Trade option.
  • No. Default. The transaction does not require individual review. You can release the pending transaction with a group of pending transactions using the Batch Release Pending Trades option or individually using the Edit and Release Pending Trade option.
PT Tolerance Check17023

Determines whether the system applies a tolerance check to the transaction as criteria for whether to pend the trade. Eagle Accounting only sends transactions that exceed the specified tolerance to the Pending Trade table for further review. This field appears if you set Pending Trade Indicator to Yes. Options include:

  • No. Default. The system does not apply a tolerance check to the transaction. 
  • Yes - Net Assets %. The system applies a net assets percentage tolerance check to the transaction using the value in the Tolerance Percentage field. The system sends transactions with a base net amount greater than the specified tolerance to the Pending Trade table for review before processing in the STAR accounting engine. The system sends transactions with a base net amount less than the specified tolerance net amount straight through to the STAR accounting engine for processing. 
  • Yes - Net Amount. The system applies a net assets amount tolerance check to the transaction using the value in the PT Net Amount Tolerance field. The system sends transactions with a base net amount greater than the specified tolerance amount to the Pending Trade table for review before processing in the STAR accounting engine. The system sends transactions with a base net amount less than the specified tolerance net amount straight through to the STAR accounting engine for processing.
Tolerance Percentage17024

Specifies the net assets percentage tolerance value for the pending trade rule detail. This field appears if you set the PT Tolerance Check field to Yes - Net Assets %. 

An example follows. The Trade Net Amount is $500, where the entity Trade Net Amount is $10,000, and the trade represents 5% of the entity's Trade Net Amount. If you use a 1% tolerance percentage, Eagle Accounting pends this trade. If you use a 10% tolerance percentage, Eagle Accounting processes this trade straight to the STAR accounting engine. 

PT Net Amount Tolerance17025Specifies the net assets amount tolerance value for the pending trade rule detail. This field appears if you set the PT Tolerance Check field to Yes - Net Amount.
Trade Status3720

Specifies the transaction status of the pended transaction. This option allows you to associate a pending trade rule detail with transactions that have a custom status. This field appears if you set Pending Trade Indicator to Yes. You can select a value such as Pending, Hold, or a custom status. Options include:

  • FOF_ALLOCATION.
  • HOLD.
  • PENDING. By default, this option has a NULL value and applies to transactions with a status of PENDING. 
  • <CUSTOM STATUS>
Notes/Comments56Specifies any comments for the pending trade rule detail.
Reason Code1 - Reason Code53884

Identifies the reason for creating the pending trade rule detail. You must assign at least one reason code to the rule. You can also assign your own values for the Flag Reason code. Options include:

  • 306 Stock
  • Affiliates
  • Collateral Out
  • Corporation Action
  • Manual Lot Selection
  • UDF1 (User Defined Flag)
  • UDF2
  • UDF3
  • UDF4
  • UDF5
  • No labels