Create Master Fund Panel Options

Master Fund Identification

Master Fund ID

1163

Specifies the unique identifier of the master fund entity. It must not contain any blank spaces.

Master Fund Long Name

29

Specifies the full name of the master fund entity.

Master Fund Name

1164

Specifies the abbreviated name of the master fund entity.

Master Fund Code

4324

Specifies the entity code of the master fund entity.

Master Fund Legal Name

1859

Specifies the legal name of the master fund entity.

Master Fund Type

3953

Identifies the type of master fund. The system uses this value for certain Control Center edits and in dilution and mil rate processing. Options include:

• Benchmark. Benchmark.

• IT. Institutional and Trustee.

• MF. Mutual Fund.

• MM. Money Market.

• OFFSHORE. Off Shore.

Money Market Type

16560

Identifies the type of money market fund for the master fund. The option you select does not affect processing. This field appears if you set the Master Fund Type field to a value of Money Market (MM). Options include:

• CNAV (Constant Net Asset Value Fund)

• IMMM (Institutional Municipal Money Market)

• IPMM (Institutional Prime Money Market)

• LVNAV (Low Volatility Net Asset Value Fund)

• VNAV (Variable Net Asset Value Fund)

Master Fund Alias

1333

Specifies the master fund entity alias.

Effective Date

1109

Specifies the effective date of the master fund entity. The default is today's date.

Legal Entity Identifier (LEI)

5089

Specifies the Legal Entity Identifier (LEI) that identifies the mutual fund as a financial party. When you enter an LEI value, the system unhides the Legal Entity Identifier Details section for data entry.

NOTE: If the LEI already exists, the LEI details appear.

Nav Election

16559

Indicates if the selected master fund entity uses daily or intraday NAV processing. Options include: 

• Intraday. The master fund is eligible for intraday NAV processing. In the Allocation Fields section, you can select an intraday NAV processing rule. 

• Daily. Default. The master fund is not eligible for intraday NAV processing.

Open/Closed-end Fund

1855

Indicates whether the entity is an open-end or closed-end fund. Options include:

• Open

• Closed

Preferred Shares Processing

16858

Indicates whether the master fund is eligible for preferred shares processing. This field appears if you set the Open/Closed-end Fund field to a value of Closed. Options include: 

• Yes. The fund is eligible for preferred shares processing. If you select Yes, under Fund Distribution Fields, the Daily Distribution Method field displays a value of Preferred Stock Distributions. Under Allocation Fields, the panel hides the Class Allocation Rule and the Sector Allocation Rule fields.  

• No. The fund is not eligible for preferred shares processing.

Legal Entity Identifier Details

Legal Name 

5090

Specifies the legal name of the mutual fund as the financial party registered with the LEI.

Entity Status

5091

Specifies the status of the mutual fund. For example, ACTIVE and INACTIVE.

Legal Form

5092

Specifies the legal form of the mutual fund as financial party registered with the LEI. For example, CORPORATION.

Assigned Date

5093

Specifies the date when the mutual fund's LEI was assigned.

Last Update Date

5094

Specifies the date when the mutual fund's LEI information was last updated.

Disabled Date

5095

Specifies the date when the mutual fund's LEI information was disabled.

Record State

5096

Specifies the record state for the mutual fund'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

5097

Specifies the certification state used to register the mutual fund's LEI. For example, CERTIFIED, NOT_CERTIFIED, STALE.

Street

5098

Specifies the street address used to register the mutual fund's LEI.

City

5099

Specifies the city used to register the mutual fund's LEI.

State

5100

Specifies the state code used to register the mutual fund's LEI.

Zip

5180

Specifies the ZIP code used to register the mutual fund's LEI.

Country Code

5181

Specifies the country code used to register the mutual fund's LEI.

Ultimate Parent Company

17930

Specifies the company that is at the top of the corporate structure. 

Validation Sources

17931

Specifies the level of validation of the reference data provided by the registrant.

Next Renewal Date

17932

Specifies the date when the Registration Status of the LEI record will be set to LAPSED, unless the Renewal process is completed.

Master Feeder Fund Structures

Master/Feeder Fund Relationship

2201

Indicates if the master fund is part of a master feeder fund structure. You can create a master and feeder fund relationship and use that relationship to allocate income, expense, realized and unrealized gains and losses from the master fund to the feeder fund. This fund structure allows you to consolidate multiple portfolios into one. This consolidation allows advisers to reduce their trading and operating cost. Options include: 

• Yes. The master fund is part of a master feeder fund structure. 

