FpML Issues Tracker

Summary

After discussion with the WG Chair I've taken the advice to present as an Issue.

For the TradeNotification use case I need to provide the Adjusted Date for a number of fields: Effective, Termination, First Stub, Last Stub.

These fields currently have the type 'AdjustableOrRelativeDate'. This means I can put in an a pre-adjusted adjustable date or a relative date, but not the adjusted date.

I'd like to be able to add an optional adjusted date for the notification use case. And capture it as an alternative to adjustable and relative dates.

I believe this is a specific example of a more general problem. There is no way in the schema representing trades to distinguish between those fields that form part of the contract/trade and those that are derived or estimated. For example the IndexLevel for a TRS may be established on EffectiveDate. I would expect both the rule for determining the Index to be present on trade date and the index level when the trade is struck. The rule forms part of the contract and matching process - but the index level is just for information.