ResetDates
Type CDM 7.2.0A data defining: the parameters used to generate the reset dates schedule and associated fixing dates. The reset dates are the dates on which the new index value (which is observed on the fixing date) is applied for each period and on which the interest rate hence begins to accrue.
Attributes
All 8 declared on ResetDates. Cardinality in amber is required.
| Name | Type | Card. | Description |
|---|---|---|---|
| calculationPeriodDatesReference | CalculationPeriodDates | 0..1 | A pointer style reference to the associated calculation period dates component defined elsewhere in the document. |
| resetRelativeTo | ResetRelativeToEnum | 0..1 | Specifies whether the reset dates are determined with respect to each adjusted calculation period start date or adjusted calculation period end date. If the reset frequency is specified as daily this element must not be included. |
| initialFixingDate | InitialFixingDate | 0..1 | The initial fixing date. |
| fixingDates | RelativeDateOffset | 0..1 | The fixing dates are the dates on which the index values are observed. The fixing dates are specified by reference to the reset date through business days offset and an associated set of financial business centers. Normally these offset calculation rules will be those specified in the ISDA definition for the relevant floating rate index (ISDA's Floating Rate Option). However, non-standard offset calculation rules may apply for a trade if mutually agreed by the principal parties to the transaction. |
| finalFixingDate | AdjustableDate | 0..1 | This attribute is not part of the FpML ResetDate, and has been added as part of the CDM to support the credit derivatives final fixing date. |
| rateCutOffDaysOffset | Offset | 0..1 | Specifies the number of business days before the period end date when the rate cut-off date is assumed to apply. The financial business centers associated with determining the rate cut-off date are those specified in the reset dates adjustments. The rate cut-off number of days must be a negative integer (a value of zero would imply no rate cut off applies in which case the rateCutOffDaysOffset element should not be included). The relevant rate for each reset date in the period from, and including, a rate cut-off date to, but excluding, the next applicable period end date (or, in the case of the last calculation period, the termination date) will (solely for purposes of calculating the floating amount payable on the next applicable payment date) be deemed to be the relevant rate in effect on that rate cut-off date. For example, if rate cut-off days for a daily averaging deal is -2 business days, then the refix rate applied on (period end date - 2 days) will also be applied as the reset on (period end date - 1 day), i.e. the actual number of reset dates remains the same but from the rate cut-off date until the period end date, the same refix rate is applied. Note that in the case of several calculation periods contributing to a single payment, the rate cut-off is assumed only to apply to the final calculation period contributing to that payment. The day type associated with the offset must imply a business days offset. |
| resetFrequency | ResetFrequency | 0..1 | The frequency at which the reset dates occur. In the case of a weekly reset frequency, also specifies the day of the week that the reset occurs. If the reset frequency is greater than the calculation period frequency then this implies that more than one reset is established for each calculation period and some form of rate averaging is applicable. |
| resetDatesAdjustments | BusinessDayAdjustments | 0..1 | The definition of the business day convention and financial business centers used for adjusting the reset date if it would otherwise fall on a day that is not a business day in the specified business center. |
Conditions
Validation rules the model enforces on this type, in Rune. An instance that breaks one of these is invalid CDM, whatever produced it.
if rateCutOffDaysOffset exists
then rateCutOffDaysOffset -> periodMultiplier < 0 if resetFrequency -> period = PeriodExtendedEnum -> W
then resetFrequency -> weeklyRollConvention exists if resetFrequency -> period <> PeriodExtendedEnum -> W
then resetFrequency -> weeklyRollConvention is absent Referenced by
1 type holds a ResetDates as an attribute.
Functions
Model functions that produce or consume this type. These are the CDM's own behaviour — the logic a correct implementation has to match.
| Function | Role | Description |
|---|---|---|
| MapFraResetDates | returns | — |
| MapInterestLegResetDates | returns | — |
| MapSwapResetDates | returns | — |
| EvaluateCalculatedRate | takes | Evaluate a calculated rate as described in the 2021 ISDA Definitions. |
| GenerateObservationDatesAndWeights | takes | Apply shifts to generate the list of observation dates and weights for each of those date. |
| ComputeCalculationPeriod | takes | Determine the calculation period to use for computing the calculated rate (it may not be the same as the normal calculation period, for instance if the rate is set in advance. |
| GetCalculatedFROCalculationParameters | takes | Initialize a calculation parameters block for an OIS or a daily average rate. Used to support FROs that include an embedded calculation. |
| EvaluateScreenRate | takes | Evaluate/lookup the value of a screen rate. |
| DetermineResetDate | takes | Determine the value of the reset date given a reset dates structure and a calculation paeriod for which it's needed. Reset dates are defined in the 2021 ISDA Definition in Section 6.5.5. |
| DetermineFixingDate | takes | Determine the observation (fixing) date needed given a reset dates structure and a reset date. |
Open ResetDates in the Model Browser
Walk the tree and the reference graph interactively, and switch releases to see how the type has changed. Free, no signup.