BDR MODI/CORR T+1:

>

Status: Best Practice Finalised, Last Updated: 15/02/2024

Question:
Historical submissions:
Summary: MODI / CORR: where ED is greater than +1 day prior to the RD:

· Note where references to DTCC event date vs. reporting date logic in this context takes place it means that the logic is checking to see if the ED is one day prior to the RD or greater than one day.
· This is important as where reporting is no more than one day after the ED, certain action types hit the TSR; if not, then only the TAR would be hit.

Historical Submissions:

MODI / CORR:

· T vs. T+1 Submissions
· Assuming both sides of the trade have to report and both submission dates are the same.
· Where submission dates are not the same the field populations would need to match.
· Where fields do not match on different submission dates trades can end up paired but not matched on the TSR report, this is because the TR currently compares the event date from day 2 and not on day 1.
· Once both sides of the trade are terminated with an ETRM then both will be removed off of the TSR and appear on the latest reconciliation report for 30 days.

· ED - Event Date
· RD - Reporting Date

· MODI & CORR:
· Action types with an historical ED (being 22.1.24) and a current RD (being 7.2.24) will:
· Hit the TAR
· Will not Hit the TSR
· Possible to Pair (pairing both cptys to one UTI driven by initial NEWT)
· MODI & CORR's that do not have a current ED and RD where the ED is only +1 day prior to the RD will impact the successful matching and reconciliation reports.
· Historical event dates on MODI/CORR will be ACK’d as long as the modification is not on a maturity date.
· Any historical MODIs/CORRs to update maturity date would not be ACKNOWLEDGED; the T+1 event date logic is required here hence ED has to be +1 day prior to RD.

Best Practice:
(SFTR-823)