Corporate Social Responsibility FAQ

Users submitting a value for Settlement Currency in any FX ISIN product template are advised that the attribute is optional and should not contain XXX without prior authorization of the DSB Product Committee.

Users are requested not to submit a value of XXX which is defined in the ISO 4217 standard as “no currency involved in the transaction” and thus is not seen as appropriate for use in FX instruments.

The Product Committee requests that users wishing to submit XXX as an input value should provide a business case to secretariat@anna-dsb.com with supporting information.

The FAQ addresses the fact that it is possible for a DSB FDL File to include more than one record for a particular ISIN.

This is a rare occurrence, but may happen when ESMA/the FCA publish data on FIRDS/FITRS after a set cut-off time and so the DSB may still be having unprocessed data for an ISIN, from the previous day, when a new data is received. This will result in multiple records for the same ISIN being recorded and so it is important for the user community to understand how these records should be handled.

Under these circumstances, the DSB recommends that the user should access the ToTV record with the latest LastModifiedDate, as that would have a complete dataset for that ISIN on that day.

Where there is a duplicate entry, the record with LastModifiedDate is the latest dataset for that ISIN.

The DSB requires the entry of underlying Reference Rates based on entries in the current version of the FpML Coding Scheme (eg: “USD-SOFR-COMPOUND”). In order to support conformance to ISO20022, the DSB also maps each FpML Reference Rate to an equivalent ISO Reference Rate value that is determined in the following way:

1. Set ISO Reference Rate to the appropriate code (if present) found in the ISO20022 BenchmarkCurveName2Code codeset.
2. Else, set ISO Reference Rate to the appropriate code (if present) found in the ISO20022 BenchmarkCurveNameCode codeset.
3. Else, construct the ISO Reference Rate value by removing any currency prefix from the FpML Reference Rate and truncating the resultant text to max. 25 chars.

It is assumed that within the ISO20022 standard, BenchmarkCurveName2Code is, and will remain, a subset of BenchmarkCurveNameCode. However, the two code sets have been listed separately in the above methodology in order to recognise their different capacities within the relevant regulations.

This approach is intended to allow for the reference rates currently published by FpML and any additional reference rates that may be added in due course.

Q: When was the last DR test?

A: The last DSB DR test was invoked against the DSB UAT environment between the 15th June – 29th June 2024. The last DSB DR test was invoked against the DSB Production environment between Saturday 23rd November 2024 – Sunday 24th November 2024.

Q: How long did the DSB take to complete the invocation?

A: The DSB successfully completed the invocation to the secondary region (UAT) in 3.5 hours (UAT). The RTO (recovery time objective) is 4 hours. The DSB successfully completed invocation to the secondary region (Production) in 3 hours and 11 minutes. The RTO (recovery time objective) is 4 hours.

Q: When is the next DR test?

A: The DSB will communicate in Q1 when the 2025 DR tests for UAT and Production will take place.

Q: What were the results of the latest DR test?

A: The DSB Successfully completed testing in the Production environment between Saturday 23rd November 2024 – Sunday 24th November 2024.

The RTO (Recovery Time Objective) was 3 hours 11 minutes and the RPO (Recovery Point Objective) with no data loss, was 0 hours.