Overview

In some markets, it is common to reissue new securities using a recycled cross reference identifier (Xref Xreference ID). This can apply to , such as the CUSIP, ISIN, SEDOL, etc. This document describes how to reuse Xref IDs in Eagle Accounting and Data Management. This can apply to the Primary Asset ID (14), Alternate Asset ID (1795), or any additional Xreference ID.

Inactive Flag

One Security

The Inactive Flag (11043) on a security master file (SMF) allows you to reuse the Xref IDs from an existing security without having to delete it or change its Xref IDs. It also prevents the security from being returned for trade processing. Follow the steps below to put a security into inactive status.

1. Open the security master file (SMF) in Issue Viewer or Reference Data Center
2. Set Inactive Flag = Yes
3. Save the security

Multiple Securities

There is also an event that can be run manually or scheduled to automatically set Inactive Flag = Yes based on each security's Maturity Date (38) or Dated Date (1183) and a specified lag. Use Auto Inactive Securities to trigger the event manually.

• Auto Inactive Securities Based On (1257): Maturity Date is the default, Dated Date is only used for TBAs with Processing Security Type (3931) = DBTATA
• Maturity Date (38) or Dated Date (1183): one or the other is required based on the previous field
  • Must be prior to current day
  • This would typically be set to yesterday's date when scheduled to run daily, in conjunction with an appropriate lag
• Exclude Securities Based On Position (1256): you can exclude securities that have accounting positions (Star Position), data management positions (Pace Position), or Both
• The following fields can be used to limit the scope of the event if you do not want it to run for your full universe of securities:
  • Investment Type (11)
  • Processing Security Type (3931)
  • Security Type (82)
• Auto Inactive days from Maturity Date/Dated Date (1567): specifies the lag in calendar days before putting a security into inactive status
  • When the event is triggered, it counts backwards using this field, inclusive of Maturity Date or Dated Date

  • For example, the results of submitting the event with Maturity Date = 2/2/2022 and a lag of 30 days are shown below

    Security	Maturity Date	Result
    Bond A	1/2/2022	Inactive
    Bond B	1/3/2022	Inactive
    Bond C	1/4/2022	Inactive
    Bond D	1/5/2022	Active
    Bond E	1/14/2022	Active

    
    

Workaround

If you cannot use the process described above, a manual workaround is available.

...