Page Comparison

In the Add/Change Entity panel, when you manually add or change basic entities, you can select various options based on the requirements of your business. See the Manage Entities section for details on adding or changing basic entities. 

The following are the options for Add/Change Entity panel:

Lookup Entity

Anchor
LookupEntity LookupEntity

• Lookup Entity ID. Specifies the unique alphanumeric identifier of an existing entity.
• Lookup Entity Name. Specifies the abbreviated name of an existing entity.
• Lookup Entity Long Name. Specifies the descriptive name of an existing entity.
• Lookup Entity Code. Stores an entity code, used for reporting purposes, for an existing entity.
• Lookup Entity Legal Name. Specifies the entity legal name, used for reporting purposes, for an existing entity.
• Language. Specifies the language for the entity. By default you add entity information in the English (US) language. If you use Eagle's multilingual capabilities, you can select a non English language for the entity. You can customize the system to display specified fields in the ML Tags section of this panel, allowing you to enter certain entity related text in the selected non English language.

Entity Identification

Anchor
EntityIdentification EntityIdentification

Legal Entity Identifier Details

Anchor
LegalEntityIdentifierDetails LegalEntityIdentifierDetails

The following are the options for Legal Entity Identifier (LEI) details:

• Legal Name (tag 5090). Specifies the legal name of the entity as the financial party registered with the LEI.
• Entity Status (tag 5091). Specifies the status of the entity. For example, ACTIVE and INACTIVE.
• Legal Form (tag 5092). Specifies the legal form of the entity as financial party registered with the LEI. For example, CORPORATION.
• Assigned Date (tag 5093). Specifies the date when the entity's LEI was assigned.
• Last Update Date (tag 5094). Specifies the date when the entity's LEI information was last updated.
• Disabled Date (tag 5095). Specifies the date when the entity's LEI information was disabled.
• Record State (tag 5096). Specifies the record state for the entity's LEI. The record state indicates the current process status of the CFTC Interim Compliant Identifier (CICI) record. For example, UNDER_REVIEW, DUPLICATE, CONFLICTING_SOURCES, INADEQUATE_SOURCES, VALIDATED, PENDING_REMOVAL.
• Certification State (tag 5097). Specifies the certification state used to register the entity's LEI. For example, CERTIFIED, NOT_CERTIFIED, STALE.
• Street (tag 5098). Specifies the street address used to register the entity's LEI.
• City (tag 5099). Specifies the city used to register the entity's LEI.
• State (tag 5100). Specifies the state code used to register the entity's LEI.
• Zip (tag 5180). Specifies the ZIP code used to register the entity's LEI.
• Country Code (tag 5181). Specifies the country code used to register the entity's LEI.

Core Accounting Fields

Anchor
CoreAccountingFields CoreAccountingFields

The following are the options for core accounting fields:

• Accounting Basis (tag 21). Specifies the primary accounting basis for the entity. You cannot edit this field after you create the entity. The system is installed with a set of values for this field. You can add additional values using the Add Code Values panel. Options include:
  –  USTAX. Default. The system is set up in accordance with domestic tax regulations.
  –  GAAP. The system is set up in accordance with Generally Accepted Accounting Principles (GAAP). This is the most common basis.
  –  IFRS. The system is set up in accordance with International Financial Reporting Standards (IFRS).
  –  STAT. The system is set up for use with statutory insurance.
• Controlling Basis (tag 4949). Indicates whether the accounting basis identified in the Accounting Basis field (tag 21) is the entity's controlling basis. The controlling basis is the accounting basis that controls lot selection when you close trades. Non controlling bases attempt to close the same lots that the controlling basis did. If you use the system to process pending transactions, the system stores pending transactions for the controlling basis only, and creates trades for each additional basis when it is processing the pending trade. An entity can have a single controlling basis. You can designate a primary or a non primary basis as the controlling basis. Options include Yes and No.
• Regulatory Category (tag 12387). Specifies the regulatory category associated with International Financial Reporting Standards (IFRS). A regulatory category is a classification that determines how to account for financial instruments. The new IFRS 9 categories that replace IAS 39 categories include Amortized Cost, Fair Value - Other Comprehensive Income, and Fair Value Profit Loss. IFRS 9 categories classify debt instruments based on their contractual cash flow characteristics and the business model in which they are held. Equity securities are classified in the FVOCI or FVPL regulatory categories. If you set the Accounting Basis field to a value of IFRS, you must specify a regulatory category. If you choose an accounting basis value other than IFRS, use of a regulatory category is optional. All investments within an entity/accounting basis must have the same regulatory category. A multi basis entity can have different regulatory categories by basis. Options include:
  –  AC (Amortized Cost). Used for debt instruments when the business model in which the financial assets are held has an objective to hold assets to collect contractual cash flows. Contractual cash flows must be solely payments of principal and interest on the principal amount outstanding (P&I).
  –  AFS (Available for Sale). Used for financial assets that are available for sale.
  –  AFSC (Available for Sale at Cost). Used for instruments that are valued at cost and are available for sale.
  –  FVO (Fair Value Option). Used for instruments managed on a fair value basis.
  –  FVOCI (Fair Value – Other Comprehensive Income). Used for debt instruments when the business model in which the financial assets are held has an objective both to hold assets to collect contractual cash flows and to sell financial assets. Contractual cash flows must be solely payments of principal and interest on the principal amount outstanding (P&I). Used for equity investments only if an entity makes an irrevocable election on initial recognition for the equity investments to be measured at FVOCI without recycling gains and losses to earnings.
  –  FVPL (Fair Value Profit Loss). Used for all other instruments, including derivatives, those held for trading, and those managed on a fair value basis. Includes debt instruments not qualified for AC or FVOCI regulatory categories. Also includes equities not designated as FVOCI and derivatives plus debt securities that are classified with an FVO election.
  –  HFT (Held for Trading). Used for instruments held with the intent of selling them.
  –  HTM (Held to Maturity). Used for non derivative financial assets that you intend to hold to the asset's maturity or payment date and whose cash value is not needed until that date.
  –  LR (Loans and Receivables). Used for non derivative financial assets with fixed or determinable payments that are not quoted in an active market.
  –  MFFVO (Mutual Fund Fair Value Option). Used with mutual funds with a Fair Value Option category. This regulatory category is for informational purposes only, and does not have a corresponding custom chart of account to use in ledger reporting. No core processes for Eagle's Accounting solution are affected.
  –  MFHFT (Mutual Fund Held for Trading). Used with mutual funds with a Held for Trading category. This regulatory category is for informational purposes only and does not have a corresponding custom chart of account to use in ledger reporting. No core processes for Eagle's Accounting solution are affected.
  –  O (Other). Used for other instruments.