• No. Default. The master fund is not part of a master feeder fund structure. 

Master/Feeder Fund Type

16618

Indicates whether the master fund is a master feeder fund or a feeder fund if you use it within a master feeder fund structure. This field appears if you set the Master/Feeder Fund Relationship field to a value of Yes. Options include: 

• Master Feeder Fund. The master fund is a master feeder fund. If you select this value, you must identify a master feeder fund allocation rule in the Allocation Fields area. 

• Feeder Fund. The master fund is a feeder fund. 

Fund to Fund/Underlying Fund Identification

Automatic Reinvestment of Daily Distribution

11957

Determines whether to automate the reinvestment of daily distributions for the top level fund. A top level fund, which holds an underlying fund, can itself be held by another fund. Options include No (Default) and Yes.

Automatic Reinvestment of Periodic Distribution

11958

Determines whether to automate the reinvestment of periodic distributions for the top level fund. Options include No (Default) and Yes.

TF Held as Security

10599

Determines whether the fund is a single class fund. Options include No (Default) and Yes. If you select Yes, the TF NAV Price Precision field and the TF Fund Primary Asset ID field appear.

TF NAV Price Precision

10600

Specifies the number of digits for the NAV precision. This option is required if you set TF Held as Security to Yes.

TF Fund Primary Asset ID

1348

Specifies the security identifier of the security representing the fund. For example, EQEQMF for funds making period distributions and DBMFDD for funds making daily distributions. This option is required if you set TF Held as Security to Yes.

Core Accounting Fields

Primary Accounting Basis

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 code values using the Codes workspace. 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

4949

Indicates whether the selected accounting basis is the entity's controlling basis for use with for same lot selection. Same lot selection allows the system to relieve the same lots across multiple bases in order to keep lots in sync across bases. Options include:

• Yes. Indicates that the accounting basis identified in the Primary Accounting Basis field (tag 21) is the entity's controlling basis. The controlling basis is the accounting basis that controls lot selection for closing transactions. An entity can have a single controlling basis. You can designate a primary or a non primary basis as the controlling basis. 

• No. Indicates that the accounting basis identified in the Primary Accounting Basis field (tag 21) is a non-controlling basis for the entity during same lot selection. A non-controlling basis attempts to close the same lots that the controlling basis closed. An entity can have one or more non-controlling bases.

• Empty. Indicates that the accounting basis identified in the Primary Accounting Basis field (tag 21) does not participate in same lot selection.

Regulatory Category

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

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

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. For more information, see Manage URGL Rules. 

ECL Method

18053

Identifies the Expected Credit Losses (ECL) method used with Expected Credit Losses when you use US GAAP OR IFRS. The system assigns the ECL method based on the regulatory category you select, and you cannot change it. Values include:

• Non-US Treatment. Identifies an accounting basis that follows IFRS regulatory treatments for Expected Credit Losses. This value appears if you set the Regulatory Category to AC (Amortized Cost) or FVOCI (Fair Value - Other Comprehensive Income).

