About Sinking Fund Schedules
If a bond has a Sink provision, the data must be stored in both the Schedule table, as a Schedule Sub Type of SINK, and in the Corporate Action History table, as a Trans Type of PMT. As part of adding a sinking fund schedule the procedure, the add_schedule event, also adds the sinking fund schedule to the Corporate Action table. The Corporate Action Status entered for the schedule flows to the sinking fund’s corporate action record. In addition the sweep date on the corporate action is set to the system post date. Finally, to correctly process the security, the entire schedule amount must be equal to 1.00.
You can use the related event, ADD_SCHEDULE, for the Add/Change Schedule process only. In the Add Schedule panel, Security Query Flag (tag 1256) = ADD, and in the Change Schedule panel, tag 1256 = CHANGE.
When you add the sink schedule, the add procedure includes a check that ensures that the sum of all the rows does not exceed 1.00 and if the primary key already exists. It does this check for both the Schedule and Corporate Action tables. If the check generates an error during the insertion into the Schedule table, nothing is inserted into either table. If, however, the errors occur during the insertion into the Corporate Action table, the insert to the Schedule table is rolled back, and no rows are inserted into either table. As long as the check passes on both tables, the data is inserted successfully.
While writing data to the Corporate Action table, if a row does not exist, a new row is inserted. If a row already exists for the Sec Alias and Effective Date, and the schedule amount has not changed, no update takes place. If the schedule amount is different, the Corporate Action Cancel/Rebook procedure is called. As a result, the Status for the original row is updated to CL; a new row is inserted, and a CANCEL record for the original row is inserted. Both are set with a Status of RD. The CANCEL record has a Sweep Date set to sys date. As for the new corporate action record, if Effective Date of the original record <= sys date, the Sweep Date is set to sys date; otherwise, Sweep Date = Effective Date.
About Pre-Refunded Information Schedules
When there is partial pre-refunded information on a particular security, you should enter the prerefunded information under the Child security (refunding security). The reason is that Eagle Accounting uses the pre-refunded information as the new Maturity Date, and amortizes any market discount or market premium, to the pre-refunded date. If you set up the pre-refunded information under the Parent security, Eagle Accounting amortizes the total amount of amortization (the total discount/premium) of the security, instead of the portion of the premium/discount associated with the amount pre-refunded.
When you add the schedule, you set the Schedule Type field (tag 1250) to a value of REFUND. You can then enter the Effective Date, Price/Rate, Schedule Subtype, and Announcement Date. The Schedule Subtype, which is recognized in the amortization process, can have a value of Entire Issue Call, Mandatory Put, or Pre-Refunded.
About Payment in Kind Information Schedules
You can create a schedule for a Payment in Kind bond (PIK) to identify whether the PIK is payment in shares for a given coupon period. When you add the schedule, you set the Schedule Type field (tag 1250) to a value of PIK Receivable Mark to Market. You can then enter the Effective Date, End Date, and Schedule Amount.
0 Comments