• Regulatory Category Effective Date (tag 9137). Identifies the date that the regulatory category is eligible for processing. This field appears after you specify a regulatory category value. When you first enter a regulatory category, this field displays the entity's inception date by default, but you can override that value. When you change a regulatory category, you can specify the effective date for that change. If you change categories, be aware that the system uses the Regulatory Category Effective Date field value to determine the chart of account in effect for reporting purposes. Reports process based on the custom chart of account that was "active" during the period, using the report end date to determine what was active.
• URGL Accounting Rule (tag 1079). Specifies the URGL (unrealized gain/loss) rule for the entity/accounting basis that establishes proper treatment of unrealized market and currency gains/losses to ensure compliance with International Financial Reporting Standards (IFRS). This option is required only if you select a regulatory category of Amortized Cost, Available for Sale, Available for Sale at Cost, Fair Value Option, Fair Value – Other Comprehensive Income, Fair Value Profit Loss, Held for Trading, Held to Maturity, or Loans and Receivables. The URGL rule used for a Fair Value – Other Comprehensive Income basis determines whether the system recognizes realized gains and losses in other comprehensive income rather than earnings. See the Manage URGL Rules section for more information.
• Cost Method (tag 22). Specifies the cost method the system uses to calculate gain/loss amounts from the sale of security lots held by the entity. You cannot edit this field once the entity has holdings. Eagle's Accounting solution is a multiple basis accounting system. If you set up an additional accounting basis, it must have the same cost method as the primary accounting basis. Options include:
  –  Identified. Default. The system determines which lot to relieve (sell) based on the value in the Lot Selection Method field. After identifying the lot, the system determines its cost and compares that to the lot's earnings to calculate a gain or loss amount for reporting purposes. If you select Identified, you can amortize fixed income securities using all the options the system has available.
  –  Average. The system determines which lot to relieve (sell) based on the value in the Lot Selection Method field. After identifying the lot, the system determines the average of all of the holdings (total cost of holdings divided by the number of holdings) to calculate a gain or loss amount for reporting purposes. If you select Average, you can amortize fixed income securities using only selected options the system has available. The system applies the total amortization to individual lots based on the percentage of total par owned in the position.
• Lot Selection Method (tag 27). Specifies the lot selection method the system uses to relieve (sell) lots of a security held by the entity. Options include:
  –  First In First Out (FIFO). Lots acquired first are sold first. The oldest lot is sold first based on the holding date. If you set the accounting basis Cost Basis Covered Indicator field (tag 2818) to Y, unknown cost lots are relieved first. The oldest cost lot is sold first based on the holding date.
  –  Last In First Out (LIFO). Lots acquired last are sold first. The most recent lot is sold first based on the holding date. If multiple lots share the same holding date, the lot with the greatest event sequence is relieved first. The event sequence, set internally by the system, indicates the processing order of transactions within the same position.
  –  High Amortized Cost or High Cost (HCLOT). The lots with the highest current cost are sold first. The system uses current unit cost, which includes amortization for debt securities. This method relieves the lots that can generate the maximum loss or the minimal gain.
  –  Low Amortized Cost or Low Cost (LCLOT). The lots with the lowest current cost are sold first. The system uses current unit cost, which includes amortization for debt securities. This method relieves the lots that can generate the minimal loss or the maximum gain.
  –  High Original Cost (HORIG). The lots with the highest original cost are sold first. The system uses the original unit base cost of the open lots. It relieves the lots that can generate the maximum loss or the minimal gain.
  –  Low Original Cost (LORIG). The lots with the lowest original cost are sold first. The system uses the original unit base cost of the open lots. It relieves the lots that can generate the minimal loss or the maximum gain.
  –  Identified Lot (IDLOT). The specified lot or lots are sold first, which determines cost and tax implications. You can optimize this option to specific tax situations by selecting the specific lots to be sold. If you select this method, the lower pane in the close trade panel displays lot details for each available lot, as determined by the entity's controlling basis. If no controlling basis exists, it displays lots for the primary basis. You must specify the quantity for one or more lots that you want to relieve. The total quantity you specify for the open lots must match the quantity entered for the total close. The close trade relieves the selected lots in each of the entity's accounting bases, and keeps the lot structures in sync. The system uses the lot's Orig Event ID field (tag 457) to match a single open lot in one basis to corresponding multiple open lots in another basis, as needed. This can occur for lots fractured as a result of wash sale processing.
  –  Best Tax. The lots are selected and sold with the objective of taking losses first (short term then long term) and gains last (long term then short term). Lots are sold in the following order:

1. 1. Short term Losses. Lots that reflect a short term loss are sold first, beginning with lots that generate the greatest short term loss down to the least short term loss.
   2. Long term Losses. Lots that reflect a long term loss are sold, beginning with lots that generate the greatest long term loss down to the least long term loss.
   3. Short term No Gains or Losses. Short term lots that reflect no gain or loss.
   4. Long term No Gains or Losses. Long term lots that reflect no gain or loss.
   5. Long Term Gains. Lots that reflect a long term gain, beginning with lots that generate the least long term gain up to the greatest long term gain.
   6. Short Term Gains. Lots that reflect a short term gain, beginning with lots that generate the least short term gain up to the greatest short term gain.
   –  Tax Advantage (TXADV). The lots with the lowest tax liability are sold first to minimize tax liability.
   –  Versus Purchases (VSP). The lots are selected and sold based on lot purchase characteristics, such as the target purchase date and the target purchase price. This option must be specified at the trade level.
   –  Pro Rata. The lots are selected and sold based on a proportionate allocation. Note that this option is available at the mixed cost basis rule detail level but is not available at the entity/basis level.
   –  Tax Efficiency. The lots with the lowest tax liability are sold first to minimize tax liability. The system calculates the tax liability based on the manipulation of entity level tax factors for long and short term gains, long and short term losses, and currency gains. The system also incorporates the wash sale disallowance effect and considers the overall tax implications of closing each individual lot.
   –  Modified FIFO (MFIFO). The open lots with the same original acquisition date (tag 216) as the close transaction are sold first, starting with the lots with the lowest unit cost local. If there are no open lots with the same acquisition date as the close transaction, or all same day lots have been sold, the oldest open lots are sold first based on the acquisition date. Within a single acquisition date, the lots with the lowest unit cost local are sold first.

• Cost Method Cash (tag 9924). Specifies the cost method the system uses to calculate gain or loss amounts from the sale of foreign currency lots held by the entity. The system bypasses rollback and replay processing for same day cost of cash activity. The system processes open and close trades for the same date in the order in which the trades arrive. As a result, some close trades may be processed prior to open trades. The average cost close trades do not include the cost of open trades that have not been processed. This may result in small variances in gains and losses for entities processing average cash. There is no effect on IDLOT gains and losses. You cannot edit this field once the entity has holdings. Options include:
  –  Average. The system determines which foreign currency lot to relieve (sell) based on the value in the Lot Selection Method Cash field, which is always FIFO. After identifying the lot, the system determines the average of all of the holdings (total cost of holdings divided by the number of holdings) to calculate a gain or loss amount for reporting purposes.
  –  Identified. The system determines which foreign currency lot to relieve (sell) based on the value in the Lot Selection Method Cash field, which is always FIFO. After identifying the lot, the system determines its cost and compares that to the lot's earnings to calculate a gain or loss amount for reporting purposes.