• US Treatment. Identifies an accounting basis that follows US GAAP regulatory treatments for Expected Credit Losses. This value appears if you set the Regulatory Category to AFS (Available for Sale or HTM (Held to Maturity).

Netting Rule Name

1887

Specifies the netting rule used to net interest rate swaps' and credit index swaps' long and short positions with the same primary asset ID. This allows you to book swaps long and short rather than as opens and closes. This rule gives you the option to net interest rate swaps' and credit index swaps' long and short positions and consolidate multiple lots into one lot when you use the global Run Swap Netting process.

Primary Accounting Basis Postmatrix Type

11708

Specifies which ledger posting matrix the entity/primary accounting basis uses when determining the accounting ledger postings required for a given event. Options include:

• Core. Default. Used if entity is an investment or mutual fund.

• Insurance. Used if entity is insurance related (Schedule D).

Primary Accounting Basis Lot Selection Rule

2299

Relieves the current holdings of a security for a primary accounting basis. This option determines processing for the open lots that are eligible to be closed on an additional accounting basis. Options include:

• Use Basis Value Unless Event = IDLOT or VSP. Default. The system uses the value in the accounting basis table unless the incoming event has a lot selection method of Identified Lot (IDLOT) or Versus Purchase (VSP).

• Use Event Value. The system uses the lot selection method from the incoming event and does not utilize the lot selection method in the accounting basis table.

• Always Use Basis Value. The system uses the accounting basis default regardless of what lot selection method is on the incoming event.

• Use Historical Method Unless Event ID = IDLOT or VSP else use event. The system uses the historical lot selection method on the accounting basis unless the lot selection method on the incoming event is equal to Identified Lot (IDLOT) or Versus Purchase (VSP).

Primary Accounting Basis Mixed Cost Basis Indicator

11664

Determines if the entity/primary accounting basis uses a mixed cost basis. A mixed cost basis allows you to override the entity's accounting basis level elections for the cost method, lot selection method, and lot selection method rule used during transaction processing. You can define mixed cost basis rules based on transaction criteria that includes processing security type (PST) group, processing security type, security type, cost basis rule type, and asset ID, as well as by using each of these criteria in combination with a specified entity. For more information, see Manage Mixed Cost Basis Rules. This field appears in the accounting basis entry panels as the Mixed Cost Basis Indicator (tag 11664) field. Options include:

• Yes. The entity/primary accounting basis uses a mixed cost basis. The Primary Basis Mixed Cost Basis Rule Name field becomes available.

• No. Default. The entity/primary accounting basis does not use a mixed cost basis. 

Primary Accounting Basis Mixed Cost Basis Rule Name

11666

Specifies the name of the mixed cost basis rule to use for the entity's primary accounting basis. This option appears if you set the Primary Basis Mixed Cost Basis Indicator field to Yes.

Cost Method

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. For more information, see Manage Amortization and Yield Calculations.

• 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. For Average Cost portfolios, Eagle Accounting supports only certain amortization methods. For more information, see Understand Average Cost Amortization.

Eagle Accounting supports the cost basis legislation regulations included in the Emergency Economic Stabilization Act of 2008. These regulations, which apply to various types of securities, affect debt securities and options posted on or after January 1, 2013. If a portfolio follows these mandatory guidelines, you must perform additional setup tasks to enable cost basis reporting. For information about enabling cost basis reporting, adding rules for covered and uncovered securities, defining mixed cost basis rules to override your basis level elections for the cost basis method, and information about changing cost methods, see the Cost Basis Legislation Quick Reference Guide.

Lot Selection Method

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. 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.

• Tax Service. (For future use)

Cost Method Cash

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. You cannot edit this field once the entity has holdings. 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 ID lot gains and losses. Options include:

• 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.

• 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.

Account Base Currency

86

Specifies the base currency of the entity. You cannot edit this field once the entity has holdings. You can set up the master fund to report on more than one base currency if you add an additional accounting basis.

Country of Tax Code

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 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 under source Eagle PACE. For more information, see Manage Tax Withholding and Reclaim Processing.

Country of Tax 

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 system uses this option as a working storage field to reconcile the Country of Tax Code field. This field is not stored in the Eagle Accounting database. The dynamic lookup is based on the COUNTRY CODE code category.

Tech Short Eligible Indicator 

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 system's rollback and replay feature 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.

• No. 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 Exceptions workspace to be reprocessed manually.

Wash Sale Inhibit Indicator

775

Indicates whether the system can apply the wash sale rule to trades. Options include:

• No. Default. 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.

• Yes. 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.

Chart of Account

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

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

8933

Displays the instance number associated with the Ledger Granularity Rule Name selected.

Ledger Granularity Rule Effective Date

155

Specifies the first date when transaction processing will apply the ledger granularity rule selected for the entity/accounting basis.

Holding Term Method

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 the system 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

1283

Identifies the entity as active or inactive. You can use the Change Entity Active Status panel to change the status. Options include:

• Active. Default. The system reports the entity as active.

• Inactive. The system reports the entity as inactive.

Short Term Price Method

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:

• 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 Cost if you are processing short term discount accruals.

• 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.

Price Level

12007

Identifies the default price level that the system uses if the entity prices short term fixed income securities priced at amortized cost. This field appears if you set the Short Term Price Method to Cost. The field displays a value of 1 by default, but you can change it to a value of 1, 2, or 3. Eagle Accounting uses the price level in Fair Value Level reporting.

Accounting Period Frequency

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.

Week End Day

1943

Specifies the week end day for the accounting period. This field appears if you set the Accounting Period Frequency field to Weekly. Options include:

• MONDAY

• TUESDAY

• WEDNESDAY

• THURSDAY

• FRIDAY

• SATURDAY

• SUNDAY

Bifurcation Method

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. For more information, see Understand the Bifurcation Method. Options include:

• Section 988. Default. 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 Codes workspace. 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.

• No. 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.

TBA Cashflow

9406

Specifies whether a To Be Announced (TBA) security functions as a buy or sell or nets the difference. For more information, see Understand To Be Announced (TBA) Trades. Options include:

• Yes. Create cash flows for the open of the TBA tax lot using cost.

• 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.

TBA Netting

18577

Specifies whether long and short TBA trades are held as separate positions or netted into a single position. For more information, see Understand To Be Announced (TBA) Trades. Options include:

• Yes. Long and short trades are netted into a single long position, with short positions represented by negative units. A single trade can take a position from long to short, or vice versa.

• No. Long and short trades generate separate positions, similar to equities and most other fixed income securities. A long open must be closed by a long close and a short open must be closed by a short close. Two trades are required to take a position from long to short, or vice versa: one to close out the open position and another to open the new position in the opposite direction.

Stale Factor Processing

8141

Specifies whether the system automatically rolls back and replays stale factor trades when performing factor processing. For more information, see About Stale Factor Processing. Options include:

• Yes. In the month the trade settles, cancel and rebook the original trade using the most recent factor.

• No. Default. Do not cancel and rebook the original trade using the most recent factor.

Swap Accrual Method

1184

Specifies how entities post interest accruals and dividends for swaps. Options include:

• Income/Expense. Posts interest accruals and dividends to Income and Expense accounts in the general ledger.

• Unrealized. Posts interest accruals and dividends to unrealized Capital accounts in the general ledger.

Calendar Business Days

824

Specifies whether the fund spreads expenses over the weekends and holidays. It affects the Average Net Assets report. Options include:

• Calendar. Default. Fund spreads expenses over the weekends and holidays.

• Business. Fund does not spread expenses over the weekends and holidays.

Expense & Capitalize Trans Costs for Opens & Closes

10705

Determines if transaction fees are expensed or capitalized for acquisitions, and if transaction fees are expensed or netted against proceeds for dispositions. This option supports International Financial Reporting Standards (IFRS) requirements for trades and transaction fees. You cannot edit this field once the entity has holdings. The following trade related fees are considered transaction fees: Commission field (tag 47), SEC Fee field (tag 48), Tax field (tag 46), Stamp Duty Tax field (tag 51), Other Fee field (tag 3752). The Federal Tax Withholding field (tag 8078) and State Tax Withholding field (tag 8079) are not considered transaction fees. Options include:

• Capitalize Trans Fees on Opens & Net Trans Fees Against Proceeds on Closes

• Expense Trans Fees on Opens & Net Trans Fees Against Proceeds on Closes

• Expense Trans Fees on Open and Close Trades

Costcash Bulking Election

2423

Specifies whether the entity uses COSTCASH bulking when you use COSTCASH processing to track foreign currency positions. COSTCASH bulking bulks or consolidates rows in the COSTCASH object to reduce the amount of data stored. Options include:

• No. If the entity uses COSTCASH processing, it does not use COSTCASH bulking.

• Yes. Default. If the entity uses COSTCASH processing, it uses COSTCASH bulking. Once you select the Yes option, you cannot change it. 

Manager Allocation

2841

Specifies whether manager allocations apply to the fund. Options include No (default) and Yes.

Backup Withholding Indicator

2768

Controls whether backup withholding is required. Options include:

• No. Default. Backup withholding is not required.

• Yes. Backup withholding is required. You must enter a value for the Backup Withholding Rule Description field. TEFRA legislation requires backup withholding if you have not provided a taxpayer ID.

Backup Withholding Rule Description

2761

Specifies the rule identifying the account subject to backup withholding and the dates the restrictions apply. You can use the Create Entity Backup Withholding Rule panel to set up the rule. This option is required if you set the Backup Withholding Indicator field to Yes.

Cost Basis Covered Indicator

2818

Determines whether a portfolio follows the mandatory reporting guidelines as stored at the accounting basis level. When enabled, the system creates a bifurcated position and determines uncovered/covered statuses for the securities/lots the portfolio holds as new trades are received.

Book Value Breakdown Flag

2904

 Indicates whether to process book value by component for fixed income securities. Options include:

• Yes. Process book value by splitting the cost of the transaction into two parts: par and cash premium/discount (CP). CP is the difference between par and the price paid. Par is booked to cost of investments and CP is booked to an asset CP account. As close transactions are booked, the par, CP, and any other fees booked are proportionally closed.

• No. Do not process book value by component.

Business Sector

9512

Identifies the business sector associated with the entity. You use this field when performing Weighted Average Balance (WAB) calculations.

Pending Trade Eligible Indicator

3679

Specifies whether the system can apply pending trade rules to place incoming transactions for the entity into the pending trade workflow. Eagle's Accounting solution can pend transactions received from upstream systems if those transactions require further evaluation prior to processing by the STAR accounting engine. Options include Yes and No.

PT Rule Name

17026

Identifies the name of the pending trade rule associated with the selected pending trade rule detail. This field appears if you set Pending Trade Eligible 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.

Margin Transaction Fees

3889

Defines the treatment of commissions for securities with variation margin. Options include:

• Expense. The system recognizes expenses for commissions on the opening and closing of contracts with variation margin. The commissions are recognized as a transaction cost rather than netted in the initial recognition of unrealized gains/losses. You can view the transaction fees on the General Ledger report.

• Capitalize. Default. The system nets the initial recognition of unrealized gains/losses on the opening and closing of contracts with variation margin.

PIK URGL Flag

3859

Indicates whether unrealized gain/loss is posted for a Payment in Kind (PIK) bond interest receivable. Options include:

• Yes. Allows the accounting basis to post daily mark to market entries for interest receivable when a security has a processing security type (PST) of Interest Bearing Debt PIK (DBIBPK) and there is a PIK Receivable Mark to Market schedule for the coupon period. For more information, see About Calculating URGL for a PIK Receivable Balance.

• No. The Accounting basis is not able to daily mark to market PIK unrealized.

Cost Cash Processing

5006

(Hidden field) Indicates whether the entity uses COSTCASH processing to track foreign cash positions. Options include:

• No. The entity does not use COSTCASH processing. When a non-base transaction is settled, the STAR engine does not create a COSTCASH position. For more information, see Understand Entities That Do Not Use COSTCASH Processing. 

• Yes. Default. The entity uses COSTCASH processing to track foreign currency positions. When a non-base transaction is settled, the STAR engine creates a COSTCASH position. For more information, see Manage COSTCASH Processing.

QDI Treaty Flag

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 Create QDI Tax Treaty panel. You can also use the Create 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.

Cash Based Div Recognition Flag

16160

Indicates whether to process cash dividend income, tax, and reclaim in the accounting ledger on ex-date or upon the settlement of the associated cash. For more information, see Recognize Dividend Income on a Cash Settlement Basis. Options include:

• No. Default. The system recognizes dividend income on an ex-date basis.

• Yes. The system recognizes dividend income on a cash settlement basis.

FX Election for Cash Div Recognition

16161

If you recognize dividend income on a cash settlement basis, indicates whether the system selects the FX rate used for foreign dividend settlement using the ex-date FX rate or the settlement date FX rate. It applies only to the settlement of dividends issued by a foreign security. This field appears if you set the Cash Based Div Recognition Flag field to a value of Yes. Options include:

• Ex-date. Recognizes the income using the ex-date FX rate.

• Settlement Date. Recognizes the income using the settlement date FX rate.

Equity Method Treatment

16084

If the selected accounting basis uses the equity method of accounting, identifies the treatment of assets held under the equity method of accounting. You cannot change this value when you edit an entity/basis. Options include:

• STAT Treatment. Indicates that you are using the equity method of accounting with a STAT accounting basis for use with statutory insurance. If you are creating or editing a STAT basis that uses the equity method, you must choose STAT Treatment. You can apply the STAT Treatment to any basis other than a GAAP basis.

• Other Treatment. Indicates that you are using the equity method of accounting with a non-STAT accounting basis, such as a GAAP basis that uses Generally Accepted Accounting Principles (GAAP). You can apply the Other Treatment to any basis other than a STAT basis.

Income Received Accounting Flag

16557

Determines whether the selected accounting basis uses the income posting treatment to create separate entries within the ledger to identify interest income received and/or dividend income received in unique income ledger accounts. This option is for use by Insurance companies that need to reconcile the investment accounting activity reflected on their investment schedules to related ledger accounts on their trial balances. See Record Unique Ledger Postings for Income Received. Options include: 

• Yes. Allows the system to use the income posting treatment to create separate entries within the ledger to identify interest income received and/or dividend income received in unique income ledger accounts. The system records unique ledger postings for interest received recorded in an income ledger account for interest income received and for dividend income received in an income account for dividend income received. When interest receivables and/or dividends receivables are reduced for cash received, additional postings entries are required to record interest or dividends received. 

• No. The system does not use the income posting treatment to create separate entries within the ledger to identify interest or dividends received in unique income ledger accounts.

Ledger Closeout Override Profile

18570

Specifies whether a custom transfer profile is assigned to an entity or accounting basis to override any regulatory or default closeout rules already assigned. Before you override the profile, you need to build a custom profile. For more information, see Manage Custom Profiles.