Eikon COM API: Specify settlement date for Eikon Bond Calculator
Hi,
For Eikon COM API, is there a way to specify the settlement delay or settle date when calling the Eikon Bond Calculator?
Right now, it seems to only be able to take in the valuation (trade) date, and then return a default T+2 settlement amount of accrued interest.
Thanks,
Simon
Best Answer
-
The settlement date is actually calculated from the valuation (trade) date according to the market convention. E.g. for US Treasuries and UK GILTs the settlement date is T+1, whereas for Eurozone Treasuries it is T+2.
If you need to use a specific settlement date you could work out the valuation date from the settlement date and use that valuation date rather than today's date when making a call to retrieve say TR.YieldToMaturityAnalytics. E.g. if you need to evaluate a US Treasury with the settlement date 8-May-2019, then in your call you could use "TR.YieldToMaturityAnalytics(ValuationDate=2019-05-07 Price=..."0
Answers
-
Hi Alex, thanks for your response. Do you have any documentation on the standard settlement delay the API will use for fixed income instruments. Is a field that can determine the settlement delay that the API will use?
0 -
The settlement rules follow market conventions. For a given bond you can retrieve the settlement rule using TR.ADF_BONDSTRUCTURE field. This field returns a string of space separated key/value pairs. This string can be directly used in BondStructure argument of Adfin Analytics functions like AdBondYield available in Eikon Excel and as part of Eikon COM APIs. E.g. for CUSIP 345277AE7 TR.ADF_BONDSTRUCTURE returns
ACC:00 CCM:BB00 CFADJ:NO CLDR:USA_FI DATED:01MAR1998 DMC:F EMC:S FRCD:01SEP1998 FRQ:2 ISSUE:04JUN1998 NOTIONAL:1 PX:C PXRND:1E-6:NEAR REFDATE:MATURITY RP:1 SETTLE:2WD XD:NO
The above string specifies a bunch of market conventions applicable to the bond. E.g. "ACC:00" tells Adfin Analytics that accrued interest should be calculated using 30/360 day count. "SETTLE:2WD" tells that settlement convention for this bond is T+2 (settlement date = trade date + 2 working days).
0 -
Thanks again Alex, this is helpful
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 625 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