• Account Base Currency (tag 86). Specifies the base currency of the entity. You cannot edit this field once the entity has holdings. You can set up the entity to report on more than one base currency if you add an additional accounting basis.
• Country of Tax Code (tag 1342). Specifies the ISO country code of the country in which the entity is located. The system uses the value in the Country of Tax Code field to calculate tax withholding and tax reclaim rates. The system uses the Country of Tax field to determine the applicable tax withholding and reclaim rates in the Global Tax table. The system provides the list of countries and their associated ISO country codes in the COUNTRY CODE code category as part of the installation upgrade process. If you enter a value in the Country of Tax Code field, the system fills in the Country of Tax field with its corresponding value. This option exists solely on the entity record and the value can be edited after the entity is established. The dynamic lookup is based on the COUNTRY CODE code category.
• Country of Tax (tag 1193). Specifies the name of the country in which the entity is domiciled. If you enter a value for the Country of Tax field, the system fills in the Country of Tax Code field with the corresponding value. The dynamic lookup is based on the COUNTRY CODE code category.
• Contract Settle Indicator (tag 3919). Specifies the settlement date the system uses when contractually settling trades and/or income. Options include:
  –  Contractual Settlement Date. The system settles the trades and/or income on the contractual settlement date.
  –  Contractual Settlement Date plus 1 Day. The system settles the trades and/or income items on the contractual settlement date plus one day.
• Contractual Cash Settlement Rule Name (tag 11833). Specifies the name of the Contract Cash Settlement Rule that the system uses to determine whether to settle trades through the contract cash process, based on the processing security type or security. You can add your own custom rules or you can select one of the default contract cash rules shown below.
  –  DEFAULTTRDINC. Settle both transactions and income for trades and corporate actions.
  –  DEFAULTTRDINCNOCA. Settle both transactions and income for trades but not for corporate actions.
  –  DEFAULTTRDONLY. Settle transactions, but not income, for trades and corporate actions.
  –  DEFAULTTRDONLYNOCA. Settle transactions, but not income, for trades but not corporate actions.
  –  DEFAULTINCONLY. Settle only income for transactions such as coupons and corporate actions.
  –  DEFAULTINCONLYNOCA. Settle only income for transactions such as coupons but not corporate actions.
  –  DEFAULTNONE. Settle neither transactions nor income for trades or corporate actions.
• Auto Settle Indicator (tag 58). Indicates whether the system settles trades, coupons, and miscellaneous income and expenses automatically. Options include:
  –  No. Default. The system does not automatically settle trades, coupons, and miscellaneous income and expenses. You must schedule the settlement for these transactions using the Contract Cash panel. Or, manually settle the transactions using the Multiple Manual Settlements panel. Eagle recommends that you set this field to No.
  –  Yes. The system automatically settles trades, coupons, and miscellaneous income and expenses. If you enter Yes, the system creates a settlement as soon as the trade is processed. There is no trade to settle date gain/loss. This applies even if the settlement date is in the future.
• Tech Short Eligible Indicator (tag 57). Indicates whether the entity can go technically short (book sell transactions prior to buys that will eventually be posted). Options include:
  –  Yes. Default. The system allows you to oversell, sell without a buy, and process a buy to cover without the short. Setting this field to Yes allows you to use the rollback and replay feature in Eagle's Accounting solution to adjust earnings. The system creates a negative long position (for an oversell or sell without a buy) or a negative short position (for a buy to cover without the short) and when the buy is received, the system replays that sell transaction. If you enter Yes, the system creates a settlement as soon as the trade is processed. There is no trade date to settle date gain/loss. This applies even if the settlement date is in the future.
  –  No. Recommended. The system does not allow you to oversell, sell without a buy, or process a buy to cover without the short. The system rejects the trade and sends it to the Workflow Manager to be reprocessed manually.
• Wash Sale Inhibit Indicator (tag 775). Indicates whether the system can apply the wash sale rule to trades. Options include:
  –  Yes. Default. The system does not apply the wash sale rule. The system records a loss on a sale of a security when you buy substantially identical securities within 30 days before or after the sale. If you select Yes, the system does not process wash sales, regardless of the value you specify for the Wash Sale Eligible Flag field on a trade panel.
  –  No. The system applies the wash sale rule. The system does not record a loss on a sale of a security when you buy substantially identical securities within 30 days before or after the sale. If you select No, the system uses the value you specify for the Wash Sale Eligible Flag field on the trade panel to determine whether to process wash sales.
• Earning Processing Frequency (tag 984). Displays the method the system uses to post earnings. The system supports only the Daily method.
• Chart of Account (tag 1641). Specifies the entity's chart of account to use in ledger reporting for the accounting basis. The system is installed with a core chart of accounts that contains more than 400 account numbers and descriptions. Custom chart of accounts are also available for each of the IFRS regulatory categories. You must select a value for this field even if you are not using the general ledger. The default field value is STAR. If you edit this value after the entity has holdings, the changes go into effect on the specified Regulatory Category Effective Date field value.
• Ledger Granularity Rule Name (tag 8939). Specifies the name of the ledger granularity rule associated with the entity/accounting basis. A ledger granularity rule allows you to customize both your core ledger posting for a breakout by holding term and your custom postings based on security master attributes as well as targeted securities.
• Ledger Granularity Rule (tag 8933). Displays the instance number associated with the Ledger Granularity Rule Name selected.
• Ledger Granularity Rule Effective Date (tag 155). Specifies the first date when transaction processing will apply the ledger granularity rule selected for the entity/accounting basis.
• Holding Term Method (tag 11479). Indicates whether the entity/accounting basis calculates the holding term for short term versus cash equivalent holdings at 90 days or at 3 months. If you use ledger granularity rules to customize your core ledger posting for a breakout by holding term, this option determines how Eagle Accounting calculates that holding term. This field appears after you select a ledger granularity rule. Options include:
  –  90 Days. When you use the system to calculate the holding term, it designates lots bought within 90 days to maturity as cash equivalent (CE) and designates lots bought within one year to maturity, taking leap years into account, as short term (ST).
  –  3 Months. Default. When you use the system to calculate the holding term, it designates lots bought within three months to maturity as cash equivalent (CE) and designates lots bought within one year to maturity, taking leap years into account, as short term (ST).
• Entity Status (tag 1283). Identifies the entity as active or inactive. Options include Active (Default) and Inactive. You can use the Change Entity Active Status panel to change the status.
• Short Term Price Method (tag 1872). Specifies how the system prices short term debt instruments. The system identifies a short term fixed income security if the period from Issue Date to Maturity Date is less than or equal to 365 days; it does not do so by Processing Security Type. Options include:
  –  Market. Default. The system prices the short term debt instruments using market prices rather than the amortized cost of the securities. Unrealized gain/loss entries are created.
  –  Cost. The system prices the short term debt instruments based on the amortized cost of the securities. No unrealized gain/loss entries are created. You must select a value of Cost if you are processing short term discount accruals.
