Entity Setup
Before any trades can be booked, the target entity must be set up appropriately. Futures & Options with Margin Transaction Fees (3889) must be populated any time the Option or underlying Future has Variation Margin (4533) = Yes
. The other Future-related fields are only required if the Option will be physically exercised into the underlying Future.
Note: Future Options are always processed as Identified
cost regardless of an entity's Cost Method (22) setting.
Entities trading Options need two specific pieces of data, which can be populated using Create/Edit Entity.
Net Option Positions (639)
No
: long and short positions in the same contract are held separately, with units always positive in Eagle AccountingShort positions have negative units in Data Management
Transaction elections are Buy, Write, Sell, and BuytoCover
Yes
: long and short positions in the same contract are netted together, allowing a trade to cross zero and bring the position from long to short or vice versaShort positions are represented by negative units in both Eagle Accounting and Data Management
Transaction elections are Buy and Sell
Options and Futures Expiration Delay Days (12101): number of days to delay automatic expiration
When NULL or zero, Eagle Accounting will auto-expire the Option on expiration date
When populated, the expiration event can only be processed on the adjusted date
Example: if Options and Futures Expiration Delay Days = 3 and expiration date = 2022-01-21, the expiration can only be processed on 2022-01-24
Entities trading Futures need three specific pieces of data, which can be populated using Create/Edit Entity or Add/Change Entity.
Lot Selection Method (27): multi-lot Future positions are often closed using
Modified FIFO
(MFIFO), which is a variation of FIFO that closes lowest cost lots first when relieving multiple open lots from a given dateIf Futures are going to be comingled with other securities, you may have to set up a Mixed Cost Basis Rule to enforce MFIFO specifically for Futures, as described in Manage Mixed Cost Basis Rules
Regular FIFO only considers the Event Sequence (126) when relieving multiple open lots from a given date
Details about MFIFO and other lot relief methods are available in Understand Lot Selection Methods
Margin Price Source (18041): this price source is used for VM processing and can be different than the price sources used for URGL
If an entity has multiple bases, this must be the same across all bases; when adding a secondary basis it will default to the same value as the primary basis
Futures & Options with Margin Transaction Fees (3889): this only affects Futures with VM and allows the commission and fees to be either included or excluded in cost for gain/loss calculations
Net Futures Positions (632)
Yes
: long and short trades are netted to a single long position (all trades are considered long, with negative units if a position or trade is short)This is allowed even if Tech Short Eligible (57) =
No
, which would typically prevent negative units
No
: long and short trades create two separate position rows (trades and positions are considered long or short, always with positive units)
Futures Clearing Broker (634): there can only be one Clearing Broker per futures trade
The trade panel will automatically default to this value, but it can be overridden if necessary
Some clients have a requirement to process the same Future with VM in certain funds and without VM in others. This can be accomplished by using a Variation Margin Override Rule. Refer to Override a Security's Variation Margin Setting for an Entity for details.
Reference Data
Storage & Configuration
Eagle has modeled Option security master files (SMFs) as single rows in Data Management. The underlying Future can be set up ahead of time and then linked to the Option via the Underlying Security fields. The Underlying Security fields are optional on the SMF, but are required for physical exercises or assignments.
Market Data
Future Option prices must be loaded directly to the contract (they will not be pulled from the underlying security).
Security Data
Options can be set up and maintained in Issue Viewer, Security Reference Manager (SRM), or Reference Data Center (RDC). The list below contains all fields required to configure a Future Option SMF.
Issue Name (961)
Primary Asset ID (14) & Type (1432)
Processing Security Type (3931) =
OPOPCM (Future Option)
Contract Size (19): number of Futures that each Option is entitled to
Issue Country (1418)
Asset Currency (85)
Expiration Date (38): date when Accounting will automatically expire the Option, unless the entity-level Options and Futures Expiration Delay Days field has been populated
Strike Price (67): price at which the Option can be exercised or assigned
Option Type (1142)
American
: Option can be exercised or assigned at any time until expiration, assuming the strike price has been reachedEuropean
: Option can be exercised or assigned on expiration date onlyBermudan
: functions the same way as American in Accounting; this option exists for reference data purposes only
Premium Type (3302)
Cost
: Option premium is settled to cash and valuation is the same as a vanilla equity optionNotional Cost
: Option premium is not settled to cash, but instead held as a notional cost similar to Futures without variation margin (VM)Variation Margin (4533, only if Premium Type = Notional Cost)
Yes
: VM is calculated and settled to cash, resulting in a MV of zero on the OptionNo
: Accounting does not calculate VM, resulting in a MV on the Option equal to its URGL
Variation Margin Rule (2289, see the Valuation section for calculation details): defines how VM or unrealized gain/loss is calculated
Standard Life to Date
: most US and foreign Future Options use this calculation10-Year Australian Government Bond
(10Yr AUDGOVTBND): for Future Options on 10-year Australian government bonds; requires that Underlying Coupon Rate and Payment Frequency be populated as well3-Year Australian Government Bond
(3Yr AUDGOVTBND): for Future Options on 3-year Australian government bond; requires that Underlying Coupon Rate and Payment Frequency be populated as wellAustralian 90-Day Bank Bill
(AUD 90 Day Bank Bill): for Future Options on Australian 90-day bank billsUS Treasury
: for Options on US Treasury Futures
Put/Call Flag (1350)
Trade Processing
Trades are entered using the Book Trade module once entity and reference data have been configured. Enter the appropriate entity, security identifier, and trade (35)/settle (37) dates and click Submit to query for the security. When you right-click the security, the options for opening and closing it will depend on whether the entity-level Net Option Positions field is set to Yes
or No
.
Open & Close
The fields below are used for both opens and closes.
Contracts (40): number of contracts being transacted
Price Per Contract (45): this is multiplied by Contracts and Contract size to calculate the premium
Commission Per Contract (971): this is multiplied by Contracts to calculate Commission Amount Local (47), which is factored into the net amount
Tax Amount (46), SEC Fee (48), Stamp Duty Tax (51), & Other Fee (3752): these are added to the premium and commission to generate the total net amount
These fields are only available when Variation Margin =
No
Broker (88)
Clearing Broker (1237): only required when Variation Margin =
Yes
Field | Open > Long | Open > Short | Close > Long | Close > Short |
---|---|---|---|---|
Event Type (55) | No VM = | No VM = | No VM = | No VM = |
Long-Short Indicator (15) | L (LONG) | S (SHORT) | L (LONG) | S (SHORT) |
Net Option Positions (639) = | Creates a long position (long with positive quantity). | Creates a short position (short with positive quantity). | Closes (partially or fully) a previously established long position. | Closes (partially or fully) a previously established short position. |
Net Option Positions (639) = | Creates a long position (long with positive quantity) or closes a previously established short position (long with negative quantity). | N/A | Creates a short position (long with negative quantity) or closes a previously established long position (long with positive quantity) | N/A |
Commission/Fees
Any commissions and fees involved in the transaction can be entered at trade time. For Future Option with Variation Margin = Yes
, the entity-level Futures & Options with Margin Transaction Fees determines how commissions and fees are treated (the default election is Capital
).
Capital
: commission + fees are added to the notional amount used for calculating VMThey will be reflected in CASH when the VM process is run for Trade Date, Approved, and Settled
Notional Cost = (contracts * price) + commission + fees
Expense
: commission + fees will be expensed and excluded from cost for subsequent gain/loss calculationsThe commission + fees are still included in margin approval process and will be reflected in CASH when the VM process is run for Trade Date, Approved, and Settled
Notional Cost = Contracts * Price
Exercise/Assign
Exercises and assignments are processed using Book Trade > Other > Exercise. By definition, purchased Options are exercised and written Options are assigned, but they use the same process in Accounting. Note: exercises of Australian Government Bond Future Options are not currently supported.
Settlement
Future Options can be exercised or assigned using cash or physical settlement. The section below focuses on Future Options with Premium Type = Notional Cost
. For Future Options with Premium Type = Cost
, refer to https://eagledocs.atlassian.net/wiki/spaces/IE/pages/1658978584/Equity+Fixed+Income+Index+Options+Best+Practices#Exercise/Assign as these function more like standard Equity Options.
Cash Settlement
Cash settlement has no effect on the underlying asset and does not generate any cash. Enter the exercise/assign price in Price Per Contract (45). This is informational only.
Variation Margin = No
Cash settlement closes the specified number of Future Option contracts with associated cost treated as realized loss (purchased) or proceeds as realized gain (written).
Variation Margin = Yes
Cash settlement closes the specified number of Future Option contracts with gain/loss calculated as shown below.
Purchased Call or Put
Gain (Loss) = # of contracts exercised * contract size * (exercise price - option open price) * price multiplier
Written Call or Put
Gain (Loss) = # of contracts exercised * contract size * (option open price - exercise price) * price multiplier
Note: realized gain/loss is not calculated based on initial price and exercise price
Physical Settlement
Physical settlement results in either opening or closing a position in the underlying asset. You must populate To Clearing Broker (5529) with the clearing broker for the underlying Future, even even if VM is turned off for the Future.
Variation Margin = No
Option cost/premium is allocated as URGL to underlying Future.
Variation Margin = Yes
Option gain or loss from VM is allocated as URGL to underlying Future
Purchased Call: establishes long position
Written Call: reduces long position; does not occur if underlying future is without VM
Purchased Put: reduces long position; does not occur if underlying future is without VM
Written Put: establishes long position
Physical Short Settlement
Not supported for Future Options.
Exercise/Assign Events
Accounting will automatically move the Option’s cost to the underlying security when the contract is exercised, via these events in Accounting:
Close the Option contract
Open or close the underlying security position (long or short)
Allocate Option cost or premium to the underlying security position
Canceling Exercise/Assign Events
Canceling an exercise or assign event requires the use of the Batch Cancel Trades panel. Query for the appropriate date range, entity, and security, then set Choose Trade to Cancel (962) = the target exercise/assign event. This will roll back the exercise/assign event by removing the action on underlying shares and restoring the original position. Option trades can be canceled using the regular Cancel Trade panel or rebooked using the Cancel & Rebook Trades module.
Accounting
Once a Future Option position has been established it will be picked up in Eagle’s global workflow. Accounting valuation is calculated when posting unrealized gain/loss and Data Management valuation is calculated in STAR to PACE.
V17 & Above: Accounting Center > Processing and Exceptions > Global Processes
Accounting Valuation: Unrealized Gain Loss Entries > Post Daily Fund Unrealized Gain Loss-Position
Data Management Valuation: Eagle STAR to Eagle PACE Direct Processing > Transfer Data - Batch
Prior to V17: Global Process Center
Accounting Valuation: Unrealized Gain Loss Entries > Post Daily Fund Unrealized Gain Loss-Position
Data Management Valuation: STAR to PACE Direct Processing > Transfer Data - Batch
For Future Options with Variation Margin = Yes
, the VM process must also be triggered. Refer to Futures (FUT) Best Practices for detailed information on the VM workflow.
Valuation
Future Option valuation varies depending on the reference data elections for Premium Type and Variation Margin (if applicable).
Premium Type =
Cost
Market Value = # of Contracts * Contract Size * Price * Price Multiplier
Premium Type =
Notional Cost
Variation Margin =
No
Market Value = # of Contracts * Contract Size * (Market Price - Trade Price) * Price Multiplier
Variation Margin =
Yes
Market Value = zero (VM settled to cash each day based on day-over-day price movement)
Note: refer to Futures (FUT) Best Practices for detailed information on valuation when using Notional Cost
and the calculations behind each Variation Margin Rule.
Expire
If the contract is not closed prior, Eagle Accounting will expire the Option on expiration date plus the number of days defined in the entity’s Options and Futures Expiration Delay Days election.
Reporting
STAR to PACE (S2P)
Almost all reports in Eagle leverage data from Data Management, which is populated by the S2P process. This will be scheduled as part of the daily workflow, but can also be triggered manually as described in the Accounting section.
The S2P process creates a single row for each Future Option in the POSITION, POSITION_DETAIL, TRADE, and CASH_ACTIVITY tables. The MARKET_VALUE_INCOME column captures the total market value. Cash activity is appropriately signed based on whether the Future Option is bought or written.
Accounting Reports
Eagle has a core set of accounting reports that can be used to review Future Option information. These are designed to support the daily operational workflow for business users, allowing Grid Reports to be easily exported to Excel and customized to provide additional details as needed. Advanced Reports are intended to be client-facing and do not provide the same level of customization.
Refer to Derivatives Reporting Best Practices for additional guidance.
Insurance Reporting
To categorize derivatives for insurance reporting, such as the Schedule DB, Derivative Elections (56) must be set toHedging Effective
, Hedging Other
, Income Generation
, Replications
, or Other
on all trades. Leaving the default of Trade
will prevent the transaction from appearing on insurance reports.Data Management Reporting
General Reporting (Eagle OLAP)
OLAP reports provide the maximum level of customization, allowing any column in Data Management to be pulled into a report. These go beyond the Eagle Accounting Grid Reports because they are not limited by core queries, can support multiple sources and various types of calculations, and provide drill-down functionality based on user-defined groupings.
Performance
The performance toolkit calculates market value-based performance for Future Options using data supplied by the S2P process. However, this can be misleading because traditional market values do not capture an Option’s true exposure. Exposure-based analyses, which can be implemented using Eagle Enrichment, calculate more accurate returns. The documentation and .egl files linked below as attachments are available for beta testing. Additional details are available in Exposure Reporting Best Practices and the Eagle Enrichment User Guide 2015.
Automation
Option SMFs and trades can be loaded through the standard Message Center (MC) streams. The SMF must be loaded prior to the trade (trades do not spawn SMFs). Refer to https://eagledocs.atlassian.net/wiki/spaces/GENERICINTER/overview for more information.
Net Option Positions =
Yes
: short positions are maintained using standard Buy and Sell transactions; set Event Type (55) =BUY
orSELL
Net Option Positions =
No
: short positions are maintained using Write and BuytoCover transactionsSet Event Type =
WRITE
orBUYCVR
to process these trades through Message Center
Sample messages for the standard interfaces are listed below.
Variation Margin | Transaction Type | Default Message Center Stream | Sample Files |
No | SMF Setup | eagle_default_in_csv_smf | |
Trade Open | eagle_default_in_csv_trades OR eagle_default_in_csv_all | ||
Partial/Full Close | eagle_default_in_csv_trades OR eagle_default_in_csv_all | ||
Yes | SMF Setup | eagle_default_in_csv_smf | |
Trade Open | eagle_default_in_csv_trades OR eagle_default_in_csv_all | ||
Partial/Full Close | eagle_default_in_csv_trades OR eagle_default_in_csv_all |
Add Comment