• Accounting Period Frequency (tag 624). Specifies the number of accounting periods per calendar year for the entity. You cannot edit this field once the entity has holdings. Options include:
  –  Daily. Default. The system establishes one accounting period for each day of the year. If the entity is using a business calendar, the system establishes an accounting period for business days only.
  –  Monthly. The system establishes twelve accounting periods for a given year.
  –  Weekly. The system establishes one accounting period for each week of the year.
• Inception Date (tag 1138). Specifies the date the entity was created in the marketplace. Eagle's Performance solution uses this information. You cannot edit this field after you create the entity.
• STAR Start Date (tag 2198). Specifies the date the entity was set up in the system. The system calculates accounting periods based on the date range you enter in the STAR Start Date and Fiscal End Date fields. You cannot edit this field after you create the entity.
• Fiscal End Date (tag 1162). Specifies the last date of the entity's fiscal year, which the system uses as the ending date range when adding accounting periods. The system uses this field during the Year End Close process, an automated process that rolls up all balances from the realized gain/loss accounts and income and expense ledger accounts and posts the balances to the accumulated undistributed gain loss ledger account (3003000100). You cannot edit this field after you create the entity.
• Month End Date Rule (tag 5161). Determines whether the system uses the last calendar day or the last business day of the month as the monthly accounting date. If you select the month end date rule, the system uses the last calendar day of the month. However, if you select a business calendar from the Calendar Name field, the system uses the last business day of the month. The month end accounting date is stored on all transactions booked to Eagle's Accounting solution. This allows you to book as of activity in the current accounting period but reflect the transaction in the monthly period that it actually occurred in. This allows you to report these transactions in the correct month end report without having to reopen closed daily valuation and accounting periods. You can generate several ledger and subledger reports based on the month end accounting date. You can also create custom month end date rules using the Add Month End Date Rule panel. You cannot edit this field after you create the entity.
• Calendar Name (tag 1941). Specifies the name of the entity's business calendar, which is used to define a specific country's non-business days for accounting purposes. Business calendars are user defined and typically set up by your system administrator. If you select a business calendar, the system creates an accounting period for each business day of the year, as specified in the selected business calendar. The value you enter for the Calendar Name field must match the value you enter for the Country of Tax Code and Earn Thru Rule Name fields. For example, if you enter CA (Canada) for the Country of Tax Code field, you must also enter CA for Calendar Name and Earn Thru Rule Name fields. After you select a value, the Non Business Day Processing field and Earn Thru Rule Name field become available. If you do not select a business calendar, The system creates an accounting period for each day of the year, including non-business days. See the Manage Business Calendars section.
• Non Business Day Processing (tag 3907). Specifies how the system processes accrued interest on bonds or other fixed income securities on non-business days. This option appears when you select a value for the Calendar Name field and is required under that circumstance. Options include:
  –  Process with Previous Business Day. The system posts non-business day accruals to the previous business day's accounting date. For example, accrued interest for Saturday and Sunday is posted on Friday.
  –  Process with Next Business Day. The system posts non-business day accruals to the next business day's accounting date. For example, accrued interest for Saturday and Sunday is posted on Monday.
• Earn Thru Rule Name (tag 8954). Specifies how the system processes accrued interest when a series of non-business days fall on a month end, quarter end, semiannual, or year end date. This option appears when you select a value for the Calendar Name field and is required under that circumstance. The calendar associated with the Earn Through Rule must match the value you enter for the Country of Tax Code and Calendar Name fields. And the Earn Thru Rule Name you select must have a Non Business Day Processing value that matches that defined for the entity.
• Bifurcation Method (tag 5825). Specifies how the system handles gains and losses on foreign securities and foreign debt instruments. Gains and losses from foreign security and debt instruments may be posted to currency gain/loss ledger accounts, capital gain/loss ledger accounts, or to both. There is no currency gain/loss for domestic securities so you can select No in this field if your organization trades only in domestic securities. Options include:
  –  No. Default. The system does not bifurcate (split into parts) the gain/loss between capital and currency. The system posts the capital and currency realized gains/losses to the capital realized gain/loss general ledger accounts only.
  –  All. The system bifurcates (split into parts) the gain/loss between capital and currency regardless of the security type. The system posts the capital realized gains/losses to the capital realized gain/loss general ledger accounts and the currency realized gains/losses to the currency realized gain/loss general ledger accounts.
  –  Section 988. The system determines whether to bifurcate (split into parts) the gain/loss between capital and currency based on the security type. You need to specify which security types are eligible for section 988 bifurcation using the Add Code Value panel. If a security is not set up with a processing security type code, it is not eligible for bifurcation under Section 988. In this case, the system posts capital and currency realized gains/losses to the capital realized gain/loss general ledger accounts.
• TBA Cashflow (tag 9406). Specifies whether a TBA (to be announced) security functions as a buy or sell or nets the difference. Options include:
  –  No. Default. Do not create cash flows for the open of the TBA tax lot, but create the net cash flow at the close of the position.
  –  Yes. Create cash flows for the open of the TBA tax lot.
• Stale Factor Processing (tag 8141). Specifies whether the system automatically rolls back and replays stale factor trades when performing factor processing. Options include:
  –  No. Default. Do not cancel and rebook the original trade using the most recent factor.
  –  Yes. In the month the trade settles, cancel and rebook the original trade using the most recent factor.
• Swap Accrual Method (tag 1184). Specifies how the system posts interest accruals and dividends for swaps. Options include:
  –  Income/Expense. The system posts interest accruals and dividends to Income and Expense accounts in the general ledger.
  –  Unrealized. The system posts interest accruals and dividends to unrealized Capital accounts in the general ledger.
• Calendar Business Days (tag 824). Specifies whether the system spreads expenses over the weekends and holidays. It affects the Average Net Assets report. Options include:
  –  Calendar. The system spreads expenses over the weekends and holidays.
  –  Business. The system does not spread expenses over the weekends and holidays.
• Costcash Bulking Election (tag 2423). Specifies whether the costcash bulking option has been elected. Options include No (Default) and Yes.
• Manager Allocation (tag 2841). Specifies whether manager allocations apply to the fund. Options include No (Default) and Yes.
• Business Sector (tag 9512). Indicates the business sector associated with the entity.
• Pending Trade Eligible Indicator (tag 3679). Specifies whether transactions that originate upstream and are manually cancelled are placed in a Pending status. This stores the trade details in a table until a required event reads the table and selects the qualified transactions not yet processed by the system. Options include Yes and No.
• QDI Treaty Flag (tag 4487). Enables the use of the QDI Tax Treaty table for securities in the entity. QDI (qualified dividend income) is a category of dividend income that is taxable at lower rates than ordinary income under the Jobs and Growth Tax Relief Reconciliation Act of 2003. The Tax Relief, Unemployment Reauthorization, and Job Creation Act of 2010 extended the QDI expiration date through the end of 2012. QDI is defined as dividends received from domestic corporations and certain foreign corporations. Options include:
  –  Yes. Dividends with countries populated on the QDI Tax Treaty table are considered QDI eligible and the QDI Eligible Flag field (tag 2905) on the security master file is ignored. To add a country to the QDI Tax Treaty table, use the Insert QDI Tax Treaty panel. You can also use the Insert QDI Tax Treaty Exclusion panel to exclude specific securities from QDI eligibility.
  –  No. Default. The entity uses the QDI Eligible Flag field (tag 2905) on the security master file to determine QDI eligibility.

Conversion Fields

Anchor
ConversionFields ConversionFields

The following are the options for conversion fields:

• Conversion Status (tag 1085). Indicates the current status of the entity. The system allows you to select entities based on conversion status for certain types of global processing, such as corporate action announcements. The system is installed with a set of values for this field. After the conversion process is completed, the status is changed to parallel. After the parallel test phase is completed, the status is changed to live. You can add additional values using the Add Code Values panel for the CONVERT STATUS code category. Options include Converting, Live, and Parallel.
• Conversion Date (tag 3915). Specifies the date the entity was converted to the system.
• Live Date (tag 3916). Specifies the date the entity went live in the system. For reference only.

Source Fields

Anchor
SourceFields SourceFields

The following are the options for source fields:

• Long Price Source (tag 1282). Specifies the pricing source the system uses for pricing long security positions for the entity. The default is Eagle PACE.
• Short Price Source (tag 5422). Specifies the pricing source the system uses for pricing short positions for the entity. The default is Eagle PACE.
• FX Source (tag 1344). Specifies the pricing source the system uses for pricing foreign exchange rates for the entity. It is used for transactions and cash settlements. The default is Eagle PACE.
• Valuation FX Source (tag 11652). Specifies the pricing source the system uses for pricing foreign exchange rates for the entity. It is used for valuation; that is, calculating market value. The default is Eagle PACE.
• Forward Price Source (tag 2920). Specifies the pricing source the system uses for forward contract processing. It is used for multi basis entities where the base currencies of the bases are different. It is also used to allow entities that use the same price source for all other assets to elect different forward point sources for pricing forward contracts.
• Variable Rate Source (tag 3301). Specifies the source the system uses to process earnings for variable and floating rates. It is used for variable rate bonds with scheduled/unscheduled variable rates, floating rates, step coupon rates, and rates that measure inflation adjustment for the entity. The default is Eagle PACE.
• MTM Rate Source (tag 5064). Specifies the pricing source the system can use to mark foreign receivables to market. You can specify use of the MTM Rate Source or the FX Source (tag 1344) when you run the global mark to market process.

Accounting Basis

Anchor
AccountingBasis AccountingBasis

Earnings/Amortization Fields

Anchor
EarningsAmortizationFields EarningsAmortizationFields

The following are the options for earnings/amortization fields:

• Primary Amortization/Accretion Rule (tag 3197). Specifies the amortization/accretion rule for the primary accounting basis that the system uses to process earnings. You can set up amortization/accretion rules for IFRS that amortize average cost portfolios on an effective yield basis. If you change the Primary Amortization Rule at the accounting basis level, the next time you process earnings the system creates a retrospective amortization rule calculation from the original settlement date of the trade (on all open lots). The system calculates the trade yield based on the primary amortization/accretion rule for the entity, so it is important to keep the values that exist on the entity and the primary accounting basis consistent. The system updates values changed on the entity panel via the primary accounting basis, but does not change entity values when you make the change through the change accounting basis panel. See the Manage Amortization/Accretion Rules section for more information.
• Gain/Loss on Paydowns (tag 1871). Specifies how the system handles the gain/loss on paydowns (repayment of part of an outstanding loan balance). This field is used with factor based debt instruments such as mortgage backed securities. Options include:
  –  Gain/Loss. The system generates a gain/loss on a paydown and displays the Paydown Gain Loss Account field.
  –  Amortization. The system records a gain/loss generated by a paydown as accelerated amortization.
• Principal Loss on Paydown Processing Flag (tag 2925). Allows you to select the method in which to process the principal loss on a paydown. The system uses the Principal Loss Factor field (tag 2926) value specified for the final factor to process the principal loss. Options include:
  –  Realized Gain/Loss. Default. The system treats the portion of a paydown that is the result of a loss (write down) at a price of zero.
  –  Accelerated Amortization. The system reduces the cost of the position by the total reduction of shares. The offset to cost is accelerated amortization. This field is only allowed if the Gain/Loss on Paydowns field is set to Amortization.
  –  Share Adjustment. The system treats the portion of paydown that is a result of a loss (write down) as a share adjustment (increase or decrease) and does not adjust cost for the loss portion.
• Coupon Spreading Period (tag 637). Specifies how the system spreads income deferrals. Options include:
  –  None. Default. The system does not spread income deferrals.
  –  Coupon. The system spreads the daily income over the coupon period. This option is used primarily for mutual funds that distribute income daily, for bonds that are set up as 30/360, and for months that do not contain 30 days.
  –  Monthly. The system spreads daily income over the course of a month. A 30/360 bond defers a portion of its income for the 31st day of the month.
• Unrealized Gain/Loss Posting (tag 5383). Indicates whether the system automatically posts unrealized gains/losses to the ledger during valuation. Options include:
  –  Yes. Default. The system automatically posts unrealized gains/losses to the ledger during valuation. Select this value only if you are using Eagle's Pricing Center to post unrealized gains/losses.
  –  No. The system does not automatically post unrealized gains/losses during valuation. You must post them manually.
• Final Close Income Recognition Date (tag 10070). Specifies how the system recognizes closed earnings, amortization, and OID (Original Issue Discount) amortization. Options include:
  –  Settle Date. Default. The system recognizes closed earnings, amortization, and OID amortization on a daily basis through the settlement date of the close.
  –  Trade Date. The system recognizes closed earnings, amortization, and OID amortization as one lump sum on the trade date of the close.
• Coupon Cash Entitlement Level (tag 11852). Specifies the level at which the system drops coupons. Options include Position Level and Lot Level.
• Accrual Convention Offset (tag 12038). Specifies when the system begins earnings accruals. The method you select does not affect coupon payments because the number evens out on the last day and the coupon generated is the same. However, it does affect valuation and Eagle Performance calculations. You can use the Accrual Convention Offset Override field (tag 1604) to override this setting at the trade level for Buy Sellback/Sell Buyback trades. Options include:
  –  Settlement Date. Default. The system accrues through the day prior to a coupon payment and then begins accruing for the new coupon on the coupon pay date.
  –  Settlement Date + 1. The system begins earnings accruals using a one day lag. It accrues through the coupon date for the current period and pays it out that day, and then begins accruing for the new coupon on the coupon date plus one day so that the accrued income on the coupon date is zero. This method can apply to countries such as Canada.
• ILB Gain/Loss Flag (tag 3856). Indicates whether ILB (inflation linked bond) gain/loss at maturity is booked to income or gain/loss. Options include Maturity Gain/Loss and Daily Income and include Both Income.
• No Negative Income Flag (tag 3857). Determines whether the system allows no negative income at the entity/basis level for Identified Cost portfolios. This field appears if you set the Cost Method field to a value of Identified. Options include:
  –  Allow Negative Income. Default. The system recognizes negative income.
  –  Do Not Allow Negative Income. The system does not recognize negative income. The system uses the following calculation to determine if there is negative income: Total Income LTD = Accrual LTD + Amortization LTD + ILB LTD + OID LTD. If Total Income LTD is less than zero, ILB income, if it exists, and amortization are deferred until Total Income LTD reaches a value of 0 (zero).

Basis Processing Rule

Anchor
BasisProcessingRule BasisProcessingRule

The following are the options for basis processing rules:

• Basis Processing Rule Name (tag 7152). Specifies the name of the processing rule to use for the entity and accounting basis. This rule contains securities and the associated security processing rules to be used for accounting processing/treatment.
• Basis Processing Rule ID (tag 2965). Specifies the instance of the processing rule to be used for the entity and accounting basis.

Month End Fields

Anchor
MonthEndFields MonthEndFields

The following are the options for month end fields:

• Month End Processing Indicator (tag 9697). Indicates whether the accounting basis is using month end processing, which allows transactions to be reported in the correct month end report without having to reopen closed daily valuation and accounting periods. Options include Yes and No. If you select Yes, the Month End Long Price and Month End Short Price fields become available. If you set both this field and the Control Center Entity field to Yes, messages are sent to establish month end accounting periods, which is necessary to view funds in Control Center.
• Month End Long Price (tag 9676). Specifies the target pricing source used for month end valuation of long positions. This field appears when you set the Month End Processing Indicator field to Yes and is required under this circumstance.
• Month End Short Price (tag 9677). Specifies the target pricing source used for month end valuation of short positions. This field appears when you set the Month End Processing Indicator field to Yes and is required under this circumstance.

Other Information Fields

Anchor
OtherInformationFields OtherInformationFields

The following are the options for other information fields:

• Tax ID Number (tag 1341). Specifies the tax identification number for the entity. You can enter up to 10 characters. For reference only.
• Manager ID (tag 1149). Specifies the identification number of the entity manager. For reference only.
• Inception Value (tag 1160). Specifies the monetary value of the entity at the inception date. For reference only.
• Termination Date (tag 1161). Indicates the date by which an entity should no longer be included in GIPS composites.

S2P Direct Interface Fields

Anchor
S2PDirectInterfaceFields S2PDirectInterfaceFields

The following are the options for STAR to PACE Direct interface fields:

• Delta Process Flag (tag 4758). Indicates whether the entity's backdated transactions and affected position records are transferred from STAR to PACE for reporting purposes using the STAR to PACE Direct Interface. Options include:
  –  No. Default. The system does not use the STAR to PACE Direct to transfer an entity's open positions and cash balances.
  –  Yes. The system uses the STAR to PACE Direct to transfer an entity's open positions and cash balances.
• Create Performance Cash Flows in PACE (tag 5398). Indicates whether the STAR/PACE integration procedure processes cash currency and copies cash flow information for reporting by Eagle's Performance solution. Options include:
  –  No. Default. The STAR/PACE integration procedure does not create cash currency records for performance reporting. If you do not use Eagle Performance, select No.
  –  Yes. The STAR/PACE integration procedure creates cash currency records for performance reporting. If you use Eagle Performance, select Yes.
• Store Cash Positions in PACE (tag 5563). Indicates whether the STAR/PACE integration procedure exports the entity's cash positions from STAR to PACE. Options include:
  –  No. Default. The STAR/PACE integration procedure does not export cash position records from STAR to PACE. If your organization does not need currency balances, select this value to improve efficiency.
  –  Yes. The STAR/PACE integration procedure exports the cash position records from STAR to PACE and stores the cash balances in the position detail table in the PACE data warehouse. If you use Eagle Performance, select Yes.
• Value at Cost - No Price Found (tag 11454). Specifies whether to use the cost value when no price is found for the selected entity/accounting basis. This setting does not affect futures contracts market values. If you run STAR to PACE Direct in Batch mode using the Recent price option (that is, you set the Price Date Switch option to Recent in the Transfer Data - Batch panel), be aware that any recent price is used before the asset is priced at cost. Options include:
  –  Yes. Use cost value. If no price is found, STAR to PACE Direct defaults the amortized cost into the PACE market value fields in the position detail and lot level position tables.
  –  No. Do not use cost value. Use the default value of 0. The amortized cost is not used even if there is no pricing available.

Portfolio Turnover

Anchor
PortfolioTurnover PortfolioTurnover

The following are the options for portfolio turnover:

Process Center Fields

Anchor
ProcessCenterFields ProcessCenterFields

The following are the options for Process Center fields:

• Process Center (tag 4896). Specifies the entity's process center. A process center allows you to group entities into centers to control the timing of global processes, such as accruals, corporate action processing, maturities, contractual cash settlements, and STAR to PACE Direct processes. If specified, the system uses the date associated with the process center as the post date on all transactions. Eagle strongly recommends the use of process centers.

Control Center

Anchor
ControlCenter ControlCenter

The following are the options for Control Center:

• Control Center Entity (tag 10462). Indicates if you can view an entity's status using the Control Center. The Control Center allows you to view entity statuses for all system events in real time. The Control Center provides a central location for applying business edits, reviewing and controlling transactions, and performing valuations and audits of entities. Options include:
  –  No. Default. The system does not allow you to view the entity status using the Control Center.
  –  Yes. The system allows you to view the entity status using the Control Center. All edit test procedures check this flag to ensure the fund is set up as a Control Center fund. If you select Yes, additional fields in this section become available.
• Trading Gain/Loss Rule Id (tag 9231). Specifies the trading gain/loss rule for the entity. The trading gain/loss process determines the impact of a trade by comparing a transaction's trade price to the prior market price. This field is required if you set Control Center Entity to Yes. Options include:
  –  DEFAULT INCLUDE. Tests new purchases by using the current day market exchange price.
  –  DEFAULT EXCLUDE. Does not post trading gain/loss for new security purchases.
  –  DEACTIVATE.
• Control Center Entity Tests (tag 2297). Specifies how you assign edit tests during fund setup. This field appears when you set Control Center Entity to Yes and is required under this circumstance. Options include:
  –  Core. Attaches out of the box edit tests upon fund setup through the ADD_CC_TEST_FOR_START_ENTITY procedure.
  –  Non-Core. Adds customized edit tests to funds during the fund setup process.
  –  None. Assigns edit tests in the module after establishing them. Assigning edit tests at the composite level (not fund level) is easier to maintain.
• Control Center Process Center (tag 11407). Specifies the Control Center Process Center code for the entity. The Control Center uses this code for queries and processes that push edit test result data to the Status Map tables. This field is appears when you set Control Center Entity to Yes and is required under this circumstance.
• Control Center Daily Map (tag 3975). Specifies the daily Control Center status map used for the entity. This field appears when you set the Control Center Entity field to Yes.
• Control Center Monthly Map (tag 80). Specifies the month end Control Center status map used for the entity. This field appears when you set the Month End Processing Indicator field (tag 9697) to Yes and you set the Control Center Entity field to Yes.

Accrue Cash Balance Fields

Anchor
AccrueCashBalanceFields AccrueCashBalanceFields

The following are the options for accrue cash balance fields:

Tax Fields

Anchor
TaxFields TaxFields

The following are the options for tax fields:

• Taxable Indicator (tag 1143). Indicates whether the entity is taxable. For reference only. Options include No (Default) and Yes.
• Accrue Interest Tax Indicator (tag 3911). Indicates whether the system accrues interest for tax withholding and reclaims. Options include:
  –  No. The system does not accrue interest for tax withholdings and reclaims on a daily basis. Instead, tax withholdings and reclaims are calculated on the coupon payment date.
  –  Yes. The system accrues interest for tax withholdings and reclaims on a daily basis. If you select Yes, you cannot set the Tax Accounting Method field to Gross Income because the Gross Income method ignores all withholding tax on dividends and coupons.
• Tax Accounting Method (tag 3912). Specifies how the system processes tax withholdings and reclaims on dividends and other interest transactions. Options include:
  –  Gross Income Method. Default. The system ignores any withholding tax on dividends or coupon entitlements, even if applicable tax rates are set up in tax tables, and tax reclaim will not process. The gross amount of the dividend or coupon entitlement is posted as a receivable. The receivable is then relieved against the cash receipt on the coupon or dividend pay date. You cannot select this value if you set the Accrue Interest Tax Indicator field (tag 3911) to Yes.
  –  Gross Liability Method. The system generates both a receivable and a payable amount for the withholding tax. A receivable is created at the gross amount of the dividend or coupon entitlement less the amount of the reclaim. A separate receivable is created for the reclaim amount, if any. A payable is also created for the unrecoverable tax amount (tax expense). The system relieves both the payable and receivable against the cash receipt on the coupon or dividend pay date.
  –  Net Method. The system generates a receivable at the net income amount (gross income less withholding tax) and a separate receivable for the reclaim amount, if any. The payable for the tax expense is not created.
• Entity Tax Type (tag 3929). Defines the entity's tax status and allows you to group entities for tax accounting purposes. The system uses this value to calculate tax withholding and tax reclaim rates. You can group entities by entity tax type, entity tax qualifier, or both. Options for this field are user defined. The system is installed with a set of values for this field. You can add additional values for this field using the Add Code Value panel for the ENTITY TAX TYPE code category.
• Entity Tax Qualifier (tag 3930). Defines the entity's tax status and allows you to group entities for tax reporting purposes. The system uses this value field to calculate tax withholding and tax reclaim rates. You can group entities by entity tax type, entity tax qualifier, or by both. Options for this field are user defined. The system is installed with a set of values for this field. You can add additional values for this field using the Add Code Value panel for the ETAX QUALIFIER code category.
• Tax Exempt Processing Flag (tag 4948). Determines whether income is posted to taxable or tax exempt general ledger accounts. This field works with the Tax Exempt Indicator field (tag 1545), which exists at the security level. The Tax Exempt Processing Flag field impacts the Net Investment Income (NII) process when calculating the mixed expense taxable allocation percentage. If this field set to Yes, the net distributable income is processed against tax exempt income and expenses. Options include:
  –  Yes. If the security level Tax Exempt Indicator field is also set to Yes, the system posts the income to tax exempt general ledger accounts. If the security level Tax Exempt Indicator field is set to No, the system posts income to taxable general ledger accounts.
  –  No. If the security level Tax Exempt Indicator field is set to Yes, the system posts the income to taxable general ledger accounts. If the security level Tax Exempt Indicator field is set to No, the system posts the income to taxable general ledger accounts.

Corporate Action Fields

Anchor
CorporateActionFields CorporateActionFields

The following are the options for corporate action fields:

• Cost Allocation Indicator For Rights Issues (tag 3917). Identifies the cost allocation for rights issues. If you do not select a value, the system uses Allocate Cost as the default. Options include:
  –  Allocate Cost. Default. The system allocates a percentage of the cost of the original security to the rights issue.
  –  Do Not Allocate Cost. The system does not allocate a percentage of the cost of the original security to the rights issue.
  –  Calculate 15 Rule. The system determines whether to allocate cost to the rights issue based on the market value. If the market value of the rights issue is more than 15% of the cost of the original security, the cost is allocated to the rights issue. If the market value of the rights issue is less than 15% of the cost of the original security, the cost is not allocated to the rights issue.
• Treatment of Fractional Shares Override (tag 8251). Specifies how the system treats fractional shares. A fractional share is less than a single share of stock. It often results from stock splits, stock dividends and similar corporate action events. The value in this field overrides the fractional shares value on corporate action announcement panels. Options include:
  –  Round Down. The system rounds the fractional share entitlement down to zero decimals. No fractional shares are created.
  –  Post Fractional Shares. The system posts the fractional share entitlement, calculating the amount to two decimal places.
  –  Round Up. The system rounds the fractional share entitlement up to the next whole number. No fractional shares are created.
  –  European. The system calculates the fractional share entitlement as follows: 1. Divides the position by the divisor, 2. Drops the decimals on the number that is calculated, 3. Multiplies the whole number by the multiplier.
  –  Round to Nearest Whole Share. The system rounds the fractional shares to the nearest number of whole shares. If the calculated entitlement is greater than or equal to 0.50, the system rounds the fractional shares up to the next whole share. If the calculated entitlement is less than or equal to 0.49, the system drops the fractional shares.
• Corporation Action FX Rule (tag 9705). Specifies the foreign exchange rate that the system uses for posting corporate actions. Options include:
  –  Recent. The system uses the trade date exchange rate if available. Otherwise, it uses the most recent exchange rate.
  –  Actual. The system retrieves only the exchange rate for the trade date. It rejects the transaction if no exchange rate is found.
• Awarded Rights Expiration Rule (tag 9921). Specifies how the system handles the treatment of loss generated by the expiration of a right or warrant. Options include:
  –  Loss. Default. The system applies the loss generated by the expiration of a right or warrant to the right or warrant.
  –  Transfer. The system applies the loss generated by the expiration of a right or warrant to the original security.
• Cash Div Cash Entitlement Level (tag 9922). Specifies whether to use lots or positions to determine cash entitlements for cash dividends. Options include:
  –  Position. Default. The system uses positions to determine cash entitlements for cash dividends.
  –  Lot. Default. The system uses lots to determine cash entitlements for cash dividends.
• Cash Dividend Distribution (tag 3928). Specifies whether cash dividends are paid for corporate actions. It is used for Fund of Funds Distributions. Options include No and Yes.
• Non Tax Merger Close Method (tag 11495). Specifies the method to use to close lots on the original security for non-taxable mergers. Options include:
  –  Pro-Rata Method. Default. The system closes a portion of all lots, ignoring lot selection methods.
  –  Lot Selection Method. The system selects lots to close based on the lot selection method found on the accounting basis.
• Rights and Warrants Expire Delay Days (tag 4605). Specifies the number of days to delay the expiration of rights and warrants, allowing you to delay the maturity processing of rights and warrants. The default is 0 (zero days).
• Limit Gain Loss Eligible (tag 2487). Determines if gain loss processing occurs for corporate actions for certain cash/stock mergers. Requires the Limit Gain Loss Indicator field (tag 8553) to be set to Yes on the corporate actions panel to be in effect. When applicable, at the lot level, the gain associated with these mergers is the lesser of the cash amount or the gain to be recognized had the entire transaction been taxable. If the result is a loss, it is disallowed. The disallowed component is then treated as a return of capital. In the case of certain taxable mergers, any loss that is generated at the lot level is disallowed. There are U.S. tax provisions that limit the amount of reportable gains and losses for certain mergers with taxable components. Options include:
  –  No. No gain loss processing for corporate actions.
  –  Yes. Gain loss processing occurs for nontaxable mergers with taxable cash. For taxable mergers, gain/loss rules are used for the calculation of losses only.

Settlement Fields

Anchor
SettlementFields SettlementFields

Period Close Fields

Anchor
PeriodCloseFields PeriodCloseFields

The following are the options for period close fields:

• Accounting Period Rule (tag 2300). Specifies the criteria that the system uses to identify period close rules for the entity. A period close rule determines how the system assigns accounting dates when it processes transactions. See the Manage Accounting Period Close Rules section for details. Options include:
  –  Entity/Security Type/Message Type/Event Type. Uses period close rules for all business transactions for the entity that have a specified security type, message type, and event type.
  –  Entity/Security Type. Uses period close rules for all business transactions for the entity that have a specified security type.
  –  Entity. Uses period close rules for all business transactions for the entity.
  –  Entity Group/Security Type/Message Type/Event Type. Uses period close rules for all business transactions for a set of entities that belong to a group, and have a specified security type, message type, and event type. If you select this option, the Accounting Date Rule Group field becomes available.
  –  Entity Group/Security Type. Uses period close rules for all business transactions for a set of entities that belong to a group and have a specified security type. If you select this option, the Accounting Date Rule Group field becomes available.
  –  Entity Group. Uses period close rules for all business transactions for a set of entities that belong to a group. If you select this option, the Accounting Date Rule Group field becomes available.
  –  System Default. Default. Uses period close rules for all business transactions for all entities.
• Accounting Date Rule Group (tag 4303). Specifies the accounting date rule group for the entity. An accounting date rule group identifies a set of entities for which you define period close rules applied across a group of funds. An entity can belong to only one accounting date rule group. This field appears if you set the Accounting Period Rule field to a value of Entity Group/Security Type/Message Type/Event Type, Entity Group/Security Type, or Entity Group. You can add additional values using the Add Code Values panel for the PERIOD CLOSE GR code category under the source Eagle PACE.

Forward Fields

Anchor
ForwardFields ForwardFields

The following are the options for forward fields:

• Forward Position By Broker (tag 3913). Indicates whether to use the broker code to distinguish forward contracts made with a different broker but the same two currencies and maturity date. Options include:
  –  Yes. The system uses the broker code. If the broker is unique on each transaction, the system creates a new security master record for each forward trade with the same sell/buy currency and maturity date.
  –  No. The system does not use the broker code. The system does not create a new security master record for each forward trade with the same sell/buy currency and maturity date.
• Forward Close Eligible (tag 3924). Indicates whether the entity allows closes of forward contracts. Options include:
  –  Yes. The system allows closes of forward contracts prior to maturity. It closes open forward contracts by offsetting forward contracts.
  –  No. The system holds all forward contracts until maturity. It records separate long and short positions for offsetting forward contracts.
• Forward Settlement Currency (tag 3926). Specifies the settlement currency to use for closing a forward contract. The system creates receivable records and payable records based on the value in this field.
• Forward Security Exists (tag 675). Indicates whether you must add the forward contract to the security master file prior to booking a forward trade. A forward contract is a type of foreign exchange transaction whereby a contract is made to exchange one currency for another at a fixed date in the future at a specified exchange rate. Options include:
  –  Yes. You must add the forward contract to the security master file prior to booking a forward trade.
  –  No. You do not need to add the forward contract to the security master file prior to booking a forward trade. The system creates two security master records, one for each leg of the forward contract, when you book the trade.

Futures Fields

Anchor
FuturesFields FuturesFields

The following are the options for futures fields:

• Net Futures Positions (tag 632). Indicates whether you can book short future trades. Options include:
  –  Yes. The system does not allow you to book short future trades. All futures transactions are processed in one net position by the clearing broker.
  –  No. The system allows you to book short future trades. This value allows an entity to be long and short in one futures position. If this field is set to No, you cannot book open or close short future trades.
• Futures Clearing Broker Code (tag 634). Specifies a clearing broker code for settling variation margins. You can override this field by adding a value in the Clearing Broker Code field on the futures trade panels.
• Future Cost Ledger Method (tag 641). Specifies how the system records the futures cost in the general ledger. Options include:
  –  Core. Default. The system posts a variation margin. No cost is recorded for the future transaction and commission is included as part of the cost and not paid out separately.
  –  UK. The system posts an unrealized gain loss. The system records the cost of the futures and commissions are paid right away.

Options Fields

Anchor
OptionsFields OptionsFields

The following are the options for options fields:

Caps/Floors Fields

Anchor
CapsFloorsFields CapsFloorsFields

The following are the options for caps/floors fields:

• Net Cap Floor (tag 5830). Determines how the system processes caps/floors. Options include:
  –  Yes. The system nets a buy and sell of a cap/floor on the same entity into a single position.
  –  No. The system treats a buy and sell of a cap/floor on the same entity as two separate positions.

Entity Level Engine Routing

Anchor
EntityLevelEngineRouting EntityLevelEngineRouting

The following are the options for entity level engine routing:

• Entity Engine Number (tag 4623). Specifies the engine number code value.
• Entity Engine Description (tag 7025). Specifies the entity engine description.

Partition Assignment

Anchor
PartitionAssignment PartitionAssignment

The following are the options for partition assignment:

• Entity Partition (tag 1334). Specifies the segment of the database where you store the entity transactions. Entity partitioning is used for strategic high volume clients that require partitioning of the ESTAR database schema. Eagle clients that do not use partitioning use the default value of 1.